On 19 March 2010 16:07, Grary 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
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.
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.
Tha
2 matches
Mail list logo