Is there any way, to force a write of an object, which does not throw a stale object exception, thus overwriting the data table.

I have a dialog, which ops up during a stale object exception, and shows the user, the two states of the same object. their in-memory object, and the latest persistent object from the database.
The choice then, is to abandon their object, and refresh from the database, or to force an overwrite of the database, with their object.

But how do I stop another stale object exception from happening.
I've tried setting the version property of the in-memory object to that of the stored object, but an exception happens.

Any clues ?

Thanks

Hi,

I suspect your best bet is to simply overwrite the properties of the most recently loaded object to avoid the stale object exception.

In addition, consider what would happen if you attempt to 'force' a write but, in the time taken for the user to confirm, yet another person has comitted further changes. I suspect the user would then be unaware that they have overwritten subsequent changes sine the first exception.

Regards,
Richard

Good point.

Maybe I can lock the offending record in the table, when the first exception occurs - I need to investigate, and test the possibility of deadlocks etc.

It seems that 'persist' will do the trick for writing the object.

thanks for your advice.