Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
От | Peter Eisentraut |
---|---|
Тема | Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx |
Дата | |
Msg-id | 3e694442-0df5-4f92-a08f-c5d4c4346b85@eisentraut.org обсуждение исходный текст |
Ответ на | Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
|
Список | pgsql-hackers |
On 24.07.24 07:04, Michael Paquier wrote: > This commit introduces three additional commands: \parse, \bindx and > \close. > \parse creates a prepared statement using extended protocol. > \bindx binds and execute an existing prepared statement using extended > protocol. > \close closes an existing prepared statement using extended protocol. I'm wondering now if \close is a good name of this command. I hadn't seen any discussion around the name choice in this thread. On the SQL level, the CLOSE command operates on cursors. I think it would be useful to keep SQL and psql aligned (e.g., COPY, \copy). On the protocol level, the "Close" message operates on both cursors and statements, but those are actually two different message (sub-)types. And this is not something users ever see, so the connection would not be obvious. Maybe this should be called something more specific like \close_stmt.
В списке pgsql-hackers по дате отправления: