| From: | "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org, Gerhard Haering <haering_postgresql(at)gmx(dot)de> |
| Subject: | Re: PerformPortalClose warning in 7.3 |
| Date: | 2002-12-23 06:05:25 |
| Message-ID: | 200212230605.gBN65PA17887@bajor.mug.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane writes:
> Gerhard Haering <haering_postgresql(at)gmx(dot)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.
Yes, it's a pyPgSQL bug. The code has been updated on SourceForge and is
available from the pyPgSQL project's CVS repository.
I am also attaching the patch
Later.
| Attachment | Content-Type | Size |
|---|---|---|
| patch.20021223 | text/plain | 485 bytes |
| unknown_filename | text/plain | 199 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2002-12-23 09:38:11 | Re: Getting 2002-12-18T17:32:40-05:00 (ISO 8601) from to_date() |
| Previous Message | Billy G. Allie | 2002-12-23 06:00:28 | Re: {GENERAL] |