From: Sharon Rosner <ciconia@...>
Date: 2008-02-13T04:16:39+09:00
Subject: Re: Comparing Active Record VS Datamapper...?

> The problem with Sequel as far as I understand it, is that you have to
> be disciplined enough to create the Domain Object layer yourself to
> abstract away more complex model logic and it appears to be a lot more
> code to hide the Sequel code for non-trivial scenarios.  Otherwise you
> get a very stripped down DB-oriented (rather than object-oriented)
> database adaption API for your application.
>
> If you do not create a Domain Object layer, you end up with all the
> logic (controller AND model logic) in the controller layer, which is
> only maintainable when you have very trivial model logic.  This doesn't
> work in richer model logic environments.

Not true. Sequel includes a model class implementation based on the
ActiveRecord pattern with features such as: composite primary keys,
relationships, caching using memcached, validations and callbacks,
among others.

sharon