Repository navigation
Conversation
schema.sql defines tickets.updated_at with default now() but no update
trigger, and PUT /tickets/{id} never set it, so the column always held
the creation time. update_ticket now sets it to the current UTC time on
every edit. Added tests for update (sets a tz-aware timestamp) and
create (leaves it to the DB default).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0171zWzjtpJq63QvkcDXeLGk
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Nov 12, 2026
This branch was successfully deployed
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.
Summary
schema.sqlgivestickets.updated_atadefault now(), but there's no update trigger, andPUT /tickets/{id}never set the column. As a result,updated_atalways held the creation time.update_ticketnow sets it to the current UTC time on every edit. Creating a ticket still uses the DB default.No open PR (#17–#71) or issue touches
updated_at. #45 and #47 also editupdate_ticket/Ticket, so a small merge conflict is possible, but neither changes this logic.Testing
test_update_ticket_sets_updated_at(checks for a tz-aware timestamp) andtest_create_ticket_does_not_send_updated_at.pytest: 45 passed (withSUPABASE_URL/SUPABASE_KEYset).ruff checkandruff format --checkare clean.Generated by Claude Code