From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Sascha Kuhl <yogidabanli(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add Boolean node |
Date: | 2021-12-27 10:15:00 |
Message-ID: | CAFj8pRDSPoGuYKo5tHkaqBfJTRrc5fz9SZ+JW3=Ux1-Tgu0h3A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
po 27. 12. 2021 v 11:08 odesílatel Sascha Kuhl <yogidabanli(at)gmail(dot)com>
napsal:
> Can that boolean node be cultural dependent validation for the value? By
> the developer? By all?
>
why?
The boolean node is not a boolean type.
This is an internal feature. There should not be any cultural dependency
Regards
Pavel
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> schrieb am Mo., 27. Dez. 2021,
> 10:09:
>
>>
>>
>> po 27. 12. 2021 v 10:02 odesílatel Peter Eisentraut <
>> peter(dot)eisentraut(at)enterprisedb(dot)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
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-12-27 10:18:45 | Re: Add Boolean node |
Previous Message | Sascha Kuhl | 2021-12-27 10:08:42 | Re: Add Boolean node |