| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json casts |
| Date: | 2014-05-28 03:55:43 |
| Message-ID: | CA+TgmoYrmQAC12tBAwtTia+KbG_irCXat25NFoocqi0U1tMsbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 27, 2014 at 5:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'd be inclined to think a more useful answer to this issue would be to
> make json.c special-case timestamps, as it already does for numerics.
I wonder if anyone besides me is nervous about changing the semantics
here. It seems like the sort of backward-compatibility break we
normally avoid. If we do make such a compatibility break, it should
certainly be release-noted.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2014-05-28 04:10:40 | Re: Spreading full-page writes |
| Previous Message | Robert Haas | 2014-05-28 03:53:14 | Re: Re-create dependent views on ALTER TABLE ALTER COLUMN ... TYPE? |