noooooooooooooo
for every request you are issuing that query.... once WAL is active,
there's no further need to issue that statement, unless you revert to the
default journal mode or delete phisically the file.
remove also the part of "if request.env.web2py_runtime_gae" if you're not
using it.
Don't really know where you saw the 100k user statement.....SQLite performs
pretty well as long as you read from it, so blog application without
comments? yes .... blog without user interactions ? yes ..... editing a
single table from multiple users ... no.
As soon as you start to write in it and even with 5 concurrent users you'll
get your db locked at some point.
On Saturday, April 6, 2013 2:23:28 AM UTC+2, BlueShadow wrote:
>
> Hi,
> i got a couple of errors today which tell me the database is locked. I
> know I'm using sqlite. which is less than ideal. I got about 30 users a day
> which should be perfectly fine with SQLite.
> Especially since I added this part of code:
>
> if not request.env.web2py_runtime_gae:
> ## if NOT running on Google App Engine use SQLite or other DB
> db = DAL('sqlite://storage.sqlite', migrate=False)
> try:
> db.executesql("PRAGMA journal_mode=WAL;")
> except:
> pass
> Or do I have to add something else to enable the write ahead option?
> from the things I read SQLite should be usable upto 100k Users a day with
> this WAL.
>
> I tired to migrate to postgresql but since there are a couple things which
> are not allowed in postgres (for example: Field "Content") I have to move
> the db manually which will have to wait quite a bit.
>
>
--
---
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/groups/opt_out.
