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
Some of our code for adding foreign key constraints to the macrostrat schema is creating multiple constraints. I assume this is due to re-running ALTER TABLE statements without checking existence. One way to address this would be to set a certain name for the foreign key constraint, rather than just allowing it to be named dynamically on table creation.
The text was updated successfully, but these errors were encountered:
Some of our code for adding foreign key constraints to the
macrostrat
schema is creating multiple constraints. I assume this is due to re-runningALTER TABLE
statements without checking existence. One way to address this would be to set a certain name for the foreign key constraint, rather than just allowing it to be named dynamically on table creation.The text was updated successfully, but these errors were encountered: