From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: Add hstore_to_json() |
Date: | 2009-12-18 19:39:47 |
Message-ID: | 200912181939.nBIJdll08613@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> >
> >> You're correct that we don't necessarily need a new type, we could just
> >> make it text and have a bunch of operations, but that seems to violate
> >> the principle of data type abstraction a bit.
> >>
> >
> > I think the relevant precedent is that we have an xml type. While I
> > surely don't want to follow the SQL committee's precedent of inventing
> > a ton of special syntax for xml support, it might be useful to look at
> > that for suggestions of what functionality would be useful for a json
> > type.
> >
> > [ I can already hear somebody insisting on a yaml type :-( ]
> >
> >
> >
>
> Now that's a case where I think a couple of converter functions at most
> should meet the need.
I can see this feature getting web developers more excited about
Postgres.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-12-18 19:49:38 | Re: PATCH: Add hstore_to_json() |
Previous Message | Andrew Dunstan | 2009-12-18 19:37:19 | Re: PATCH: Add hstore_to_json() |