> It appears to me that the onUpdate() method is not getting called when it should.
onUpdate() gets called only when you explicitly pass a transient object to Session.update(). ie. its called when a transient object becomes "sessional". Its not called when an dirty object is UPDATEd on the database. I'm not sure if that is the source of some confusion, or if there is an actual bug. I know it seems to make sense to have a callback just before changes are persisted, and I spent a lot of time thinking about that. However, I decided that this was actually not a good idea for a number of reasons (I will describe them if you want but my girlie wants to us the computer now so I don't have time...) > Before I go digging around and trying to fix this, I wanted to make sure no one else was working on it. Yeah, could you please check thats its working as I described. There is a test for this but tests are not infallible. > PS - Is anyone working on adding outer join support for Oracle? If not, then I'd like to volunteer to do this. Yes, please. No-one is working on this AFAIK and I'm not planning to implement it myself. I'm playing around with a little ODMG-compliant API adaptor at the moment. Much less powerful API than Hibernate, because ODMG was designed as a lowest-common-denominator thing. But its is an established standard. Doesn't hurt to support it as an alternative. ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
