Norm wrote:
>>   
> There should be a lot of good information in your log files like what
> was sent to the controller and what the sql for accessing the database
> looked like.  It  sounds like you did not get an error which means that
> your parameters and sql were ok.  I would suspect you somehow are
> looking for your data in the wrong place.
> When you say it is not saving, do you mean that it is not fetched if you
> try to list it (or do something like a=Type.find :all in a
> script/console window).

Not really, this is what I see:

Processing AdminController#create_user (for 127.0.0.1 at 2008-11-15 
12:39:02) [POST]
  Session ID: 055075e032051a9365cecbcbf4abb283
  Parameters: {"commit"=>"Submit", 
"post"=>{"emailvrfy"=>"[EMAIL PROTECTED]", "passwordvrfy"=>"test72", 
"password"=>"test72", "email"=>"[EMAIL PROTECTED]"}, 
"action"=>"create_user", "controller"=>"admin"}
   [4;35;1mUser Columns (0.007000) [0m    [0mSHOW FIELDS FROM users [0m
   [4;36;1mSQL (0.003000) [0m    [0;1mBEGIN [0m
   [4;35;1mUser Load (0.000000) [0m    [0mSELECT * FROM users WHERE 
(users.email IS NULL) LIMIT 1 [0m
   [4;36;1mSQL (0.000000) [0m    [0;1mCOMMIT [0m
Redirected to http://localhost:3000/league/beginning
Completed in 0.03700 (27 reqs/sec) | DB: 0.01000 (27%) | 302 Found 
[http://localhost/admin/create_user]

When I try and manually add a user through irb nothing even though it 
appears that it is saving. The only thing that I can guess is that it is 
being saved to another table somewhere but my .yml seems to think it is 
using the same table that I am looking at.
-- 
Posted via http://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to