| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb, unicode escapes and escaped backslashes |
| Date: | 2015-01-29 06:51:03 |
| Message-ID: | CAMkU=1xqmpPj94RtrWaK5Zc0OFnBtn7mxWRVJg2qYCARS5EuYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 28, 2015 at 1:13 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Bausch | 2015-01-29 07:10:10 | Re: Parallel Seq Scan |
| Previous Message | Josh Berkus | 2015-01-29 05:26:11 | Re: pg_upgrade and rsync |