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
Additionally, there needs to be some dependency tracking between the statements to make sure they are executed in order.
They should probably be put into a single transaction (with BEGIN and COMMIT) to prevent concurrent access hullaballoos.
As an alternative to these, just a single create statement could be generated with constraints inside instead of creating a table and then altering it.
Create statement and it's constraint could be merged. I couldn't find a strong reason for it to be separate.
Merging that alone won't solve all the dependency issues.
We need to create a DAG between the statement and topologically sort it and execute in that order to avoid sql errors.
At least in postgres, we can run those DDL statement in single transaction but its tricky in db like mysql which doesn't have transaction support for DDL.
I'm aware this is still an in development method but
mkMigrationTable
generates invalid sql for all checks, defaults and foreign keys.UNIQUE
,NOT NULL
, properties such as the size of string fields, etc...The text was updated successfully, but these errors were encountered: