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.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
