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

Re: [Bug 11257] New: Should IDBCursor.update be able to create a new entry?

From: Jeremy Orlow <jorlow@chromium.org>
Date: Thu, 11 Nov 2010 16:11:19 +0300
Message-ID: <AANLkTi=m5ctpp0HZ1mMcY5y7LBs7vne7h5k7G74-Zu-D@mail.gmail.com>
To: public-webapps@w3.org
On Mon, Nov 8, 2010 at 2:12 PM, <bugzilla@jessica.w3.org> wrote:

> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11257
>
>           Summary: Should IDBCursor.update be able to create a new entry?
>           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: jonas@sicking.cc
>         QAContact: member-webapi-cvs@w3.org
>                CC: mike@w3.org, public-webapps@w3.org
>
>
> What should happen in the following case:
>
> db.transaction(["foo"]).objectStore("foo").openCursor().onsuccess =
> function(e)
> {
>  var cursor = e.result;
>  if (!cursor)
>    return;
>
>  cursor.delete();
>  cursor.update({ id: 1234, value: "Benny" });
> }
>
>
> This situation can of course arrive in more subtle ways:
>
> os = db.transaction(["foo"]).objectStore("foo");
> os.openCursor().onsuccess = function(e) {
>  var cursor = e.result;
>  if (!cursor)
>    return;
>
>  cursor.update({ id: 1234, value: "Benny" });
> }
> os.delete(1234);
>
>
> As specified, IDBCursor.update behaves just like IDBObjectStore.put and
> just
> creates a new entry, but this might be somewhat unexpected behavior.
>

Let's just remove update and delete from IDBCursor and be done with it.

J
Received on Thursday, 11 November 2010 13:13:40 GMT

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