| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Jan Urbański <wulczer(at)wulczer(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Claes Jakobsson <claes(at)gluefinance(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Wieck <janwieck(at)yahoo(dot)com> |
| Subject: | Re: JSON for PG 9.2 |
| Date: | 2011-12-21 02:04:29 |
| Message-ID: | A3838829-7DF8-4787-BE11-D69C67492C94@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 19, 2011, at 9:00 PM, Robert Haas wrote:
>> +1, though I think the core type will at least need some basic operators and indexing support.
>
> And I'm willing to do that, but I thought it best to submit a bare
> bones patch first, in the hopes of minimizing the number of
> objectionable things therein. For example, if you want to be able to
> index a JSON column, you have to decide on some collation order that
> is consistent with JSON's notion of equality, and it's not obvious
> what is most logical. Heck, equality itself isn't 100% obvious. If
> there's adequate support for including JSON in core, and nobody
> objects to my implementation, then I'll throw some ideas for those
> things up against the wall and see what sticks.
+1 Sounds good to me.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2011-12-21 02:05:30 | Re: JSON for PG 9.2 |
| Previous Message | Tom Lane | 2011-12-21 01:23:36 | Re: sorting table columns |