-
Improvement
-
Resolution: Unresolved
-
Major
-
2.2
-
Any
-
MOODLE_22_STABLE
-
MDL-30799-Master
Moodle has never had foreign keys in its database, because we started in the dark days of MySQL 3.x. It would be really nice if we could enable them. It would detect many bugs, and so make Moodle more robust. However, there are a lot of steps required on the way to achieving that.
- has a non-specific relationship to
-
MDL-9271 XMLDB: Keys are lost when changing table settings
- Closed
-
MDL-21115 Several foreign key fields defined in the install script have incorrect data types
- Closed
-
MDL-16981 Referential integrity problems in the gradebook
- Closed
-
MDL-17623 Summary of Violated Foreign Key Constraints from 700+ Moodles
- Closed
- has been marked as being related by
-
MDL-53795 Missing logstore_standard index significantly slows backups with logs
- Closed
-
MDL-71793 Extend check_database_schema to look for potentially missing foreign relations
- Development in progress
-
MDL-49795 Add missing Primary/Foreign Key relationships to core Moodle tables
- Closed
- will be (partly) resolved by
-
MDL-20437 When I set $foreign_keys=true in in sql_generator.php, the ddl is not created.
- Closed
-
MDL-21116 When uninstalling a block the tables in install.xml should be dropped in reverse order
- Closed
1.
|
New flag for each install.xml file: Foreign keys are safe | Closed | Unassigned | |
2.
|
New option $CFG->foreignkeys = NONE | SAFE | ALL in config.php | Closed | Unassigned |