Two Airtable Traps From One Afternoon—and Why I Moved the Sort to JavaScript
Airtable's API stores single-select values as JSON arrays. Migrate them 'as-is' and every downstream caller that expects a bare string will blow up.
Databases, sync, analytics and data that has to stay right.
Airtable's API stores single-select values as JSON arrays. Migrate them 'as-is' and every downstream caller that expects a bare string will blow up.
When you batch-process a registry of inputs, one malformed item will eventually reach production. If you don't isolate it, it aborts everything afte
schemaname='public' in a Postgres migration doesn't mean 'this app's tables.' On a shared database, it means every table from every tenant. We caugh
If your data source takes more than ~500ms, don't block your UI on every read. Serve the last known value instantly, revalidate in the background. T
We had a Supabase project shared across five apps with one Google OAuth client and no domain restriction on signups. We gated every table with RLS b
an internal digital asset manager had a blanket Row-Level Security policy with with check(true) covering every table — including memberships, the ta
A Zod .max(500) added for security silently became a hard limit on real batch operations. The fix is a sequential chunking loop — and every caller tha
When you bolt a junction table onto a legacy singular FK, your schema is multi-entity. Your validation logic? Still isn't. Every constraint that rea
Supabase auto-enables RLS on every new table. Without a policy, Postgres returns zero rows — silently. The fix is one line, but only after you've st
PostgREST's PGRST201 isn't just a loud crash — it can be a perfectly silent one. Here's how that happened to me, and the two-line sweep that catches
If you're doing multi-table writes as sequential supabase-js calls, one mid-loop error leaves your database in a broken half-state. Push it into a
If your sync watermark advances before a batch fully commits, you have a silent data-loss trap. Freeze it until the whole batch is done.
If your database splits names across columns (firstname / lastname), a full-string ILIKE against either column will never match a two-w
GA4 (Google Analytics 4) hard-blocks service accounts from Workspace-org properties. Don't fight it — authenticate as a real user with a refresh tok
If you're pulling GA4 pagePath data via the Data API and using matchType: CONTAINS, your click counts are probably wrong. Use EXACT. For A/B v
If your database identifies an entity through a relationship, your search query has to traverse that relationship — or it will return nothing for the mo
Prove your numbers on a stateless preview route before you touch the database. In that order, every time.
We had 13 Supabase RLS policies set to using(true). That meant any Google account in the world could read our Shopify orders through PostgREST — c
If your Halo Effect pulls all-time orders without a time fence, you're not measuring event impact — you're measuring your entire customer history. Fix i
If you're attributing Shopify sales to a webinar (or any campaign), you MUST exclude orders tagged Subscription Recurring Order. They're Recharge
If a metric varies by both sides of a many-to-many relationship — not just one — it belongs on the join table. I had to learn this a third time be
Supabase auto-enables Row Level Security (RLS) on every new table — no policy = deny-all, and supabase-js returns { data: [], error: null } with
PostgREST silently caps query results at 1000 rows. No error. The data shape looks fine. Your math is just… wrong. Move aggregation into SQL functions c
Before shipping a single feature chart, scaffold your shared primitives — palette, container, tooltip styles, selectors. Every styling bug you hit a
I called the advisor before shipping an Airtable data migration — it caught real blockers. Same week I skipped that step on a Shopify sync, and a 30-sec
If a Supabase helper creates its own createClient(), it has no session. RLS rejects the read. It fails silently. Everyone gets denied. Pass the
if a sync job upserts on a shared key, every re-run can silently blow away manual edits. Add a per-record lock flag the importer checks before writing
One confirm dialog is not enough. Stack four guards — flag, hardcoded env ref, pre-approved mapping file, and a typed 'DESTROY' prompt that shows ro
Stop aggregating in JavaScript. Move the math into a Postgres SQL function, call it via supabase.rpc(), and MATERIALIZED the shared base CTE so
If your Supabase aggregation numbers look plausible but wrong, check the row count first. PostgREST silently caps at 1,000. Push the math into a SQL