Comments on: HTML5 Web SQL Database – Intro to Versioning and Migrations http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/ ruby, ubuntu, etc Tue, 03 Aug 2010 17:02:20 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Max http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-314 Max Sun, 06 Jun 2010 01:48:18 +0000 http://blog.maxaller.name/?p=263#comment-314 Robin, it's worth noting that the Webkit bug you mention was supposedly fixed in October 2009. Naturally, this doesn't mean that the fix has been picked up by all browsers using the Webkit engine, but the fix will propagate eventually. Robin, it’s worth noting that the Webkit bug you mention was supposedly fixed in October 2009. Naturally, this doesn’t mean that the fix has been picked up by all browsers using the Webkit engine, but the fix will propagate eventually.

]]> By: Robin http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-313 Robin Sun, 06 Jun 2010 01:01:44 +0000 http://blog.maxaller.name/?p=263#comment-313 schory, not only does it not work on iPhone, it also doesn't work on certain Safari versions because of a bug (id 27836, see https://bugs.webkit.org/show_bug.cgi?id=27836 ) I've found a workaround like this : _db.changeVersion(_db.version, version, function(tx){ // transaction tx.executeSql(migrations[version]); }, function(err){ // error if (err.code == 2) { // Safari bug 27836 probably occured // changeVersion() will never work on a Safari version with this bug, so we need to do the transaction again, and manually maintain the version number _doSafariBugMigration(versions, migration); } JuSy.log(err); }, function(){ // success JuSy.log("[Html5Db] Database migrated to version : " + version); _doMigration(versions, migrations); } ); // end changeVersion() I know it's fighting a symptom instead of solving the problem, but I can't think of any other way... schory, not only does it not work on iPhone, it also doesn’t work on certain Safari versions because of a bug (id 27836, see https://bugs.webkit.org/show_bug.cgi?id=27836 )

I’ve found a workaround like this :

_db.changeVersion(_db.version, version,
function(tx){ // transaction
tx.executeSql(migrations[version]);
},
function(err){ // error
if (err.code == 2) {
// Safari bug 27836 probably occured
// changeVersion() will never work on a Safari version with this bug, so we need to do the transaction again, and manually maintain the version number
_doSafariBugMigration(versions, migration);
}
JuSy.log(err);
},
function(){ // success
JuSy.log(“[Html5Db] Database migrated to version : ” + version);
_doMigration(versions, migrations);
}
); // end changeVersion()

I know it’s fighting a symptom instead of solving the problem, but I can’t think of any other way…

]]> By: Max http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-305 Max Tue, 01 Jun 2010 17:56:16 +0000 http://blog.maxaller.name/?p=263#comment-305 Hmm, that's pesky. I'll see if there's anything I can do about it. I won't be able to test it on the iPhone, but of course I can test it on Safari for Windows. I'll send you an email when I update the post. Hmm, that’s pesky. I’ll see if there’s anything I can do about it. I won’t be able to test it on the iPhone, but of course I can test it on Safari for Windows. I’ll send you an email when I update the post.

]]> By: schory http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-304 schory Tue, 01 Jun 2010 07:45:05 +0000 http://blog.maxaller.name/?p=263#comment-304 Elegant and very useful! Sadly enough, Migrator won't work on iPhone because the new database version number becomes visible in Safari only in future sessions. See last paragraph in: http://developer.apple.com/safari/library/documentation/iphone/conceptual/safarijsdatabaseguide/usingthejavascriptdatabase/usingthejavascriptdatabase.html Any attentions on publishing a version that works around that problem? Is it possible to have Migrator check and update the version number only once while executing the entire migrations array? Elegant and very useful!

Sadly enough, Migrator won’t work on iPhone because the new database version number becomes visible in Safari only in future sessions. See last paragraph in: http://developer.apple.com/safari/library/documentation/iphone/conceptual/safarijsdatabaseguide/usingthejavascriptdatabase/usingthejavascriptdatabase.html

Any attentions on publishing a version that works around that problem? Is it possible to have Migrator check and update the version number only once while executing the entire migrations array?

]]> By: Max http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-274 Max Mon, 26 Apr 2010 16:33:09 +0000 http://blog.maxaller.name/?p=263#comment-274 Uh....gzip your javascript? :) That is a valid point. One solution I can think of is to break up your migrations into like groups of 10 or something, then detect which migrations a user needs to download, i.e. if I'm going from schema v15 to v25, I'll need to download migrations1.js and migrations2.js, but if I'm going from v24 to v25 I only need migrations2.js. Annoying, but I'm sure a system could be worked out for that fairly easily. Uh….gzip your javascript? :) That is a valid point. One solution I can think of is to break up your migrations into like groups of 10 or something, then detect which migrations a user needs to download, i.e. if I’m going from schema v15 to v25, I’ll need to download migrations1.js and migrations2.js, but if I’m going from v24 to v25 I only need migrations2.js. Annoying, but I’m sure a system could be worked out for that fairly easily.

]]> By: Geal http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-273 Geal Mon, 26 Apr 2010 09:56:38 +0000 http://blog.maxaller.name/?p=263#comment-273 Thank you, this is definitely useful! I was wondering how web developers expected to update their applications for users with different versions, and you answered it :) Now, the annoying question: won't the code become too big overtime, if you have to embed all the migration scripts? Thank you, this is definitely useful! I was wondering how web developers expected to update their applications for users with different versions, and you answered it :)

Now, the annoying question: won’t the code become too big overtime, if you have to embed all the migration scripts?

]]> By: opendatabase http://blog.maxaller.name/2010/03/html5-web-sql-database-intro-to-versioning-and-migrations/comment-page-1/#comment-265 opendatabase Fri, 02 Apr 2010 12:05:15 +0000 http://blog.maxaller.name/?p=263#comment-265 [...] (required) Website. This template is licensed under a Creative Commons Attribution-Noncommercial ...HTML5 Web SQL Database Intro to Versioning and Migrations ...If you specify it, the openDatabase method will fail unless the database matches the ... by setting [...] [...] (required) Website. This template is licensed under a Creative Commons Attribution-Noncommercial …HTML5 Web SQL Database Intro to Versioning and Migrations …If you specify it, the openDatabase method will fail unless the database matches the … by setting [...]

]]>