Group,
Tried to upgrade to hibernate 2.1.3 today from 2.0 and discovered that one
of my tests started to fail with
"net.sf.hibernate.HibernateException: Batch update row count wrong: 0".
The test was for verifying cascadingDeletes. After digging a little I found
the root of my problem in net.sf.hibernate.impl.BatchingBatcher
(http://cvs.sourceforge.net/viewcvs.py/hibernate/Hibernate2/src/net/sf/hiber
nate/impl/BatchingBatcher.java?r1=1.4.2.3&r2=1.4.2.4&only_with_tag=v21branch
). Previously, we could call remove on an already removed object and not
have an Exception thrown, but now one is thrown.
Is there any way a More specific Exception can be thrown from the
BatchingBatcher instead of HibernateException? Right now, the only way to
tell what kind of error this really is, is to check the error string.
Here's the junit test in case you were curious:
public void testCascadingRemove() throws Exception {
Pet pet = new Pet(getName(), (Person)getPersistent());
try{
PetStore.getInstance().save(pet);
remove(getPersistent());
StoreTestUtils.assertRemoved(pet, PetStore.getInstance());
}
finally{
// this is where the the test fails.
PetStore.getInstance().remove(pet);
}
}
thanks,
eric.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
