| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Hannu Krosing <hannu(at)krosing(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? |
| Date: | 2012-05-04 20:12:26 |
| Message-ID: | 12299.1336162346@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 Fri, May 4, 2012 at 3:49 PM, Hannu Krosing <hannu(at)krosing(dot)net> wrote:
>> Can we at least have the xxx_to_json() functions try cast to json first
>> and fall back to text if the cast fails.
> I think the idea that you can involve the casting machinery in this is
> misguided.
It is possible that that can be made to work, but it's a research
project, not something to be crammed into 9.2 at the last possible
minute. In any case, I really dislike the idea that array_to_json
and row_to_json would contain two entirely different behaviors.
Leave the extensibility ideas for a future to_json() function.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2012-05-04 20:40:18 | Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? |
| Previous Message | Jim Nasby | 2012-05-04 20:04:57 | Re: Re: xReader, double-effort (was: Temporary tables under hot standby) |