to alleviate the issues, recent sqlite builds feature a mode to activate that is called "WAL" , which you can read about at https://www.sqlite.org/wal.html . you can enable it just executing PRAGMA journal_mode=WAL once in the database . if you want to do it in web2py, run this code just once
db.executesql("PRAGMA journal_mode=WAL;") On Monday, July 27, 2015 at 2:35:54 PM UTC+2, jackso...@quantachrome.com wrote: > > In the web2py book chap 29: "Notice that in SQLite the database consists > of a single file. If it does not exist, it is created. This file is locked > every time it is accessed." I assume access meant reading or writing the > database > > On Friday, July 24, 2015 at 4:52:26 PM UTC-4, jackso...@quantachrome.com > wrote: >> >> The docs say that web2py locks a sqlite3 database file always...even if >> just reading. Is there a way to circumvent this so that my database writing >> process does have to wait for web2py reading the database? >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.