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
Closing out this ticket. We have decided to NOT implement this feature.
While it is definitely tempting to add, the database SQL script(s) itself should be the definitive source of truth.
Also adding the ability to specify a custom SQL type via annotation would also make the generated schema database dependent (i.e. if one specified VARCHAR2(30) that would work great for Oracle but not for other database types).
In short, specifying the type at the annotation level in Code is not the right place to do it.
If we did want to have such a feature (to specify via code) the right place to do it would be in the SchemaSQLGenerationDataModel class.
When we create the model, an array containing <Table, Column, Custom-Type> could be passed in.
Enhance @column annotation to allow for specifying custom SQL types, as well as well as length/precision.
For this enhancement we will be taking what is in the JPA standard that is relevant to Schema generation.
https://docs.oracle.com/javaee/7/api/javax/persistence/Column.html
The text was updated successfully, but these errors were encountered: