| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tim Smith <randomdev4+postgres(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: "JSON does not support infinite date values" |
| Date: | 2015-02-26 16:15:05 |
| Message-ID: | 54EF4689.7070508@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/26/2015 07:54 AM, Tim Smith wrote:
>> So +1 for removing the error and emitting "infinity" suitably quoted.
>> Andrew, will you do that?
>>
>
> +1 here too. Otherwise there's very little point having the
> "infinity" feature in Postgres if only some of the database functions
> actually support it without throwing a tantrum. If its a database
> feature, it should be a database feature throughout.
Personally, I think the worse that can be said is that it is a case of
premature optimization. Postgres making you deal with infinity and
JSON/Javascript now instead of later.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-02-26 16:16:31 | Re: "JSON does not support infinite date values" |
| Previous Message | Jirayut Nimsaeng | 2015-02-26 16:13:01 | Re: [HACKERS] BDR Multiple database |