If you only need Windows compatibility you can use the System.Data.SQLite
port.  It's made for ADO.NET but it is also binary compatible with SQLite
and can be used from C code.  It includes Windows-specific encryption and is
free.

http://sqlite.phxsoftware.com/

With the ADO.NET stuff it's larger than SQLite but you can also compile it
without the ADO.NET parts pretty easily.

HTH,

Sam 


-------------------------------------------
We’re Hiring! Seeking a passionate developer to join our team building
products. Position is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
 
-----Original Message-----
From: Luís Santos [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 18, 2007 7:53 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Filesystem Layer problems

Hi, people

We have managed to add a simple obfuscation layer to SQLite on windows 
platform; this has been working since version 3.0.8, but We've found a 
problem on the last versions.

We've introduces a simple stream criptography layer on two functions on 
/os_win.c/ (winRead and winWrite).

The problem is: everytime a database crashes and has to be restored, we 
loose it. That happens also when an error is thrown within a trigger.

We haven't followed so closely the last changes on SQLite 
infrastructure, so I need ask for your help into it.

Is there something else I need to do now to implement my layer, what 
changed in the journal?

Thanks in advance.

--
Jason Santos


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to