"Bert Nelsen" <bert.nel...@googlemail.com> schrieb
im Newsbeitrag
news:a5ffd530912311004p26a7cc5k1f1bf6f671bef...@mail.gmail.com...
> Your .Sychronous = False property does everything
> as fast as I want, and I am not afraid of losing some
> user data (it's not a critical application) but
> I am very much afraid of having a corrupted db.
> Can anybody please confirm
> that there is no chance of getting my db corrupted?
Ah, I see now, where the "confusion" came from.
The wrappers Synchronous-Property has nothing to do
with the (relative new) async-writer-feature of SQLite -
instead it maps to SQLites Synchronous PRAGMA
(as a "convenience property").
You can set all the Pragmas alternatively also per
Cnn.Execute "PRAGMA pragma_name ..."
or read out a current Pragma-Value with:
Cnn.OpenRecordset("PRAGMA pragma_name")(0).Value
Please read about SQLite-Pragmas here:
http://www.sqlite.org/pragma.html
... and what's written there about the Synchronous-Pragma-
Settings. With the Synchronous-Pragma at 'Off' or '0', you're
risking DB-corruption.
So, I would not touch the Synchronous-Property in your
case (leaving it at its default FULL(2)) - instead you should
wrap larger insert- or update-actions within a transaction -
that works fast as well.
Also consider using the binding-support of the wrapper
(the Command-Objects), to achieve faster (and more
typesafe) operations in "write direction".
Olaf Schmidt
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
