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

Re: [IndexedDB] Behavior of IDBObjectStore.get() and IDBObjectStore.delete() when record doesn't exist

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 8 Nov 2010 15:10:21 -0800
Message-ID: <AANLkTin3Mn65rNRhxFAjpOaHmnHMg9eMRwZS6+L-O_L2@mail.gmail.com>
To: Keean Schupke <keean@fry-it.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Webapps WG <public-webapps@w3.org>
On Mon, Nov 8, 2010 at 2:39 PM, Keean Schupke <keean@fry-it.com> wrote:
> The problem I am trying to solve is not knowing if "get(key) === undefined"
> means the key does not exist or there is a key with a value of undefined.
> The solution is to disallow inserting undefined. Now there is no ambiguity,
> if get(key) returns undefined, it _must_ be because the key does not exist.
> Does this make sense so far?

But if saying "you're not allowed to insert undefined as value" is an
acceptable solution, why isn't "you can't tell them apart using get()" an
acceptable solution?

What use case does the first solution cater to that isn't solved by
the second solution?

/ Jonas
Received on Monday, 8 November 2010 23:11:09 GMT

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