Repository navigation
IBX-11939: Added the missing ON UPDATE CASCADE to ezcontentclass_attribute_ml's SQLite foreign key - #858
Draft
Steveb-p wants to merge 1 commit into
Conversation
…ibute_ml's SQLite foreign key schema.yaml declares ezcontentclass_attribute_ml_lang_fk with onUpdate: CASCADE, and the MySQL and PostgreSQL baselines have it, but the SQLite one only had ON DELETE CASCADE. The schema parity test reports it on SQLite's fresh-install scenario.
|
Steveb-p
added this pull request to stack #860
October 4, 2026 20:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Stacked on #788: it targets #788's branch and lands right after it.
Related PRs:
Description:
The SQLite baseline's
ezcontentclass_attribute_ml_lang_fklacksON UPDATE CASCADE, which the MySQL/PostgreSQL baselines have (schema.yamldeclares it on the renamedibexa_content_type_field_definition_ml_lang_fk). So on SQLite, an install through Doctrine Migrations ends up with a different foreign key than one throughSchemaBuilderEvent.This is #856's fix for 6.0: this branch's SQLite install schema is byte-identical to 4.6's before that fix, so it's the same one-line change. With it, every foreign key's
ON UPDATEmatches this branch's MySQL and PostgreSQL install schemas (the twoNO ACTIONones stay implicit, as that's SQLite's default).#788 isn't released yet, so this fixes the baseline itself rather than adding a migration.