If there were problems, then Dr. H wouldn't sell it ... The SEE extensions add a couple new API calls, specifically sqlite_key() and rekey() functions to specify the password (or change the password) for an encrypted database. Other than that, your code remains the same.
I'm pretty sure the license requires that you compile with extensions with your app, or at the very least, if compiled in a library, your library wraps your specific implementation. In otherwords, no compiling a generic sqlite library with SEE extensions and handing it out so everyone can use SEE for free. -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Andi Suhandi Sent: Saturday, October 03, 2009 11:52 AM To: sqlite-users@sqlite.org Subject: [sqlite] SQLite Encryption Extensions(SEE) for SQLite Dear All Hi, I was using sqlite as a database for my program. My program is based on C++ . Well, for my next project I want encryt the database, and I read about SQLite Encryption Extensions(SEE). My questions : 1. Are there problems if I add SEE ? 2. Do I have change a lot in my program ? 3. How to add SEE to my source code (including header, dll, etc that I have to add and the function that I call sequencially) Thank you -- Andi Suhandi Software Engineer Support _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
