Re: please define 'statement' in the glossary
От | David G. Johnston |
---|---|
Тема | Re: please define 'statement' in the glossary |
Дата | |
Msg-id | CAKFQuwYqj=_=5atc1bL0N_bPsgALzh--jH3kM6MbC2ON49P7AA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: please define 'statement' in the glossary (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-docs |
On Monday, July 14, 2025, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> If we accept that we use the words statement and command interchangeably
> then the sole remaining use of command here sticks out because now we have
> to explain why commands are different from statements. I'd rather just
> remove the parenthetical. It's poorly clarifying a point that it seems you
> don't want to clarify more fully here.
[ shrug... ] I'm inclined to go back to the "command message" wording
then. I don't find "client-issued statement" to be helpful at all;
in particular, it's flat wrong for the multi-statement-query-message
case, because surely all those statements are client-issued. I'm okay
with this text leaving out nitpicky details, but it should leave the
reader with a mental model that more or less matches reality.
Then let’s use command message. It basically the moral equivalent to my (technically, query) parenthetical.
David J.
В списке pgsql-docs по дате отправления: