On 10 Nov (00:27), Gavin King wrote: > loaded object from the session cache). The new state is then /copied/ > onto the loaded object and the loaded object is returned to the user. > We never get the exception listed above, because we don't try to add > the given object to the cache. If no object is returned from the > database, we save the given object.
Complex, I wish more people would understand lock() and update() instead of having to learn yet another method, which is certainly not a better approach. > This approach has two enormous disadvantages: > > (1) it breaks == from the user's POV Yes. > (2) it is much less efficient than just doing an update Yes. > But, as long as we have both options, all is good. I'm not sure :) > (a) help out people who are trying to make composite-id stuff work I have no mercy for people with composite identifiers ;) > (b) solve problems for people who try to do this: I'm a really not sure about this. -- Christian Bauer [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
