Migrations dont have a zero version - cant roll all the way back

[jeremyevans]

What steps will reproduce the problem?

1. Create a migration numbered 1 (or more)
2. Use the bin/sequel command with "-m dir" to migrate forward
3. Try to use the bin/sequel command with "-m dir -M 0" to get an empty database ...
4. nothing happens

What is the expected output? What do you see instead?
Expecting the database tables be dropped, like the migration file says in "def down"

What version of the product are you using? On what operating system?
tag 3.0.0 - commit 10f69a2
mac os x 10.5.7

Please provide any additional information below.
when i was using rails and activerecord, migrating down to zero was a great way to know that all
the migrations are okay both upward and downward - and did not require additional commands
to drop and re-create databases.

Google Code Info:
Issue #: 268
Author: evgeny.zislis
Created On: 2009-06-02T22:48:30.000Z
Closed On: 2009-06-02T23:03:56.000Z

[jeremyevans]

hmm, it didn't work when i had more than one create_table in the 001 migration and it failed in the middle ...
but generally it does work, so sorry - my bad.

maybe each migration should be inside a transaction?

(using mysql)

Google Code Info:
Author: evgeny.zislis
Created On: 2009-06-02T22:59:23.000Z

[jeremyevans]

MySQL doesn't allow transactional schema changes, and I think other databases might
have problems with them too. You can always use Database#transaction manually in a
migration if you want a certain part to be transactional.

Google Code Info:
Author: jeremyev...@gmail.com
Created On: 2009-06-02T23:03:56.000Z