StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7292618
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-03T10:39:09.750
FavoriteCount
0
LastActivityDate
2011-09-03T10:39:09.750
LastEditDate
2017-05-23T10:28:02.293
LastEditorUserId
-1
OwnerUserId
560073
ParentId
7031836
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The solution, just like <a href="https://stackoverflow.com/users/293686/mauricio-linhares">Maurício Linhares</a> wrote in his comment, is to go through the actors model and group by movies. The problem is that Sunspot doesn't support Solr 3.3 or 4.0, which is the only Solr versions that support grouping. Here is my solution using Sunspot 1.2.1 and Solr 3.3. In my example <code>movie_id</code> is placed in the actors table, this isn't done in my real application. <pre><code># == Schema Information # # Table name: actors # # id :integer(4) not null, primary key # name :string(255) # created_at :datetime # updated_at :datetime # movie_id :integer(4) # class Actor < ActiveRecord::Base searchable do # We need to store the movie_id as an string # So it can be sorted. We also need to pass the # stored: true params string :movie_id, stored: true do movie_id.to_s end end def search_using_solr scoped = Sunspot.new_search(Actor) scoped.build do adjust_solr_params do |params| params[:group] = true params[:"group.field"] = "movie_id_s" params[:"group.format"] = "simple" end end # Sunspot 1.2.1 doesn't support grouping, so we need to do some hacking. def scoped.hits @hits ||= @solr_result["grouped"].values.first["doclist"]["docs"].map do |doc| Sunspot::Search::Hit.new(doc, nil, self) end end def scoped.total @total ||= @solr_result["grouped"]["movie_id_s"]["matches"] || 0 end # Here we'll only fetch the stored data from Solr it self, # and then pass it manualy to ActiveRecord. Movie.where({ id: scoped.execute.hits.map{ |h| h.stored(:movie_id) } }) end end </code></pre> Cred to <a href="https://github.com/alindeman" rel="nofollow noreferrer">alindeman</a> for his <a href="https://gist.github.com/f987013b2feec5b28456" rel="nofollow noreferrer">example gist</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGroup using Sunspot/Solr?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USOleander
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGroup using Sunspot/Solr?
 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
3. 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.