"David G. Johnston" writes:
> On Tue, May 24, 2022 at 7:42 AM Tom Lane wrote:
>> Perhaps we could improve matters like this?
>> -specified, the underlying data type's default collation is used.
>> +specified, the domain has the same collation behavior as its
>> +underlyin
On Tue, May 24, 2022 at 7:42 AM Tom Lane wrote:
> I wrote:
> > Perhaps this should be documented more clearly, but it's not obviously
> > wrong. If the domain declaration doesn't include an explicit COLLATE
> > then casting to the domain doesn't create an explicit collation
> > requirement. (Th
On Wednesday, May 25, 2022, jian he wrote:
>
> I personally feel wording *non-default* may not be that correct. Because
> if the column is text then it automatically at least has default collation.
>
Non-default means “a value that is not the default value”.
David J.
postgresql 15 manual parts:
Otherwise, all input expressions must have the same implicit collation
> derivation or the default collation. If any non-default collation is
> present, that is the result of the collation combination. Otherwise, the
> result is the default collation.
>
For example, co
Please don’t top-post.
On Tuesday, May 24, 2022, jian he wrote:
>
> Otherwise, all input expressions must have the same implicit collation
>> derivation or the default collation. If any non-default collation is
>> present, that is the result of the collation combination. Otherwise, the
>> result
Otherwise, all input expressions must have the same implicit collation
> derivation or the default collation. If any non-default collation is
> present, that is the result of the collation combination. Otherwise, the
> result is the default collation.
>
I think the above quote part can be used to
I wrote:
> Perhaps this should be documented more clearly, but it's not obviously
> wrong. If the domain declaration doesn't include an explicit COLLATE
> then casting to the domain doesn't create an explicit collation
> requirement. (That is, the domain *doesn't* have a specific
> collation atta
"David G. Johnston" writes:
> On Monday, May 23, 2022, jian he wrote:
>> CREATE DOMAIN testdomain AS text;
>> --asume the default collation is as per show LC_COLLATE;
>> – on my pc, it is C.UTF-8.
>> --So the testdomain will be collation "C.UTF-8"
> My reading of the docs say this is consistent
On Monday, May 23, 2022, jian he wrote:
> CREATE DOMAIN testdomain AS text;
>
> --asume the default collation is as per show LC_COLLATE;
>
> – on my pc, it is C.UTF-8.
>
> --So the testdomain will be collation "C.UTF-8"
>
>
> => \d collate_test1
>
> Table "test.collate_t
CREATE DOMAIN testdomain AS text;
--asume the default collation is as per show LC_COLLATE;
– on my pc, it is C.UTF-8.
--So the testdomain will be collation "C.UTF-8"
=> \d collate_test1
Table "test.collate_test1"
Column | Type | Collation | Nullable | Default
--
10 matches
Mail list logo
