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
At the same point in time, there may be two versions of the schema in the TiDB cluster, so we can't create foreign key in one schema version, since this may break foreign key constraint, such as delete reference table
without foreign key constrain check in child table.
-- In TiDB-1 and Schema Version is 1insert into t_has_foreign_key values (1, 1);
-- In TiDB-0 and Schema Version is 0deletefrom t_reference where id =1; --Since doesn't know foreign key information in old version, so doesn't do foreign key constrain check.
The text was updated successfully, but these errors were encountered:
Dev Task
At the same point in time, there may be two versions of the schema in the TiDB cluster, so we can't create foreign key in one schema version, since this may break foreign key constraint, such as delete reference table
without foreign key constrain check in child table.
The text was updated successfully, but these errors were encountered: