W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

[Bug 18551] [IndexedDB] Ambiguity about operations preceding a failed createIndex.

From: <bugzilla@jessica.w3.org>
Date: Wed, 15 Aug 2012 17:00:13 +0000
Message-Id: <E1T1gx3-0005TE-VY@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18551

Jonas Sicking <jonas@sicking.cc> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonas@sicking.cc

--- Comment #2 from Jonas Sicking <jonas@sicking.cc> 2012-08-15 17:00:13 UTC ---
I think both createIndex and deleteIndex should be treated as "asynchronous
requests".

>From a web developers point of view it means that things happen in the order
that their function calls run. So I think the ending example should result in:


store.createIndex('index', 'name', {unique: true});
request1 = store.put({name: 'bob'}, 1);
request2 = store.put({name: 'bob'}, 2);
store.deleteIndex('index');

My interpretation:

index metadata added
process request1 -> success
process request2 -> fail
index metadata removed


As you can see, it makes the actions line up exactly with the order of the
function calls of the webpage.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 15 August 2012 17:00:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 August 2012 17:00:17 GMT