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
In both cases we have two tables referencing each other. But in the first scenario, the referenced columns do not make a loop, where in the second scenario they do.
Right now schemadiff rejects table cycles altogether, just based on tables referencing each other. We want to make schemadiff compliant with query-serving logic and support valid cycles.
The output of schemadiff's diff should be then applicable to Online DDL.
We will create two distinct PRs:
One, to support valid cycles in schemadiff.
Another, to handle Online DDL.
Use Case(s)
Support valid foreign key schemas.
The text was updated successfully, but these errors were encountered:
Feature Description
VTGate's query serving distinguishes between valid and invalid foreign key loop references. For example, this pseudo code FK reference is valid:
whereas the following is invalid:
In both cases we have two tables referencing each other. But in the first scenario, the referenced columns do not make a loop, where in the second scenario they do.
Right now
schemadiff
rejects table cycles altogether, just based on tables referencing each other. We want to makeschemadiff
compliant with query-serving logic and support valid cycles.The output of
schemadiff
's diff should be then applicable to Online DDL.We will create two distinct PRs:
schemadiff
.Use Case(s)
Support valid foreign key schemas.
The text was updated successfully, but these errors were encountered: