Re: Add Boolean node

Sascha Kuhl <yogidabanli@gmail.com>

From: Sascha Kuhl <yogidabanli@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-12-27T10:08:42Z
Lists: pgsql-hackers
Can that boolean node be cultural dependent validation for the value? By
the developer? By all?

Pavel Stehule <pavel.stehule@gmail.com> schrieb am Mo., 27. Dez. 2021,
10:09:

>
>
> po 27. 12. 2021 v 10:02 odesílatel Peter Eisentraut <
> peter.eisentraut@enterprisedb.com> napsal:
>
>>
>> This patch adds a new node type Boolean, to go alongside the "value"
>> nodes Integer, Float, String, etc.  This seems appropriate given that
>> Boolean values are a fundamental part of the system and are used a lot.
>>
>> Before, SQL-level Boolean constants were represented by a string with
>> a cast, and internal Boolean values in DDL commands were usually
>> represented by Integer nodes.  This takes the place of both of these
>> uses, making the intent clearer and having some amount of type safety.
>
>
> +1
>
> Regards
>
> Pavel
>
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add Boolean node

  2. Rename value node fields

  3. Refactor AlterRole()