Re: jsonb, unicode escapes and escaped backslashes - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: jsonb, unicode escapes and escaped backslashes
Date
Msg-id CAMkU=1xqmpPj94RtrWaK5Zc0OFnBtn7mxWRVJg2qYCARS5EuYw@mail.gmail.com
Whole thread Raw
In response to Re: jsonb, unicode escapes and escaped backslashes  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Wed, Jan 28, 2015 at 1:13 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:

My $0.01:

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?

I would bitch about it for text if I thought that it would do any good.
 

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_upgrade and rsync
Next
From: Daniel Bausch
Date:
Subject: Re: Parallel Seq Scan