Hello,
I have a simple database that took quite a bit of work to build. I would like to have this encrypted when I install it with my app. Before using the database I would load it into memory unencrypted.
I understand SQLite does not support database encryption.
I thought of the following scenario:
Suppose I include the database as an encrypted SQL record dump or encrypted CSV text file with my application.
On startup I would load and decrypt the dump or CSV file, hopefully into memory, or maybe to a temporary Android filesystem file.
I would then import to create a temporary, in memory, SQLite database from the SQL dump or CSV.
Does this sound reasonable? Is there a better way?
Is it possible to work with in-memory data streams or create in-memory files. I would prefer that nothing decrypted ever resides in the Android filesystem.
Thanks,
Barry.
I have a simple database that took quite a bit of work to build. I would like to have this encrypted when I install it with my app. Before using the database I would load it into memory unencrypted.
I understand SQLite does not support database encryption.
I thought of the following scenario:
Suppose I include the database as an encrypted SQL record dump or encrypted CSV text file with my application.
On startup I would load and decrypt the dump or CSV file, hopefully into memory, or maybe to a temporary Android filesystem file.
I would then import to create a temporary, in memory, SQLite database from the SQL dump or CSV.
Does this sound reasonable? Is there a better way?
Is it possible to work with in-memory data streams or create in-memory files. I would prefer that nothing decrypted ever resides in the Android filesystem.
Thanks,
Barry.