fix(weight): dedup identical same-day readings on ingest#39
Merged
Conversation
The bt-scale gateway burst-posts the same reading several times as it settles (e.g. six identical 272.20 rows for 2026-06-07 within 4 seconds), and InsertW appended every one — the source of the duplicate rows that DeleteW now has to mop up by date. InsertW now skips the insert when a row already exists for the same date and weight, while still allowing a genuinely different value on the same day (the log shows the latest recorded_at, so multiple distinct weigh-ins per day remain supported). NUMERIC comparison makes "272.2" and "272.20" equal. Verified against a live-data preview: posting the same (date, weight) three times yields one row; a different value the same day yields two; a re-posted formatting variant dedups. No schema change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Root-cause follow-up to #38. The bt-scale gateway burst-posts the same reading several times as it settles, and InsertW appended every one — the source of the duplicate weight rows. InsertW now skips inserting when a row already exists for the same date and weight, while still allowing a genuinely different value the same day (latest recorded_at wins for display). NUMERIC comparison treats 272.2 and 272.20 as equal. Verified on a live-data preview (same reading 3x → 1 row; different value same day → 2; formatting variant dedups). No schema change.
🤖 Generated with Claude Code