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
George Ionescu wrote:
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'
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
Is there any way to backup a database so it leaves the backup file and the
original vaccum'ed?
That way one could use cron, at, or whatever to programatically run a backup
using the shell or alike to backup databases and keeping the new ones
vacuum'ed. It would be useful.
Refactoring vacuum.c?
On Thu, 9 Sep 2004, Steven Van Ingelgem wrote:
I just noticed something rather stupid...
when you .dump a table via the sqlite.exe binary (2.8.15)... It dumps first
the create table, then the inserts, and afterwards the indexes
Now if you have a very big table it will take a LOT of time to
Just confirming that the patched code (cvs checkout this morning @ 8
AM PDT) works on the Opteron machine w/Gentoo 2004.1 amd_64 mentioned
earlier in this thread. Cool! Only two glitches left:
2 errors out of 14857 tests
Failures on these tests: printf-8.1 printf-8.2
the errors are
Al Danial wrote:
Just confirming that the patched code (cvs checkout this morning @ 8
AM PDT) works on the Opteron machine w/Gentoo 2004.1 amd_64 mentioned
earlier in this thread. Cool! Only two glitches left:
2 errors out of 14857 tests
Failures on these tests: printf-8.1 printf-8.2
the
