| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | 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-27 17:23:41 |
| Message-ID: | 20753.1422379421@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 01/27/2015 12:24 AM, Noah Misch wrote:
>> +1 for splitting development that way. Fixing the use of escape_json() is
>> objective, but the choices around the warning are more subtle.
> OK, so something like this patch? I'm mildly concerned that you and I
> are the only ones commenting on this.
Doesn't seem to me like this fixes anything. If the content of a jsonb
value is correct, the output will be the same with or without this patch;
and if it's not, this isn't going to really improve matters.
I think coding anything is premature until we decide how we're going to
deal with the fundamental ambiguity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2015-01-27 17:29:30 | Re: Re: Abbreviated keys for Numeric |
| Previous Message | Tom Lane | 2015-01-27 17:08:25 | Re: numeric access out of bounds |