The "first_time" just means that's the first time the task is being 
invoked in this rake run, I believe.  Doesn't mean it thinks you're 
running migrations for the first time ever.

I encountered this error with a plugin that had not been upgraded to be 
compatible with Rails 2.x.  I would recommend running rake --trace 
again, but then look at the call stack that gets dumped to figure out 
exactly which task is causing this error, and perhaps what plugin may or 
may not be related.

dwh

Ben Lieber wrote:
> Hi I have an unusual one, hoping one of you geniuses can give me a hint
> as I don't know where else to look.
>
> I'm running an combo of Rails/Sql Server (I know, I know, legacy though)
> using Ubuntu/UnixODBC/FreeTDS/activerecord-odbc-adapter. The app seems
> to be talking to the DB perfectly. When I have a clean database, I'm
> able to run rake db:migrate and everything generates correctly. However,
> if I add another migration and run the migrations again, I get this
> error:
>
> rake aborted!
> S0001 (2714) [unixODBC][FreeTDS][SQL Server]There is already an object
> named 'schema_migrations' in the database.
>
> Which, of course there is! I'm just attempting to add a new table,
> column, etc. The only way I've been able to add migrations thus far is
> to wipe the database and rerun the migrations from scratch. Obviously
> can't keep that up forever.
>
> with a --trace argument, I do notice that it thinks I'm running them for
> the first time. Where does the rake task look to decide this?
>
> ** Invoke db:migrate (first_time)
> ** Invoke environment (first_time)
>
> Thanks so much for any help you can provide!
>
> -Ben
>   

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to