| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json casts |
| Date: | 2014-05-28 06:35:16 |
| Message-ID: | 538583A4.6000109@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/27/2014 11:55 PM, Robert Haas wrote:
> 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.
>
Yes, certainly it should be.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-05-28 06:41:06 | Re: Spreading full-page writes |
| Previous Message | Amit Kapila | 2014-05-28 06:15:14 | Re: Proposing pg_hibernate |