NHibernate 1.2.0.Beta2

Am I correct in stating that Versioning won't work when you use custom SQL for the update statements on an object?

For example in the class mapping file

<sql-update>exec up_UpdateData ?, ?, ?, ?</sql-update>

is used to so when we call

session.Update(myTestObject);

no StaleObjectStateException is thrown even though it's passing to the stored procedure the new and old version number associated with myTestObject.

It works when we don't override the Update and I was hoping for it to work in the same manner when we did.

Thanks
Rhys

I am having exactly the same problem here.


This is the mapping file:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.2">

<class name="Server.Test03, Server" table="Table02" lazy="false">
<cache usage="read-write"/>
<id name="Key" column="myKey" unsaved-value="null">
<generator class="assigned" />
</id>
<version name="Version" column="version" type="Int32" unsaved-value="0" />
<property name="MyValue" column="myName" type="String" length="50"/>
</class>

</hibernate-mapping>

When i try to force (for testing purposes) a StaleObjectException this works fine. But as soon as I change the mapping file to use a stored procedure for updates like this:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.2">

<class name="Server.Test03, Server" table="Table02" lazy="false">
<cache usage="read-write"/>
<id name="Key" column="myKey" unsaved-value="null">
<generator class="assigned" />
</id>
<version name="Version" column="version" type="Int32" unsaved-value="0" />
<property name="MyValue" column="myName" type="String" length="50"/>
<sql-update>exec up_UpdateData3 ?, ?, ?, ?</sql-update>
</class>

</hibernate-mapping>

The data just gets updated and no stale exception is thrown when it should be. Why would this be the case does anyone know??

Clare

I am having exactly the same problem here.


This is the mapping file:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.2">

<class name="Server.Test03, Server" table="Table02" lazy="false">
<cache usage="read-write"/>
<id name="Key" column="myKey" unsaved-value="null">
<generator class="assigned" />
</id>
<version name="Version" column="version" type="Int32" unsaved-value="0" />
<property name="MyValue" column="myName" type="String" length="50"/>
</class>

</hibernate-mapping>

When i try to force (for testing purposes) a StaleObjectException this works fine. But as soon as I change the mapping file to use a stored procedure for updates like this:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.2">

<class name="Server.Test03, Server" table="Table02" lazy="false">
<cache usage="read-write"/>
<id name="Key" column="myKey" unsaved-value="null">
<generator class="assigned" />
</id>
<version name="Version" column="version" type="Int32" unsaved-value="0" />
<property name="MyValue" column="myName" type="String" length="50"/>
<sql-update>exec up_UpdateData3 ?, ?, ?, ?</sql-update>
</class>

</hibernate-mapping>

The data just gets updated and no stale exception is thrown when it should be. Why would this be the case does anyone know??

Clare

Does your stored procedure return 1 affected row in case it succeeded and 0 affected rows in case it failed? This is what NHibernate expects in this case.

Also, you can try detecting stale state in your stored procedure and signal an error manually.

I traced the database called and it definately returnes

(1 row(s) affected)

Clare Stinton

In fact it returns this each time it is called (it successfully runs) even when trying to update a stale object.

Clare

The stored proc should return 0 affected rows if the object is stale

Yes thanks for that, I had to change the stored procedure to take account of the version in the update.