I'm having a very odd problem with db:migrate. I'm using Rails 1.2.5
on Windows XP SP2 and Ruby 1.8.6
I have seven migrations. If I run them with an empty database, it
runs the first three, then halts. When I look in schema_info, the
version is 3.
If I run db:migrate VERSION=7, then it runs through the remaining 4
migrations, and the version is 7 in the DB. Committed and everything.
If I then run db:migrate on its own, then Rails will REVERT BACK those
4 migrations and set the version to 3 again.
I don't understand this behaviour. I've tried --trace and --verbose
and neither explains why it is that Rails wants to roll back when the
version is 7.
I've only just recently arrived to Rails and Rake, so I'm not familiar
with the internal structure, but I don't see this behaviour mentioned
in any of the documentation. Can anyone help?