rubyonrailsin

On 19 March 2010 16:07, Grary <grary.stimon@gmail.com> 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 rubyonrails-talk@googlegroups.com.
> To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
> 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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.