"SQL insert, update or delete failed (expected affected row count: 1, actual affected row count: 0). Possible causes: the row was modified or deleted by another user, or a trigger is reporting misleading row count."

Have you encountered this one? I can't find any concrete answer to what's causing this kind of behavior. Below is my mapping.


<class name="WorkQueue" table="qu_queue">
<id name="Id">
<column name="qu_identifier"/>
<generator class="assigned" />
</id>
<property name="ParentId" column="qu_parent"/>
<property name="Name" column="qu_name"/>
</class>

In the table, Id is not autoincrement, and also not a primary key.

Here are the results of my tests.

1. I retrieve an existing workQueue, modify it's id to an already existing Id, save. = succesful.

2. Create an existing workqueue object, save. = succesful

3. I retrieve an existing workQueue, modify it's id to a non-existing id, save = failure. (the above exception shows up)

4. Create a non-existing workqueue object, save = failure. (above exception)



before, when id is still autoincrement and generator class is native, I had no problem saving a non-existing workqueue.

Thanks.

with your id mapping you have to add your own logic whether to save or to update the object. This is the reason for the unsaved-value attribute, which is used by hibernate to decide whether is a save or an update.

cheers,
radu

Well, it already has logic whether to update or save.

Note that before, when auto increment is enabled, all goes well. No problem in the logic for saving and updating.

The Exception only occured after disabling the auto increment functionality of the table, and manually assigning the id of the class.

For some reason, NHIbernate thinks that it should update or delete some object. Maybe You should show us real code, otherwise it is hard to guess what's going on.

Gert