Re: pgsql: Properly lowercase identifiers, uppercase keywords, in doc - Mailing list pgsql-committers

From Thom Brown
Subject Re: pgsql: Properly lowercase identifiers, uppercase keywords, in doc
Date
Msg-id AANLkTikkA1qOpWarSXuUfHgCCnbyQKmj=X23sYWv9Ur9@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Properly lowercase identifiers, uppercase keywords, in doc  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 11 August 2010 23:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> momjian@postgresql.org (Bruce Momjian) writes:
>> Log Message:
>> -----------
>> Properly lowercase identifiers, uppercase keywords, in doc examples
>
> Bruce, did you do that with a blind sed script?  You totally destroyed
> the point of these examples.  Kindly revert.
>

Whilst that change definitely needs reverting, I noticed the following
doesn't read well:

"Additionally, comments can occur in SQL input. They are not tokens,
they are effectively equivalent to whitespace.

For example, the following is (syntactically) valid SQL input:"

You'd expect an example with comments in after reading that, but there isn't.

Maybe that "Additionally..." bit should be moved beneath the "This is
a sequence..." paragraph?

--
Thom Brown
Registered Linux user: #516935

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Properly lowercase identifiers, uppercase keywords, in doc
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Extend psql's \e and \ef commands so that a line number can be