Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
Date
Msg-id CAGECzQRZ07N7fZ6OYua28RQ2-BzZYDdpU7gbBWtsy4By_vykQw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
One more usability thing. I think \parse and \close should not require
a \g to send the message. You can do that by returning PSQL_CMD_SEND
instead of PSQL_CMD_SKIP_LIN.
I feel like the main point of requiring \g for \bind and \bindx is so
you can also use \gset or \gexec. But since \parse and \close don't
return any rows that argument does not apply to them.

And regarding the docs. I think the examples for \bindx and \close
should use \parse instead of PREPARE. ISTM that people will likely
want to use the extended query protocol for preparing and executing,
not a mix of them. I know that it's possible to do that, but I think
the examples should cover the most common use case.



pgsql-hackers by date:

Previous
From: Mats Kindahl
Date:
Subject: Re: Add test module for Table Access Method
Next
From: Maiquel Grassi
Date:
Subject: New Window Function: ROW_NUMBER_DESC() OVER() ?