W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

[Bug 11349] New: [IndexedDB] Null should not be a valid key type

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Nov 2010 11:55:51 +0000
To: public-webapps@w3.org
Message-ID: <bug-11349-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11349

           Summary: [IndexedDB] Null should not be a valid key type
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


It's really odd that objectStores and unique indexes can store just a single
item with type null.  At TPAC, we discussed why we allow null and decided that
we should remove null from the list of valid key types and instead come up with
a way to say that a particular keyPath is optional for indexes.  (This is a
bigger discussion that needs to happen, and I believe Jonas is going to start
it on public-webapps in the near future about this.)

-- 
Configure bugmail: http://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 Friday, 19 November 2010 11:55:57 GMT

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