StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17301557
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-25T15:35:34.543
FavoriteCount
0
LastActivityDate
2013-06-25T16:22:53.193
LastEditDate
2013-06-25T16:22:53.193
LastEditorUserId
229044
OwnerUserId
229044
ParentId
17301368
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Rails doesn't evaluate the query until you actually try to access the results. Calling <code>Model.where</code> just returns an <code>ActiveRecord::Relation</code> onto which you can chain additional <code>where</code>/<code>order</code>/etc calls. Try this (<code>.all</code> forces the query to be evaluated and returns an array of results): <pre><code>def self.my_func Interest.where(id: [1,2]).all end </code></pre> Note that should shouldn't actually do this. It's much better for your model to just allow the <code>ActiveRecord::Relation</code> to be returned from the method, so the calling code can apply additional scoping/ordering methods to it. Also note that, instead of manually building an <code>id in (?)</code> query, Rails is smart enough to do it for you if you just use <code>where(id: [1,2])</code>. <hr> Bonus notes: On the terminal, the results get evaluated from <code>Model.where</code> immediately because IRB invokes <code>inspect</code> on the result of each expression you enter so it has something to print, and the returned <code>ActiveRecord::Relation</code> evaluates its query when inspected. You can bypass this to prove the point to yourself by adding <code>;nil</code>, so that your statement evaluates to <code>nil</code>; note that the <code>SELECT</code> doesn't happen until I manually call <code>x.inspect</code>: <pre><code>irb(main):008:0> x = User.where("name like 'bob'"); nil => nil irb(main):009:0> x.inspect User Load (0.5ms) SELECT "users".* FROM "users" WHERE (name like 'bob') => "[]" </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POActiveRecord .where() method ignored
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmeagar
UserOwnerUserId
1. USmeagar
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POActiveRecord .where() method ignored
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COYes! You saved me lot of time! I didn't know that the query isn't executed until I try to access result. Thank you soooo much !
 singulars
 PostPostId
 PO
 UserUserId
 USGozup

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.