Yep, these dot commands only mean anything to the sqlite3 command line
program, not SQlite itslef. I thought of executing a script to issue
the .time but honestly, the LC loop is 6 lines of code so it's not a
big deal to keep it in LC.
STill got to get around to doing my tests over a netwo
NVM I tried it. I guess it's only a shell command. Still, you might wanna try
shelling into the database before opening it and executing this command. Check
out this link:
http://www.sqlite.org/sqlite.html
Bob
> Have you tried this?
>
> .timeout MSTry opening locked tables for M
Have you tried this?
.timeout MSTry opening locked tables for MS milliseconds
Set that to 2000 for a 2 second "retry" on the cheap maybe?
Bob
On Nov 30, 2010, at 4:13 PM, Peter Haworth wrote:
> Good idea, but it got thrown back with an error. It's not a valid SQL
> statement, j
Good idea, but it got thrown back with an error. It's not a valid SQL
statement, just something the tcl/c api understands I think. Not a
big deal though, it's pretty easy to set that timeout loop in within LC.
Pete Haworth
On Nov 30, 2010, at 12:05 PM, Bob Sneidar wrote:
Did you try to is
Did you try to issue this as a query, with and without substituting db1 with
your database name?
Bob
On Nov 29, 2010, at 4:46 PM, Peter Haworth wrote:
>> db1 timeout 2000
>> The argument to the timeout method is the maximum number of milliseconds to
>> wait for the lock to clear. So in the e
rence to a lock timeout interval anywhere in the
SQLite documentation other than this article and another one that
describes the C/C++ API. I suspect the APIs implement the timeout
stuff internally.
I think SQLite locking will work OK for me but it is pretty
primitive. There really needs to be
I think the solution here is to wait until all user input is acquired, then do
the lock/write/unlock in a single blocking call. The only thing that would hurt
you here is a system lockup or disconnect during this very very brief moment of
time. Unlikely, but possible.
I read this in a writeup
eply-To: How to use LiveCode
Subject: SQLite Locking
The recent discussion on the pluses/minuses of using SQLIte and
associated locking mechanisms got my attention since I'm using SQLIte
and I expect my app to be used by a small number of users with an
occasional coincidence of more than 1 per
13:09:33
To: How to use LiveCode
Reply-To: How to use LiveCode
Subject: SQLite Locking
The recent discussion on the pluses/minuses of using SQLIte and
associated locking mechanisms got my attention since I'm using SQLIte
and I expect my app to be used by a small number of users wi
The recent discussion on the pluses/minuses of using SQLIte and
associated locking mechanisms got my attention since I'm using SQLIte
and I expect my app to be used by a small number of users with an
occasional coincidence of more than 1 person trying to change the
database at the same time
10 matches
Mail list logo
