Its not only the cache entry that is the problem; also FK violations. We would need to force the parent to be inserted earlier. (Which is possible, I guess - simply track whether the parent has children with identity ids, at startup time.)
Simon Spero wrote:
On Sep 4, 2004, at 11:20 PM, Gavin King wrote:
Saw your JIRA issue; this has been discussed before, and I decided not to try and fix it.
There are straightforward workarounds....
It's probably not worth fixing in 2.x, but it might be simpler to do the right thing in 3?
I did think about trying to build the CacheEntry when the suspension is created, but I couldn't convince myself that all necessary cascades have happened by then.
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
