[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] Christian Bauer updated ANN-604: -------------------------------- Issue Type: New Feature (was: Bug) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] Nicolae Bucalaete commented on ANN-604: --------------------------------------- If you put this on "Priority = Minor" you should have a workaround for this problem. Do you have a workaround ? If you don't have then this is a critical problem. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] Max Rydahl Andersen commented on ANN-604: ----------------------------------------- workaround: set the default column manually at db level. default values are not relevant unless you use dynamic-insert anyway. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] david durham commented on ANN-604: ---------------------------------- They're particularly relevant if you add a non-nullable column to a table definition after initial creation. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] Thomas Einwaller commented on ANN-604: -------------------------------------- @Nate: as David pointed out this feature would be especially useful when adding columns do an existing table that already contains entries - in this case all the existing entries get a null value in the database and therefor can not be restored anymore -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-604?page=co... ] Jean-Baptiste BRIAUD commented on ANN-604: ------------------------------------------ The main problem is when you use Hibernate to propduce the database schema. Then, the default value is not a constraint in the schema because no annotation allows you to specify it. This is a blocker for me right now. Also, as you start accessing the DB via other application than the one where Hibernate manage the persistance, the DB and not Java must be aware of this default value. Again in that case, this is a blocker. The workaround works only in one case : all access to the DB has to be done via the same Hibernate application, this could be done via Java declaration but this is not always the case. This works in XML definition and this is the only real workaround but you have to like XML more than 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4341?page=c... ] Gabriel Millán commented on HHH-4341: ------------------------------------- I agree the priority of this issue should be higher. There is no way to make the schema have a default value without using columnDefinition, which will mean having specific database notation on your entities. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4341?page=c... ] Rodrigo Queiroz commented on HHH-4341: -------------------------------------- In Oracle database, even setting the column with a default value woudn't work. In this example: CREATE TABLE TEST ( ID NUMBER(20) NOT NULL, T NUMBER 20 DEFAULT 0 ) if we try: INSERT INTO TEST (ID) VALUES (1); we'll get: ID, T 1, 0 But with hibernate, the generated insert is: INSERT INTO TEST (ID, T) VALUES (1, NULL); Which will force Oracle to accept the NULL value to T, giving us: ID, T 1, NULL In my case, the T column should be NOT NULL. Even though I have a default value to the column, I still get a constraint violation. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4341?page=c... ] tscho commented on HHH-4341: ---------------------------- A possible workaround is to use the columnDefinition parameter in the @Column annotation. For example: @Column(name="myInt", columnDefinition="INTEGER DEFAULT 17"). Though this solution is database specific it worked fine for me so far. But there is a major problem with this solution when it comes to primary keys (PK is a random UUID in a PostgreSQL 8.4 database): class PkEntity { @Id @Column(nullable = false, unique = true, updatable = false, columnDefinition = "uuid DEFAULT uuid_generate_v4()") java.util.UUID id; } When this entity is referenced from another entity like this (nullable FK): class FkEntity { @ManyToOne(optinal=true) @JoinColumn PkEntity pkEntity; } the generated schema looks like this: CREATE TABLE fk_entity ( pk_entity uuid DEFAULT uuid_generate_v4() ) and this is of course not what I want my nullable FK to look like! -- 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