Re: PostgreSQL versioning for ORM was: Hibernate, JBoss, PostgreSQL, timestamp read doesn't match during update

oops, forgot to reply-all. :(

On Fri, Mar 20, 2009 at 7:38 PM, Richard Broersma
<richard(dot)broersma(at)gmail(dot)com> wrote:
> On Fri, Mar 20, 2009 at 11:13 AM, Roland Roberts <roland(at)astrofoto(dot)org> wrote:
>
>> Then why bother having the generated attribute to version?  That flies in the
>> face of the design of *Hibernate* in allowing this.  Hibernate *does* do the
>> right thing in querying the column to get the value back after the update.
>>  You're telling me to not do what Hibernate explicitly say I can do.  Why?
>
> This is a question from an ORM beginner.  It is possible to use
> PostgreSQL's build in row versioning (i.e. CTID or XMIN) for
> Optimistic locking in ORMs like Hibernate and JPA?
>
> --
> Regards,
> Richard Broersma Jr.
>
> Visit the Los Angeles PostgreSQL Users Group (LAPUG)
> http://pugs.postgresql.org/lapug
>

--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug