W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

RE: http://www.w3.org/TR/IndexedDB/#key-construct ordering confusion

From: Eliot Graff <Eliot.Graff@microsoft.com>
Date: Fri, 19 Aug 2011 21:57:42 +0000
To: Jonas Sicking <jonas@sicking.cc>, Jim Jewett <jimjjewett@gmail.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <CE3A5BFD1228D84A8D9C158EEC195FD53CCE8111@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
> > According to the text, I would expect negative infinity to be the
> > lowest possible key, and the highest possible key to be undefined
> > (because an array of any candidate highest key followed by another
> > valid key would be even higher)
> 
> Yes. You are correct.
> 
> / Jonas
> 

I rewrote the note to say the following and published to the Editor's Draft:

As a result of the above rules, negative infinity is the lowest possible value for a key. There is no highest possible key value. This is because an array of any candidate highest key followed by another valid key is even higher.

Thanks so much,

Eliot
Received on Friday, 19 August 2011 21:58:12 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT