From: | Raoul Callaghan <ausit(at)bigpond(dot)net(dot)au> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | "select for update" question.... |
Date: | 2001-05-20 19:31:04 |
Message-ID: | B72E57DF.2AD7%ausit@bigpond.net.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
As I understand it:
Issuing a ³select for update² within a transaction will prevent other users
from modifying data. (exclusive lock)
I¹m contemplating using the DBI interface as a permanent client to postgres
for a group of users, and have a few questions.
Will the above procedure still exclusively lock the row, when using a
browser to issue a ³select for update²?
I¹m confused about sth->finish; and will it finish the transaction, before
the user re-submits the form data to update the row....
Can anyone help me or offer some ³howtos² to read regarding postgres and
DBI?
thanks.
Raoul.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew McMillan | 2001-05-20 19:46:36 | Re: Re: External search engine, advice |
Previous Message | Stephan Szabo | 2001-05-20 18:55:02 | Re: Functions returning sets |