rails--rails/activerecord/test/models/toy.rb

# frozen_string_literal: true

class Toy < ActiveRecord::Base
  self.primary_key = :toy_id
  belongs_to :pet

  has_many :sponsors, as: :sponsorable, inverse_of: :sponsorable

  scope :with_pet, -> { joins(:pet) }
end
Use frozen-string-literal in ActiveRecord 2017-07-09 13:41:28 -04:00			`# frozen_string_literal: true`

Ensure has_many :through works with changed primary keys [#736 state:resolved] Signed-off-by: Pratik Naik <pratiknaik@gmail.com> 2009-03-09 09:42:51 -04:00			`class Toy < ActiveRecord::Base`
Deprecate set_primary_key in favour of self.primary_key= 2011-11-29 13:58:41 -05:00			`self.primary_key = :toy_id`
Ensure has_many :through works with changed primary keys [#736 state:resolved] Signed-off-by: Pratik Naik <pratiknaik@gmail.com> 2009-03-09 09:42:51 -04:00			`belongs_to :pet`
The join_nodes must be passed to the JoinDependency initializer and therefore counted by the alias tracker. This is because the association_joins are aliased on initialization and then the tables are cached, so it is no use to alias the join_nodes later. Fixes #2556. 2011-08-29 10:01:17 -04:00
Fix has_many_inversing with touch: true on a belongs_to association with inverse `has_many_inversing` adds records to a has_many association. It does so with destroyed records, too. So if a child was destroyed with a `touch: true` association on the parent and the parent was not loaded, it tried to load the parent to touch it. While loading the parent it added the child record to the parent's has_many association. The logic doing this always set the child's parent id – even if it was correct/the same already. But since the child is destroyed, it resulted in a `FrozenError`. This commit prevents doing the unnecessary setting of the identical id and therefore fixes this error. Fixes #40943 by not doing an unneeded attribute set. Closes #40969. [Markus Doits + Rafael Mendonça França] 2021-01-07 17:15:24 -05:00			`has_many :sponsors, as: :sponsorable, inverse_of: :sponsorable`

Deprecate eager-evaluated scopes. Don't use this: scope :red, where(color: 'red') default_scope where(color: 'red') Use this: scope :red, -> { where(color: 'red') } default_scope { where(color: 'red') } The former has numerous issues. It is a common newbie gotcha to do the following: scope :recent, where(published_at: Time.now - 2.weeks) Or a more subtle variant: scope :recent, -> { where(published_at: Time.now - 2.weeks) } scope :recent_red, recent.where(color: 'red') Eager scopes are also very complex to implement within Active Record, and there are still bugs. For example, the following does not do what you expect: scope :remove_conditions, except(:where) where(...).remove_conditions # => still has conditions 2012-03-21 18:18:18 -04:00			`scope :with_pet, -> { joins(:pet) }`
Ensure has_many :through works with changed primary keys [#736 state:resolved] Signed-off-by: Pratik Naik <pratiknaik@gmail.com> 2009-03-09 09:42:51 -04:00			`end`