The fix is very simple - uninstall the SVN software which causes the
problem. I would imagine that Sqlite is not the only piece of software
which expects to have exclusive access to its journals.
Sqlite can be changed for Windows so that it can live with other
processes messing with its journal, and probably should be since there
will always be anti-virus and similar activity on Windows. My guess is
that allowing read sharing on the journal on Windows would be sufficient
and not create parasitic problems.
JS
Costas Stergiou wrote:
Can someone propose a reasonable workaround until this issue is fixed?
Is "synchronous=off" really a solution? Or there is a failure 'behind' the
scenes' that is just overlooked?
Not really knowing how difficult it is to overcome this issue (and just
trying to add an 'objective' opinion), I could just say that it is
reasonable to expect consistency from a db engine, no matter what the
underlying deficiencies.
I cannot think of oracle or mysql claiming that due to a Windows buggy
implementation, the database may fail occasionally and unexpectedly!
I will need to admit thought that the limit is a bit vague here...
Costas
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Δευτέρα, 5 Ιουνίου 2006 12:27 πμ
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] reasonable assumptions
Dave Dyer <[EMAIL PROTECTED]> wrote:
I think this is a very reasonable assumption.
It's a lot easier to drive if you assume you're the only
car on the road.
I think a more apt analogy is that it is easier to
drive when the stearing wheel is not jerked out of
your hand at random intervals.
--
D. Richard Hipp <[EMAIL PROTECTED]>
