> adrian.kla...@aklaver.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> It seems that there must be different underlying mechanisms at work and that
>> this explains why creating a cursor using SQL to execute a prepared
>> statement fails but doing this using PL/pgSQL succeeds. What's going on
On 4/16/23 11:02, Bryn Llewellyn wrote:> statement fails but doing this
using PL/pgSQL succeeds.
What's going on under the covers?
Pretty sure:
https://www.postgresql.org/docs/current/spi.html
--
Adrian Klaver
adrian.kla...@aklaver.com
> b...@yugabyte.com wrote:
>
>> david.g.johns...@gmail.com wrote:
>>
>>> b...@yugabyte.com wrote:
>>>
>>> I found this email from Peter Eisentraut:
>>> https://www.postgresql.org/message-id/762cc764-74f0-13fb-77ed-16f91c90f40d%402ndquadrant.com
>>>
>>> It caused the 42601 error, « syntax error
> david.g.johns...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> I found this email from Peter Eisentraut:
>> https://www.postgresql.org/message-id/762cc764-74f0-13fb-77ed-16f91c90f40d%402ndquadrant.com
>>
>> It caused the 42601 error, « syntax error at or near “execute” ». So it
>> look
On Sat, Apr 15, 2023 at 2:15 PM Bryn Llewellyn wrote:
> I found this email from Peter Eisentraut:
>
> https://www.postgresql.org/message-id/762cc764-74f0-13fb-77ed-16f91c90f40d%402ndquadrant.com
>
> It caused the 42601 error, « syntax error at or near “execute” ». So it
> looks like Peter’s patch
I found this email from Peter Eisentraut:
https://www.postgresql.org/message-id/762cc764-74f0-13fb-77ed-16f91c90f40d%402ndquadrant.com
> I have developed a patch that allows declaring cursors over prepared
> statements... This is an SQL standard feature. ECPG already supports it (with
> differen
