On May 18, 2010, at 12:50 PM, Jonas Sicking wrote: > On Tue, May 18, 2010 at 12:46 PM, Jonas Sicking <jo...@sicking.cc> wrote: >> On Tue, May 18, 2010 at 12:37 PM, Nikunj Mehta <nik...@o-micron.com> wrote: >>> If the use case here is to avoid tripping up on schema changes, then: >>> >>> 1. Lock the database when starting a database connection. This is the >>> non-sharing access mode defined in 3.2.9 as the first option under step 2. >> >> Will locking the database prevent others from creating new >> objectStores? Step 2 only talks about acquiring locks on the existing >> database objects. > > Also, what happens to already existing database connections? Do you > have to wait until the user has closed all other tabs which use the > same database before making the upgrade?
I won't talk about tabs and such. Let's make clarification questions be related to spec text. A database connection that locks the entire database cannot be opened if there is another database connection that locks at least one database object, e.g., an index or object store.