Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
MariaDB 12.1 introduced a change to constraint naming behavior through MDEV-28933. This modification affects metadata queries that rely on joins between INFORMATION_SCHEMA.KEY_COLUMN_USAGE and INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS tables.
Previously, joins could be performed using only the three columns: CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and CONSTRAINT_NAME. However, due to this change, queries must now include TABLE_NAME as an additional join condition to ensure accurate results.
This breaking change specifically impacts the following metadata operations:
- getExportedKeys()
- getImportedKeys()
- getCrossReference()
Attachments
Issue Links
- is caused by
-
MDEV-28933 Per-table unique FOREIGN KEY constraint names
-
- Closed
-
-
MDEV-37592 FK naming change breaks connector compatibility - revert default names from '1' to '<table>_ibfk_1'
-
- Closed
-
- relates to
-
CONCPP-143 Possible issues in getImportedKeys, getExportedKeys and getCrossReference with 12.1 server
-
- Closed
-