'merb-gen destroy migration name' tries to delete a non-existent migration
Reported by Ahsan Ali | May 30th, 2008 @ 11:15 AM | in 1.0
'merb-gen destroy migration xyz' tries to delete 002_xyz_migration.rb, when it should be deleting 001_xyz_migration.rb.
Create a new migration
- merb-gen migration xyz
create schema/migrations
exists schema
exists schema/migrations
create schema/migrations/001_xyz_migration.rb
Destroy the migration
- merb-gen destroy migration xyz
missing schema/migrations/002_xyz_migration.rb
notempty schema/migrations
notempty schema
notempty schema
notempty schema/migrations
notempty schema
Basically, the destroy action takes the next available number, instead of grabbing the index of the specified migration.
Comments and changes to this ticket
-
Michael Klishin (antares) June 29th, 2008 @ 10:12 AM
- → Tag changed from “” to “bug merb_activerecord migrations”
- → Milestone changed from “” to “1.0”
- → State changed from “new” to “open”
New migrations generator uses timestamps and this issue is even worse: it has no way currently to find migration file with a timestamp in it's name.
Investigating.
-
Michael Klishin (antares) September 6th, 2008 @ 01:01 PM
- → Assigned user changed from “Michael D. Ivey (ivey)” to “Jonas Nicklas”
Jonas,
We decided to not delete migrations at all, correct?
-
Michael Klishin (antares) October 5th, 2008 @ 12:43 PM
- → State changed from “open” to “invalid”
It has a duplicate in -more.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Jonas Nicklas
Michael D. Ivey (ivey)