I agree with Jonas on this. I think accessing the index values is an important
feature (in addition to joins you can imagine add an extra property or two to
the index key* to create a covering index and avoid fetching the object in a
perf-critical path).
That said, to me it's just about
On 9/17/2010 3:14 PM, Jonas Sicking wrote:
How do you then guarantee that a transaction that spans multiple
objectStores either fully succeeds or is fully rolled back? Especially
in the event of a crash during commit.
If you don't use write ahead logging, and connect to each database with
On Fri, Sep 17, 2010 at 1:06 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Sep 16, 2010 at 2:23 PM, Jeremy Orlow jor...@chromium.org wrote:
On Thu, Sep 16, 2010 at 8:53 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Sep 16, 2010 at 2:15 AM, Jeremy Orlow jor...@chromium.org
wrote:
On Fri, Sep 17, 2010 at 2:46 AM, Jeremy Orlow jor...@chromium.org wrote:
On Fri, Sep 17, 2010 at 1:06 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Sep 16, 2010 at 2:23 PM, Jeremy Orlow jor...@chromium.org wrote:
On Thu, Sep 16, 2010 at 8:53 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Sep 15, 2010 at 10:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Heh, I've also been thinking about this exact issue lately. There is a
similar question for IDBCursor.delete.
On Wed, Sep 15, 2010 at 8:55 AM, Jeremy Orlow jor...@chromium.org wrote:
I think it's clear what IDBCursor
On Thu, Sep 16, 2010 at 10:15 AM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Sep 15, 2010 at 10:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Heh, I've also been thinking about this exact issue lately. There is a
similar question for IDBCursor.delete.
On Wed, Sep 15, 2010 at 8:55 AM,
On Thu, Sep 16, 2010 at 10:15 AM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Sep 15, 2010 at 10:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Heh, I've also been thinking about this exact issue lately. There is a
similar question for IDBCursor.delete.
On Wed, Sep 15, 2010 at 8:55 AM,
On Thu, Sep 16, 2010 at 2:15 AM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Sep 15, 2010 at 10:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Heh, I've also been thinking about this exact issue lately. There is a
similar question for IDBCursor.delete.
On Wed, Sep 15, 2010 at 8:55 AM,
On Thu, Sep 16, 2010 at 4:08 AM, Jeremy Orlow jor...@chromium.org wrote:
On Thu, Sep 16, 2010 at 10:15 AM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Sep 15, 2010 at 10:45 PM, Jonas Sicking jo...@sicking.cc wrote:
Heh, I've also been thinking about this exact issue lately. There is a
On Thu, Sep 16, 2010 at 8:53 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Sep 16, 2010 at 2:15 AM, Jeremy Orlow jor...@chromium.org wrote:
Wait a sec. What are the use cases for non-object cursors anyway? They
made perfect sense back when we allowed explicit index management, but
now
On Thu, Sep 16, 2010 at 2:23 PM, Jeremy Orlow jor...@chromium.org wrote:
I think we should leave in openObjectCursor/getObject but remove
openCursor/get for now. We can then revisit any of these features as soon
as there are implementations (both in the UAs and in web sites) mature
enough for
On Thu, Sep 16, 2010 at 11:04 PM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Thu, Sep 16, 2010 at 2:23 PM, Jeremy Orlow jor...@chromium.org wrote:
I think we should leave in openObjectCursor/getObject but remove
openCursor/get for now. We can then revisit any of these features as
soon
On Thu, Sep 16, 2010 at 2:23 PM, Jeremy Orlow jor...@chromium.org wrote:
On Thu, Sep 16, 2010 at 8:53 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Sep 16, 2010 at 2:15 AM, Jeremy Orlow jor...@chromium.org wrote:
Wait a sec. What are the use cases for non-object cursors anyway? They
13 matches
Mail list logo
