I have a really weird problem.
I need to create a custom sqlite3 database engine under Android OS, but I also want to use a database provider implementation. Unfortunately, while studying the sources of Android 1.6, I noticed that this is not so simple.
Many classes, including android.database .; packages use the original provider, and many other parts of the framework use android.database.sqlite .; packages that, of course, make this abstraction a bit confusing and unattractive.
But I will turn to my question. Should there be any way to extend the database interfaces to use sqlite custom implementation (or any other database)?
source
share