[web2py] Re: Optimizing web2py app for GAE

2011-12-30 Thread dlypka
Perhaps these links will help: http://groups.google.com/group/google-appengine/browse_thread/thread/21478bd9185dcc32/f61b532da5c46588?lnk=gst&q=index+reads#f61b532da5c46588 http://groups.google.com/group/google-appengine/browse_thread/thread/bdb45e04dd8f959e/0659767c7878bafb?lnk=gst&q=index+rea

[web2py] Re: Optimizing web2py app for GAE

2011-12-30 Thread Anthony
On Friday, December 30, 2011 11:25:51 AM UTC-5, Massimo Di Pierro wrote: > > You have to do: > > db.define_table('name',...,migrate=settings.migrate) > > The table has to be defined because web2py needs to know how to map > SQL types into web2py types. The migrate argument, when set to False, >

[web2py] Re: Optimizing web2py app for GAE

2011-12-30 Thread Massimo Di Pierro
You have to do: db.define_table('name',...,migrate=settings.migrate) The table has to be defined because web2py needs to know how to map SQL types into web2py types. The migrate argument, when set to False, will prevent the "CREATE TABLE". Anyway, web2py does not "CREATE TABLE" if it exists alrea

[web2py] Re: Optimizing web2py app for GAE

2011-12-30 Thread Anthony
On Friday, December 30, 2011 4:22:29 AM UTC-5, Joseph Jude wrote: > > Let us say I have the below code in db.py under models > > define_table(db, ) > > If I change that to, > if settings.migrate: >define_table(db,...) > > rest of the queries based on this table doesn't work. I want to skip

[web2py] Re: Optimizing web2py app for GAE

2011-12-30 Thread Joseph Jude
Let us say I have the below code in db.py under models define_table(db, ) If I change that to, if settings.migrate: define_table(db,...) rest of the queries based on this table doesn't work. I want to skip the definition altogether if the table is already present. Reason: I assume that