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

RE: [indexeddb] Cursor data Question

From: Israel Hilerio <israelh@microsoft.com>
Date: Tue, 26 Apr 2011 01:48:27 +0000
To: Jonas Sicking <jonas@sicking.cc>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <F695AF7AA77CC745A271AD0F61BBC61E3D02AADF@TK5EX14MBXC113.redmond.corp.microsoft.com>
On Mon, Apr 25, 2011 at 6:41 PM, Jonas Sicking wrote:
> On Mon, Apr 25, 2011 at 6:23 PM, Israel Hilerio <israelh@microsoft.com>
> wrote:
> > In reading the spec, there doesn't seem to be any long-term state
> > associated with a cursor.  However, there is an edge case I would like
> > to validate with everyone.
> >
> > If I have cursor pointing to a specific data record and then I delete
> > the record before accessing it, what happens to the value and key of
> > the cursor object?  Do we expect the cursor instance to still have the
> > values of the currently accessed record?
> Yes, .value and .key are synchronous, so we don't want them to have to
> access data in the database. Instead they copy the data once fetched from the
> database.
> We discussed this specifically on the list iirc. This also has the effect that
> calling cursor.update() can create a new entry, if the old entry was removed
> before the call.
> By the way, for all of these questions, feel free to add explicit text to the
> specification. Preferably in the form of a note. The spec template supports
> this by adding:
> <p class=note>
>   ....
> </p>
> / Jonas

Great!  I will work with Eliot to add text to spec to capture this behavior.

Received on Tuesday, 26 April 2011 01:48:56 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:31 UTC