Menu
▾
▴
[Hibernate-issues] [Hibernate-JIRA] Created: (HB-153) A method to get the next id in a database/generator independent way
|
From: <leg...@at...> - 2003-06-24 15:34:57
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-153 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-153 Summary: A method to get the next id in a database/generator independent way Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: Andrea Aime Created: Tue, 24 Jun 2003 10:34 AM Updated: Tue, 24 Jun 2003 10:34 AM Description: As you say in the developers guide, Hibernate is not well suited for mass updates. So, ok, let's do them the hard way with prepared statements and batching, but one question is open: how do I generate the same id that Hibernate would generate, so that I can avoid duplicated primary keys in a database independent manner? A method like Session.getNextId(Class class) would be useful (returning null if identity columns are used, or some other way to know that an identity column is used for the specific class). I've set major priority since I see no way to perform jdbc mass inserts in a database independent way and Hibernate could provide some support for this... (I mean, Hibernate is not only good for OR mapping, but also to write database independent applications, this problem is a limit when writing high performance apps that need mass inserts) --------------------------------------------------------------------- JIRA INFORMATION: 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/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
