Uh oh!
There was an error while loading. Please reload this page.
fix(db): seed _exists_by uses a real column, not hardcoded id - #278
Conversation
user_profiles is keyed on user_id and has no `id` column, so the idempotency pre-check's `select=id` 400'd against staging. Select a column we're already filtering on (the natural/PK key) instead — works for every table. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | frontend-staging | 703b5a7 | Commit Preview URL Branch Preview URL | Jun 24 2026, 10:21 PM |
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Second issue surfaced by seeding staging. The seed's idempotency pre-check
_exists_bydidselect("id"), butuser_profilesis keyed onuser_idwith noidcolumn (0024 identity split) → PostgREST400on the select. Now it selects a column from the filter (the natural/PK key), which always exists. Audited the rest of the seed against the real schemas —node_mastery_events/graph_nodes/graph_edges/documents/notesall haveidand matching conflict-keys, so this is the only such spot. Seed unit tests green (9), ruff clean.