On Sat, Sep 28, 2013 at 1:04 AM, Simon Slavin <[email protected]> wrote:
> Frankly, if you're using SQLite as a mutex base you'd do better using the > presence or absence of a file instead. To signal that your database is > locked, create a file. If, when you create the file, you get an error > message, some other process/thread has the database locked. > In my case a dot lock would be bad because it could leave a stale lock and i'm only available for this customer once per week (so they'd be a week offline worst-case). Had i thought about it, i would have investigated flock() first, but it didn't occur to me that PHP supports that. i simply could have locked the PHP file being executed. The sqlite solution is in place now, so i'll leave it there. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
