Hi Fred, Thanks. Apparently it has been fixed in this release, because migrations now work in 4.2.1rc3, though I couldn't find specific bugfix commit.
On Thursday, March 5, 2015 at 6:04:19 PM UTC+1, Frederick Cheung wrote: > > >>> I've also commented in the commit, so you can have a look for more info >>> there. >>> >>> >>> https://github.com/rails/rails/commit/290e8e117fd33189fec25d13b37e686b27247ad1#commitcomment-9757150 >>> >>> > Given that it is apparently fixed on 4-2 stable, have you tried one of the > 4.2.1 release candidates? > > Fred > > > >> Any ideas on how to solve it? >>> >>> Thank you! >>> >>> Giedrius >>> >> -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/022b724a-b3b0-4051-89f7-83916ff45dbd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
