W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

[Bug 16714] New: IndexedDB: creating an object store with Array-type key path and key generator should be forbidden

From: <bugzilla@jessica.w3.org>
Date: Thu, 12 Apr 2012 15:51:43 +0000
To: public-webapps@w3.org
Message-ID: <bug-16714-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16714

           Summary: IndexedDB: creating an object store with Array-type
                    key path and key generator should be forbidden
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jsbell@chromium.org
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Per discussion on the list, specifying both a key generator for an object store
(via autoIncrement: true) and a key path which is an Array (via keyPath: [...])
would lead to inconsistent keys. This should not be supported.

This spec change should cover it:

OLD: If the optionalParameters parameter is specified, and autoIncrement is set
to true, and the keyPath parameter is specified to the empty string, or
specified to an Array and one of the items is an empty string, this function
must throw a InvalidAccessError exception.

NEW: If the optionalParameters parameter is specified, and autoIncrement is set
to true, and the keyPath parameter is specified to the empty string, or
specified to an Array, this function must throw a InvalidAccessError exception.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 12 April 2012 15:51:46 GMT

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