Fix slot_number column references after removal migration - #111
Merged
Merged
Conversation
The remove_slot_number migration dropped the column from the database but left references in TypeScript types, service layer code, and trigger functions, causing "column participants.slot_number does not exist" errors at runtime. - Remove slot_number from supabase.ts type definitions (Row/Insert/Update) - Remove get_next_slot_number RPC function type - Remove slot_number destructuring in participantService - Remove slot_number from GroupParticipant Omit type - Add migration to fix log_participant_joined and log_participant_withdrew trigger functions that still referenced NEW/OLD.slot_number - Remove slot_number from test fixtures https://claude.ai/code/session_0136Xfeh42PrgYwiokuxKxjQ
michaelchu
temporarily deployed
to
claude/fix-participants-slot-number-6HVEU - Roster PR #111
February 15, 2026 15:22 — with
Render
Destroyed
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.
The remove_slot_number migration dropped the column from the database
but left references in TypeScript types, service layer code, and
trigger functions, causing "column participants.slot_number does not
exist" errors at runtime.
trigger functions that still referenced NEW/OLD.slot_number
https://claude.ai/code/session_0136Xfeh42PrgYwiokuxKxjQ