Scott Leighton wrote:
I have finally succeeded in getting DBD::SQLite v 1.02 compiled and installed
on my AMD64 and have therefore started working with SQLite3. After reading
the documentation about locking and concurrency here
http://www.sqlite.org/lockingv3.html I am left with the impression that the
life of the -journal file on disk should be relatively limited. IOW, once the
transactions are committed, the -journal is deleted from disk.
I'm not seeing that here, the -journal file seems to sit there throughout the
life of the program (in this case, a deamon that runs in the background). In
fact, it remains on disk even after the program is terminated and only
disappears after the program is restarted (only to come back again,
presumably after a change to the db).
Is this the correct behavior or should I start looking for a problem with
either the perl program itself or DBD::SQLite?
You should start looking for problems. The -journal file should be deleted
the moment a transaction commits. In fact, transaction commit is defined
as the moment when the journal file is deleted. If the journal is never
deleted, then the commit never occurs.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
