Re: jsonb, unicode escapes and escaped backslashes

From: Bruce Momjian <bruce(at)momjian(dot)us>
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 12:22:29
Message-ID: 20150129122229.GB2316@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 28, 2015 at 03:13:47PM -0600, Jim Nasby wrote:
> 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.

+1

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-01-29 12:46:55 Re: Possible typo in create_policy.sgml
Previous Message Amit Kapila 2015-01-29 12:21:54 Re: Parallel Seq Scan