Developers in the two different paradigms SQL vs GAE have different
concerns. I have no knowledge of all the things that the web2py DAL
does but it seems to me it has a few purposes that are great in the
world of SQL databses but either moot or a hinderence in terms of App
Engine.
they are :
1: Broad portability of a web2py app: with a single api to implement
use most common databases
to this point i don't think there are many people sweating bullets
over the portability of their app engine apps, their sweating bullets
over performance and scalability and doing new interesting things that
are hard to do with SQL or only possible under that specific platform.
2: Object Relational Management: is this a separate layer or part of
the DAL? I dunno but isn't the app engine api already objectified as
if an ORM was built into app engine? Perhaps I'm mistaken on this.
I love web2py but i fear a tyranny of dead ideas here. Holding to the
old way of doing things eg. "have a DAL so people don't have to think
about databases" that can be great if by "databases" you mean SQL
databases. Are we overlaying a good design pattern in a completely
different context that leads to something that is decidedly sub
optimal.
so i guess what I'm trying to say is.. in my native dialect of js
if(dataStore == "SQL") {
alert("DAL/ORM FTW!!");
} else if(dataStore == "GAE") {
alert("DAL/ORM... wheres the beef");
}
my $0.2
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
