Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Remove migrate directory on last destroy

#5101

This is petty, but..

When you create a new rails app, no 'migrate' directory is created in the 'db' directory. If you generate a model, the 'migrate' directory is created, but if you then destroy that model (the last or only model) the migrate directory is left in-tact.

Like I said, it's petty and small, but it seems that the logic should be followed thru.

Reported by Donnie · July 12th, 2010 @ 10:30 PM

State: invalid
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Rohit Arondekar
    Rohit Arondekar
    • Importance changed from to Low

    Why complicate things? Is there any issue if the migrate directory remains in-tact?

    September 13th, 2010 @ 02:08 AM

  2. David Trasbo
    David Trasbo

    First of all: Yes, that is petty. Secondly: I agree with Rohit.

    To be honest I think db/migrate should just be there by default.

    September 13th, 2010 @ 11:26 AM

  3. Rohit Arondekar
    Rohit Arondekar
    • State changed from new to invalid

    I think it's fine just the way it is. :)

    September 18th, 2010 @ 02:47 AM