From: Lyle Johnson <lyle.johnson@...>
Date: 2005-01-23T01:01:01+09:00
Subject: Re: Use of scaffolding in the ONLamp Rails tutorial

On Sat, 22 Jan 2005 21:06:42 +0900, David Heinemeier Hansson
<david@loudthinking.com> wrote:

> Have a look in the log by doing something like "tail -f
> log/development.log" -- then you'll be able to see all the SQL
> statements being fired off and whether the request is coming in right.

I tried this before posting; the SQL statements (e.g. to INSERT the
new row(s) into the database) are never getting printed out.

> If you have additional questions, please do come hang out on
> #rubyonrails for real-time assistance or use the dedicated Rails
> mailing list. You can read more about both on
> http://wiki.rubyonrails.com.

I had been chatting with several of the guys on #rubyonrails about
this problem before finally giving in and posting a query here. ;) You
are of course correct that they were really helpful, and that's a good
resource for anyone to check out. We just weren't able to track down
the problem.

We *did* note that when I went out to the console and tried
instantiating a new Recipe object and then calling its save() method,
it *did* get added to the database; so the AR layer certainly seems to
be doing the right thing. Indeed, the form that was displayed in the
web browser (when I visited the recipe/new page) showed all of the
expected fields -- so it was getting the correct table description
from the database. But something was definitely breaking down when I'd
click the "Create" button. No *errors* were printed to
development.log; it's just that it didn't do what it was supposed to
do.

> Welcome to the Rails world!

Thanks! After talking with the guys on #rubyonrails, it sounds like I
ultimately won't want to depend on the "scaffolding" feature anyways,
and so I regard this as just a temporary hiccup in my getting started.
I'm looking forward to learning more about how to use Rails over the
next few weeks. I was mainly checking in to see if, by chance, anyone
else had run into this particular problem with Curt's tutorial.

P.S. Apologies for the duplicate post that kicks off this thread.
There was an unusual delay before the first one showed up, and so I'd
resubmitted it to ruby-talk in the meantime...