mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 07:42:23 +00:00
The persistent mood-rollup writer bucketed on the UTC truncation of `mood_logged_at` and ignored the canonical per-row `MoodEntry.date` label. Every coverage-miss fallback keys on `entry.date`, so the rollup tier disagreed with the fallback and with the day the user logged the mood: a late-evening or after-midnight local mood landed on the wrong calendar day, and the label shifted the moment the boot backfill flipped a user from the live fallback onto the rollup tier. Key every bucket off the stored `date` label instead — DAY, WEEK, MONTH and YEAR — with `bucket_start` set to that label's UTC-midnight instant. The rollup is now byte-identical to the live `entry.date` fallback and timezone-independent by construction: DST correctness stays where it already lives, in `moodDateKey` at write time. No consumer changes, no schema change; every rollup reader already formats `bucket_start` as a UTC day label. Migration 0269 empties `mood_entry_rollups` so the boot-time full-backfill worker re-mints every user's buckets under the corrected keying; the worker now deletes-then-refolds so it is self-cleaning against any row left by an older instance. While the table is empty, reads fall back to the live `date`-keyed walk, which was already correct, so there is no window where a wrong day is shown.
19 lines
987 B
SQL
19 lines
987 B
SQL
-- v1.32.12 — mood rollup timezone re-key.
|
|
--
|
|
-- The mood rollup writer used to bucket on the UTC truncation of
|
|
-- `mood_logged_at`, so a mood logged late in the evening (or after
|
|
-- midnight) in a non-UTC timezone landed on the wrong calendar day.
|
|
-- The writer now keys every bucket on the canonical per-row
|
|
-- `mood_entries."date"` label instead, byte-identical to the live
|
|
-- fallback and to the day the user logged the mood in their own zone.
|
|
--
|
|
-- Data-only migration: no schema change. `MoodEntryRollup` is a derived
|
|
-- cache, fully reconstructible from `mood_entries` at any time. Emptying
|
|
-- the table drops every stale UTC-keyed row; the app then serves correct
|
|
-- data through the live `date`-keyed fallback until the rollups are
|
|
-- rebuilt, and the boot-time full-backfill worker
|
|
-- (`enqueueBootTimeMoodRollupBackfill` → delete-then-refold) re-mints
|
|
-- every mood-owning user's buckets under the new keying. No mood data is
|
|
-- touched.
|
|
DELETE FROM "mood_entry_rollups";
|