Two Apps, One Contacts Table, and the Hardcoded List That Made It Invisible
One shared Supabase table + a roles array beats two per-app contact tables. But the canonical isn't done when the rows merge — grep every hardcoded li
Databases, sync, analytics and data that has to stay right.
One shared Supabase table + a roles array beats two per-app contact tables. But the canonical isn't done when the rows merge — grep every hardcoded li
CREATE OR REPLACE FUNCTION can change a Postgres function's body — but NOT its return shape. Add or remove a column from RETURNS TABLE(...) and
When PostgREST has two paths between two tables, it picks neither — and one of those failures looks exactly like 'no data.'
If your polling job widens its lookback window on failure, it will silently replace your watermark with a guess. The fix: the cursor only ever advan
I assumed I knew the shape of a TakeShape API response. I was wrong. 856 of 859 cancer treatment centers silently lost their addresses. Fixed in one com
If you're reading a live-written SQLite database you don't own, open it with mode=ro — NOT immutable=1. The difference is subtle, the failure is bru
Running unrelated migrations triggers a PostgREST schema cache reload. If any of your embeds have latent FK ambiguity, that reload will enforce it — and
SWR's revalidateOnFocus, revalidateOnReconnect, and revalidateIfStale are all true by default. On a drag-and-drop board, that's lethal. Wrap
CMS rich-text fields store content with HTML tags and entity codes. Strip the tags, and the entities survive — literally. You need two passes. Always.
When you create a parent row and child junction rows in separate Supabase calls, you're responsible for rolling back. PostgREST gives you no transac
rlsenablednopolicy looks scary. Whether it IS scary depends entirely on how your app connects to Postgres. Know your connection architecture
the setup
In Swift, named parameters to struct memberwise initializers must match declaration order — not the order that looks logical to you. Get it wro
Supabase rolled out new-format API keys. The anon key is now sbpublishable..., not the old eyJ... JWT. If you're bootstrapping a Swift project