StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11786244
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
13
CommunityOwnedDate
CreationDate
2012-08-02T21:42:53.543
FavoriteCount
0
LastActivityDate
2012-08-02T22:10:01.910
LastEditDate
2012-08-02T22:10:01.910
LastEditorUserId
820254
OwnerUserId
820254
ParentId
11785914
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It looks like you have your <code>:cars</code> resource nested inside your <code>:users</code> resource: <pre><code>resources :users do resources :cars do ... </code></pre> If you structure your routes this way, then you need to specify a user as well when calling http actions. This won't work: <pre><code>post :create, :car => @car </code></pre> because it's missing a <code>:user_id</code>, which you access in the controller: <pre><code>@user = User.find(params[:user_id]) </code></pre> To solve this, pass a <code>:user_id</code> and then mock or stub <code>User</code> to return a user or mock user. UPDATE: It's not generally good practice to mix mocks and actual records, so here's how you could do it without mocks: <pre><code>before(:each) do @user = User.create(...) @car = {:brand => "example", :color => "foobar", :model => "foobar", :year =>"2012" } end it "should create a car" do lambda do post :create, :car => @car, :user_id => @user.id end.should change(Car, :count).by(1) end it "should redirect to the user welcome page" do post :create, :car => @car, :user_id => @user.id response.should redirect_to user_car_path end </code></pre> Insert whatever minimal attributes you need to create a user into <code>User.create(...)</code>. I think that should do it. If you want to do this with mocks (which is generally better practice, to keep controller/model specs decoupled), here's <a href="http://www.vaporbase.com/postings/Rspec_example_for_nested_resource_index_action" rel="nofollow">a good starting point on how to do it</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POActionController::RoutingError with rspec
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USChris Salzberg
UserOwnerUserId
1. USChris Salzberg
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.