Jim Nasby <jim.na...@bluetreble.com> writes:
> While I sympathize with Noah's sentiments, the only thing that makes sense to
> me is that a JSON text field is treated the same way as we treat text. Right
> now, that means NUL is not allowed, period.
> If no one has bitched about this with text, is it really that big a problem
> with JSON?
Oh, people have bitched about it all right ;-). But I think your real
question is how many applications find that restriction to be fatal.
The answer clearly is "not a lot" for text, and I don't see why the
answer would be different for JSON.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
