This project is archived and is in readonly mode.
hmt needlessly pushes join record onto through collection, duplicating create! action
Reported by Paul Bowsher | October 16th, 2010 @ 02:50 PM
Given a standard hmt setup, e.g. User <-> Membership <-> Group, user.groups << group persists just one Membership, but pushes the Membership onto the user instances memberships collection twice.
This should be left to through_association.create! to do, but the membership is manually pushed as well
Comments and changes to this ticket
-
Paul Bowsher October 16th, 2010 @ 02:57 PM
- Tag set to patch
Patch attached. Tests passing (as far as I can tell)
-
Santiago Pastorino February 2nd, 2011 @ 04:30 PM
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:30 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>