Use Android's Sqlite abstraction instead of raw android.database.* classes.

[yesitskev]

Could there be some investigation and perhaps implementation of a mechanic to allow for switching between Android's default SQLite engine or one issued by Requery?

@JakeWharton have you given this any thought?

[AlecKazakova]

seems like something worth forking for? It shouldn't require many changes but it would have to depend on requery/sqlite-android which i doubt sqlbrite ever will.

[JakeWharton]

A shim was proposed for SQLCipher support already and we rejected it. It's
highly unfortunate Android's APIs aren't abstracted to be reused. Maybe we
should push for an official support library for this? That would be
something we would support then.

On Tue, May 10, 2016 at 6:46 PM Alec Strong notifications@github.com
wrote:

seems like something worth forking for? It shouldn't require many changes
but it would have to depend on requery/sqlite-android which i doubt
sqlbrite ever will.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#109 (comment)

[JakeWharton]

Vote (not comment) on http://b.android.com/202658. We're going to try to push this issue first.

[JakeWharton]

Here's the rejected SQLCipher change for reference: #101

[JakeWharton]

Waiting for the first-party SQLite abstraction to reach 1.0 before we can depend on it.

[JakeWharton]

Can't wait for this. Will have to be a V3.