14318 2011-09-27 22:11:54 +0000 Importance of the upgradeneeded event should be more explicit 2011-12-27 22:00:39 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED FIXED P1 normal --- 1 me dave.null eliotgra jonas mike public-webapps public-webapps-bugzilla oldest_to_newest 57453 0 me 2011-09-27 22:11:54 +0000 It is never explicitly stated that the upgradeneeded event is your one chance to modify the database schema. This only becomes apparent after reading the VERSION_CHANGE transaction steps in detail. It's easy to miss this subtle point (at least it was for me :-P). 57458 1 jonas 2011-09-28 00:36:54 +0000 Did it seem like there was any other way to get a VERSION_CHANGE transaction? If so, where? There would likely be the place to indicate that it does not, in fact, produce a VERSION_CHANGE transaction. 62066 2 eliotgra 2011-12-27 22:00:39 +0000 Added the following note to the Editor's Draft of 12/27: A VERSION_CHANGE transaction is automatically created when, during the open database API, a database version number is provided that is greater than the current database version. This transaction will be active inside the onupgradeneeded event handler, allowing the creation of new object stores and indexes. Thanks, Eliot