[Rails] single transaction migrations

[Esad Hajdarevic]

Hi!

It seems that migration doesn't use single transcation to execute the 
needed migrations for the database upgrade, so if I have database at 
version 5, and I wrote some migrations 6..10, and error occurs while 
executing migration 7, the database stays in state 6?

I also think that migration taks could use some more verbosity, for 
example if migration fails, there's no reference to migration number nor 
statement, only something like:

rake aborted!
uninitialized constant SalePoint

Are there any plans for improving on this or maybe even some code in 
trunk already? ;-)

Greetings,

Esad


-- 
Posted via http://www.ruby-forum.com/.