Re: SQLite Locking

2010-12-01 Thread Peter Haworth
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

Re: SQLite Locking

2010-12-01 Thread Bob Sneidar
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

Re: SQLite Locking

2010-11-30 Thread Bob Sneidar
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

Re: SQLite Locking

2010-11-30 Thread Peter Haworth
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

Re: SQLite Locking

2010-11-30 Thread Bob Sneidar
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

Re: SQLite Locking

2010-11-29 Thread Peter Haworth
I'm kinda doing that. In some cases, the db update consists of several insert operations which would leave the db in an inconsistant state if any of them failed before they all completed. So after getting all the input, I lock the db, do all the insertions, then unlock it. If any proble

Re: SQLite Locking

2010-11-29 Thread Bob Sneidar
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

Re: SQLite Locking

2010-11-27 Thread Peter Haworth
Yep, the SQLite docs have some words about that, especially when using NFS. Since I'm running on a Mac and so will the other users of may app) I was glad to see: The versions of SQLite that come preinstalled on Apple Mac OS X computers contain a version of SQLite that has been extended to

Re: SQLite Locking

2010-11-27 Thread jonathandlynch
You might want to check to see if the locking works as desired across a network connection - not all networks do file locking properly. Sent from my Verizon Wireless BlackBerry -Original Message- From: Peter Haworth Sender: use-livecode-boun...@lists.runrev.com Date: Sat, 27 Nov 2010 13