From: Christopher Browne <cbbrowne@ca.afilias.info>
To: pgsql-interfaces@postgresql.org
Subject: Re: Lost updates vs resumable connections/transactions
Date: Wed, 15 Dec 2004 16:22:49 -0500
Message-ID: <60ekhrdzo6.fsf@dba2.int.libertyrms.com> (raw)
References: <Pine.A41.4.58.0412091641060.68588@zivunix.uni-muenster.de>
<41C06961.8020406@Yahoo.com>
<87is73qrde.fsf@stark.xeocode.com>
gsstark@mit.edu (Greg Stark) writes:
> Jan Wieck <JanWieck@Yahoo.com> writes:
>> Even applications that have statefull enduser terminals (like SAP R/3 for
>> example) never allow an open transaction over user interaction.
>
> I'm not sure using SAP as your paragon of design excellence is a
> wise choice here. From what I understand SAP implemented its own
> locking system because the database it was based on didn't offer any
> locking at all.
I don't think "design excellence" is the point; I'd point at Sabre/STS
as another example of "never an open transaction").
You (as a travel agent, out at the "client level") don't get to open
up user level transactions to the airline reservation system.
Instead, you fill a 3270 screen or some part thereof with data, and
then submit an "update."
As a result, each request is a fully-formed transaction, if a small
one.
> But your basic point is sound. For a web site I would definitely
> avoid using anything like database locks and even avoid doing
> anything with application locks if possible.
> If you really really want to expose the database session state I
> think he's on the right track using SQLRelay. This would let him
> handle reconnecting a user with her session even if she's connecting
> to a different Apache process.
We've got some web apps where it would be kind of nice to keep a
cursor around for a little while.
But there have been plenty of times when I have had to rue the fact of
transactions being held open for a long time by one thing or
another...
--
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/;
Christopher Browne
(416) 673-4124 (land)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: cbbrowne@ca.afilias.info
Subject: Re: Lost updates vs resumable connections/transactions
In-Reply-To: <60ekhrdzo6.fsf@dba2.int.libertyrms.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox