I do a save(), but hibernate attempts to do an Update.
Therefore I get:

net.sf.hibernate.HibernateException: SQL insert, update or delete failed (row not found)
at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:25)


Here's the beginning of the HBM:

<class name="MasterHibernate" table="RMASTER" >

<id name="masterID" unsaved-value="null" type="com.lbss.framework.hibernate.domain.types.IntegerMapper">
<column name="RMSFILENUM" not-null="true"/>
<generator class="assigned"/>
</id>


And here's the simple code:
MasterHibernate pojo = new MasterHibernate();
pojo.setMasterID(new Integer(199));
pojo.setBlockPayment(LBSSBoolean.FALSE);
session.save(pojo);


I've tried unsaved-value=any but it gives the same problem. I must be missing something obvious here, but I've been through the faqs and docs and can't see what I'm doing wrong.

I'm pretty new to Hibernate but from what I've read, the unsaved-value doesn't make sense on an assigned identifier.
Because it's assigned there will never be a value that indicates it's unsaved.

If you use an assigned identifier then you need to provide a version property or a timestamp with an unsaved-value.

Problem solved. But no idea why.

If I'm issuing a session.save(entity), surely Hibernate should do an insert.

I've actually tracked this down to the deepCopy() method on a custom type that i had on my entity. I have to return the object instead of a copy and it all works fine:


public Object deepCopy(Object x) {
return x;
//return new LBSSCurrency(((LBSSCurrency)x).getValue());
}


But why on earth this has fixed the problem I have no idea.

Just an fyi, hib does not necessarily do an insert when sess.save is called.

If your id is assigned, then a timestamp column/property can be used, of some other prop for "unsaved value"

James