#2725 negative migration version - 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.

#2725 ✓invalid

negative migration version

Reported by keymone | May 27th, 2009 @ 07:28 AM | in 3.x

a tiny patch which allows you to specify negative migration version:

rake db:migrate VERSION=-N

such command will revert last N migrations

negative_migration_version.diff 926 Bytes

Comments and changes to this ticket

You flagged this item as spam.
keymone May 27th, 2009 @ 07:41 AM
- Tag changed from “2.3.x, active_record, migrator” to “2.3.x, active_record, migrator, patch”
You flagged this item as spam.
Bart Zonneveld July 27th, 2009 @ 02:19 PM
+1
Michael Koziarski August 3rd, 2009 @ 06:02 AM
don't we already have db:migrate:down VERSION=...?
You flagged this item as spam.
keymone August 3rd, 2009 @ 07:16 AM
we do, but we still have to type full version number like 200910xxxxxxx and looking up for that number each time i do downgrades really frustrates me (even though i do not downgrade very frequently) and
```
rake db:migrate VERSION=-1
```
makes me feel happy
Michael Koziarski August 5th, 2009 @ 07:05 AM
It just seems a little terse to me.

Could we fix it by simply making sure db:migrate:down has sensible defaults?
You flagged this item as spam.
keymone August 5th, 2009 @ 08:02 AM
the only sensible default for db:migrate:down i can think of is to downgrade to previous version however if you want to downgrade 2 or 3 versions you still have to lookup for correct version number

one more thing i noticed when downgrading using full version number - everytime i stop and think what exactly rake db:migrate:down VERSION=xxxxxx means? will it revert all migrations including xxxxxx nor will it leave database alone at that point? it is not a problem but it does confuse me sometimes on the other hand when i type VERSION=-5 i know it will revert exactly 5 migrations.
José Valim August 8th, 2009 @ 05:46 PM
Isn't db:rollback STEP=N used for this purpose?
Jeremy Kemper May 4th, 2010 @ 06:48 PM
- Milestone changed from “2.x” to “3.x”
[bulk edit]
Dan Pickett May 9th, 2010 @ 07:29 PM
- Tag changed from “2.3.x, active_record, migrator, patch” to “2.3.x, active_record, bugmash, migrator, patch”
Jeff Kreeftmeijer May 15th, 2010 @ 05:45 PM
-1

Like José said, we have rake db:rollback STEP=n for this. I could be completely missing something though.
Also, I don't really like the VERSION=-n syntax.
You flagged this item as spam.
Anil Wadghule May 15th, 2010 @ 05:49 PM
-1 Not a necessary feature. VERSION value should only be timestamp or migration number. VERSION as count is confusing.
You flagged this item as spam.
keymone May 15th, 2010 @ 05:51 PM
yes, db:rollback is what i failed to find in the first place.
Jeff Kreeftmeijer May 15th, 2010 @ 05:56 PM
Cool, this one can be closed then. :)
José Valim May 15th, 2010 @ 05:57 PM
- Tag changed from “2.3.x, active_record, bugmash, migrator, patch” to “2.3.x, active_record, migrator, patch”
- State changed from “new” to “invalid”