bvandeusenandClaude Opus 5.5
6028d78844
release / govulncheck (push) Successful in 17s
release / web (push) Successful in 1m33s
release / go (push) Successful in 1m49s
release / integration (push) Successful in 5m42s
release / android (push) Successful in 5m59s
release / Build signed APK (releases and dev) (push) Successful in 6m9s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Successful in 16s
release / Verify release artifacts (tag releases only) (push) Skipped
Applies rule 32's migration exception: each header still says what the schema was, what changes and what it prevents, but task, milestone, decision and rule ids are replaced by the practice they stood for, the operator quotes by the decision, single-install counts are dropped, and pointers to a deleted package and an external design doc are gone. golang-migrate keeps no checksum, so editing applied migrations' comments is safe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 lines
714 B
SQL
14 lines
714 B
SQL
-- 0095_tracks_emptied_at.up.sql — a slot the duplicate resolver emptied
|
|
-- waits for a copy fetched again.
|
|
--
|
|
-- When the resolver removes a file filed under another song's title and the
|
|
-- album holds no copy of that song as long as the song is, the row is marked
|
|
-- missing and stamped here with the same time. Missing-pair folding then pairs
|
|
-- it by title only with a track added after that time, a copy fetched again,
|
|
-- and not with one already on the album, which under that title holds
|
|
-- another song.
|
|
--
|
|
-- The stamp counts only while it equals missing_since: a row whose file came
|
|
-- back and later went missing again is an ordinary missing row.
|
|
ALTER TABLE tracks ADD COLUMN emptied_at timestamptz;
|