For an alternative see my article at
http://pivots.pivotallabs.com/users/alex/blog/articles/305-collapsing-migrations
If you make it part of your process to regularly collapse migrations
(like after every deploy), you avoid both of the problems mentioned
above (referencing old class definitions a
On Feb 21, 2008, at 3:10 PM, Michael Koziarski wrote:
>> 1) Prepare's strategy is to dump the current schema, blow away the
>> test db, and then rebuild the test schema from the dump. This
>> strikes
>> me as dangerous in the event that someone has mucked with the db
>> outside of a migration-
On Thu, Feb 21, 2008 at 9:53 AM, Student <[EMAIL PROTECTED]> wrote:
>
> I'm having fun with a legacy DB (SQL Server), and in the process found
> some code in rails/lib/tasks/databases.rake which feels wrong.
>
> 0) Errors which occur during this phase of a rake:test or rake:spec
> tend to be i
