| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unexpected psql "feature" |
| Date: | 2016-07-13 21:57:33 |
| Message-ID: | CAKFQuwaADV-WyLtpB455J_MZ6bT8A6Ld6SU1Zya+Zajejm1JtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 13, 2016 at 5:44 PM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
> Hello Tom,
>
> Although "\;" behavior is not documented, I would have expected both
>>> results to be shown one after the other, or having a an error, but not a
>>> quiet discard.
>>>
>>
>> See the documentation for PQexec(): all but the last query result is
>> discarded.
>>
>
> Sure. That is developer-level answer to "why", although it does not really
> say why the developer chose PQexex over PQsendQuery. At the user-level the
> behavior is still pretty surprising.
Lets try putting it this way...
As a psql user I want some way to choose whether I send my query via
"PQexec" or "PQsendQuery". I'm not sure why the "PQexec" access point is
undocumented but this "\;" syntax, vis-a-vis ";" provides me that choice.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-13 22:37:41 | Upcoming PG release schedule |
| Previous Message | David G. Johnston | 2016-07-13 21:53:48 | Re: unexpected psql "feature" |