Re: [sqlite] Random locking errors using Sqlite.NET

[Mike King]

Are you accessing data off the share as well? The Sqlite website is quite
categoric that this is not a recommended mode of operation. Also given the
database locks when a record is written it is entirely possible one user is
locking the table.

Cheers,
Mike

On Tuesday, 4 November 2014, Mike McWhinney  wrote:

> Hello,
>
> I continue to have random errors on SQLite.NET (ADO provider).  I have the
> version 3.8.6 (System.Data.SQLite.dll with version 1.0.94.0).
>
> I am getting random locking errors during the execution of my program. The
> program resides on a network and each client has a mapped share
> with full read/write access to the folder as well as the .db file used by
> SQLite.
>
> In my connection string I have the following:
>
> public static string OMconnectionString = "URI=file:oslermedicine.db;
> Default Timeout=10; Pooling=True; Max Pool Size=100;";
>
>
>
> What might I be doing wrong? I am disposing of all objects (data readers,
> tables, commands) after use.
>
> Thanks
> Mike
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org 
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Random locking errors using Sqlite.NET

[Simon Slavin]

On 4 Nov 2014, at 5:45pm, Mike McWhinney  wrote:

> I am getting random locking errors during the execution of my program. The 
> program resides on a network and each client has a mapped share
> with full read/write access to the folder as well as the .db file used by 
> SQLite.

I don't know if this is what's causing your specific problem, but ...



"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."

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Random locking errors using Sqlite.NET

[Mike McWhinney]

Hello,

I continue to have random errors on SQLite.NET (ADO provider).  I have the 
version 3.8.6 (System.Data.SQLite.dll with version 1.0.94.0).

I am getting random locking errors during the execution of my program. The 
program resides on a network and each client has a mapped share
with full read/write access to the folder as well as the .db file used by 
SQLite.

In my connection string I have the following:

public static string OMconnectionString = "URI=file:oslermedicine.db; Default 
Timeout=10; Pooling=True; Max Pool Size=100;";
   


What might I be doing wrong? I am disposing of all objects (data readers, 
tables, commands) after use.

Thanks
Mike
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users