You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user-java@ibatis.apache.org by mule_user <sg...@aol.com> on 2008/08/18 23:39:04 UTC

iBATIS 2.3 -Handling Concurrent Update

What are the options for handling concurrent updates in iBATIS 2.3?
As Clinton Begin's "iBATIS in Action" book specifies using timestamp, or
version number as a column in database table.

Is any other strategy being introduced in the newer version of iBATIS?
-- 
View this message in context: http://www.nabble.com/iBATIS-2.3--Handling-Concurrent-Update-tp19040516p19040516.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

Re: iBATIS 2.3 -Handling Concurrent Update

Posted by Clinton Begin <cl...@gmail.com>.

You can use pessimistic locking if you want... just with SQL... SELECT FOR
UPDATE....

I wouldn't recommend it, as for most apps optimistic locking is fine.  Use
dates or incrementing version numbers....

What else is there?

clinton

On Mon, Aug 18, 2008 at 3:39 PM, mule_user <sg...@aol.com> wrote:

>
> What are the options for handling concurrent updates in iBATIS 2.3?
> As Clinton Begin's "iBATIS in Action" book specifies using timestamp, or
> version number as a column in database table.
>
> Is any other strategy being introduced in the newer version of iBATIS?
> --
> View this message in context:
> http://www.nabble.com/iBATIS-2.3--Handling-Concurrent-Update-tp19040516p19040516.html
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>
>