Re: [sqlite] SQLite.NET Class Library Documentation Feedback: Limitations

2016-10-05 Thread Jens Alfke

> On Oct 5, 2016, at 5:49 AM, Santiago Bayeta  wrote:
> 
> But I also read from SQLite docs that now SQLite supports unlimited Reading 
> operations while writing.

It does if the databases uses a WAL (Write-Ahead Log). This is a persistent 
per-database setting that can be enabled by a ‘pragma’ call.

> I just wanted to ask whether SQLite.NET  supports this 
> latter locking.

It will, unless it tries to do its own locking above SQLite. For instance if it 
uses a C# read-write lock that prevents other threads from making SQLite calls 
at all while one thread is in a transaction, because it “knows” that they’d 
just block.

But if it just stays out of the way and lets your code call the database, it 
should be OK. It wouldn’t be hard to write a little test app to see if this is 
the case.

—Jens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] SQLite.NET Class Library Documentation Feedback: Limitations

2016-10-05 Thread Santiago Bayeta
Hi,

I’m just starting with SQLite.NET and found this in the documentation (chm file 
downloaded from sqlite.org).

“When a connection locks the database for writing, no other connection or 
process may read or write to the database until the write operation is 
complete.”

But I also read from SQLite docs that now SQLite supports unlimited Reading 
operations while writing.

I just wanted to ask whether SQLite.NET supports this latter locking.

Thanks,
Santiago

Enviado desde Correo para 
Windows 10

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


[sqlite] SQLite.NET Class Library Documentation Feedback: Limitations

2015-06-08 Thread Saurabh Gupta
Is the following statement still relevant even with write ahead logging mode
of latest sqlite



"..timeouts will only occur if one thread is attempting to read while
another thread is attempting to write.."



Saurabh