| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gerhard Haering <haering_postgresql(at)gmx(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PerformPortalClose warning in 7.3 |
| Date: | 2002-12-23 02:36:27 |
| Message-ID: | 28406.1040610987@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces pgsql-performance |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-23 02:39:20 | Re: Vectors in Pl/PgSQL |
| Previous Message | Tom Lane | 2002-12-23 02:26:33 | Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilya Kiselyov | 2002-12-23 10:39:22 | where's libpq++ library in 7.3? |
| Previous Message | Gerhard Haering | 2002-12-23 01:18:46 | Re: PerformPortalClose warning in 7.3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Silverman | 2002-12-23 21:55:01 | Re: Speed Question |
| Previous Message | Gerhard Haering | 2002-12-23 01:18:46 | Re: PerformPortalClose warning in 7.3 |