Re: SELECT FOR UPDATE - Mailing list pgsql-general

From will trillich
Subject Re: SELECT FOR UPDATE
Date
Msg-id 20010823033012.H15403@serensoft.com
Whole thread Raw
In response to Re: SELECT FOR UPDATE  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-general
On Wed, Aug 22, 2001 at 09:01:10PM -0400, Jan Wieck wrote:
> jose wrote:
> > - Is it possible to know  in advance if the records of a given query are
> > locked, to prevent to be locked for ever?
>     Anyway,  the  answer  is  no.  Standard  SQL doesn't have any
>     mechanism to check wether a given row is locked or to force a
>     query to fail with an error in the case a required lock isn't
>     available immediately.
>
>     But the question itself tells that you're about to  implement
>     a  major  design  error in your application. Holding database
>     locks during user interaction IS A BAD  THING.  Never,  never
>     ever  do  it  that  way.   And  anybody telling you something
>     different is an overpaid idiot.

"never ever do it THAT way." okay.

what way SHOULD we do it?

--
Khan said that revenge is a dish best served cold. I think
sometimes it's best served hot, chunky, and foaming.
    - P.J.Lee ('79-'80)

will@serensoft.com
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!

pgsql-general by date:

Previous
From: Jeff Davis
Date:
Subject: Re: add, subtract bool type
Next
From: Miroslav Koncar
Date:
Subject: Re: problems transfering databases