pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: listeria@disroot.org
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Section 4.1.2.3 repeats information presented in section 4.1.1
Date: Tue, 12 Dec 2023 11:25:26 -0500
Message-ID: <2445458.1702398326@sss.pgh.pa.us> (raw)
In-Reply-To: <170232539471.398198.13861151281926916858@wrigleys.postgresql.org>
References: <170232539471.398198.13861151281926916858@wrigleys.postgresql.org>

PG Doc comments form <noreply@postgresql.org> writes:
> The following documentation comment has been logged on the website:
> Page: https://www.postgresql.org/docs/16/sql-syntax-lexical.html
> Description:

> it just threw me off to read the exact same thing twice in quick succession,
> I'd suggest linking to section 4.1.2.3 in section 4.1.1 instead.

They are *not* the same.  The quoting is different and the
meaning is quite different, just as "slon" and 'slon' are
not equivalent in SQL.  Moreover, there's little reason to
assume that somebody coming to 4.1.2.3 necessarily just
read 4.1.1.

Perhaps it'd be better to use different example strings though?

			regards, tom lane





view thread (2+ messages)

Message-ID: <2445458.1702398326@sss.pgh.pa.us>
Permalink:  ../2445458.1702398326@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2445458.1702398326@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, listeria@disroot.org, pgsql-docs@lists.postgresql.org
  Subject: Re: Section 4.1.2.3 repeats information presented in section 4.1.1
  In-Reply-To: <2445458.1702398326@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox