| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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:37:19 |
| Message-ID: | 4B2BD9EF.7040308@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-12-18 19:39:47 | Re: PATCH: Add hstore_to_json() |
| Previous Message | Bruce Momjian | 2009-12-18 19:29:18 | Removing pg_migrator limitations |