| 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:05:39 |
| Message-ID: | CAARyMpBmM8GvDVsY1MkS6hhs+N-KwhycrAypmtKnUCxUo-ETOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 24, 2011 at 2:19 PM, Florian Pflug <fgp(at)phlo(dot)org> wrote:
> The downside being that we'd then either need to canonicalize in
> the equality operator, or live with either no equality operator or
> a rather strange one.
It just occurred to me that, even if we sort object members, texteq
might not be a sufficient way to determine equality. In particular,
IEEE floats treat +0 and -0 as two different things, but they are
equal when compared. Note that we're only dealing with a decimal
representation; we're not (currently) converting to double-precision
representation and back.
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.
- Joey
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joey Adams | 2011-07-25 05:35:05 | Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON |
| Previous Message | Harshitha S | 2011-07-25 04:59:42 | Re: Tracing in Postgres |