[Backport 1.28.x] diskquota/jdbc: fix renameLayer leaving TILESET.KEY stale (#1526)#1532
Merged
Conversation
JDBCQuotaStore.renameLayer only updated LAYER_NAME, leaving the layer-name prefix in TILESET.KEY and TILEPAGE.TILESET_ID stale - later lookups missed the row, getOrCreateTileSet inserted duplicates, and quota by id was split across two rows. The rename SQL now rewrites KEY too; ON UPDATE CASCADE on the TILEPAGE FK keeps TILESET_ID in lockstep. OracleDialect keeps the legacy behavior (no ON UPDATE CASCADE on Oracle); a follow-up will use deferrable constraints there. on-behalf-of: @camptocamp <info@camptocamp.com>
groldan
force-pushed
the
backport-1529-to-1.28.x
branch
from
16a04ef to
8734aa1
Compare
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
2 participants
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.
Backport #1529
Authored by: @groldan