On Jul 19, 9:56 pm, Carl Franz <[email protected]>
wrote:
> Well, I started a completely new application and I built two models
> using the 'script/generate scaffold' and am still having the problem.
>
> Version/Environment is still:
> Windows XP rev3
> Ruby - 1.8.6
> Rails - 2.3.2
> Rake - 0.8.7
> mysql - 5.0.51a
> Also, I'm running everything via the Windows command line.
>
> Why would this version of Rake be attempting to use the &*^%& version
> numbers and not the version timestamps? Any ideas?
if there is an environment variable called VERSION then rails tries to
migrate to that version (this is largely because until recently rake
didn't allow you to pass arguments to tasks so it's faked up with
environment variables eg rake db:migrate FOO=123 )
Unfortunately VERSION is quite a non specific word and occasionally
you may find that other software has set that environment variable, in
this particular case to 3. Rails thinks you are telling it "migrate to
version 3" and is complaining because it couldn't find that file.
Running db:migrate again after you added the second migration did
nothing because rails still thinks you're saying 'i want to migrate to
version 3'.
Fred
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
