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
aschuch247 opened this issue
Sep 26, 2019
· 3 comments
Assignees
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
phpMyAdmin supports custom relations between rows as stored in pma__relation table. The GUI calls them internal relationships. If the tables are of MyISAM, the operations tab shows a Check referential integrity section. If the tables are InnoDB, the operations tab does not contain a Check referential integrity section.
InnoDB foreign keys come at a performance cost. But InnoDB supports transactions. So in order to use transaction, I am using InnoDB without foreign keys. But I like to configure relations in phpMyAdmin to be able to easily navigate around.
The text was updated successfully, but these errors were encountered:
I'm pretty sure that the decision was made 16 years ago because phpMyAdmin did not allow internal relations for InnoDB types. It didn't make sense to run the referential integrity at the time on an InnoDB table. The ability to add internal relations on other table types was added a few years ago and I feel this change, while beneficial, was completely overlooked at the time. I agree about fixing this.
williamdes
changed the title
'Check referential integrity' not present for InnoDB tables without foreign key, but with configured phpMyAdmin relation
Check referential integrity' not present for InnoDB tables without foreign key, but with configured phpMyAdmin relation
Oct 28, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
Describe the bug
phpMyAdmin supports custom relations between rows as stored in
pma__relationtable. The GUI calls theminternal relationships. If the tables are of MyISAM, the operations tab shows aCheck referential integritysection. If the tables are InnoDB, the operations tab does not contain aCheck referential integritysection.To Reproduce
relation_test.table1.Structurein the top navigation.Relation view.Internal relationshipsand add a relation fortable2_idtorelation_test.table2.table2_id.relation_test.table1.Operations.Check referential integritysection is shown.table1fromInnoDBtoMyISAM.Check referential integritysection is shown.Note: Clicking the links does not properly work right now due to #14598.
Expected behavior
I expect the
Check referential integritysection to be shown even when using InnoDB as table engine.Server configuration
Additional context
InnoDB foreign keys come at a performance cost. But InnoDB supports transactions. So in order to use transaction, I am using InnoDB without foreign keys. But I like to configure relations in phpMyAdmin to be able to easily navigate around.
The text was updated successfully, but these errors were encountered: