I believe that trying to adapt db to datastore would be like trying to fit a square into a circle. Gae's datastore is such a different paradigm shift that I doubt a db wrapper would be possible or useful. You can try doing it, but soon you'll realize that db's features don't map well to datastore's, and in the end it would be more an annoyance than a advantage.
And to tell the truth, once you understand the different paradigms, it's not hard at all to use gae's datastore api. In fact, it is very handy and vey well designed. I'd love to be probed wrong though... Luis On Jan 8, 3:25 pm, adelevie <[email protected]> wrote: > I also might add that this is why I think a db wrapper for GAE would > be a killer feature for web.py. It would make web.py the most portable > framework with near-seemless transtitions between GAE and more > traditional hosts. > > On Jan 8, 1:24 pm, adelevie <[email protected]> wrote: > > > I thought about this for a while myself. I think when using GAE, it's > > best to use webapp. Web.py's top features are either non-functional or > > a PITA when using GAE. You can't use web.py's db wrapper (which I like > > a lot) and templates must be constantly compiled if you choose to use > > Templetor (which I also like a lot). What's left (at least in my > > case), are some nice conveniences with web.py but nothing game > > changing. For example, it's a bit more annoying to write > > self.response.out.write instead of just return. Or render.templatename > > (vars) is a lot easier than template_values = { > > 'var': var > > } > > path = os.path.join(os.path.dirname(__file__), > > 'template.html') > > self.response.out.write(template.render(path, > > template_values)) > > > On Jan 8, 1:30 am, Tzury Bar Yochay <[email protected]> wrote: > > > > Your web.py code will be useful when/if you decide to use it outside > > > of GAE. > > > Basically, all you need is a data layer adapter. > > > > On Jan 7, 9:32 pm, SM <[email protected]> wrote: > > > > > I'm trying to decide if it makes more sense to do a Google App Engine > > > > project using Google's webapp framework or to use webpy. First of all, > > > > I'm struck by how similar webapp looks to webpy which makes the > > > > decision more tricky (or maybe not). Given the superficial (at least) > > > > similarities, does it make a big difference? What are the pros/cons of > > > > each framework? > > > > > Also, webpy is currently at version 0.3. I'm wondering if it will > > > > continue to be developed and supported? Webapp will presumably > > > > continue to be developed and supported by Google. > > > > > Thanks. As I'm learning about it, I really like the simplicity and > > > > elegance of webpy so far. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
