Personally, I would use Sequel's. The Rails API seems to change often on a whim while Sequel breaks backwards compatibility on much rarer occasions. Plus, if implemented right, you can invest your business logic in your models and maintain easy portability to other systems.
Right now, I have one folder I keep my model definitions in coupled with a heavy dose of specs to keep them well-tested and these model files don't depend on Rails, Ramaze, or any other framework. I am using these same model classes in three different Ramaze-based apps, several cronjob and rake-only ETL (extract, transform, load) tasks as well as beanstalkd job processing. Just something to think about. Rails, Ramaze, Sinatra, etc. look like they come and go with fairly rapid turnover/evolution, while the data access layer seems to remain a bit more stable and long-lived, so for me, a deliberate and conscious design decision was made to invest in keeping the models well-structured, encapsulated, and well-covered via specs so that I may be free to choose any of the other tools I need to get a job done. Michael -- http://ramblings.gibberishcode.net -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en.
