StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7116770
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-19T03:53:41.830
FavoriteCount
0
LastActivityDate
2011-08-19T17:50:32.117
LastEditDate
2011-08-19T17:50:32.117
LastEditorUserId
194869
OwnerUserId
194869
ParentId
7114290
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I thought this would get me what I needed, but it doesn't. Calling <code>feature.assets</code> (with <code>feature</code> as an item returned in my query) does another query to look for all <code>assets</code> related to that <code>feature</code>. <pre><code>Feature.joins("LEFT OUTER JOIN assets on assets.feature_id = feature.id AND asset.issue_date = #{Date.tomorrow}") </code></pre> So here's what does work. Seems a little cleaner, too. My <code>Feature</code> model already has a <code>has_many :assets</code> set on it. I've set up another association with <code>has_many :tomorrows_assets</code> that points to <code>Assets</code>, but with a condition on it. Then, when I ask for <code>Feature.all</code> or <code>Feature.name_of_scope</code>, I can specify <code>.includes(:tomorrows_assets)</code>. Winner winner, chicken dinner. <pre><code>has_many :tomorrows_assets, :class_name => "Asset", :readonly => true, :conditions => "issue_date = '#{Date.tomorrow.to_s}'" </code></pre> I can successfully query <code>Features</code> and get just what I need included with it, only if it matches the specified criteria (and I've set <code>:readonly</code> because I know I'll never want to edit <code>Assets</code> like this). Here's an IRB session that shows the magic. <pre><code>features = Feature.includes(:tomorrows_assets) feature1 = features.find_all{ |f| f.name == 'This Feature Has Assets' }.first feature1.tomorrows_assets => [#<Asset id:1>, #<Asset id:2>] feature2 = features.find_all{ |f| f.name == 'This One Does Not' }.first feature2.tomorrows_assets => [] </code></pre> And all in only two SQL queries.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails 3: ActiveRecord query with :includes only returns results that have related values in included table?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBen Kreeger
UserOwnerUserId
1. USBen Kreeger
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails 3: ActiveRecord query with :includes only returns results that have related values in included table?
 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
 VTUndeletion
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.