StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18187999
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-12T13:16:39.407
FavoriteCount
0
LastActivityDate
2014-05-08T21:59:52.647
LastEditDate
2014-05-08T21:59:52.647
LastEditorUserId
1082743
OwnerUserId
2527338
ParentId
18180389
PostTypeId
2
Score
32
ViewCount
0
LastEditorDisplayName
text
Body
There are 2 differences but the result is exactly the same. Both are in regards to the rspec mocks/expectations syntax. <ol> <li>Use of #allow instead of #stub method. First case uses the new rspec syntax introduced this year. This is now the preferred way of using rspec. Altough the old syntax isn't deprecated, it will probably be disabled by default in rspec3. More info on this topic from the maintainer of rspec: <a href="http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax">http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax</a> <a href="http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3">http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3</a></li> <li>Use of block instead of #and_return to define the returning value. This has nothing to do with the mentioned syntax change; both approaches have been available for quite a while (since rspec 1). It is more appropriate to use the #and_return method, since it is (a) the default way, (b) more readable and (c) comes without any runtime overhead. The second approach using block is usually reserved to the corner cases, when you wish to return something of more dynamic nature - not a constant, but some kind of calculation.</li> </ol> The answer to your question would be to use combination of both: <ul> <li>use the #allow instead of #stub </li> <li>use #and_return instead of block, unless you need to return dynamically calculated value</li> </ul> E.g.: <pre><code>book = double('book') allow(book).to receive(:title).and_return('The RSpec Book') </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAllow vs Stub, what's the difference?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDamon Aw
UserOwnerUserId
1. USjurglic
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAllow vs Stub, what's the difference?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.