sase.tr/apps/api/drizzle/0002_boring_the_stranger.sql at 2bf5e1622cb1d8c0c7d89c843ef14dd4c80109a0 - sase.tr - Gitea: Git with a cup of tea

root/sase.tr

Files

Sase Dev cd62ae1737 fix(migrate): make 0002 timings column add idempotent

The previous deploy of c4f6cc1 failed because I had applied the timings
column manually via psql before the deploy ran, leaving the hash-based
migrate runner with raw ADD COLUMN that conflicts with the existing column.
Hash differs after this change so the runner will retry on next deploy
and succeed (no-op on the already-applied column, success path records
the hash).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-12 11:35:05 +00:00

1 line

66 B

SQL

Raw Blame History

ALTER TABLE "query_logs" ADD COLUMN IF NOT EXISTS "timings" jsonb;