Hello Andrey,
you could be right with the timeout, because every time I read a large
dataset from the database, I get the mentioned error.
I went for sqlite, because it is really easy to set up and the sqlite
homepage [1] mentions, that it works great with database engines ("SQLite
usually will work great as the database engine for low to medium traffic
websites"). However, maybe you are right and I should try some other
database systems.
On Monday, October 7, 2013 3:54:25 PM UTC+2, Andrey Kuzmin wrote:
>
> Perhaps it is caused by db operations taking too much time, so timeout
> occur while waiting for db to be available in concurrent request.
> Sqlite is not designed for production use, have you considered switch to
> another db?
>
> On Monday, October 7, 2013 4:10:48 PM UTC+4, Bernhard B wrote:
>>
>> Unfourtanely, the error is back. With the web.py database wrapper, the
>> 'database is locked' error doesn't occur as often as without the wrapper,
>> but it still occurs. Does anybody have an idea what the problem could be?
>>
>
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/webpy.
For more options, visit https://groups.google.com/groups/opt_out.
