On Wed, 17 Apr 2013 15:39:50 +0200 "J Trahair" <[email protected]> wrote:
> I'm looking for a way to ensure other users aren't allowed to write > to the database during this quarter-second period. That might work for you this time, but it doesn't scale well; historically that's why the DBMS took over locking. You might instead want to consider a more relational approach. For example, you could have a "current version" table somewhere with one row. Various tables would have "version" columns. The application could select from views that join to the current-version table. Your update could add rows with a new version, update the current-version row, and at its leisure delete rows for the prior version. Because the update is atomic, the transition is instantaneous; no one is ever blocked but for an instant. Of course I don't know specifically what you're trying to do. I'm just saying that lock-the-world isn't a general solution, and the DBMS supports many general alternatives. --jkl _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
