Re: cast to domain with default collation issue.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: jian he <jian.universality@gmail.com>,
"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Date: 2022-06-14T21:48:16Z
Lists: pgsql-general
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Tue, May 24, 2022 at 7:42 AM Tom Lane <tgl@sss.pgh.pa.us> 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 >> + underlying data type. > +1 Pushed then, thanks for thinking about it. regards, tom lane
Commits
-
Doc: clarify the default collation behavior of domains.
- e0047269a8c9 10.22 landed
- d6d9ea0a468b 13.8 landed
- d26ac35d0d7c 15.0 landed
- cc5de7ba255d 12.12 landed
- be35a6456901 14.5 landed
- a8c63282ddce 11.17 landed