Re: jsonb, unicode escapes and escaped backslashes

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: jsonb, unicode escapes and escaped backslashes
Дата
Msg-id 54C7D11E.607@dunslane.net
обсуждение исходный текст
Ответ на Re: jsonb, unicode escapes and escaped backslashes  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: jsonb, unicode escapes and escaped backslashes  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 01/27/2015 12:23 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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.
>
>             


The input \\uabcd will be stored correctly as \uabcd, but this will in 
turn be rendered as \uabcd, whereas it should be rendered as \\uabcd. 
That's what the patch fixes.

There are two problems here and this addresses one of them. The other 
problem is the ambiguity regarding \\u0000 and \u0000.

cheers

andrew




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Marco Nenciarini
Дата:
Сообщение: Re: File based incremental backup v6
Следующее
От: Marco Nenciarini
Дата:
Сообщение: File based Incremental backup v7