vendor/ruby/2.1.0/gems/activerecord-4.1.1/lib/active_record/associations/collection_association.rb
# Should we deal with assoc.first or assoc.last by issuing an independent query to
# the database, or by getting the target, and then taking the first/last item from that?
#
# If the args is just a non-empty options hash, go to the database.
#
# Otherwise, go to the database only if none of the following are true:
#   * target already loaded
#   * owner is new record
#   * target contains new or changed record(s)


If the args is just a non-empty options hash, go to the database.

Otherwise, go to the database only if none of the following are true:
target already loaded
owner is new record
target contains new or changed record(s)
If the args is just a non - empty options hash go to the database . Otherwise go to the database only if none of the following are true : target already loaded owner is new record target contains new or changed record ( s )
def fetch_first_nth_or_last_using_find?(args)
          if args.first.is_a?(Hash)
            true
          else
            !(loaded? ||
              owner.new_record? ||
              target.any? { |record| record.new_record? || record.changed? })
          end
        end
def fetch_first_nth_or_last_using_find? ( args ) if args . first . is_a? ( Hash ) true else ! ( loaded? || owner . new_record? || target . any? { | record | record . new_record? || record . changed? } ) end end
Should we deal with assoc.first or assoc.last by issuing an independent query to
the database, or by getting the target, and then taking the first/last item from that?
Should we deal with assoc . first or assoc . last by issuing an independent query to the database or by getting the target and then taking the first / last item from that?
args
<not_specific>