On Thursday, September 21, 2023, Wyatt Alt <
wyatt.alt@gmail.com> wrote:
I am not sure if this is a bug or a known inconvenience.
It’s a reason to not use json in new development and instead use jsonb.
Once the null byte is inserted the JSON operator ->> can no longer be applied to the column. JSONB columns don't allow null bytes at all. Should the same constraint apply on JSON? If not, applications must be vigilant to guard against null bytes, or queries could break at read time. My reading of table 8.23 in
https://www.postgresql.org/docs/16/datatype-json.html is they should be disallowed at insert.
That table basically describes how jsonb behaves, not json. I agree that fact could be made clearer instead of having to deduce that from reading the prose which explicitly says json is basically lacks safeties for any usage within the database. But it also imposes fewer restrictions in exchange.
David J.