W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

[Bug 18558] [IndexedDB] Define error seen when key generator maximum value is reached

From: <bugzilla@jessica.w3.org>
Date: Wed, 20 Feb 2013 00:53:14 +0000
To: public-webapps@w3.org
Message-ID: <bug-18558-2927-JXf7KP3GiG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18558

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |eliotgra@microsoft.com
         Resolution|---                         |FIXED

--- Comment #6 from Eliot Graff <eliotgra@microsoft.com> ---
Added the following:

In 3.1.13 (7th bullet)
...
When the current number of a key generator reaches above the value 2^53
(9007199254740992) any attempts to use the key generator to generate a new key
will result in a ConstraintError. It's still possible to insert records into
the object store by specifying an explicit key, however the only way to use a
key generator again for the object store is to delete the object store and
create a new one. 

In Section 5.1, Object Store Storage Operation
...
2. If store uses a key generator and key is undefined, set key to the next
generated key. If store also uses in-line keys, then set the property in value
pointed to by store's key path to the new value for key, as shown in the steps
to assign a key to a value using a key path. If the current number of a key
generator reaches above the value 2^53 (9007199254740992) any attempt to use
the key generator to generate a new key fails with a ConstraintError. 

Commit #382

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 20 February 2013 00:53:15 GMT

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