You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating a DB migration targeting multiple platforms ... and using UUID types the generated type of the UUID properties is controlled by the default platform type (rather than each specific platform).
Expected behavior
We expected the appropriate DDL column definition for "logical UUID" types based on the platform. So H2 and Postgres have native UUID type support but MySql, Oracle, Sqlite don't and we would expect VARCHAR(40), VARCHAR2(40) etc or BINARY(16) depending on the ServerConfig DbUuid setting.
When generating a DB migration targeting multiple platforms ... and using UUID types the generated type of the UUID properties is controlled by the default platform type (rather than each specific platform).
Expected behavior
We expected the appropriate DDL column definition for "logical UUID" types based on the platform. So H2 and Postgres have native UUID type support but MySql, Oracle, Sqlite don't and we would expect VARCHAR(40), VARCHAR2(40) etc or BINARY(16) depending on the ServerConfig DbUuid setting.
Steps to reproduce
The text was updated successfully, but these errors were encountered: