We made the mods in os_win.c, in the read and write routines, after the read and before the write. A more robust solution would have been to modify the code in os_mac.c and os_unix.c as well, but we didn't need that. It was very easy and the only caveat is that once you modify it, it will no longer read existing databases. That was not a problem for us, but it might be if you want to convert a database.

Joey.

At 06:11 PM 9/9/2004, you wrote:
Joey,

Where in the code did you do that?  Was it easy to put in one or two places?

-brett

try IeToolbox Passwords & Notes Keeper, Form Filler and much more
www.ietoolbox.com



Joey Blankenship wrote:

Not to respond out of turn here, but we had a need to obfuscate the plain text (due to some users that are a little too curious for their own good) that was stored but did not want the performance burden that encryption/decryption would place on the PocketPC. Prior to writing and subsequent to reading, we just perform a simple mangle of the read/written data. A byte NOT or XOR works pretty well and does not cause an extreme performance hit. Again, no real encryption, but it hides the data from casual viewing.

Joey.

At 05:34 AM 9/9/2004, you wrote:

Hello sqlite users,
Hello Dr. Hipp,

I would like to know if there is a way to encrpyt the data stored in the database but to still be able to use SQL queries with plain text, something like

CREATE TABLE TEST (fld)
INSERT INTO Test VALUES ('some string')
SELECT * FROM Test WHERE fld = 'some string'

but, when the sqlite database is opened in a file viewer, 'some string' would not be visible but only it's encrypted form.

Regards,
George Ionescu





Reply via email to