Sqlcipher support #38
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
goal: support either SQLite or SqlCipher.
design: abstract the common behavior into the interfaces Database and OpenHelper and implementations of
these. for SQLite the library uses AndroidSQLiteDatabase and ProviGenSQLiteOpenHelper. for SqlCipher it
uses SQLCipherDatabase and ProviGenSQLCipherOpenHelper.
use: an application using SQLite should use ProviGenSQLiteOpenHelper in its ContentProvider in place of
SQLiteOpenHelper. for SqlCipher, the application uses ProviGenSQLCipherOpenHelper. SqlCipher also requires
the app to make to calls:
SQLiteDatabase.loadLibs(getApplicationContext());
ProviGenSQLCipherOpenHelper.setPassword("swordfish");
these are usually called in Application.onCreate(). they should be called before any use of the database.
loadLibs() is required for any app using SqlCipher. as the SqlCipher database file is encrypted call
ProviGenSQLCipherOpenHelper.setPassword() to provide the password used to decrypt it.
a new sample, ProviGenSqlcipherSample, shows how to use SqlCipher with ProviGen.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
i use sqlcipher and like ProviGen so i'm sending the code i did to allow them to work together. from the comment comment:
goal: support either SQLite or SqlCipher.
design: abstract the common behavior into the interfaces Database and OpenHelper and implementations of these. for SQLite the library uses AndroidSQLiteDatabase and ProviGenSQLiteOpenHelper. for SqlCipher it uses SQLCipherDatabase and ProviGenSQLCipherOpenHelper.
use: an application using SQLite should use ProviGenSQLiteOpenHelper in its ContentProvider in place of SQLiteOpenHelper. for SqlCipher, the application uses ProviGenSQLCipherOpenHelper. SqlCipher also requires the app to make to calls:
SQLiteDatabase.loadLibs(getApplicationContext());
ProviGenSQLCipherOpenHelper.setPassword("swordfish");
these are usually called in Application.onCreate(). they should be called before any use of the database. loadLibs() is required for any app using SqlCipher. as the SqlCipher database file is encrypted call ProviGenSQLCipherOpenHelper.setPassword() to provide the password used to decrypt it.
a new sample, ProviGenSqlcipherSample, shows how to use SqlCipher with ProviGen.