You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been using SQLAlchemy text type for UUID columns rather than Postgres's native UUID column type. (See here for an example.) The latter is 1) more efficient and 2) more robust because it handles inconsistent hyphen use.
The biggest drawback to the Postgres type is that it ties triage to Postgres. Are we hoping to remain database agnostic?
Perhaps I'm being optimistic, but I'd expect this to be an easy change, and I'd be happy to do it if there are no objections.
The text was updated successfully, but these errors were encountered:
We've been using SQLAlchemy text type for UUID columns rather than Postgres's native UUID column type. (See here for an example.) The latter is 1) more efficient and 2) more robust because it handles inconsistent hyphen use.
The biggest drawback to the Postgres type is that it ties triage to Postgres. Are we hoping to remain database agnostic?
Perhaps I'm being optimistic, but I'd expect this to be an easy change, and I'd be happy to do it if there are no objections.
The text was updated successfully, but these errors were encountered: