StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCan't define :joins conditions in has_many relationship?
primarykey
Id
788582
data
AcceptedAnswerId
909132
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-04-25T09:13:03.110
FavoriteCount
2
LastActivityDate
2009-10-26T18:00:02.777
LastEditDate
LastEditorUserId
0
OwnerUserId
62612
ParentId
0
PostTypeId
1
Score
0
ViewCount
2977
LastEditorDisplayName
text
Body
I have a relationship table : <pre><code>create_table "animal_friends", :force => true do |t| t.integer "animal_id" t.integer "animal_friend_id" t.datetime "created_at" t.datetime "updated_at" t.integer "status_id", :default => 1 end </code></pre> linking animals to others. Best way to retreive associations in SQL is : <pre><code>SELECT animals.* from animals join animal_friends as af on animals.id = case when af.animal_id = #{id} then af.animal_friend_id else af.animal_id end WHERE #{id} in (af.animal_id, af.animal_friend_id) </code></pre> And I can't find a way to create a proper has_many relation in rails with this. Apparently, there's no way to provide joining conditions for has_many. I'm currently using a finder_sql : <pre><code>has_many :friends, :class_name => "Animal", :finder_sql => 'SELECT animals.* from animals join animal_friends as af on animals.id = case when af.animal_id = #{id} then af.animal_friend_id else af.animal_id end ' + 'WHERE #{id} in (af.animal_id, af.animal_friend_id) and status_id = #{Status::CONFIRMED.id}' </code></pre> but this method has the great disadvantage of breaking activerecord magic. For instance : <pre><code>@animal.friends.first </code></pre> will execute the finder_sql without limit, fetching thousands of rows, then taking the first of the array (and loosing several precious seconds / req). I guess it's a missing feature from AR, but I'd like to be sure first :) Thanks
Tags
<activerecord><join><has-many><condition>
Title
Can't define :joins conditions in has_many relationship?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGravis
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCan't define :joins conditions in has_many relationship?
 UserUserId
 USAdrian M.
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POCan't define :joins conditions in has_many relationship?
 UserUserId
 USMike
 VoteTypeVoteTypeId
 VTFavorite
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.