Databases
StackOverflow2013
Postsdbo
POHMT collection_singular_ids= deletion of join models is direct, no destroy callbacks are triggered
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHMT collection_singular_ids= deletion of join models is direct, no destroy callbacks are triggered
    primarykey
    data
    text
    <p>Just ran into an issue with a has_many :through association and after/before-destroy callbacks not being triggered.</p> <p>Say, I have users, groups, and an intermediate relation called membership. I have a form that allows users to be enrolled into groups by creating a new membership record when they check off associated checkboxes. Basically an array of group_ids.</p> <p>Looks something like this:</p> <pre><code>Which group would you like to join? (check all that apply) [] Group A [] Group B [] Group C </code></pre> <p>And I wish to record actions such as joining a group or leaving a group to activity log table and do some other less important thigns.</p> <p>I have the following defined:</p> <pre><code>class Group &lt; AR::Base has_many :memberships has_many :users, :through =&gt; :memberships end class Membership &lt; AR::Base belongs_to :user belongs_to :group after_create :log_event_to_audit_table after_destroy :log_event_to_audit_table end class User &lt; ActiveRecord::Base has_many :memberships has_many :groups, :through =&gt; :memberships attr_accessible :group_ids # enables mass-assignment end </code></pre> <p>When a new membership record is created the after_create is run as expected. However, the after_destroy does not get triggered!</p> <p>After google-ing and read up the docs I discovered the reason why:</p> <blockquote> <p>"Automatic deletion of join models is direct, no destroy callbacks are triggered" - from Ruby Guides.</p> </blockquote> <p>Hmmmmmm...</p> <p>So the join model's (in this case Membership's) destroy callbacks are not being triggered. Well that's a downer. Any reason as to why?</p> <p>So my question what is the best way to work around this issue? Should I define my own membership_ids= method in User model that calls membership.destroy directly?</p> <p>Open to any suggestions about the best practices in such a scenario.</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSwartz
    1. USSwartz
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHMT collection_singular_ids= deletion of join models is direct, no destroy callbacks are triggered
      1. USpjumble
      1. VTFavorite
    2. VO
      singulars
      1. POHMT collection_singular_ids= deletion of join models is direct, no destroy callbacks are triggered
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHMT collection_singular_ids= deletion of join models is direct, no destroy callbacks are triggered
      1. This table or related slice is empty.
      1. VTUpMod
    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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload