* Duncan Mac-Vicar P. <[EMAIL PROTECTED]> [Apr 12. 2008 19:36]: > 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! [...]
> > 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. The main advantage of using patterns like ActiveRecord is abstraction which in turn makes it much easier to refactor/replace components in the stack. Properly used, it provides flexibility and prevents (database) vendor lock-in. > Now go an shout to the world "use always ActiveRecord", and you will > screw it up and all kittens will die. *g* I do shout "use abstractions" and "ActiveRecord is a good abstraction". Having to (re-)learn SQL for simple database manipulations (like the one showed in the video) just doesn't feel right. And doing it via _G_QL might lock you into Google ... Klaus -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
