Re: [GENERAL] Serialized Access

Phillip Mills wrote: On Wed, Jun 25, 2008 at 10:21 PM, Craig Ringer <[EMAIL PROTECTED] > wrote: You might want to look into advisory locking. If your locks don't need to be longer than the life of an active EntityManager session then you can probably just

Re: [GENERAL] Serialized Access

On Wed, Jun 25, 2008 at 10:21 PM, Craig Ringer <[EMAIL PROTECTED]> wrote: > > You might want to look into advisory locking. If your locks don't need > to be longer than the life of an active EntityManager session then you > can probably just issue a native query through the EntityManager to > acqu

Re: [GENERAL] Serialized Access

On Wed, Jun 25, 2008 at 10:55 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote: > Until you benchmark it for your app you really don't know how > inefficient it really is compared to pessimistic locking. > Sure. The question was about more about finding the right approach/layer for implementing pessi

Re: [GENERAL] Serialized Access

On Wed, Jun 25, 2008 at 9:21 AM, Phillip Mills <[EMAIL PROTECTED]> wrote: > I'm working on an application that uses EJB3 entities in JBoss, with > Hibernate and a PostgreSQL database. One of the entity tables needs > consistent, synchronized updates to rows in an environment where telling the > us

Re: [GENERAL] Serialized Access

Phillip Mills wrote: > I'm working on an application that uses EJB3 entities in JBoss, with > Hibernate and a PostgreSQL database. One of the entity tables needs > consistent, synchronized updates to rows in an environment where telling the > user that their operation failed and starting over is n

[GENERAL] Serialized Access

I'm working on an application that uses EJB3 entities in JBoss, with Hibernate and a PostgreSQL database. One of the entity tables needs consistent, synchronized updates to rows in an environment where telling the user that their operation failed and starting over is not an option. Because it's t