#5101 Remove migrate directory on last destroy - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#5101 ✓invalid

Remove migrate directory on last destroy

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

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.

Comments and changes to this ticket

Rohit Arondekar September 13th, 2010 @ 02:08 AM
- Importance changed from “” to “Low”
Why complicate things? Is there any issue if the migrate directory remains in-tact?
David Trasbo September 13th, 2010 @ 11:26 AM
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.
Rohit Arondekar September 18th, 2010 @ 02:47 AM
- State changed from “new” to “invalid”
I think it's fine just the way it is. :)