On my not-so-limited experience with SQLite and multiprocessing, I found out that it's a real PITA even with WAL enabled.
If you turn on DEBUG logging, the amount of lines logged is going to block operations just for logging sake, so I'd definitely not recommend SQLite as a logging backend for the scheduler (as I don't recommend it for being the backend for multiple scheduler's running). A single scheduler instead is fine, but at least in my usecases I always use at least 2 or 3 of them. @spies: sorry for the digressions, any luck figuring out what database backend you're using ? -- 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/groups/opt_out.
