On Thu, 11 Jan 2007, Brad W wrote:
and it worked.
Oops, that’s incorrect. It wasnt the same as my model name, which was
Movie, but the same as the table name in my DB.
I’ll bet you have a controller file called movies_controller.rb
When you connect to the application, the routing mechanism zeros in on
a particular controller action, based on the URL (with some
interpretation thereof by the route recognizer). If you connect to
/movies, then by default that will look for the “index” action in the
“movies” controller (i.e., movies_controller.rb).
Even if the table name is the same, it’s not involved at this stage.
Q. What is THE Ruby book for Rails developers?
A. RUBY FOR RAILS by David A. Black (http://www.manning.com/black)
(See what readers are saying! http://www.rubypal.com/r4rrevs.pdf)
Q. Where can I get Ruby/Rails on-site training, consulting, coaching?
A. Ruby Power and Light, LLC (http://www.rubypal.com)