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
19 lines
550 B
Ruby
19 lines
550 B
Ruby
# @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 ApiSecret < ApplicationRecord
|
|
has_secure_token :secret
|
|
|
|
belongs_to :user
|
|
|
|
validates :description, presence: true, length: { maximum: 300 }
|
|
validate :user_api_secret_count
|
|
|
|
private
|
|
|
|
def user_api_secret_count
|
|
return if user && user.api_secrets.count < 20
|
|
|
|
errors.add(:user, "API secret limit of 20 per user has been reached")
|
|
end
|
|
end
|