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>
9 lines
526 B
SQL
9 lines
526 B
SQL
-- 0060_play_events_track_index.up.sql — play_events by track.
|
|
--
|
|
-- play_events is indexed by (user_id, started_at) and (user_id, track_id), both
|
|
-- led by user. Nothing reached it by track alone until the duplicates report,
|
|
-- which shows each copy's play count — a scan of the whole table per copy — and
|
|
-- the duplicate merge, which repoints a duplicate's play history onto the copy
|
|
-- being kept. Both ask "every play of this track", whoever played it.
|
|
CREATE INDEX play_events_track_idx ON play_events (track_id);
|