| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON_TABLE output collations |
| Date: | 2022-06-07 14:51:35 |
| Message-ID: | 80775d2e-24b5-378b-7f4b-664e34efc85d@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-06-07 Tu 09:19, Peter Eisentraut wrote:
>
> The present implementation of JSON_TABLE sets the collation of the
> output columns to the default collation if the specified data type is
> collatable. Why don't we use the collation of the type directly?
> This would make domains with attached collations work correctly.
>
> See attached patch for how to change this. I hacked up a regression
> test case to demonstrate this.
Looks reasonable.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2022-06-07 14:52:38 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | vignesh ravichandran | 2022-06-07 14:41:11 | Re: pg_rewind: warn when checkpoint hasn't happened after promotion |