Until defaults are implemented in Trino, we can attempt to implement them as column properties. This will require parsing a string SQL expression and then executing it, but should allow things like:
using SQL functions to generate data, possibly to get a different distribution
referencing other fields, like date_add('day', CAST(random() * 10 AS INTEGER), created_at) to make sure some constraints are met - this could be harder to implement as a CHECK constraint
Until defaults are implemented in Trino, we can attempt to implement them as column properties. This will require parsing a string SQL expression and then executing it, but should allow things like:
date_add('day', CAST(random() * 10 AS INTEGER), created_at)to make sure some constraints are met - this could be harder to implement as a CHECK constraint