StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17938591
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-30T04:55:17.940
FavoriteCount
0
LastActivityDate
2013-07-30T04:55:17.940
LastEditDate
LastEditorUserId
0
OwnerUserId
1459553
ParentId
16507012
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I had exactly the same issue following the same Ajax section of Chapter 11 in the RailsTutorial(with Rails 3.2). I think Michael de Silva was right in that the xhr were unfortunately mixed with the RSpec here. Anyways, I decided that for the sake of completeness (I'm almost done with the tutorial) - I was going to get xhr to somehow work here. I think Mike Hartl's Listing 11.37 should have used the ActionDispatcher::Integration::RequestHelpers method xhr, as in <a href="http://api.rubyonrails.org/classes/ActionDispatch/Integration/RequestHelpers.html#method-i-xhr" rel="nofollow">http://api.rubyonrails.org/classes/ActionDispatch/Integration/RequestHelpers.html#method-i-xhr</a> rather than the ActionController::TestCase::Behavior method xhr, as in <a href="http://api.rubyonrails.org/classes/ActionController/TestCase/Behavior.html#method-i-xhr" rel="nofollow">http://api.rubyonrails.org/classes/ActionController/TestCase/Behavior.html#method-i-xhr</a> So I replaced the reference to actions :create and :destroy with their named routes and the test examples in Listing 11.37 turned green. The original <pre><code>expect do xhr :post, :create, relationship: { followed_id: other_user.id } end.to change(Relationship, :count).by(1) </code></pre> becomes, <pre><code>expect do xhr :post, relationships_path, relationship: { followed_id: other_user.id } end.to change(Relationship, :count).by(1) </code></pre> and, the original <pre><code>expect do xhr :delete, :destroy, id: relationship.id end.to change(Relationship, :count).by(-1) </code></pre> becomes, <pre><code>expect do xhr :delete, relationship_path(relationship.id), id: relationship.id end.to change(Relationship, :count).by(-1) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POI'm learning Rails with M. Hartl's Tutorial. Ch. 11.2.5 and got this error in tests: ArgumentError: bad argument (expected URI object or URI string)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USwr200m
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThis should be accepted answer! Had the exact same problem and it works. Thanks!
 singulars
 PostPostId
 PO
 UserUserId
 USLevara

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.