|
|
|
Issue Links:
|
Dependency
|
|
This issue will help resolve:
|
|
MDL-19695
Any field operation (drop, rename, change_xxx) must look for field dependencies (indexes, keys...)
|
|
|
|
|
|
|
|
In Moodle 2.0 we have introduced field dependencies checking, so some actions, like dropping a field, now detect if there are some dependency (index using that field) and throws an exception if necessary.
Make the XMLDB PHP generator able to find such dependencies (in the xmldb model, not in real db) and provide with the needed PHP code needed to avoid that exception, normally:
- dropping the index/es before dropping the field for non unique indexes/keys
- re-adding the index - with the dropped field out for non unique indexes/keys
- BIG WARN if the dependent indexes/keys are defined as UNIQUE. Only drop is safe for 1-column indexes. Everything else, isn't because can lead to errors.
References: http://moodle.org/mod/forum/discuss.php?d=127196 and MDL-19695
|
|
Description
|
In Moodle 2.0 we have introduced field dependencies checking, so some actions, like dropping a field, now detect if there are some dependency (index using that field) and throws an exception if necessary.
Make the XMLDB PHP generator able to find such dependencies (in the xmldb model, not in real db) and provide with the needed PHP code needed to avoid that exception, normally:
- dropping the index/es before dropping the field for non unique indexes/keys
- re-adding the index - with the dropped field out for non unique indexes/keys
- BIG WARN if the dependent indexes/keys are defined as UNIQUE. Only drop is safe for 1-column indexes. Everything else, isn't because can lead to errors.
References: http://moodle.org/mod/forum/discuss.php?d=127196 and MDL-19695 |
Show » |
| There are no comments yet on this issue.
|
|
Sub-task
Open
