On Wed, Jan 28, 2015 at 1:13 PM, Jim Nasby <jim.na...@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.
