Not being a huge expert myself, here's what I would do: 1. Setup model files (by hand for each table) app/model/table.rb 2. Set any naming exceptions in each model file (if columns are not well named for example) 3. Setup your database config to point to your remote database (config/database.yml)
Now you can generate scaffolds to deal with it. I'd just loadup the console (script/console) first, and do some test queries to see if you can connect. Eg: # script/console # > Table.find(:first) etc. - Erison Smith http://www.funadvice.com On 3/20/07, Shanon Clemmons <[EMAIL PROTECTED]> wrote: > > How does one (a complete newbie) model and scafford an legacy database > remotely. The tables appear to be in the correct form of pural names and > the connection is correct > > any help would be greatfully > > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
