Skip to content

fix a versioned insert that adds a second version when the stored id has another text form - #694

Merged
azahnen merged 1 commit into
masterfrom
versioned-insert-id-check
Nov 9, 2026
Merged

azahnen merged 1 commit into
masterfrom
versioned-insert-id-check

Conversation

@cportele

@cportele cportele commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

The pre-flight of a batch of versioned inserts compared the ids returned by the database with the given ids as text. For an id stored in another text form, e.g. 7 for '007' in an integer column, a UUID in lower case or a char(n) value with padding, no conflict was found and a second version of the feature was inserted. The query now checks the existence of each given id, as the check of a single id does, and returns the given ids.

…has another text form

The pre-flight of a batch of versioned inserts compared the ids returned by the database with the
given ids as text. For an id stored in another text form, e.g. 7 for '007' in an integer column, a
UUID in lower case or a char(n) value with padding, no conflict was found and a second version of
the feature was inserted. The query now checks the existence of each given id, as the check of a
single id does, and returns the given ids.
@azahnen
azahnen merged commit 0cbaaf1 into master Nov 9, 2026
3 checks passed
@azahnen
azahnen deleted the versioned-insert-id-check branch November 9, 2026 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants