-
Notifications
You must be signed in to change notification settings - Fork 713
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Android openDatabase does not call success or error callbacks #110
Comments
Yup, this is a known issue. There's even a TODO right in the java code. To fix, it would basically be a one-liner. Pull requests are welcome! :) |
OK. Will do. |
…ng openDatabase()/db.close()/deleteDatabase() callbacks; double db.executeSql() callbacks; deleteDatabase() not reliable); small changes to deleteAndConfirmDeleted() helper function for existing test of sqlitePlugin.deleteDatabase()
Simple open callback test on WP(8) is working, test to open the same database twice does not pass on WP(8) version. |
My current WP8 build passes the double open test, as well as implementing close and delete. I'm stiull working on testing it in our app, but issue a pull request if that would be useful. |
On Thu, Aug 21, 2014 at 12:26 PM, Typhlosaurus notifications@github.com
Chris |
Certainly. Is it Ok if I simply give you the whole things as a Pull Mark |
On Thursday, August 21, 2014, Typhlosaurus notifications@github.com wrote:
Yes. I will just cherry-pick the commits that I need from the development Thanks again for your help. Please make sure that I get your name in the Chris Sent from my mobile |
Now fixed in |
The android implementation of openDatabase does not report a result, and hence never calls the success, Web SQL does not define an error callback, but SQLitePlugin.js does define one, and it too is not called.
I have not tested this on WP8 or iOS but by inspection the WP8 source should call the callbacks depending on whether valid parameters have been provided (not on actual database open success).
N.B. This can be worked around by immediatly executing any bit of legal SQL and recognising any database open errors.
The text was updated successfully, but these errors were encountered: