Re: cursors with prepared statements - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: cursors with prepared statements
Date
Msg-id CAA4eK1Lr4fdo6JqHJ=VFHCMDEQTZenXUN8N4ax6GPWHR=TauBw@mail.gmail.com
Whole thread Raw
In response to Re: cursors with prepared statements  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Mon, Jun 11, 2018 at 9:56 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 6/11/18 09:57, Amit Kapila wrote:
>> Sounds like a reasonable approach.  Have you not considered using a
>> special OPEN syntax because there are some other forms of problems
>> with it?
>
> There is no OPEN command in direct SQL.  Do you mean whether I have
> considered introducing an OPEN command?
>

Yes.

>  Yes, but it seems to me that
> that would create weird inconsistencies and doesn't seem very useful in
> practice.
>

Okay, if that doesn't make the job easy, then there is not much use in
pursuing that direction.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: assert in nested SQL procedure call in current HEAD
Next
From: Tom Lane
Date:
Subject: Re: late binding of shared libs for C functions