from my experience if u running web2py on apache with mod_wsgi u will get
database locked more often than running web2py alone with it's buildin
webserver.
u should also avoid using session on sqlite database.
On Saturday, April 6, 2013 11:14:16 PM UTC+8, BlueShadow wrote:
I know that I
2013/4/7 vince lapcc...@gmail.com
from my experience if u running web2py on apache with mod_wsgi u will get
database locked more often than running web2py alone with it's buildin
webserver.
web2py + apache + mod_wsgi is my configuration.
ok, I will try the internal webserver.
u should
noo
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.
thanks Niphlod
I have the google app engine still active I guess thats the problem or at
least I hope so.
On Saturday, April 6, 2013 3:19:16 PM UTC+2, Niphlod wrote:
noo
for every request you are issuing that query once WAL is active,
there's no further need to issue that
Don't really know where you saw the 100k user statement
http://www.sqlite.org/whentouse.html
for every request you are issuing that query once WAL is active,
there's no further need to issue that statement
I agree, +1
editing a single table from multiple users ... no.
with WAL
I did check the version: 3.7.9
So it should be fine.
I got very little db writes like I said 30 users a day and incresing an
integer per page view is about all I do.
On Saturday, April 6, 2013 3:29:24 PM UTC+2, Vasile Ermicioi wrote:
Don't really know where you saw the 100k user statement
and are you sure that wal is enabled?
--
---
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
so, you're writing to the db for every page every user hits. expect other
lockings, even with SQLite with WAL.
On Saturday, April 6, 2013 3:41:26 PM UTC+2, BlueShadow wrote:
I did check the version: 3.7.9
So it should be fine.
I got very little db writes like I said 30 users a day and
On Saturday, April 6, 2013 3:29:24 PM UTC+2, Vasile Ermicioi wrote:
Don't really know where you saw the 100k user statement
http://www.sqlite.org/whentouse.html
Make a simple app (even with less bloated frameworks) that writes to a db
every time a user hits a page. I bet I can lock
How can I test if wal is enabled?
On Saturday, April 6, 2013 3:54:10 PM UTC+2, Vasile Ermicioi wrote:
and are you sure that wal is enabled?
--
---
You received this message because you are subscribed to the Google Groups
web2py-users group.
To unsubscribe from this group and stop
I know that I will eventually have that problem. thats why I got the plan
to migrate to postgres when I got more time. the problem with postgres
migration is that I used a couple field names which you are not allowed to
use in postgres so I can't simply move the db with me thats quite a bit of
this statement
PRAGMA journal_mode
returns the current journal mode. By default should return delete, while
if the db is in WAL mode, it returns wal
On Saturday, April 6, 2013 5:11:16 PM UTC+2, BlueShadow wrote:
How can I test if wal is enabled?
On Saturday, April 6, 2013 3:54:10 PM
[(u'wal',)]thats what the db.executesql(PRAGMA journal_mode) returns. :(
I guess I have to migrate faster.
--
---
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
If I would change from SQlite to another system, what do you propose?
2013/4/6 BlueShadow kevin.bet...@gmail.com
[(u'wal',)]thats what the db.executesql(PRAGMA journal_mode) returns. :(
I guess I have to migrate faster.
--
---
You received this message because you are subscribed to the
14 matches
Mail list logo
