| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: improve description of allowed spellings for Boolean input. |
| Date: | 2019-06-13 02:55:24 |
| Message-ID: | E1hbFtc-00041k-Tk@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Doc: improve description of allowed spellings for Boolean input.
datatype.sgml failed to explain that boolin() accepts any unique
prefix of the basic input strings. Indeed it was actively misleading
because it called out a few minimal prefixes without mentioning that
there were more valid inputs.
I also felt that it wasn't doing anybody any favors by conflating
SQL key words, valid Boolean input, and string literals containing
valid Boolean input. Rewrite in hopes of reducing the confusion.
Per bug #15836 from Yuming Wang, as diagnosed by David Johnston.
Back-patch to supported branches.
Discussion: https://postgr.es/m/15836-656fab055735f511@postgresql.org
Branch
------
REL9_4_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/df88137a398b5a45a95bca14c334b6b708c8018e
Modified Files
--------------
doc/src/sgml/datatype.sgml | 66 ++++++++++++++++++++++++++++++----------------
1 file changed, 43 insertions(+), 23 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-06-13 03:05:44 | pgsql: Doc: fix bogus example. |
| Previous Message | Bruce Momjian | 2019-06-13 02:48:08 | pgsql: docs: PG 12 relnotes, update btree items |