This problem is definitely at Sqlite level. "Everything seems to be all right when I test it" == single user
"but with as few as 2 simultaneous users I (sometimes) run into trouble" == database locked by transaction Sqlite has no problems with concurrency, it is a simple, fast, very high quality, single-user database engine by design. Its limitations precisely defined in its docs, for example here: http://www.sqlite.org/threadsafe.html In Sven's case I suggest to replace it with PostgreSQL (for example). On Apr 2, 7:56 am, Vasile Ermicioi <elff...@gmail.com> wrote: > problems could be at any levels: flash, sqlite, pyamf, web2py > > sqlite is known to have problems with concurrency.. > > what is the remote error that you get? (even if you consider it not too > important) > > web2py usually creates tickets when is a problem at the web2py level (server > side execution code) -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
