On Sat, Apr 13, 2019 at 1:12 AM Alvaro Herrera wrote:
> I'm inclined to reject this patch.
On Fri, Jul 5, 2019 at 6:47 PM Peter Eisentraut
wrote:
> But you're not really supposed to use it for multiple queries or
> multiple result sets anyway. There are other functions for this.
>
> If a source
On 2019-04-12 17:51, Fabien COELHO wrote:
> Hmmm. I obviously agree that PQexec is beyond awkward.
>
> Now I'm not sure how anyone is expected to guess the actual function
> working from the available documentation, and without this knowledge I
> cannot see how to write meaningful code for the m
Hello Alvaro,
I'm looking at psql's use of PQexec for implementing some feature.
When running with multiple SQL commands, the doc is not very helpful.
From the source code I gathered that PQexec returns the first COPY results
if any, and if not the last non-empty results, unless all is empty
On 2019-Apr-12, Fabien COELHO wrote:
> I'm looking at psql's use of PQexec for implementing some feature.
>
> When running with multiple SQL commands, the doc is not very helpful.
>
> From the source code I gathered that PQexec returns the first COPY results
> if any, and if not the last non-emp
Hello devs,
I'm looking at psql's use of PQexec for implementing some feature.
When running with multiple SQL commands, the doc is not very helpful.
From the source code I gathered that PQexec returns the first COPY results
if any, and if not the last non-empty results, unless all is empty in
