Re: [hibernate-dev] Possible to confirm that versioning is broken forPersistentSets?

Ok. The isDirty()/write()/add()/clearDirty() idiom explains why the patch was producing NPEs in other tests. Otherwise, the only other failures that seemed they could be related were from the optlock tests. Two were failing earlier (see

RE: [hibernate-dev] Possible to confirm that versioning is broken forPersistentSets?

Oops: protected void configure(Configuration cfg) { super.configure( cfg ); cfg.setProperty( Environment.BATCH_VERSIONED_DATA, false ); } The reasoning being that certain drivers (oracle and db2 that I know of) report an unknown status for these