On 23 Apr (04:10), Gavin King wrote: > I have confirmed this. It is not intended behavior. > > PersistentCollectionType.isDirty() > DirtyCollectionSearchVisitor > > should both check that the collection is not inverse="true" before > returning true. > > Add it to TODO list.
I still think that this not entirely correct, even if we say that "inverse" versions are not updated. What is the reason for that and what is the reason for saying that unidirectional associatons have incremented version numbers? Why is the versioning dependent on the inverse? It looks like that versioning is currently really limited to the optimistic Hibernate locking and can't be used for anything else. With a small change, it could be usable. -- Christian Bauer [EMAIL PROTECTED] http://www.hibernate.org/ ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
