Hi Snaky - Identical source code can be deployed both to GAE and elsewhere without editing, you don't need to edit connection strings before deploying to GAE. The default db.py code you get with a new project detects if gae is running with the line if request.env.web2py_runtime_gae: ... using this it can choose the right connection at runtime.
I can recommend this page here for the kind of database queries that will work with GAE http://www.web2py.com/AlterEgo/default/show/248 - Alex On Feb 22, 2:43 pm, Snaky Love <[email protected]> wrote: > Hi, > > is there a how-to on what to avoid doing wrong when building a webapp > with web2py which should run on Google App Engine? I found, of course, > everything that is listed here: > > http://web2py.com/book/default/search?search=app+engine > > But I still do not feel very confident about which traps to avoid > stepping in... > > Of course I really, really would like to have the app also beeing able > to run not only on GAE but everywhere else - as I understand it now, a > simple change of the connection string will make it able to use, let´s > say mysql with a more "traditional" hosting environment? > > That would look like > > db = DAL('gae') > > to run on appengine and change to > > db = DAL('mysql://username:passw...@localhost/test', pool_size=0) > > to make it run anywhere else? > > [Of course, only if I do not use libs that are blacklisted on GAE] > > Or will the need for datastore-specific programming break my app for > other databases? > Certainly it will not be optimized for SQL-Engines, but still run? > > Sorry for too many questions :) > > Thanks you very much for your attention, > Snaky -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
