On 19 Feb 2011, at 11:40pm, Robert Hairgrove wrote: > This works fine, but I would like to offer the user the option to > encrypt the database before writing it to disk. If it is encrypted, they > would need to decrypt it again when it was loaded into memory (duh!)
An alternative to the 'straight SQLite' solution would be to write your own routine to dump to disk instead of using the backup API. I have no idea whether this would be better or worse, but it could be done without learning intimate details of SQLite and should be easier to adapt and modify for different platforms and database engines. It would also mean the disk version of the database was in a format that could be read by a program which didn't have SQLite compiled into it. You could start from something like 'SELECT * FROM mytable' or even using 'group_concat()' on each column. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
