| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json casts |
| Date: | 2014-05-27 23:25:46 |
| Message-ID: | 53851EFA.6010100@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/27/2014 07:17 PM, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> * Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
>>> Given that this would be a hard coded behaviour change, is it too
>>> late to do this for 9.4?
>> No, for my 2c.
> If we do it by adding casts then it'd require an initdb, so I'd vote
> against that for 9.4. If we just change behavior in json.c then that
> objection doesn't apply, so I wouldn't complain.
>
>
I wasn't proposing to add a cast, just to allow users to add one if they
wanted. But I'm quite happy to go with special-casing timestamps, and
leave the larger question for another time.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-05-27 23:27:18 | Re: Why is pg_lsn marking itself a preferred type? |
| Previous Message | Tom Lane | 2014-05-27 23:17:43 | Re: json casts |