Re: Row Lock

From: Dave Tenny <jeffrey(dot)tenny(at)comcast(dot)net>
To: Waldomiro <wmiro(at)ig(dot)com(dot)br>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Row Lock
Date: 2003-10-03 13:34:28
Message-ID: 3F7D7AE4.7090708@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

-- begin transaction
SELECT rowstuff FROM table WHERE record-of-interest = somekey FOR UPDATE
... get new value from the user
UPDATE rowstuff WHERE record-of-interest = somekey
COMMIT

-----------------------

However, it is considered exceedly poor application design to have any
interactive
dialogs in the midst of a transaction. (Really bad, don't do it!
You'll block potentially all users
for potentially unlimited amounts of time).

Suggest you get the row value, remember it, present to the user for
update OUTSIDE a transaction,
then start a transaction to update when you have the new value. If the
row value has changed to something incompatible
with the user's value, abort and complain, otherwise do the update.

Waldomiro wrote:

> Hello,
>
> I have an aplication which ask a code to bring up the data on screen,
> then the user can change the data and save it.
>
> My problem is :
>
> 2 users at same time can put the same code and make diferent changes.
>
> Are there any way to lock this record in postgres when the first user
> is changing the data on screen ?
>
> What shoud I do ?
>
> Thanks
>
> Waldomiro C Neto.
> Shx Informática Ltda.
> +55 (11) 5581-1551
> www.shx.com.br <http://www.shx.com.br>
> wmiro(at)shx(dot)com(dot)br <mailto:wmiro(at)shx(dot)com(dot)br>
>

In response to

  • Row Lock at 2003-10-03 13:29:06 from Waldomiro

Responses

  • Re: Row Lock at 2003-10-07 09:04:41 from Alessandro Polverini

Browse pgsql-jdbc by date

  From Date Subject
Next Message Craig Moon 2003-10-03 14:20:41 Re: Concurrent Connections - User only allowed one
Previous Message Waldomiro 2003-10-03 13:29:06 Row Lock