Repository navigation
corpus: owned sequences with options of their own, and named for a table's old name - #20
Merged
Merged
Conversation
…ble's old name Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Two migration cases from GitLab's schema:
owned_sequence_with_options_of_its_own: a new table whose id comes from a sequence it owns that starts at 1000.partitioned_table_owns_a_sequence_named_for_its_old_name: a partitioned table still owning a sequence named for the table it was renamed from.Either one, written as a
serial, gives the copy a different sequence from the source's.Released DBDiff fails both; DBDiff/DBDiff#288 passes them. This should be merged once a DBDiff release includes that fix, since merging publishes.
🤖 Generated with Claude Code