Re: Ruby on Rails on i site back up

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

> 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).

Things like this in the latest frameworks makes me wonder how much long term
real world experience some of these framework writers have.  Hibernate (
www.hibernate.org) suffers from the same issues of idealogical DB structures
(at least it did in V2.x, not so sure about V3.x).  Note I am not saying the
majority of RPG shop table structures are good, but they do/did account for
a lot of major company's data back-ends.

Aaron Bartell
www.SoftwareSavesLives.com

On Sat, Dec 26, 2009 at 3:55 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:

> The gem requires Java 6 so I am running the 32bit version
> (/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit).
>
> The gem really streamlines everything so outside of the 'gem install
> glassfish' command I just had to switch to my application folder and
> then invoke glassfish (glassfish -e production - p 3030).  Couldn't have
> been easier getting a Rails app deployed.
>
> 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).
>
> Pete