This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11349 - [IndexedDB] Null should not be a valid key type
Summary: [IndexedDB] Null should not be a valid key type
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jeremy Orlow
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2010-11-19 11:55 UTC by Jeremy Orlow
Modified: 2010-12-10 15:39 UTC (History)
2 users (show)

See Also:


Description Jeremy Orlow 2010-11-19 11:55:51 UTC
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.)
Comment 1 Jeremy Orlow 2010-12-10 15:39:18 UTC
changeset:   99:0fa45b18a8ea
tag:         tip
user:        Jeremy Orlow <>
date:        Fri Dec 10 15:38:53 2010 +0000
summary:     Remove null from the list of valid key types.