W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[Bug 10674] New: [IndexedDB] Changes to indexes (and their cursors)

From: <bugzilla@jessica.w3.org>
Date: Wed, 22 Sep 2010 13:03:06 +0000
To: public-webapps@w3.org
Message-ID: <bug-10674-2927@http.www.w3.org/Bugs/Public/>

           Summary: [IndexedDB] Changes to indexes (and their cursors)
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: andreip@google.com
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org

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"

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 22 September 2010 13:03:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:11 UTC