Skip to main content
For the live PostgreSQL-to-PostgreSQL workflow, keep destination columns explicit and conservative.
Source shapeDestination type
identifiersbigint, uuid, or text
names and labelstext
amountsnumeric
timestampstimestamptz
datesdate
booleansboolean
nested JSONjsonb or selected scalar columns

​
Casts

Use Normalisation casts for simple structural coercion before SQL models run. Use SQL for more specific conversions, null handling, JSON extraction, or column derivation.

​
Destination validation

The destination table must contain every model output column you intend to deliver. Extra nullable destination columns are usually safe; missing required model columns are not.