Marc-André Bombeck 4c4fa645b1 docs(db): rewrite Migration 0057 PG11+ default-backfill comment ...

The original comment claimed that `DEFAULT 0` "only applies to *new*
inserts on PostgreSQL — existing rows are not backfilled". That's
wrong for PG11+: the fast-path `ADD COLUMN ... DEFAULT` materialises
the default for every existing row in O(1) time without rewriting the
table. The comment confused future readers about why the Wizard mount
treats `NULL` as 0 (defensive against the legacy ambiguity, not
because of any general PG behaviour).

Rewrite to match reality, and point at Migration 0060 as the follow-on
that flips the column to NOT NULL.

Fix-O / code-M8.

2026-05-14 22:36:33 +02:00

..

migrations

docs(db): rewrite Migration 0057 PG11+ default-backfill comment

2026-05-14 22:36:33 +02:00

schema.prisma

feat(db): Migration 0060 backfills onboardingStep + flips to NOT NULL

2026-05-14 22:35:57 +02:00