ee0a521a83
* Favoring delete_all on user relationships Prior to this commit, several of the user's "has_many" were marked as `depenedent: :destroy`. In the case of :destroy, ActiveRecord instantiates each object and then runs destroy. Whereas in the case of :delete, ActiveRecord issues a SQL command to delete the related files. It is often "safer" to use :destroy, as it guarantees that you'll instantiate the record and run it's callbacks. But sometimes you have to go with the speed of SQL. And while not directly related to #15424 it is representative of our callback ecosystem creating some unexpected computational loads. Related to #15442 and #15424 * Noting models that user no longer cascade destroys
11 lines
395 B
Ruby
11 lines
395 B
Ruby
module Ahoy
|
|
# @note When we destroy the related user, it's using dependent:
|
|
# :delete for the relationship. That means no before/after
|
|
# destroy callbacks will be called on this object.
|
|
class Visit < ApplicationRecord
|
|
self.table_name = "ahoy_visits"
|
|
|
|
has_many :events, class_name: "Ahoy::Event", dependent: :destroy
|
|
belongs_to :user, optional: true
|
|
end
|
|
end
|