So yeah. Numbers are hard.
Firstly, anyone that mentioned RFC 4627 or JavaScript behavior is
walking down a path entirely orthogonal to the issue at hand. Jason
almost had it when he talked about them being different but then he
went off on some weird tangent and lost me.
In a nutshell, the issue
On Mon, Feb 13, 2012 at 12:30 AM, Robert Newson wrote:
> I'm in favor of adding it to breaking changes and keeping the new
> behaviour. Both ejson and jiffy use %g to encode numbers. This favors
> a shorter encoding. On reflection, this is more desirable than
> pretending that json distinguishes b
On Sun, Feb 12, 2012 at 9:58 PM, Benoit Chesneau wrote:
> On Sun, Feb 12, 2012 at 3:03 PM, Jason Smith wrote:
>> tl;dr = Minor disagreement with Benoit but happy to go with his decision.
>>
>> On Sun, Feb 12, 2012 at 1:10 PM, Benoit Chesneau wrote:
>>> On Sun, Feb 12, 2012 at 12:03 PM, Jason Smi
Hi Everyone-
I have been using CouchDB for several years and I absolutely love working
with it most of the time. Thanks to everyone who has made it such a joy to
work with. There are however a few consistent situations where I run into
trouble and that I would like to fix if possible. I have a
Hi Everyone-
I have been using CouchDB for several years and I absolutely love working
with it most of the time. Thanks to everyone who has made it such a joy to
work with. There are however a few consistent situations where I run into
trouble and that I would like to fix if possible. I have a
On Sun, Feb 12, 2012 at 5:48 PM, Noah Slater wrote:
> I've been over this before:
>
> http://code.google.com/p/simplejson/issues/detail?id=34
>
>
> From Bob Ippolito:
>
> Try alert(2.2002 == 2.2) in ANY browser. It will say true.
>> JavaScript uses IEEE double for Number, always has,
On Sun, Feb 12, 2012 at 18:30, Robert Newson wrote:
> I'm in favor of adding it to breaking changes and keeping the new
> behaviour. Both ejson and jiffy use %g to encode numbers. This favors
> a shorter encoding. On reflection, this is more desirable than
> pretending that json distinguishes betw
On Sun, Feb 12, 2012 at 17:48, Noah Slater wrote:
> Try alert(2.2002 == 2.2) in ANY browser. It will say true.
>> JavaScript uses IEEE double for Number, always has, always will.
>
> The general consensus seems to be that if you don't want JSON messing
> around with your numbers, then
On Sun, Feb 12, 2012 at 6:30 PM, Robert Newson wrote:
> [..] On reflection, this is more desirable than
> pretending that json distinguishes between ints and floats.
>
Why? (or, can you share this reflection ? ;)
- benoît
I'm in favor of adding it to breaking changes and keeping the new
behaviour. Both ejson and jiffy use %g to encode numbers. This favors
a shorter encoding. On reflection, this is more desirable than
pretending that json distinguishes between ints and floats.
Sent from my iPhone
On 12 Feb 2012, at
I've been over this before:
http://code.google.com/p/simplejson/issues/detail?id=34
>From Bob Ippolito:
Try alert(2.2002 == 2.2) in ANY browser. It will say true.
> JavaScript uses IEEE double for Number, always has, always will.
The general consensus seems to be that if you don'
On Sun, Feb 12, 2012 at 3:03 PM, Jason Smith wrote:
> tl;dr = Minor disagreement with Benoit but happy to go with his decision.
>
> On Sun, Feb 12, 2012 at 1:10 PM, Benoit Chesneau wrote:
>> On Sun, Feb 12, 2012 at 12:03 PM, Jason Smith wrote:
>>> On Sun, Feb 12, 2012 at 10:15 AM, Benoit Chesnea
[
https://issues.apache.org/jira/browse/COUCHDB-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206419#comment-13206419
]
Roger Moffatt commented on COUCHDB-1408:
Thanks guys. I've made the small change
tl;dr = Minor disagreement with Benoit but happy to go with his decision.
On Sun, Feb 12, 2012 at 1:10 PM, Benoit Chesneau wrote:
> On Sun, Feb 12, 2012 at 12:03 PM, Jason Smith wrote:
>> On Sun, Feb 12, 2012 at 10:15 AM, Benoit Chesneau
>> wrote:
>>> well as a database, CouchDB shouldn't chan
[
https://issues.apache.org/jira/browse/COUCHDB-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206411#comment-13206411
]
Jan Lehnardt commented on COUCHDB-1408:
---
The wiki states "You need to be added to
On Sun, Feb 12, 2012 at 12:03 PM, Jason Smith wrote:
> On Sun, Feb 12, 2012 at 10:15 AM, Benoit Chesneau wrote:
>> well as a database, CouchDB shouldn't change the way data are saved
>> in. I expect that the number I saved under the json type Number [1]
>> defined by the spec [2] is correctly sav
On Sun, Feb 12, 2012 at 10:15 AM, Benoit Chesneau wrote:
> well as a database, CouchDB shouldn't change the way data are saved
> in. I expect that the number I saved under the json type Number [1]
> defined by the spec [2] is correctly saved and returned as is. No
> roundtrip or precision lost sho
On Sat, Feb 11, 2012 at 3:32 PM, Robert Newson wrote:
> I'd like some opinions on whether COUCHDB-1407 constitutes a release
> blocking issue. Yes, I understand that the JSON spec is very weak on
> numbers, blah blah boo splat. Is this because of the switch to ejson?
> Is jiffy more compatible on
On Sun, Feb 12, 2012 at 10:46 AM, Dirkjan Ochtman wrote:
> On Sun, Feb 12, 2012 at 02:15, Jason Smith wrote:
>> Does CouchDB store my **JSON** (and mutate it minimally, for _rev)?
>>
>> Or does CouchDB store my **data**, where JSON is simply how we express
>> the underlying "stuff" to be stored?
On Sun, Feb 12, 2012 at 02:15, Jason Smith wrote:
> Does CouchDB store my **JSON** (and mutate it minimally, for _rev)?
>
> Or does CouchDB store my **data**, where JSON is simply how we express
> the underlying "stuff" to be stored?
Yeah, I thought a little further about it during my night's sle
20 matches
Mail list logo
