KamoCRM

Add binders.is_scratch

FeatureInitializerService
Shipped
21 ஆகஸ்ட், 2026 அன்று 6:21 AM UTC
Author
Kamo
Commit
ec216b0

Four statements rather than one ALTER: binders is populated, and Yugabyte rejects the whole ADD COLUMN … NOT NULL statement rather than the clause, so the column arrives nullable, is backfilled, gains its DEFAULT, and only then is tightened. @Order(0) per the column-add convention — the shared-lib entity now maps is_scratch, so any runner that loads a Binder before this one dies on a column that does not exist yet.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing