Re: Add Boolean node

You think, all values are valid. Is a higher german order valid for Turkey,
that only know baskets, as a Form of order. For me not all forms of all are
valid for all. You cannot Export or Import food that You dislike, because
it would hurt you. Do you have dishes that you dislike? Is all valid for
you and your culture.

It is ok that this is an internal feature, that is not cultural dependent.
Iwanted to give you my Interpretation of this Feature. It is ok It doesn't
fit 😉

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> schrieb am Mo., 27. Dez. 2021,
11:15:

>
>
> 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
>>>
>>>