Lines Matching full:setversion
101 // "setVersion" on the database and supplying a new version. This also starts a new
103 // setVersion which we'll get into later.
109 var request = db.setVersion("1.0");
116 // We are now in a setVersion transaction. Such a transaction is the only place where one
175 // any way) keys or values is asynchronous and any other call (besides setVersion and open) are
190 // allowed in a normal (i.e. non-setVersion) transaction. This is useful so that data migrations
210 // Transactions (besides those created with setVersion) are created synchronously. Like
414 // The way setVersion is supposed to work:
415 // To keep things simple to begin with, objectStores and indexes can only be created in a setVersion
420 // Because a setVersion transaction could stall out nearly forever until the user closes windows,
421 // we've added a "blocked" event to the request object returned by setVersion. This will fire if the
422 // setVersion transaction can't begin because other windows have an open connection. The app can then
428 // Once inside a setVersion transaction, you can do anything you'd like. The one connection which
429 // was allowed to stay open to complete the setVersion transaction will stay alive. Multiple
430 // setVersion transactions can be queued up at once and will fire in the order queued (though
433 // The current status of setVersion in Chromium/WebKit:
435 // setVersion transaction starts" rule. We also don't implement database.close() or have a blocked
436 // event on the request .setVersion() returns.
