Transaction object is getting lost

[ghost]

I am using this plugin for one of my phonegap project. I am facing issue with the database transaction object. I am calling one android activity from javascript and after finishing that activity, i am trying to access database using "db.transaction" call, but it is unable to call the transaction and it is not giving any error also. After debugging, when i commented line 1 & 2, it started to work but now sometimes transaction call is behaving randomly.

SQLitePlugin.prototype.addTransaction = function(t) {
this.txQ.push(t);
if (this.txQ.length === 1) { ----->Line 1
t.start();
} ------>Line 2
};

Kindly suggest me what exactly this code is doing.

[nolanlawson]

This plugin does not currently work with multi-page architecture or with multi-activity Android apps. Sorry about that; it's a big TODO that we never got around to.

Just FYI, you do know that the native Web SQL database is supported in every WebView back to Android 2.2, yes? You can just follow these steps to enable it, and then you don't even need this plugin. In fact on Android, this plugin is slower than the native Web SQL database and offers no advantages that I'm aware of.

[nolanlawson]

Also on PhoneGap, I believe it does those steps by default, so you can just call window.openDatabase() and you're done.

[brodycj]

FYI there are two major advantages of this plugin on the Android platform: database will be in a known location (always) and there is no practical limitation to the database file size.

[nolanlawson]

@brodybits You're right; I'm sorry for being so glib. The known location thing is incredibly useful; pre-Android 4.4. you could actually tell the WebView where to store WebSQL databases, but post-4.4 that's not an option anymore.

[brodycj]

A less buggy sqlite plugin would be nice, though.

I suspect the issue #193 (Android not saving the inserts upon abnormal exit) is due to changes in android / platform_external_sqlite - I am thinking in commit d4f30d0. The workaround to close and reopen the db for every transaction (which I am planning to support in an openDatabase option) is pretty bad. Hopefully the Android team will fix it someday 😄