Re: boolean and bool in documentation - Mailing list pgsql-hackers

From Robert Haas
Subject Re: boolean and bool in documentation
Date
Msg-id CA+TgmoZ9G+YDKN7+kNFiYP_MLw1=32xudc8FLFdA1fMGwzzyrA@mail.gmail.com
Whole thread Raw
In response to Re: boolean and bool in documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: boolean and bool in documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Feb 21, 2019 at 7:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> FWIW, I'm not excited about this.  We accept "bool" and "boolean"
> interchangeably, and it does not seem like an improvement for the
> docs to use only one form.  By that argument, somebody should go
> through the docs and nuke every usage of "::" in favor of
> SQL-standard CAST(...) notation, every usage of "float8"
> in favor of DOUBLE PRECISION, every usage of "timestamptz" in
> favor of the long form, etc etc.

I'm not terribly excited about it either, but mostly because it seems
like a lot of churn for a minimal gain, and it'll be consistent for
about 6 months before somebody re-introduces a conflicting usage.  I
do not, on the other hand, believe that there's no point in being
consistent about anything unless we're consistent about everything;
that's a straw man.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Problems with plan estimates in postgres_fdw
Next
From: Alvaro Herrera
Date:
Subject: Re: partitioned tables referenced by FKs