> ... 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
Great. Will do.
> The new DAL will have lots more room for customization so we should
> focus on design before implementation.
I've been m
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/web
Great, thanks for this.
I'm interested in seeing how you mimic ListProperty in a relational
database, Massimo. My gut says it doesn't belong, because it breaks
down normalization and/or it just seems like a proxied data type in a
relational database. Not sure how I feel about it since it seems li
> Can you make a concrete example? It will help us improve.
The oft-cited ListProperty is a great example. Because GAE/BigTable
doesn't provide substr support, we have a couple options for a search
facility. One is to take a string, say "foobar" and tokenize it into
parts.
['fo','oo','ba','ar','
> Perhaps some unification between these two - so that applications can be
> portable accross both types - will emerge, and this would be useful.
>
> But I think the first step is to cleanly, intentionally separate the two
> kinds of back ends and see where that leads.
These two statements are ke
5 matches
Mail list logo
