Re: Conventions

2022-02-02 Thread Bruce Momjian
On Wed, Jan 26, 2022 at 09:51:53PM -0500, Bruce Momjian wrote: > > I'd suggest a separate para at some point before the first usage, > > along the lines of > > > >In this section, we follow the usual Tcl convention of using question > >marks, rather than brackets, to indicate an optional e

Re: Conventions

2022-01-26 Thread Bruce Momjian
On Wed, Jan 26, 2022 at 09:33:58PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > OK, updated patch attached. I don't think we even show TCL syntax > > anywhere anymore, so I removed that text, rather than moving it. > > I really don't care for this phrasing at all: > > - the body of a

Re: Conventions

2022-01-26 Thread Tom Lane
Bruce Momjian writes: > OK, updated patch attached. I don't think we even show TCL syntax > anywhere anymore, so I removed that text, rather than moving it. I really don't care for this phrasing at all: - the body of a PL/Tcl function: + the body of a PL/Tcl function (brackets ([ and +

Re: Conventions

2022-01-26 Thread Bruce Momjian
On Wed, Jan 26, 2022 at 02:01:40PM -0300, Álvaro Herrera wrote: > On 2022-Jan-26, Bruce Momjian wrote: > > > On Tue, Jan 25, 2022 at 06:45:47PM -0800, Dave Stewart wrote: > > > I'm good with it.  Thank you! > > > > OK, updated patch attached. I don't think we even show TCL syntax > > anywhere an

Re: Conventions

2022-01-26 Thread Alvaro Herrera
On 2022-Jan-26, Bruce Momjian wrote: > On Tue, Jan 25, 2022 at 06:45:47PM -0800, Dave Stewart wrote: > > I'm good with it.  Thank you! > > OK, updated patch attached. I don't think we even show TCL syntax > anywhere anymore, so I removed that text, rather than moving it. We do here: https://www

Re: Conventions

2022-01-26 Thread Tom Lane
Bruce Momjian writes: > OK, updated patch attached. I don't think we even show TCL syntax > anywhere anymore, so I removed that text, rather than moving it. WFM. regards, tom lane

Re: Conventions

2022-01-26 Thread Bruce Momjian
On Tue, Jan 25, 2022 at 06:45:47PM -0800, Dave Stewart wrote: > I'm good with it.  Thank you! OK, updated patch attached. I don't think we even show TCL syntax anywhere anymore, so I removed that text, rather than moving it. -- Bruce Momjian https://momjian.us EDB

Re: Conventions

2022-01-25 Thread Dave Stewart
I'm good with it. Thank you! On Tue, Jan 25, 2022 at 6:15 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Tuesday, January 25, 2022, Tom Lane wrote: > >> Bruce Momjian writes: >> > How is this patch? >> >> I'd still drop the Tcl bit, or if you must have it, move it to >> pltcl.s

Re: Conventions

2022-01-25 Thread David G. Johnston
On Tuesday, January 25, 2022, Tom Lane wrote: > Bruce Momjian writes: > > How is this patch? > > I'd still drop the Tcl bit, or if you must have it, move it to > pltcl.sgml. Otherwise OK by me. > > > Agreed. David J.

Re: Conventions

2022-01-25 Thread Tom Lane
Bruce Momjian writes: > How is this patch? I'd still drop the Tcl bit, or if you must have it, move it to pltcl.sgml. Otherwise OK by me. regards, tom lane

Re: Conventions

2022-01-25 Thread Bruce Momjian
On Tue, Jan 25, 2022 at 07:15:45PM -0500, Tom Lane wrote: > "David G. Johnston" writes: > > There is an implied "anything else not noted here should be taken as > > literal token to type, or a variable, as context dictates" [1] - and since > > () isn't mentioned... > > I'd probably rather make tha

Re: Conventions

2022-01-25 Thread Tom Lane
"David G. Johnston" writes: > There is an implied "anything else not noted here should be taken as > literal token to type, or a variable, as context dictates" [1] - and since > () isn't mentioned... > I'd probably rather make that implied part explicit and avoid mentioning > parentheses explicitl

Re: Conventions

2022-01-25 Thread Dave Stewart
Thanks, all, for considering this update. I like the "anything not noted here..." phrase better than "parentheses should be interpreted literally." That's a little vague to me. And *bold_italic* for variables was somehow obvious to me, but I agree with [1] that it could also be made explicit, to

Re: Conventions

2022-01-25 Thread David G. Johnston
On Tue, Jan 25, 2022 at 1:24 PM Bruce Momjian wrote: > On Tue, Jan 25, 2022 at 03:31:03AM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/12/notation.html > > Description: > > > > In section 3

Re: Conventions

2022-01-25 Thread Bruce Momjian
On Tue, Jan 25, 2022 at 03:31:03AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/notation.html > Description: > > In section 3, Conventions, it would be helpful to point out that > parentheses,

Re: conventions

2021-07-07 Thread Euler Taveira
On Wed, Jul 7, 2021, at 1:30 PM, rir wrote: > > The conventions page is weak. Here is a proposed start for > change. Seeing SQL as an early language, I have tried to use something > like plain English. Here "early" could describe a mail merge user > wandering into programming SQL after seeing s