Re: Relaxing NaN/Infinity restriction in JSON fields - Mailing list pgsql-general

From Mitar
Subject Re: Relaxing NaN/Infinity restriction in JSON fields
Date
Msg-id CAKLmikP7PgKUC8a-J7bOiZC48zifFC_5KhuaKqyqrC-aJBFV7A@mail.gmail.com
Whole thread Raw
In response to Re: Relaxing NaN/Infinity restriction in JSON fields  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
Hi!

On Wed, May 8, 2019 at 6:09 AM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> If you want to complain about JSON, it's IETF that you need to talk
> about, not us -- we're just implementing their spec.  As for storing the
> numbers in a database, you can already do that, just not on the JSON
> datatype.

Yes, I see why then so many implement variations on JSON, like BSON
and stuff. So that they can have mostly compatible structure, but with
all floats and datetime structure.

What are thoughts of adding something like that? PgJSON variant. :-)


Mitar

-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m



pgsql-general by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: PostgreSQL on Amazon RDS
Next
From: Julie Nishimura
Date:
Subject: postgresql 9.4 restart