- Shipped
- 4 Septemba 2026, 06:01 UTC
- Author
- Kamo
- Commit
- 4b91083
The field was declared `@Column(nullable = false)` with no columnDefinition, so ddl-auto emitted `ADD COLUMN published boolean not null` — which Postgres REFUSES on a table that already has rows. KamoInitializer logged column "published" of relation "system_bug" contains null values and carried on, so the column simply did not exist. The first service deployed with this entity would then have 500'd on every SystemBug read with `column s1_0.published does not exist`, which is exactly how the careers columns broke DocsService earlier today. The javadoc directly above already promised "the column default says the same thing, so every row filed before this existed reads as published". This is what actually writes that default. Found while applying an unrelated schema run on 2026-09-03; the column and idx_system_bug_published now exist.