| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Petr Jelinek <pjmodos(at)pjmodos(dot)net>, Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Add JSON support |
| Date: | 2010-04-06 17:31:49 |
| Message-ID: | 23394.1270575109@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Apr 6, 2010 at 12:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> To me, what this throws into question is not so much whether JSON null
>> should equate to SQL NULL (it should), but whether it's sane to accept
>> atomic values.
> With this, I disagree. I see no reason to suppose that a JSON NULL
> and an SQL NULL are the same thing.
Oh. If they're not the same, then the problem is easily dodged, but
then what *is* a JSON null?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-04-06 17:39:56 | Re: BUG #5394: invalid declspec for PG_MODULE_MAGIC |
| Previous Message | Heikki Linnakangas | 2010-04-06 17:29:35 | Re: Remaining Streaming Replication Open Items |