[web2py] Re: OperationalError: no such table: contacts

2019-05-31 Thread João Matos
If you don't need any data in the db, delete everything in databases and check that in models\db.py the DAL creation has migrate=True. Then restart your app. All tables should be recreated. quarta-feira, 29 de Maio de 2019 às 20:13:07 UTC+1, karthikeyan p escreveu: > > i am running my web2py app

[web2py] Re: OperationalError: no such table:

2010-09-03 Thread mdipierro
This is a known problem with the web based shell likely due to database timeout. Do not use the web shell for db operations. Instead use a the regular shell: python web2py.py -S yourapp -M -N until we figure out why the db gets closed. On Sep 3, 2:45 am, Geo wrote: > All this web2py is new for

[web2py] Re: OperationalError: no such table:

2010-09-03 Thread Geo
All this web2py is new for me so it's likely that I messed up something. It's all part of a monitoring page where I can check the processes running on the server. from: applications\monitor\views\default\index.html I call: {{=TD(LOAD(url=URL(r=request,f='getProcesStatus',args=proces_key), ajax=Tru

[web2py] Re: OperationalError: no such table:

2010-09-02 Thread mdipierro
I do not understand this line monitordb.updates['processes']=dict(updatetime=datetime.datetime.now()) I do not think this is valid. Anyway, that is not the problem you asked about. Where are you executing these lines? From shell? Did you do -M? From another model? remember they are executed alp

[web2py] Re: OperationalError: no such table: auth_user

2010-01-25 Thread Cliff Brake
On Jan 18, 8:38 pm, mdipierro wrote: > SVN is no longer updated. Please try the tarball form web2py.com Sorry I did not make myself clear. I was using web2py from a tarball, but checking my application in/out of SVN. I did figure out the problem -- I had checked some of the databases/*.table fi

[web2py] Re: OperationalError: no such table: auth_user

2010-01-18 Thread mdipierro
SVN is no longer updated. Please try the tarball form web2py.com On Jan 18, 7:27 pm, Cliff Brake wrote: > Any idea what is causing the following? > > I have the following in default.py > > def user(): >     """ >     exposes: >    http:///[app]/default/user/login >    http:///[app]/defau