Do not over increment identitiy sequence on Oracle #6816
Merged
+42
−9
Conversation
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
morozov
force-pushed
the
oracle-do-not-over-increment-sequence
branch
3 times, most recently
from
a9979e3 to
5ff0c2b
Compare
morozov
force-pushed
the
oracle-do-not-over-increment-sequence
branch
from
5ff0c2b to
9e3c313
Compare
greg0ire
approved these changes
Mar 3, 2025
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.
This isn't really a bug bug, but something that could be improved. If an explicit value is inserted into an auto-increment column on Oracle, the next auto-increment value will be not +1 but +2.
Apparently, such a case doesn't affect the internal auto-increment sequence on Postgres and DB2 at all, but there's nothing we can do here.