[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5429?page=c... ] Max Giesbert commented on HHH-5429: ----------------------------------- Just rechecked with Derby 10.6.2.1 and Hibernate 3.6.0 final. Problem still exists. Work-around is to set GenerationType to TABLE. -- 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

[ https://hibernate.onjira.com/browse/HHH-5429?page=com.atlassian.jira.plug... ] Fabien Marsaud commented on HHH-5429: ------------------------------------- I believe this issue can be closed: Hibernate now simply abides by http://db.apache.org/derby/docs/10.6/ref/rrefsqlj37836.html ID generation. Let's assume your entities are declared with: @javax.persistence.Id @GeneratedValue(strategy = GenerationType.AUTO) public Long getId() { return id; } At the time of Hibernate 3.3, if your DB was created using the output of configuration.generateSchemaCreationScript(new DerbyDialect()), you must have got some HIBERNATE_UNIQUE_KEY table which acted as a sequence for Hibernate to fill entities' IDs before INSERT. With Hibernate 3.5+ the DDL statements would contain "generated by default as identity" next to each PK declaration. In other words, now, Hibernate has a good reason *not* to fill the ID of entities to be inserted: it considers Derby should manage them instead. If you want to keep your Derby IDs as they *were* (without generated identity), just fill the ID column yourself before INSERT. We could have the same with not autoincremented MySQL tables PKs. To fix, you may want to export data, drop contraints+tables, regenerate creation script, check it contains "generated always/by default as identity", create tables, re-insert data, restore constraints, enjoy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://hibernate.onjira.com/browse/HHH-5429?page=com.atlassian.jira.plug... ] Fabien Marsaud edited comment on HHH-5429 at 2/21/12 8:31 PM: -------------------------------------------------------------- I believe this issue is not a regression and that it can be closed: Hibernate now simply abides by http://db.apache.org/derby/docs/10.6/ref/rrefsqlj37836.html ID generation. Let's assume your entities are declared with: @javax.persistence.Id @GeneratedValue(strategy = GenerationType.AUTO) public Long getId() { return id; } At the time of Hibernate 3.3, if your DB was created using the output of configuration.generateSchemaCreationScript(new DerbyDialect()), you must have got some HIBERNATE_UNIQUE_KEY table which acted as a sequence for Hibernate to fill entities' IDs before INSERT. With Hibernate 3.5+ the DDL statements would contain "generated by default as identity" next to each PK declaration. In other words, now, Hibernate has a good reason *not* to fill the ID of entities to be inserted: it considers Derby should manage them instead. If you want to keep your Derby IDs as they *were* (without generated identity), just fill the ID column yourself before INSERT. We could have the same discussion with non-autoincremented MySQL tables PKs. To fix, you may want to export data, drop contraints+tables, regenerate creation script, check it contains "generated always/by default as identity", create tables, re-insert data, restore constraints, enjoy. was (Author: fabmars): I believe this issue is not a regression and that it can be closed: Hibernate now simply abides by http://db.apache.org/derby/docs/10.6/ref/rrefsqlj37836.html ID generation. Let's assume your entities are declared with: @javax.persistence.Id @GeneratedValue(strategy = GenerationType.AUTO) public Long getId() { return id; } At the time of Hibernate 3.3, if your DB was created using the output of configuration.generateSchemaCreationScript(new DerbyDialect()), you must have got some HIBERNATE_UNIQUE_KEY table which acted as a sequence for Hibernate to fill entities' IDs before INSERT. With Hibernate 3.5+ the DDL statements would contain "generated by default as identity" next to each PK declaration. In other words, now, Hibernate has a good reason *not* to fill the ID of entities to be inserted: it considers Derby should manage them instead. If you want to keep your Derby IDs as they *were* (without generated identity), just fill the ID column yourself before INSERT. We could have the same with non-autoincremented MySQL tables PKs. To fix, you may want to export data, drop contraints+tables, regenerate creation script, check it contains "generated always/by default as identity", create tables, re-insert data, restore constraints, enjoy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira