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
Database object IDs are currently able to be deployed in a number of fashions which allow for custom setups but don't lend themselves well to integrating with other Pacifica instantiations. This issue also hampers a clean unique id structure when it comes to adding projects, instruments, and users to the metadata schema.
The use of some other unique id structure, maybe uuid, or some other method should be considered as a way to maintain the uniqueness of all objects in the database.
The text was updated successfully, but these errors were encountered:
GitBytes
changed the title
Enforce unique object identifiers for users, instruments, projects, other
[BUG/Enhancement] Enforce unique object identifiers for users, instruments, projects, other
Mar 16, 2019
Database object IDs are currently able to be deployed in a number of fashions which allow for custom setups but don't lend themselves well to integrating with other Pacifica instantiations. This issue also hampers a clean unique id structure when it comes to adding projects, instruments, and users to the metadata schema.
The use of some other unique id structure, maybe uuid, or some other method should be considered as a way to maintain the uniqueness of all objects in the database.
The text was updated successfully, but these errors were encountered: