Skip to content

chore: triggering re-deploy of resources to aws #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emilylm merged 1 commit into from
Apr 30, 2026
Merged

chore: triggering re-deploy of resources to aws #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions schema.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -505,6 +505,10 @@ CREATE INDEX IF NOT EXISTS idx_submission_attempt_lock_expires_at ON submission_
-- ==========================================
-- Submission events (append-only audit trail)
-- ==========================================
-- Note: Each submission creates multiple rows (claimed -> released/accepted/rejected)
-- This provides full audit history but means ~2x rows per submission.
-- TODO: If table size becomes an issue, consider switching to single-row-per-submission
-- with UPDATE instead of INSERT for state transitions.

CREATE TABLE submission_event (
id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
Expand Down
Loading