Re: Ruby on Rails on i site back up

I did a quick search on this and came up with several results on how to deal with "legacy" databases. It doesn't appear to be all that difficult to deal with in ActiveRecord. It's a matter of turning off certain default behaviors, particularly with regard to table naming and an identity column as the primary key.

I think the main place that RoR blazed a trail is that it brought some pragmatism back into framework design. The preference for convention over configuration has started to work its way into many other languages and platforms, including some of the recent Java specifications. JSF 2 and EJB 3 embraced this philosophy and are far more productive as a result.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: Sunday, December 27, 2009 3:28 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Ruby on Rails on i site back up

Pete Helgren skrev:

The next Rails challenge is to get a rails app running using a legacy
database table. That is, a table that hasn't implemented some
simplifying conventions designed for Rails (like a primary key called ID
and primary keys that are identity columns).

I think that Rails wants to be in control of the database tables, so
retrofitting it to existing tables may be quite a challenge.