Skip site navigation (1) Skip section navigation (2)

Re: idiom for interactive client applications.

From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
To: syan tan <kittylitter(at)people(dot)net(dot)au>, pgsql-novice(at)postgresql(dot)org
Subject: Re: idiom for interactive client applications.
Date: 2007-10-13 03:49:00
Message-ID: 250828.31397.qm@web31801.mail.mud.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-novice
--- syan tan <kittylitter(at)people(dot)net(dot)au> wrote:
> What other ways are there of doing such an app?

The two ways that I know of are:

BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE;

--if the tuple was modified by another transaction, this transaction will fail on commit.

SELECT FOR UPDATE... -- pre-lock the tuple of interest from other commits.

Regards,
Richard Broersma Jr.

In response to

pgsql-novice by date

Next:From: Syan TanDate: 2007-10-13 04:28:13
Subject: Re: idiom for interactive client applications.
Previous:From: syan tanDate: 2007-10-13 02:14:21
Subject: idiom for interactive client applications.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group