Martin Alfredsson wrote:
Hi !
Tried to solve a problem and what I did was to open the
database over the net and then physically disconnect
the machine.
I can still SELECT !
sqlite3_prepare() works and gives SQLITE_OK
sqlite3_step() gives SQLITE_ROW but is very, very slow
sqlite3_finalize() works.
First when I do INSERT/UPDATE/DELETE I get an error.
Is this normal ?
I understand that parts of the database could be cached
but then the time to do sqlite3_step() should not be affected.
Or is the code doing sqlite_stop() and when it does not get
a reply it takes a cached copy ????
/Martin
SQLite shouldn't be used in a network share.
Sometimes it works, sometimes it doesn't.
From http://www.sqlite.org/whentouse.html
Situations Where Another RDBMS May Work Better
* Client/Server Applications
If you have many client programs accessing a common database over
a network, you should consider using a client/server database
engine instead of SQLite. SQLite will work over a network
filesystem, but because of the latency associated with most
network filesystems, performance will not be great. Also, the file
locking logic of many network filesystems implementation contains
bugs (on both Unix and windows). If file locking does not work
like it should, it might be possible for two or more client
programs to modify the same part of the same database at the same
time, resulting in database corruption. Because this problem
results from bugs in the underlying filesystem implementation,
there is nothing SQLite can do to prevent it.
A good rule of thumb is that you should avoid using SQLite in
situations where the same database will be accessed simultaneously
from many computers over a network filesystem.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
