On Mon, 10 Nov 2014 20:33:04 +0200
RSmith wrote:
>
> On 2014/11/10 20:22, Mike McWhinney wrote:
> > So SQLite shouldn't be used at all on a network? Aren't there any
> > other provisions to handled the locking errors if/when they occur?
>
> It is not about SQLite, it is about the Networking sy
On Mon, Nov 10, 2014 at 12:56 PM, wrote:
> On 2014-11-10 18:33, RSmith wrote:
>
>
>> There is one Client-Server implementation of SQLite (SQLightening I
>> think) but it is neither free nor easy to convert to.
>>
>
> Doing some Googling, this looks like the thing:
>
> http://sqlitening.com
>
>
On 10 Nov 2014 at 19:38, Mike McWhinney wrote:
> I am using Sqlite.NET client in C#. How would I go about defining a sqlite
> busy timeout handler?
Is the API not documented somewhere (I don't know what Sqlite.NET client or C#
are, so can't help)? Surely you must have some doc or how else do y
On Mon, Nov 10, 2014 at 12:56 PM, wrote:
> On 2014-11-10 18:33, RSmith wrote:
>
>
>> There is one Client-Server implementation of SQLite (SQLightening I
>> think) but it is neither free nor easy to convert to.
>>
>
> Doing some Googling, this looks like the thing:
>
> http://sqlitening.com
>
>
On 2014-11-10 18:33, RSmith wrote:
There is one Client-Server implementation of SQLite (SQLightening I
think) but it is neither free nor easy to convert to.
Doing some Googling, this looks like the thing:
http://sqlitening.com
They don't seem to sell it any more (last version was released
I am using Sqlite.NET client in C#. How would I go about defining a sqlite busy
timeout handler?
Thanks
Mike
On Monday, November 10, 2014 1:35 PM, Tim Streater
wrote:
On 10 Nov 2014 at 18:22, Mike McWhinney wrote:
> So SQLite shouldn't be used at all on a network? Aren't there any
On 10 Nov 2014 at 18:22, Mike McWhinney wrote:
> So SQLite shouldn't be used at all on a network? Aren't there any other
> provisions to handled the locking errors if/when
> they occur?
You tried setting a timeout as pointed to here?
https://www.sqlite.org/faq.html#q5
(not that this would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 10:22 AM, Mike McWhinney wrote:
> So SQLite shouldn't be used at all on a network? Aren't there any
> other provisions to handled the locking errors if/when they occur?
Network filesystems do not implement locking and other operations
*
On 10 Nov 2014, at 6:22pm, Mike McWhinney wrote:
> So SQLite shouldn't be used at all on a network?
SQLite is not designed for hosting a database on a server for access by lots of
different computers at the same time. To do that efficiently you need a
client/server design and SQLite doesn't
On 2014/11/10 20:22, Mike McWhinney wrote:
So SQLite shouldn't be used at all on a network? Aren't there any other
provisions to handled the locking errors if/when
they occur?
It is not about SQLite, it is about the Networking systems lying about whether a file is locked or not. No RDBMS can
So SQLite shouldn't be used at all on a network? Aren't there any other
provisions to handled the locking errors if/when
they occur?
On Monday, November 10, 2014 12:10 PM, Roger Binns
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 09:41 AM, Mike McWhinney wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 09:41 AM, Mike McWhinney wrote:
> Please let know if there are any other solutions to this database
> locking problem as used on a network.
Yes. Do not do it. See the FAQ:
https://www.sqlite.org/faq.html#q5
Roger
-BEGIN PGP SI
Hello,
I continue to have "database is locked errors" when running an application
which accesses a SQLite dabase on a network.
I have tried many of the connection string options: pooling, changing default
time out.
I just recently tried a block of code which does a BeginTransaction and Commi
13 matches
Mail list logo
