[EMAIL PROTECTED] uttered:
Jens Miltner <[EMAIL PROTECTED]> wrote:
OTOH, our customers might also have antivirus software installed, so
this still would not be a solution :(
Does anybody have advice on how to make sqlite work smoothly with
antivirus software [on Windows]? (Probably depends on the antivirus
software?)
Virus scanners will slow things down and cause problems.
This is the fault of the virus scanners and SQLite cannot
really do much about it.
But there have been *some* changes to try to work around
the virus scanner problem. See, for example,
http://www.sqlite.org/cvstrac/chngview?cn=3200
Looking at this reminded me. What is the point of deleting the rollback
log? Why not just truncate it when committing a transaction, and deleting
it only when closing the database?
The benefits could be:
- Improved performance:
- No delete of the rollback log to cause synchronous IO on the
directory.
- Only need to create the rollback log when it doesn't exist. Else,
just the existing empty one.
- Would play better with Virus scanners on Windows. No deleting of the
rollback log would cause no file locked errors until we're closing the
database.
So long as the rollback code handled the case of the rollback journal not
being present, this should be backward compatible with existing versions.
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
