From: Richard Conroy <richard.conroy@...>
Date: 2010-11-11T11:18:16+09:00
Subject: Re: ruby ORM

--0016367d6e9ac37cdd0494bd808e
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 11, 2010 at 1:43 AM, zuerrong <zuerrong@gmail.com> wrote:

> Hello,
>
> which is the best ORM for ruby?
> and, is ORM really good on database handling?
>
>
It all depends on what you want exactly. A Database ORM is an abstraction of
a database, that inherently introduces compromises in how you work with it.
The Ruby ORMs are quite famous - ActiveRecord made a huge case for ORMs all
on its own. DataMapper is an excellent purist ORM. Also in Ruby you should
consider the Sequel library, which includes an ORM layer (not as abstracted
as either AR or DM, but that may be a really good compromise when dealing
with legacy schema).

As a rule, I think the Sequel library may be unfairly overlooked in the
'good ways to deal with databases category'.

There are genuinely good reasons for using ORMs in many cases, but usually
the reason to use an ORM is to hide the nuisance of SQL. This means that
ORMs can often be used in situations that they really shouldn't. I think
Sequel goes a huge way towards making SQL a lot easier to use in a program,
and therefore ORM layers can be introduced on their merits.

That said, I haven't used Sequel in anger, favouring DataMapper in my Ruby
programs.

-- 
http://richardconroy.blogspot.com | http://twitter.com/RichardConroy

--0016367d6e9ac37cdd0494bd808e--