| From: | Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Date: | 2011-07-25 05:35:05 |
| Message-ID: | CAARyMpAjort+79p_vS=9Htm9YG5+=6p7JdQ_i-2Mm+ad6o4Dqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 25, 2011 at 1:05 AM, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com> wrote:
> Should we mimic IEEE floats and preserve -0 versus +0 while treating
> them as equal? Or should we treat JSON floats like numeric and
> convert -0 to 0 on input? Or should we do something else? I think
> converting -0 to 0 would be a bad idea, as it would violate the
> intuitive assumption that JSON can be used to marshal double-precision
> floats.
On the other hand, JavaScript's own .toString and JSON.stringify turn
-0 into 0, so JSON can't marshal -0 around, anyway (in practice). Now
I think turning -0 into 0 would be fine for canonicalizing numbers in
json_in.
- Joey
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Pihlak | 2011-07-25 07:33:29 | Re: libpq SSL with non-blocking sockets |
| Previous Message | Joey Adams | 2011-07-25 05:05:39 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |