Yes, I've certainly given the role of seed data due consideration in another context, but it's not relevant in the case at hand, I don't think. In that case at hand, the large data set I seek to include in my development is used for autocompletion and by business logic on the model side.
Thanks, Grar On Mar 19, 1:50 pm, Colin Law <[email protected]> wrote: > On 19 March 2010 16:07, Grary <[email protected]> wrote: > > > Hi, > > > I prefer to keep one migration per model, but lately I'm adding data > > that's expensive to drop every time I change my models. > > It is considered a bad idea to seed data using migrations, if that is > what you are doing. Google for rails migration seed for many > discussions on this issue, including on this list. Perhaps this is > your fundamental problem. > > Colin > > > > > How do I db:drop and db:migrate only selected tables/files? Basically, > > I want to ignore certain tables and migrations altogether during > > certain development phases. > > > Thanks, > > > Grar > > > -- > > 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 > > athttp://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.
