> * Remove the exception that occurs if you save an object > that is already associated with the session. This > makes save() consistent with saveOrUpdate().
>Lets make this change. > * Remove the exception that occurs if you delete an object > that is already deleted in that session. >Lets make this change also (for consistency). Max, I don't see >much value in making this configurable. We don't want to spawn >millions of config properties for minor issues like these. <snif> ;( bummer.... The methods will still throw an exception if I delete/save the same entity with two different instances, or ? e.g. Person p1 = s1.load(Person.class, 42); Person p2 = s2.load(Person.class, 42); // P1 and P2 are same entity, but two different instances s1.delete(p1); s1.delete(p1); // will now not throw an exception s1.delete(p2); // would be nice if it blew.... (and the same for save()) That would ensure that I can still be "notified" if someone has "screwed" up their save/delete sequence... /max ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
