Klaus Kaempf wrote: > But using SQL statements (see the video) is ugly. Lets see when Google > adds the active record pattern > (http://en.wikipedia.org/wiki/Active_record_pattern) ;-) > It is not ugly. Don't judge too fast!
Actually the Google DataStore is not a relational database, but based on Bigtable. Amazon's SimpleDB is also a distributed hash. "The datastore API provides two interfaces for queries: a query object interface, and a SQL-like query language called GQL. A query returns entities in the form of instances of the model classes that can be modified and put back into the datastore." So the Sql part is only an interface. An ActiveRecord pattern is also provided: http://code.google.com/appengine/docs/datastore/modelclass.html Sql is a pretty good DSL. ActiveRecod is recommended only because applications use to do trivial stuff where verbosity and maintenance can be simplified by using ActiveRecord. Now go an shout to the world "use always ActiveRecord", and you will screw it up and all kittens will die. Nothing in computer science is bad or good by definition*. Right tool for the right job. Patterns can't be applied so early in design. Duncan * may be a couple of exceptions. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
