[OGR provider] Enable foreign key enforcement for newer transactions #43330
Conversation
This file contains 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
Fixes qgis#34728 Note however that integrity of existing content w.r.t foreign key is *not* checked at opening (see qgis#9939), so this is just about not adding new violations.
rouault
added
the
Bug
|
Sounds good to me! |
m-kuhn
approved these changes
May 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #34728
Note however that integrity of existing content w.r.t foreign key is
not checked at opening (see #9939), so this is just about not adding
new violations.
Likely not material for backport
@m-kuhn any opinion regarding this ?