From: Michael Meskes <meskes@postgresql.org>
To: pgsql-interfaces@postgresql.org
Subject: Re: FOR UPDATE is not allowed in this context
Date: Wed, 21 Feb 2001 14:02:21 +0100
Message-ID: <20010221140221.A28917@feivel.credativ.de> (raw)
In-Reply-To: <8766.982717138@sss.pgh.pa.us>
References: <F76sa7qEqlehFvHkQFY00003779@hotmail.com>
<8766.982717138@sss.pgh.pa.us>
On Tue, Feb 20, 2001 at 07:58:58PM -0500, Tom Lane wrote:
> This seems to me to be a bug in ecpg: the variable ForUpdateNotAllowed
> doesn't get reset between statements. If you experiment more you'll
It should have been resetted at the beginning of a statement. But then it
does not exist anymore in the actual release.
> exist anymore ... but I think there are related bugs associated with
> some other ad-hoc flags in the ecpg parser, none of which get reset at
> what I would consider a reasonable place to reset them ...
Which one do you think of? I agree that some of this stuff is just a hack I
needed to get that check into the parser. But so far I have yet to see a bug
reported on these. Except for the one we are talking about of course.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
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: meskes@postgresql.org
Subject: Re: FOR UPDATE is not allowed in this context
In-Reply-To: <20010221140221.A28917@feivel.credativ.de>
* 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