Hi: Assuming using SEE, do is there the ability to decide what I/O operations are to be performed encrypted or with the plain (as is) content?
I'm planning an application with only selected data encripted (in each row of certain tables, there is a flag showing the encrypted/plain state). Thanks in advance. > > ---- Mensaje original ---- > De: Richard Hipp <d...@sqlite.org> > Para: Paul Vercellotti <pverce...@yahoo.com>, General Discussion of SQLite > Database <sqlite-users@sqlite.org> > Fecha: Wed, 27 Jun 2012 21:28:30 +0200 > Asunto: Re: [sqlite] SQLite Encryption Extension Performance? > > >SEE is a drop-in replacement for public-domain SQLite. In other words, it >will read and write ordinary unencrypted database files, and it will do so >with no speed penalty. > >For performance sensitive applications, what developers sometimes do is >break up their content into sensitive and non-sensitive, storing each in >separate databases, and only encrypt the sensitive content. SEE is able to >open both databases at once (using the ATTACH command) and do joins on >tables between the two databases, even though only one of the two is >encrypted. > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
