From: Mike Stephens <rubfor@...>
Date: 2009-08-13T23:26:43+09:00
Subject: Re: Destroying related objects doubt ... basic oop question

Christopher Dicely wrote:
>  the  data is still being controlled by the Ruby program.

That would mean anyone across the entire corporation is somehow going to 
have to call your classes to manipulate the data. Believe me, that isn't 
going to happen.

If you're Warner Brothers and you want to work out what DVDs you've sold 
today in the South American Regions you aren't going to use Ruby. It's 
going to be Oracle and related special products, and that's what it's 
like everywhere. Once other people have access to the data then the OO 
position is undermined.

Encapsulate private program data but leave shared business data to 
databases.

My other concern is why build your own wrappers when relational 
databases already have excellent wrappers built in (you won't beat SQL) 
and millions of man hours of optimisation code.

If you are not familiar with databases then by all means use an ORM but 
I would have thought most developers would be better served by filling 
in that knowledge gap at an early stage.

If you're just writing a shopping cart or social networking forum etc 
your data might be quite simple but if you moved say to monthly billing, 
discounts, credit limits, then I think it starts to get like eating food 
with chop sticks - entirely a dodgy idea.

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