StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13616682
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-11-29T00:09:09.410
FavoriteCount
0
LastActivityDate
2012-12-01T09:35:33.433
LastEditDate
2017-05-23T11:51:05.997
LastEditorUserId
-1
OwnerUserId
820254
ParentId
13595883
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Update: I found a slightly more "magical" way to do this using <a href="http://api.rubyonrails.org/classes/ActiveRecord/NestedAttributes/ClassMethods.html#method-i-accepts_nested_attributes_for" rel="nofollow noreferrer"><code>accepts_nested_attributes_for</code></a>. First, add a line to your <code>CauseUserMembership</code> model: <pre><code>class CauseUserMembership < ActiveRecord::Base attr_accessible :cause_id, :user_id belongs_to :user belongs_to :cause accepts_nested_attributes_for :cause </code></pre> With that change, you can do this: <pre><code>def create @membership = current_user.memberships.build @membership.cause = Cause.new(params[:cause].merge(:created_by => current_user.id) respond_to do |format| if @membership.save ... </code></pre> Because you have told rails to accept nested attributes for the <code>cause</code> association on <code>CauseUserMembership</code>, it will save the new cause you assigned to <code>@membership.cause</code> when it saves the membership itself. So you can save both the cause and membership records at one time, rather than separately. Original answer: I think what you've done is pretty much the right way to do this. It can be simplified a tad bit: you don't need to build <code>cause</code> from <code>current_user</code>, you can just use <code>new</code> (the <code>:through</code> associations on <code>cause</code> and <code>current_user</code> are set when you create <code>@membership</code>). So like this (I only changed the first line in <code>create</code>): <pre><code>def create @cause = Cause.new(params[:cause].merge(:created_by => current_user.id)) respond_to do |format| if @cause.save @membership = current_user.cause_user_memberships.build(:cause_id => @cause.id) @membership.save ... </code></pre> See also: <a href="https://stackoverflow.com/questions/9432343/many-to-many-through-association-build-create-properties-in-rails-app">Many-to-Many through association Build/Create properties in Rails app</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails 3: Has_many through and Me
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USChris Salzberg
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails 3: Has_many through and Me
 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

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.