David Trasbo

Jeff,

Another option is to wrap <script> in a <tt> tag. I've attached a patch that does just that - it also makes sure to wrap at 80 characters.

Neither was I:

➜  script/rails c
Loading development environment (Rails 3.1.0.beta)
ruby-1.9.2-p0 > a = Date.new(2010, 9, 30)
 => Thu, 30 Sep 2010 
ruby-1.9.2-...

+1

Patch applies cleanly and the included test fails without the fix but passes with it.

Whether or not that's inconsistent is rather subjective. Of course, if you try to reload a Active Record object that doesn't exist in the database anymore that ...

That turned out to be a bit crufty. Here we go again:

➜ ../../bin/rails new ticket_5549 --dev -d mysql...
➜ cd ticket_5549 ➜ bundle exec rails g model foo...
➜...

I was unable to reproduce this on edge Rails using Ruby 1.9.2:

➜  in ~/code/rails/railties/tmp on 5549 (✔) using ruby-1.9.2-p0@edgerailsapp ../../bin/rails ne...

I was unable to reproduce this issue.

I switched to ruby-1.8.7-p302 (the latest) with rvm, created a rails3 gemset, and did a gem install rails. It ran all the ...

Awesome. FYI, I'm in there now if you have time.

Adrian,

Maybe, maybe not - I can't tell. Why don't you hop into #railsbridge at irc.freenode.org and ping me there? I'm dtrasbo.

Here's a patch that makes rails g model and rails g migration remove the colliding migration file if you pass --force to it.