[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co...
]
Luke Maurer commented on ANN-604:
---------------------------------
Agreed - and I would submit that this ins't in fact "minor" as there's
no good workaround when you want the DDL to reflect the default. For us, 90% of the time
when a database schema change requires manual intervention by every developer with a local
development database, it's because of a column that's been added that should not
be null (or not by default). Often this leads to subtle "bugs" on development
boxes if not everyone keeps their schema current (or not everyone follows procedure when
checking in a schema change).
Docs suggest the use of the columnDefinition attribute, but this requires us to specify
the SQL data type explicitly, which has its own problems.
There is no annotation to specify default value for a column
------------------------------------------------------------
Key: ANN-604
URL:
http://opensource.atlassian.com/projects/hibernate/browse/ANN-604
Project: Hibernate Annotations
Issue Type: New Feature
Components: binder
Affects Versions: 3.3.0.ga
Reporter: Nicolae Bucalaete
Priority: Minor
In hibernate annotation you can't specify default value for a column.
If you use xml files for mapping then you have this feature.
I consider that this is a major problem with annotation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira