--- Zbigniew Baniewski <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 16, 2007 at 05:47:07PM -0700, Trevor Talbot wrote:
>
> > The default locking mechanism relies on the underlying filesystem to
> > provide the needed locking guarantees. In this case, the OP is
> > needing to access a database on a networked filesystem, and many
> > networked filesystems are unable to provide proper locking. So no, if
> > the underlying filesystem is "broken", the database is not protected.
>
> And what you mean about sharing SQLite's database file - among WinXP-driven
> computers - in "network neighborhood"? Does Window's filesystem assure
> enough protection?
You can do a crude check to verify it with the sqlite3 commandline shell
and 3 networked computers: A, B, C. (any OS).
Host a shared database file on computer A, say shared.db.
>From computer B, open shared.db remotely and execute "BEGIN EXCLUSIVE;".
>From computer C, open shared.db remotely and execute "BEGIN EXCLUSIVE;".
If computer C has the error "SQL error: database is locked", then
its locking probably works.
Repeat the test with just 2 computers to test local locking versus remote
locking.
____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
