Skip to content

fix: change shift_covers.schedule_id from serial to integer#193

Merged
jakebromberg merged 2 commits intomainfrom
fix/18-schedule-id-type
Mar 10, 2026
Merged

fix: change shift_covers.schedule_id from serial to integer#193
jakebromberg merged 2 commits intomainfrom
fix/18-schedule-id-type

Conversation

@jakebromberg
Copy link
Member

@jakebromberg jakebromberg commented Feb 21, 2026

Summary

  • shift_covers.schedule_id used serial (auto-increment) instead of integer for a foreign key column
  • Inserts without explicit schedule_id would get sequence-generated values rather than failing

Test plan

  • Schema assertion test verifying column is not serial

Made with Cursor

Note: This fix is consolidated in #199 (coordinated schema migration batch). Consider closing in favor of #199.

FK columns should not auto-increment. Using serial meant inserts
without explicit schedule_id would get sequence-generated values
that may not reference valid schedule rows.

Co-authored-by: Cursor <cursoragent@cursor.com>
@AyBruno AyBruno force-pushed the fix/18-schedule-id-type branch from 4cf6824 to ff832b3 Compare March 9, 2026 22:15
@AyBruno
Copy link
Collaborator

AyBruno commented Mar 9, 2026

Tests will pass once #195 is merged in and this is rebased onto main.

@jakebromberg jakebromberg merged commit 6766bf6 into main Mar 10, 2026
4 checks passed
@jakebromberg jakebromberg deleted the fix/18-schedule-id-type branch March 10, 2026 05:13
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