| From: | Ilmar Y <tanswis42(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Subject: | Re: Ambiguity in IS JSON description and logic |
| Date: | 2025-11-18 11:56:50 |
| Message-ID: | 176346701044.1015.11502436206879063762.pgcf@coridan.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
I’ve sent a docs patch to pgsql-docs in the
“Ambiguity in IS JSON description and logic” thread.
The patch clarifies that the WITH/WITHOUT UNIQUE KEYS clause for IS JSON
controls an additional test for duplicate object keys, that WITH UNIQUE KEYS
enforces this constraint recursively, and that WITHOUT UNIQUE KEYS (the default)
disables this additional test rather than requiring duplicates to be present.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-11-18 16:37:21 | Re: Ambiguity in IS JSON description and logic |
| Previous Message | r314tive | 2025-11-18 11:55:00 | Re: Ambiguity in IS JSON description and logic |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Geier | 2025-11-18 12:07:38 | Re: Performance issues with parallelism and LIMIT |
| Previous Message | r314tive | 2025-11-18 11:55:00 | Re: Ambiguity in IS JSON description and logic |