From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gerhard Haering <haering_postgresql@gmx.de>
Cc: pgsql-general@postgresql.org
Subject: Re: PerformPortalClose warning in 7.3
Date: Sun, 22 Dec 2002 21:36:27 -0500
Message-ID: <28406.1040610987@sss.pgh.pa.us> (raw)
In-Reply-To: <slrnb0cp0i.aji.haering_postgresql@lilith.my-fqdn.de>
References: <3DF91030.A372DF7C@nsd.ca>
<2C6CDB6A-0E24-11D7-8E88-000393A48A3C@mac.com>
<slrnb0cp0i.aji.haering_postgresql@lilith.my-fqdn.de>
Gerhard Haering <haering_postgresql@gmx.de> writes:
> To show this, we use the undocumented, but very handy toggleShowQuery
> flag. The effect is that we can see what SQL pyPgSQL sends to the
> backend using libpq (the lines staring with QUERY: below):
> QUERY: DECLARE "PgSQL_0811F1EC" CURSOR FOR select * from test
> ...
> QUERY: CLOSE PgSQL_0811F1EC
This looks like a pyPgSQL bug to me. If it's going to use a mixed-case
name for the cursor then it must either always double-quote the name or
never do so. Failing to double-quote in the CLOSE command is wrong.
regards, tom lane
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: tgl@sss.pgh.pa.us, haering_postgresql@gmx.de, pgsql-general@postgresql.org
Subject: Re: PerformPortalClose warning in 7.3
In-Reply-To: <28406.1040610987@sss.pgh.pa.us>
* 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