This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10674 - [IndexedDB] Changes to indexes (and their cursors)
Summary: [IndexedDB] Changes to indexes (and their cursors)
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Andrei Popescu
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-22 13:03 UTC by Jeremy Orlow
Modified: 2010-10-25 18:16 UTC (History)
3 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-09-22 13:03:05 UTC 
On Fri, Sep 17, 2010 at 3:14 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>> Given that the key-returning versions of these functions are just
>> optimizations, at the very least, we should change the names though:
>> get->getKey (or maybe getPrimaryKey?)
>> openCursor->openKeyCursor (or maybe openPrimaryKeyCursor?)
>> getObject->get
>> openObjectCursor->openCursor

This sounds like a workable solution. And also make IDBCursor.update
and IDBCursor.delete throw an exception if called on a key-cursor.


This was the resolution of this thread: "[IndexedDB] IDBCursor.update for cursors returned from IDBIndex.openCursor" http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0859.html
Comment 1 Jonas Sicking (Not reading bugmail) 2010-10-25 18:13:13 UTC 
Fixed: http://dvcs.w3.org/hg/IndexedDB/rev/c2618f86a774