From: Joe Van Dyk <joevandyk@...>
Date: 2005-07-17T11:07:31+09:00
Subject: Re: Just seen on c.l.py

On 7/16/05, James Britt <james_b@neurogami.com> wrote:
> Phil Tomson wrote:
> > In article <05th9VCgqN2CFwW4@objmedia.demon.co.uk>,
> > Stephen Kellett  <snail@objmedia.demon.co.uk> wrote:
> >
> >>Hi Folks,
> >>
> >>Just browsing c.l.py and found this advertised as a Rails killer... hmmm
> >>not very friendly.
> >>
> >>       http://www.djangoproject.com/
> >>
> >>Make of it what you will.
> >>
> >
> >
> > I'm not much of a web programmer nor have I done any SQL so when I went
> > through Curt Hibb's Rails tutorial I kept thinking "why do I have to mess
> > with this SQL stuff?  Why can't I describe the data/tables in Ruby and
> > then have Rails take care of all that stuff for me" (it seemed somehow like
> > the DRY principle was being violated).
> 
> This is how Nitro works.  The class definitions drive the tables, not
> the other way around.
> 
> www.nitrohq.com
> 
> 

If you use Migrations (introduced very recently with Rails), you can
specify the database structure in Rails.  All that's needed is for you
to create the database.