Re: [IndexedDB] setVersion with multiple IDBDatabase objects

On 9/28/2010 7:42 AM, Jeremy Orlow wrote:
> What do we want to do if the user calls window.indexedDB.open("myDB", "some
> description") twice and stores the result as db1 and db2, calls
> db1.setVersion(), and then in the success handler does
> db2.createObjectStore?  In other words, is the setVersion transaction tied
> to the database instance that setVersion was called on, or is it available
> to any instance/object that points to that particular database for that
> particular origin in that particular page/worker?
While I can see an argument either way, I think I'd prefer it to be tied 
to the instance.  I like this because then it works the same as it does 
being in different windows.  I don't have a strong opinion on this though.

Cheers,

Shawn

Received on Tuesday, 28 September 2010 14:49:18 UTC