Re: [web2py] Re: Cannot operate on a closed database

2011-09-06 Thread appydev
Why not so with: request = current.request? Is it safe to use the following? # modules/myobjects.py from gluon import * request,session,response,T,cache = current.request,current.session,current.response,current.T,current.cache and then use some class method : if form.accepts(request, session):

Re: [web2py] Re: Cannot operate on a closed database

2011-07-04 Thread Pierre Thibault
2011/6/26 Massimo Di Pierro > I found the problem > > http://groups.google.com/group/web2py/msg/aaa803e14404fc62 > > This is not a problem with web2py. > > @ Pierre, I did found a non-related problem with web2py. > > models/meteo.py uses custom_import to import modules/meteo.py. The latter > impo

Re: [web2py] Re: Cannot operate on a closed database

2011-06-26 Thread Manuele Pesenti
On 26/06/2011 20:03, Massimo Di Pierro wrote: Hope this makes sense. thanks a lot I got it now :) Manuele

Re: [web2py] Re: Cannot operate on a closed database

2011-06-24 Thread Manuele Pesenti
On 24/06/2011 20:40, Massimo Di Pierro wrote: When you deleted the db, did you also delete the associated .table files? You should have everything in the databases directory... Manuele

Re: [web2py] Re: Cannot operate on a closed database

2011-06-24 Thread pbreit
I don't think SQLite does pools. SQLite DBs are easy to deal with...just delete everything in the "databases" directory and start over. Might want to double-check that your connection string is pointing to the right place.

Re: [web2py] Re: Cannot operate on a closed database

2011-06-24 Thread Manuele Pesenti
On 24/06/2011 20:13, Massimo Di Pierro wrote: Is this is a sqlite or other? yes, it was sqlite. At the moment I solved using postgres witrh pool_size=100 but I didn't try if this parameter is really necessary. what's the difference between the two db in this case?? Manuele