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
The plan is to insert / upsert the DB of osparc into the DB of sim4life. To do this, all osparc postgres tables will be audited and made ready for this procedure. Some tables might be empty (by design), some tables might not need to be moved and can be dropped, and some tables might need adjustments.
In order to avoid collisions in the DB, such as with tables that have monotonically increasing primary keys starting from 1, we have identified two ways to make the DB-tables of osparc.io "ready":
Add a large integer (needs to be determined individually) to all primary keys of osparc.io OR sim4life.io, to avoid collisions. [Note: This doesnt always work, e.g. in the users DB mail adresses are presumably expected to be unique even though they are not enforced to be unique in postgres?
Add the product as a second primary key and thereby make combinations of user-id & product etc. unique.
Likely, both ways would go via a PR with an alembic migration
The plan is to insert / upsert the DB of osparc into the DB of sim4life. To do this, all osparc postgres tables will be audited and made ready for this procedure. Some tables might be empty (by design), some tables might not need to be moved and can be dropped, and some tables might need adjustments.
In order to avoid collisions in the DB, such as with tables that have monotonically increasing primary keys starting from
1
, we have identified two ways to make the DB-tables of osparc.io "ready":osparc.io
ORsim4life.io
, to avoid collisions. [Note: This doesnt always work, e.g. in theusers
DB mail adresses are presumably expected to be unique even though they are not enforced to be unique in postgres?product
as a secondprimary key
and thereby make combinations ofuser-id & product
etc. unique.Likely, both ways would go via a PR with an alembic migration
The text was updated successfully, but these errors were encountered: