On Fri, Sep 3, 2010 at 8:59 AM, PalaniKannan K <[email protected]> wrote:
> I feel that, this is same kind of results I got in google search... Creating > model using dumped schemas of existing table. but, its not working. "its not working" isn't particularly useful information. So you have an existing table, say "things". You create a model for it, e.g. class Thing < ActiveRecord::Base end Done. Maybe you have to tell it there's a non-Rails-standard index field, etc., but basically that's it. There's no reason to be fooling with migrations if you have an existing table, unless you can and want to do transformations on them to make them more Rails-like. So what have you tried, and what's the actual problem? -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
