From: Mike Stephens <rubfor@...>
Date: 2010-11-18T21:24:12+09:00
Subject: Re: ORM's - Don't Do It!

Phillip Gawlowski wrote in post #962325:
> > So, how do you access them, then? ORM is not an option, so how do you
> et the data into a report, a quoting app, or shove it over to accounts
> payable?
>

I'm not sure what you're getting at. The normal ways of dealing with
databases are to call an SQL interface or a stored procedure. This is
relatively painless if you accept SQL is one of the principal tools in
the developer's toolbag. You may get a relation returned (which is easy
to map to a hash or whatever) or a cursor. You have to write a small
method to make the call and transfer the data but in return you have the
flexibility to adjust the SQL to use its terrific power. Ruby might be
fun but so is SQL.

For a long time after relational databases came in you would see
developers writing code that just used SQL to write and read records.
Nothing had changed since the days of ISAM, IMS, IDMS etc etc. Nowadays
you see database calls that cover two pages of SQL. People have realised
they can solve an awful lot before they get the data back into their
progams. I just worry ORMs tempt new people down the old path.

-- 
Posted via http://www.ruby-forum.com/.