ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hugh Ross" <hh4r...@gmail.com>
Subject Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies
Date Thu, 30 Oct 2008 16:39:54 GMT
One thing you might consider would be to carry two timestamps in your
POJO(s).  One old_ts and one new_ts.  Selects or read DAOs could populate
both.  Updates would use new_ts in the SET clause, and old_ts in the WHERE
clause.  Clients should never change the old_ts.

On 10/10/08, mule_user <sgho@aol.com> wrote:
>
>
> Yes, all these posts do answer my question. And, agree with Clinton Begin
> as
> he said - "there is no magic there..."
>
> --
> View this message in context:
> http://www.nabble.com/IBATIS-2.3.3%2C-JDK-1.5---Optimistic-locking-strategies-tp19867989p19924928.html
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>
>

Mime
View raw message