From: Tobias (JIRA) <no...@at...> - 2006-06-29 12:34:49
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1280?page=comments#action_23482 ] Tobias commented on HHH-1280: ----------------------------- It does, and we need a quite ugly workaround to circumvent this. We check the problematic relations before "refresh" and remove all Entities which have no identifier yet. > Cascade refresh and new instances > --------------------------------- > > Key: HHH-1280 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1280 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Gavin King > > > I have a report that if you have a managed object, with a reference to a new object, where cascade refresh is enabled, and you refresh the managed object, then you will get an exception as refresh tries to cascade to the new object. In fact, the new object should just be ignored. > Looking at the code, this does appear to be the case. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |