StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6405861
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-20T00:09:19.047
FavoriteCount
0
LastActivityDate
2011-06-20T00:09:19.047
LastEditDate
LastEditorUserId
0
OwnerUserId
674329
ParentId
6400530
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>I've found the trick is this gem <a href="http://rubygems.org/gems/nested_has_many_through" rel="nofollow">http://rubygems.org/gems/nested_has_many_through</a> which can do something like this:</p> <pre><code>class Author < User has_many :posts has_many :categories, :through => :posts, :uniq => true has_many :similar_posts, :through => :categories, :source => :posts has_many :similar_authors, :through => :similar_posts, :source => :author, :uniq => true has_many :posts_of_similar_authors, :through => :similar_authors, :source => :posts, :uniq => true has_many :commenters, :through => :posts, :uniq => true end class Post < ActiveRecord::Base belongs_to :author belongs_to :category has_many :comments has_many :commenters, :through => :comments, :source => :user, :uniq => true end </code></pre> <p>This has super-simplified my queries and collections.</p> <p>This is all the code I ended up needing. I'm told the gem nested_has_many_through will be standard in Rails 3.1</p> <h1>User model</h1> <pre><code> has_many :products, :dependent => :destroy has_many :product_posts, :through => :products, :source => :posts, :uniq => true has_many :food_orders, :through => :product_posts, :source => :orders, :uniq => true </code></pre> <h1>OrdersController</h1> <pre><code> @orders_for_my_products = current_user.food_orders.all </code></pre> <h1>Orders index</h1> <pre><code><%= render :partial => "order", :collection => @orders_for_my_products, :locals => {:order => @order} %> </code></pre> <p>This returns the deep nested data via relationships using minimal code. I sure hope its efficient, but at least my sanity is spared!</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORender a partial with a collection through multiple levels of has_many associations
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USthejonster
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORender a partial with a collection through multiple levels of has_many associations
  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
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.