Robert Haas writes:
> On Thu, Feb 21, 2019 at 7:31 PM Tom Lane 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 a
On Thu, Feb 21, 2019 at 7:31 PM Tom Lane 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 "::"
Bruce Momjian writes:
> On Tue, Feb 19, 2019 at 12:56:19AM +0900, Masahiko Sawada wrote:
>> AFAICS there seems not to be explicit rules and policies for usage of
>> 'boolean' and 'bool'. We use 'bool' for colum data type of almost
>> system catalogs but use 'boolean' for some catalogs (pg_pltempla
On Tue, Feb 19, 2019 at 12:56:19AM +0900, Masahiko Sawada wrote:
> AFAICS there seems not to be explicit rules and policies for usage of
> 'boolean' and 'bool'. We use 'bool' for colum data type of almost
> system catalogs but use 'boolean' for some catalogs (pg_pltemplate and
> pg_policy). The sam
HI,
I realized that 'boolean' and 'bool' are mixed as SQL data type in the
documentation. Here is the quick check result;
$ git grep -c "bool" doc
doc/src/sgml/bki.sgml:1
doc/src/sgml/btree-gin.sgml:1
doc/src/sgml/catalogs.sgml:88
doc/src/sgml/datatype.sgml:1
doc/src/sgml/ecpg.sgml:2
doc/src/sgml
