> Hot to activate SQLite WAL when using DAL?
>
you need to have a sqlite3 (or pysqlite2) linked to a sqlite version >=
3.7.0.
There are two version number: the module itself and the linked static
library (.so on unix and .dll on Windows)
>>> import sqlite3 #or from pysqlite2 import dbapi2 a
Hot to activate SQLite WAL when using DAL?
Dne čtvrtek, 26. července 2012 10:04:23 UTC+2 Niphlod napsal(a):
>
> Couchdb support is still experimental in web2py. If auth is not working
> you'd likely to wait (or help Massimo with) a better implementation of the
> DAL.
>
> If you need ultra-fast
Thanks. I'll try using SQLite and WAL - that having been said I'd still be
vote for getting the scheduler working with NoSQL (couchDB) at some stage.
Ted
On Thursday, 26 July 2012, Niphlod wrote:
> Couchdb support is still experimental in web2py. If auth is not working
> you'd likely to wait (or
Couchdb support is still experimental in web2py. If auth is not working
you'd likely to wait (or help Massimo with) a better implementation of the
DAL.
If you need ultra-fast tasks you'd want to use celery (or pyres, or rq).
The current scheduler with SQLite can process ~5 tasks per second per
Hi Niphlod,
Since the usecase for a Scheduler often needs concurrent fast write/reads
and updates (from multiple clients) with information that is largely
temporary I think a Nosql DB is a great way to handle scheduler data.
In my case I don't want the overhead of installing a full relational d
Scheduler was meant to run on relational dbs. Actually, I think noone ever
tested it on Nosql adapters, but if this is a popular requirement I could
see into it.
BTW, I posted an app to test the scheduler in trunk for this kind of tests.
https://groups.google.com/d/topic/web2py/E_mASrZIpvw/disc
6 matches
Mail list logo
