well ok , he can use a migration then is not like the logic is very different , he just has to move the connection related code.
On Mon, Sep 27, 2010 at 3:29 PM, Marnen Laibow-Koser <[email protected]>wrote: > >> PLEASE QUOTE WHEN REPLYING! How many times must I say this? >> >> radhames brito wrote: >> > he would first create the appropriate tables with a migrations, if you >> > look >> > at the rake that i gave is does not create any tables, i suggest he adds >> > them first then move everything with a migration or a task >> >> Unnecessary. The migration should contain everything that is necessary >> to both create the schema and fit the data into the new schema. The >> whole point of migrations is that each migration contains everything >> that is necessary to bring the database from one consistent state to >> another. >> >> Best, >> -- >> Marnen Laibow-Koser >> http://www.marnen.org >> [email protected] >> -- >> Posted via http://www.ruby-forum.com/. >> >> -- >> 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]<rubyonrails-talk%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-talk?hl=en. >> >> -- 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.
