Try to commit the database in shell. That should take the lock off. On Wednesday, March 25, 2015 at 5:02:40 AM UTC-4, Roberto De Ioris wrote: > > > > Hello Peter. > > > > I've got also a problem with scheduler/sqlite, "OperationalError: > database > > is locked". > > Have you found a solution? > > > > Thanks. > > > > > > > You can't generally solve it. > > Sqlite has a pretty "weak" concurrent support, so if a process try to do > something while another has initiated a still-uncommitted transaction you > get that error. > > You should find various posts about it (for the various languages), there > is some trick, but generally if you need strong concurrency sqlite is not > a good solution. > > > -- > Roberto De Ioris > http://unbit.com >
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
