Skip to content

corpus: a sequence filled by a trigger, and a default on a sequence its column does not own - #21

Merged
jasdeepkhalsa merged 1 commit into
mainfrom
corpus/sequences-without-default
Nov 10, 2026
Merged

jasdeepkhalsa merged 1 commit into
mainfrom
corpus/sequences-without-default

Conversation

@jasdeepkhalsa

Copy link
Copy Markdown
Member

Two migration cases for sequences that a column owns but no default uses. Both shapes come from GitLab's schema.

  • owned_sequence_filled_by_a_trigger: a trigger fills the id from a sequence the column owns, so the column has no default. A tool that reads this as the column's serial never creates the sequence, and the first insert fails.
  • default_on_a_sequence_the_column_does_not_own: the id default draws on one sequence, while the column owns another that nothing uses. Writing the column as a serial makes the copy's default draw on the owned one.

Checked with DBDiff's Corpus suite on PostgreSQL 18: all 4 runs (both directions of each case) fail on DBDiff master and pass with the DBDiff fix for these shapes. This package's own tests are unchanged: 44 tests, 0 failures.

🤖 Generated with Claude Code

…ts column does not own

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jasdeepkhalsa
jasdeepkhalsa merged commit 6edb32a into main Nov 10, 2026
6 checks passed
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.

1 participant