| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Steve Singer <steve(at)ssinger(dot)info>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json generation enhancements |
| Date: | 2013-02-24 23:33:53 |
| Message-ID: | 512AA361.1030904@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/24/2013 09:58 PM, Andrew Dunstan wrote:
>
> Adding a cast to json for a builtin type will have no effect unless
> you also change this code. We can relax that but my view was that we
> should know how to generate JSON from builtin types and just do it.
If json generation from built-in types is complete with full coverage of
all useful types when this first ships, then I'm happy. I was only
concerned about the BC argument "you can't add a proper json-aware cast
from interval to json because we've already been doing it via a cast to
text and changing the result would break existing code".
That's all I'm worried about, and if that won't be an issue then I'm
perfectly happy.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2013-02-24 23:48:21 | Re: Show type in psql SELECT |
| Previous Message | Peter Eisentraut | 2013-02-24 23:14:00 | Re: Show type in psql SELECT |