Re: IndexedDB: updates through cursors on indexes that change the key

Please look at the mail archives.  IIRC, it seemed confusing that you could
be looking at old data.  Iterating on live data seems more consistent with
run to completion semantics.

J

On Tue, Feb 1, 2011 at 5:26 PM, Keean Schupke <keean@fry-it.com> wrote:

> So whats the benefit of allowing a cursor to modify the data under it?
>
> Cheers,
> Keean.
>
>
> On 2 February 2011 01:17, Jonas Sicking <jonas@sicking.cc> wrote:
>
>> On Tue, Feb 1, 2011 at 4:48 PM, Keean Schupke <keean@fry-it.com> wrote:
>> > Sorry, sent that before I was finished.
>> >
>> > Seems prone to problems in environments with multiple parallel accesses
>> to
>> > the same database.
>>
>> As long as you're inside a transaction, no other environments (be they
>> separate tabs running in a separate process, workers running in a
>> separate thread, or separate components running in the same page) will
>> be able to mutate the data under you.
>>
>> / Jonas
>>
>
>