Maybe I'm the only one still using the classic Mac code path in SQLite, but for the record I'll describe a problem I had with Norton AntiVirus. It was causing sqliteOsDelete to fail with a file-busy error, presumably because NAV was checking the file for viruses, and then a subsequent attempt to recreate the file failed. I fixed it by making sqliteOsDelete call the BSD version of unlink when running on Mac OS X.

In analyzing this problem, I wondered whether it might be inefficient for SQLite to be continually deleting and recreating the same journal file. I saw the comment above sqliteOsOpenExclusive saying that "To avoid a potential security problem, we do not allow the file to have previously existed." I'd be interested to know what that security problem is.
--
James W. Walker, ScriptPerfection Enterprises, Inc.
<http://www.write-brain.com/>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to