Details
-
New Feature
-
Status: In Testing (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
Description
Currently there is no easy way for a user to check if a database is consistent.
One can check individual tables with CHECK TABLE but there is now to check that
all foreign key tables has all the required keys and that the original table has all the rows
expected by the foreign key table.
We should extended CHECK TABLE .. EXTENDED or alternative CHECK TABLE ... REFERENCES to check that all foreign key relations are consistent.
This should preferably be done on the upper, sql, level and not in InnoDB.
Attachments
Issue Links
- causes
-
MDEV-35730 Server crashes in Field::ptr_in_record / handler::check_record_reference
-
- In Testing
-
-
MDEV-35731 Assertion `(mem_root->flags & 4) == 0' failed upon 2nd execution of CHECK TABLE with FK
-
- In Testing
-
-
MDEV-35733 ASAN errors in row_mysql_store_col_in_innobase_format / check_key_referential_integrity
-
- In Testing
-
-
MDEV-35734 ASAN errors in cmp_dtuple_rec_with_match_low / check_key_referential_integrity
-
- Closed
-
-
MDEV-35737 MSAN errors in check_table_referential_checks_needed upon LOAD INDEX
-
- In Testing
-
-
MDEV-35908 Unexpected error, crash, MSAN errors, assertion failures upon CHECK
-
- Stalled
-
-
MDEV-35936 More ASAN errors in check_key_referential_integrity
-
- In Testing
-
-
MDEV-35961 Not quite correct error message upon CHECK with FK violation due to wrong engine
-
- Open
-
-
MDEV-36643 Assertion failures upon concurrent CHECK and DML on table with FK
-
- Open
-
- is blocked by
-
MDEV-36171 Specify requirements for foreign keys
-
- Stalled
-
- relates to
-
MDEV-16356 Allow ALGORITHM=NOCOPY for ADD CONSTRAINT
-
- Open
-
-
MDEV-35962 CREATE INDEX fails to heal a FOREIGN KEY constraint
-
- Closed
-
- mentioned in
-
Page Loading...
Activity
Transition | Time In Source Status | Execution Times |
---|
|
67d 4h 19m | 1 |
|
26d 16h 15m | 3 |
|
7d 2h 21m | 1 |
|
2d 13h 22m | 1 |
|
84d 5h 22m | 4 |
|
3d 9h 39m | 1 |