| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Wyatt Alt <wyatt(dot)alt(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: why are null bytes allowed in JSON columns? |
| Date: | 2023-09-22 21:37:37 |
| Message-ID: | e68bfe8c-fea8-99eb-a86a-c65e24d1a6ad@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-09-21 Th 21:57, Wyatt Alt wrote:
> Thanks for the clarification. I now see the "Note" above the table
> explains this.
Essentially the json data type allows anything that is syntactically
valid according to the standard. That doesn't mean that functions
operating on the type can always work, and this is the most obvious of
such restrictions.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-09-22 23:35:05 | Re: BUG #17928: Standby fails to decode WAL on termination of primary |
| Previous Message | Christian Stork | 2023-09-22 21:32:15 | Re: BUG #18131: PL/pgSQL: regclass procedure parameter wrongly memoized(?) |