I fixed it. I don't like poking around in MySQL. It's like putting my
hands in the wood chipper.
I did
mysqldump -u user --database development_database > backup.sql
then I dropped the whole database and recreated it's name.
I did
rake db:schema:load
to recreate all of the tables. I saw so
It depends on your operating system. I am on a Mac and really enjoy
TextMate and the Terminal as my development environment. There are,
obviously, much fancier all-in-one systems, but this one works for me.
--~--~-~--~~~---~--~~
You received this message because you
I suspect this is because it is a 1.x application which was upgraded,
but my migrations don't "stick." If I
Coder-iMac:patton colin$ rake db:migrate
(in /Users/colin/Desktop/patton)
== 20090217193953 AddLastYearToTarget: migrating
==
== 20090217193953 AddLastYearToTarge
Thanks Bill!
That worked. I had
<%= link_to_remote("Say hello",{:action => 'hello'}) %>
and changed it to:
<%= link_to_remote("Say hello", :url =>{:controller =>
'java', :action => 'hello'}) %>
And now it works. That's mysterious to me. I thought the controller
would be constant on a pa
In my app/views/layouts/application.rhtml:
<%= javascript_include_tag :defaults %>
--~--~-~--~~~---~--~~
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 ruby
Martijn,
I have faced some of this. I found that doing
sudo gem update --system
sudo gem cleanup
Really helped. Sometimes I did them a couple times in a row.
The error about Rails 2.1.0 already running (or something like that)
might have to do with the environment.rb file you have, which mi
Hello,
I am certain this is a simple thing. The crazy thing is that last
summer I created my first Rails application with some .rjs templates
and that still works. But making a new one recently I have become
totally stumped. I thought it was something complicated I was doing
(update the DOM, inse
7 matches
Mail list logo
