From: <leg...@at...> - 2003-10-29 21:25:14
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-434 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-434 Summary: Have the ability to turn off and on Hibernate constraints Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Assignee: Reporter: John Towell Created: Wed, 29 Oct 2003 3:24 PM Updated: Wed, 29 Oct 2003 3:24 PM Description: In most relational DB's you are able to disable FK constraints and then enable them later. This is helpful when loading the DB with data. It would be beneficial to allow Hibernate to do the same. (i.e) do not throw the net.sf.hibernate.ObjectNotFoundException: No row with the given identifier exists: for a certain amount of time. This would allow the use of Hibernate delete's in the data clean-up before the FK constraints are turned back on. I guess if people wish do disable the Hibernate constraints altogether that would be a possibility as well. Some postings where this is adressed. http://forum.hibernate.org/viewtopic.php?t=219 http://forum.hibernate.org/viewtopic.php?t=925118 --------------------------------------------------------------------- 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/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |