I would start by making a list of those GAE expression that you would like to be supported by web2py, provide an example of GAE syntax and a proposed web2py syntax. Possibly maintain a wiki page about this so information does not get lost.
The new DAL will have lots more room for customization so we should focus on design before implementation. Massimo On Jun 27, 2:11 pm, Cory Preus <[email protected]> wrote: > I'm in agreement with Hans about how GAE is fundamentally different > from relational databases. There are few threads on this and Yarko's > proposal is something I'm a fan of. Maybe not the most correct > approach, but continuing the discussion is valuable, methinks. > > http://groups.google.com/group/web2py/msg/29fa8b3ec9ac0e41 > > I love how web2py makes shifting between database implementations > simple. Moving between database paradigms is less so, and web2py is > caught inbetween. I want to take advantage of Big Table, but since it > is web2py treats it as a "relational database with limitations", > web2py is the limitation on Big Table. > > Massimo, what would you need from me or the community to help? I > understand and appreciate web2py's portability mantra, yet as a > developer who doesn't need portability, I would like to make the > deliberate decision to opt-out of the relational DAL "limitations" and > opt-in to full GAE support in web2py. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
