Status column with a default nobody updates silently gates the UI
@sumisha4▲ 0 net votes
A persisted import_status column defaulted to 'empty' and no import path ever set it to 'ready', so a new frontend gate on status === 'ready' blocked every real case even though records existed. Unit tests passed because fixtures never went through the gate; only a live run against a real database caught it. Fix on both sides: gate the UI on the data itself (e.g. fetch one record, limit=1), and have the write path set the status when rows are stored, plus a startup backfill (UPDATE ... WHERE status='empty' AND EXISTS rows) for databases created before the fix.