Joost,
Everyone has to do a select for update, then they will be serialized.
Dave
On 3-Jul-06, at 6:45 AM, Joost Kraaijeveld wrote:
Hi,
I have a table with events that must be handled by multiple
clients. It
does not matter which client handles an event, but no two clients may
handle the same event and an event may only handled once. A client
can
only determine the availability of an event by querying the database.
The access to the table should be queue-like with synchronization.
My idea was that a client should do a "SELECT" on the table and
mark the
selected records as "being handled" to avoid double handling.
I have read the manual about "LOCK", "SET TRANSACTION" and
"SELECT...FOR
UPDATE", but from what I understand, they cannot prevent a "SELECT"
from
another client, based on the "SELECT".
Is there a way to make this possible?
TIA
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl
---------------------------(end of
broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
