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

RE: [IndexedDB] setVersion with multiple IDBDatabase objects

From: Pablo Castro <Pablo.Castro@microsoft.com>
Date: Wed, 29 Sep 2010 06:25:20 +0000
To: ben turner <bent.mozilla@gmail.com>, public-webapps WG <public-webapps@w3.org>
Message-ID: <F753B2C401114141B426DB383C8885E05E891AA0@TK5EX14MBXC128.redmond.corp.microsoft.com>

-----Original Message-----
From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of ben turner
Sent: Tuesday, September 28, 2010 8:19 AM

>> Yes, let's have it tied to the instance on which setVersion() was called.
>> As Shawn pointed out that is consistent with the behavior that
>> database instances from different windows will observe. As Jeremy
>> pointed out that is consistent with the way object stores and indexes
>> are tied to a transaction instance. Also, the |event.source| will be
>> db1 in the given example, so it seems natural to allow changes only to
>> the database we pass in the event and no other.
>> -Ben

+1, let's tie it to the instance and make it consistent with stores/indexes.

Received on Wednesday, 29 September 2010 06:25:57 UTC

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