Files
twenty/packages
Charles Bochet 5138ab9d22 fix(server): skip composite fields with missing columns in NormalizeCompositeFieldDefaultsCommand
Some workspaces created before the actor composite type's `context` sub-property was added are missing the corresponding workspace-schema columns (e.g. `attachment.createdByContext`). The migration runner then fails with `column "createdByContext" of relation "attachment" does not exist` when this 2.5 workspace command tries to ALTER COLUMN ... SET DEFAULT NULL on the missing column.

Before building the metadata update, query `information_schema.columns` for the workspace schema and filter out any composite field whose sub-property columns aren't all physically present. Skipped fields are logged so the missing columns can be backfilled in a follow-up.
2026-05-14 19:34:40 +02:00
..
2026-05-04 11:09:34 +02:00