From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: prepared statement "cu1" already exists (but it does not) |
Date: | 2024-04-09 16:36:50 |
Message-ID: | 3751333.1712680610@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> writes:
>>> Is it an issue if I use the same name for a prepared statement and the server cursor? I mean:
>> From memory, I think those share the same "portal" namespace.
> Can you please elaborate?
> Is it supported to do:
> PQprepare(pgConn, "cu1", "declare cu1 cursor for ... ", ... )
> PQexecPrepared(pgConn, "cu1", ... )
> ?
> So far this has always worked.
Ah, sorry, what I should have said is that the SQL PREPARE command
works with the same namespace as PQprepare (which is a thin wrapper
over the wire-protocol Parse command). There is a different namespace
for cursors. Cursors do share that namespace with the wire-protocol
"portal" concept, but libpq doesn't directly expose portals.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thiemo Kellner | 2024-04-09 16:48:44 | Re: [Code: 0, SQL State: 0A000] when "typing" from pg_catalog |
Previous Message | yudhi s | 2024-04-09 16:36:30 | Re: Moving delta data faster |