| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> | 
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> | 
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: JSON NULLs | 
| Date: | 2013-02-06 19:36:39 | 
| Message-ID: | 5112B0C7.2030300@dunslane.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On 02/06/2013 02:24 PM, Merlin Moncure wrote:
> On Wed, Feb 6, 2013 at 1:08 PM, David E. Wheeler <david(at)justatheory(dot)com> wrote:
>> Hackers,
>>
>> While playing with Andrew’s JSON enhancements, I noticed this:
>>
>>      david=# select * From json_each_as_text('{"baz": null}'::json);
>>       key | value
>>      -----+-------
>>       baz | null
>>
>> It is returning 'null'::text there, not NULL::text. I had expected the latter, because otherwise it's not possible to tell the difference between '{"foo": null}' and '{"foo": "null"}'.
> IMO, this is bug in proposed implementation.  json unquoted null
> should not map to string 'null' but to SQL,  casting behavior from
> text as implemented looks correct. (only SQL null should produce json
> null)
>
Probably. I'm on it.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-02-06 19:42:54 | Re: Alias hstore's ? to ~ so that it works with JDBC | 
| Previous Message | Merlin Moncure | 2013-02-06 19:24:41 | Re: JSON NULLs |