2010-05-08 19:06:05 -04:00
|
|
|
module ActiveRecord
|
2015-07-08 06:16:16 -04:00
|
|
|
# = Active Record \Persistence
|
2010-05-08 19:06:05 -04:00
|
|
|
module Persistence
|
2011-12-15 15:07:41 -05:00
|
|
|
extend ActiveSupport::Concern
|
|
|
|
|
|
|
|
module ClassMethods
|
|
|
|
# Creates an object (or multiple objects) and saves it to the database, if validations pass.
|
|
|
|
# The resulting object is returned whether the object was saved successfully to the database or not.
|
|
|
|
#
|
2011-12-25 08:28:25 -05:00
|
|
|
# The +attributes+ parameter can be either a Hash or an Array of Hashes. These Hashes describe the
|
2011-12-15 15:07:41 -05:00
|
|
|
# attributes on the objects that are to be created.
|
|
|
|
#
|
|
|
|
# ==== Examples
|
|
|
|
# # Create a single new object
|
2012-10-23 07:02:34 -04:00
|
|
|
# User.create(first_name: 'Jamie')
|
2011-12-15 15:07:41 -05:00
|
|
|
#
|
|
|
|
# # Create an Array of new objects
|
2012-10-23 07:02:34 -04:00
|
|
|
# User.create([{ first_name: 'Jamie' }, { first_name: 'Jeremy' }])
|
2011-12-15 15:07:41 -05:00
|
|
|
#
|
|
|
|
# # Create a single object and pass it into a block to set other attributes.
|
2012-10-23 07:02:34 -04:00
|
|
|
# User.create(first_name: 'Jamie') do |u|
|
2011-12-15 15:07:41 -05:00
|
|
|
# u.is_admin = false
|
|
|
|
# end
|
|
|
|
#
|
|
|
|
# # Creating an Array of new objects using a block, where the block is executed for each object:
|
2012-10-23 07:02:34 -04:00
|
|
|
# User.create([{ first_name: 'Jamie' }, { first_name: 'Jeremy' }]) do |u|
|
2011-12-15 15:07:41 -05:00
|
|
|
# u.is_admin = false
|
|
|
|
# end
|
2012-09-12 12:35:05 -04:00
|
|
|
def create(attributes = nil, &block)
|
2011-12-15 15:07:41 -05:00
|
|
|
if attributes.is_a?(Array)
|
2012-09-12 12:35:05 -04:00
|
|
|
attributes.collect { |attr| create(attr, &block) }
|
2011-12-15 15:07:41 -05:00
|
|
|
else
|
2012-09-12 12:35:05 -04:00
|
|
|
object = new(attributes, &block)
|
2011-12-15 15:07:41 -05:00
|
|
|
object.save
|
|
|
|
object
|
|
|
|
end
|
|
|
|
end
|
2012-11-29 10:45:31 -05:00
|
|
|
|
2014-08-07 22:05:21 -04:00
|
|
|
# Creates an object (or multiple objects) and saves it to the database,
|
|
|
|
# if validations pass. Raises a RecordInvalid error if validations fail,
|
|
|
|
# unlike Base#create.
|
2014-08-06 13:52:48 -04:00
|
|
|
#
|
|
|
|
# The +attributes+ parameter can be either a Hash or an Array of Hashes.
|
2014-08-07 22:05:21 -04:00
|
|
|
# These describe which attributes to be created on the object, or
|
|
|
|
# multiple objects when given an Array of Hashes.
|
2014-08-05 11:36:29 -04:00
|
|
|
def create!(attributes = nil, &block)
|
|
|
|
if attributes.is_a?(Array)
|
|
|
|
attributes.collect { |attr| create!(attr, &block) }
|
|
|
|
else
|
|
|
|
object = new(attributes, &block)
|
|
|
|
object.save!
|
|
|
|
object
|
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2012-11-29 10:45:31 -05:00
|
|
|
# Given an attributes hash, +instantiate+ returns a new instance of
|
2014-05-20 04:33:50 -04:00
|
|
|
# the appropriate class. Accepts only keys as strings.
|
2012-11-29 10:45:31 -05:00
|
|
|
#
|
|
|
|
# For example, +Post.all+ may return Comments, Messages, and Emails
|
|
|
|
# by storing the record's subclass in a +type+ attribute. By calling
|
|
|
|
# +instantiate+ instead of +new+, finder methods ensure they get new
|
|
|
|
# instances of the appropriate class for each record.
|
|
|
|
#
|
2016-03-02 16:32:52 -05:00
|
|
|
# See <tt>ActiveRecord::Inheritance#discriminate_class_for_record</tt> to see
|
2012-11-29 10:45:31 -05:00
|
|
|
# how this "single-table" inheritance mapping is implemented.
|
2016-08-31 08:54:38 -04:00
|
|
|
def instantiate(attributes, column_types = {}, &block)
|
2014-05-20 04:33:50 -04:00
|
|
|
klass = discriminate_class_for_record(attributes)
|
2014-11-14 12:45:53 -05:00
|
|
|
attributes = klass.attributes_builder.build_from_database(attributes, column_types)
|
2016-08-31 08:54:38 -04:00
|
|
|
klass.allocate.init_with("attributes" => attributes, "new_record" => false, &block)
|
2012-11-29 10:45:31 -05:00
|
|
|
end
|
|
|
|
|
|
|
|
private
|
|
|
|
# Called by +instantiate+ to decide which class to use for a new
|
|
|
|
# record instance.
|
|
|
|
#
|
2014-11-14 12:45:53 -05:00
|
|
|
# See +ActiveRecord::Inheritance#discriminate_class_for_record+ for
|
2012-11-29 10:45:31 -05:00
|
|
|
# the single-table inheritance discriminator.
|
|
|
|
def discriminate_class_for_record(record)
|
|
|
|
self
|
|
|
|
end
|
2011-12-15 15:07:41 -05:00
|
|
|
end
|
|
|
|
|
2010-08-12 11:04:16 -04:00
|
|
|
# Returns true if this object hasn't been saved yet -- that is, a record
|
2014-02-27 11:10:47 -05:00
|
|
|
# for the object doesn't exist in the database yet; otherwise, returns false.
|
2010-05-08 19:06:05 -04:00
|
|
|
def new_record?
|
2013-01-24 23:42:39 -05:00
|
|
|
sync_with_transaction_state
|
2010-11-28 10:55:48 -05:00
|
|
|
@new_record
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Returns true if this object has been destroyed, otherwise returns false.
|
|
|
|
def destroyed?
|
2013-01-24 23:42:39 -05:00
|
|
|
sync_with_transaction_state
|
2010-05-08 19:06:05 -04:00
|
|
|
@destroyed
|
|
|
|
end
|
|
|
|
|
2011-12-25 08:41:50 -05:00
|
|
|
# Returns true if the record is persisted, i.e. it's not a new record and it was
|
|
|
|
# not destroyed, otherwise returns false.
|
2010-05-08 19:06:05 -04:00
|
|
|
def persisted?
|
2015-03-02 10:51:29 -05:00
|
|
|
sync_with_transaction_state
|
|
|
|
!(@new_record || @destroyed)
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Saves the model.
|
|
|
|
#
|
2015-10-13 08:02:14 -04:00
|
|
|
# If the model is new, a record gets created in the database, otherwise
|
2010-05-08 19:06:05 -04:00
|
|
|
# the existing record gets updated.
|
|
|
|
#
|
2015-10-13 08:02:14 -04:00
|
|
|
# By default, save always runs validations. If any of them fail the action
|
2016-01-30 14:03:54 -05:00
|
|
|
# is cancelled and #save returns +false+, and the record won't be saved. However, if you supply
|
2016-09-25 00:39:05 -04:00
|
|
|
# <tt>validate: false</tt>, validations are bypassed altogether. See
|
2010-05-08 19:06:05 -04:00
|
|
|
# ActiveRecord::Validations for more information.
|
|
|
|
#
|
2014-12-29 18:31:04 -05:00
|
|
|
# By default, #save also sets the +updated_at+/+updated_on+ attributes to
|
|
|
|
# the current time. However, if you supply <tt>touch: false</tt>, these
|
|
|
|
# timestamps will not be updated.
|
|
|
|
#
|
2014-12-15 01:10:15 -05:00
|
|
|
# There's a series of callbacks associated with #save. If any of the
|
|
|
|
# <tt>before_*</tt> callbacks throws +:abort+ the action is cancelled and
|
|
|
|
# #save returns +false+. See ActiveRecord::Callbacks for further
|
2010-05-08 19:06:05 -04:00
|
|
|
# details.
|
2013-04-17 06:33:33 -04:00
|
|
|
#
|
|
|
|
# Attributes marked as readonly are silently ignored if the record is
|
|
|
|
# being updated.
|
2014-12-27 18:17:57 -05:00
|
|
|
def save(*args)
|
|
|
|
create_or_update(*args)
|
2012-11-19 09:50:44 -05:00
|
|
|
rescue ActiveRecord::RecordInvalid
|
|
|
|
false
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Saves the model.
|
|
|
|
#
|
2014-12-24 16:02:01 -05:00
|
|
|
# If the model is new, a record gets created in the database, otherwise
|
2010-05-08 19:06:05 -04:00
|
|
|
# the existing record gets updated.
|
|
|
|
#
|
2015-10-13 08:02:14 -04:00
|
|
|
# By default, #save! always runs validations. If any of them fail
|
2016-01-30 14:03:54 -05:00
|
|
|
# ActiveRecord::RecordInvalid gets raised, and the record won't be saved. However, if you supply
|
2016-09-25 00:39:05 -04:00
|
|
|
# <tt>validate: false</tt>, validations are bypassed altogether. See
|
2015-10-13 08:02:14 -04:00
|
|
|
# ActiveRecord::Validations for more information.
|
2010-05-08 19:06:05 -04:00
|
|
|
#
|
2014-12-29 18:31:04 -05:00
|
|
|
# By default, #save! also sets the +updated_at+/+updated_on+ attributes to
|
|
|
|
# the current time. However, if you supply <tt>touch: false</tt>, these
|
|
|
|
# timestamps will not be updated.
|
|
|
|
#
|
2014-12-15 01:10:15 -05:00
|
|
|
# There's a series of callbacks associated with #save!. If any of
|
|
|
|
# the <tt>before_*</tt> callbacks throws +:abort+ the action is cancelled
|
|
|
|
# and #save! raises ActiveRecord::RecordNotSaved. See
|
2010-05-08 19:06:05 -04:00
|
|
|
# ActiveRecord::Callbacks for further details.
|
2013-04-17 06:33:33 -04:00
|
|
|
#
|
|
|
|
# Attributes marked as readonly are silently ignored if the record is
|
|
|
|
# being updated.
|
2014-12-27 18:17:57 -05:00
|
|
|
def save!(*args)
|
2015-01-06 07:31:08 -05:00
|
|
|
create_or_update(*args) || raise(RecordNotSaved.new("Failed to save the record", self))
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Deletes the record in the database and freezes this instance to
|
|
|
|
# reflect that no changes should be made (since they can't be
|
|
|
|
# persisted). Returns the frozen instance.
|
|
|
|
#
|
2010-08-04 19:09:09 -04:00
|
|
|
# The row is simply removed with an SQL +DELETE+ statement on the
|
2010-05-08 19:06:05 -04:00
|
|
|
# record's primary key, and no callbacks are executed.
|
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# Note that this will also delete records marked as {#readonly?}[rdoc-ref:Core#readonly?].
|
2014-12-03 11:31:25 -05:00
|
|
|
#
|
2010-05-08 19:06:05 -04:00
|
|
|
# To enforce the object's +before_destroy+ and +after_destroy+
|
2012-10-14 19:00:57 -04:00
|
|
|
# callbacks or any <tt>:dependent</tt> association
|
2010-05-08 19:06:05 -04:00
|
|
|
# options, use <tt>#destroy</tt>.
|
|
|
|
def delete
|
2012-03-01 22:10:06 -05:00
|
|
|
self.class.delete(id) if persisted?
|
2010-05-08 19:06:05 -04:00
|
|
|
@destroyed = true
|
|
|
|
freeze
|
|
|
|
end
|
|
|
|
|
2010-08-12 11:04:16 -04:00
|
|
|
# Deletes the record in the database and freezes this instance to reflect
|
2010-06-16 13:38:14 -04:00
|
|
|
# that no changes should be made (since they can't be persisted).
|
2012-06-05 02:35:05 -04:00
|
|
|
#
|
2014-12-15 01:10:15 -05:00
|
|
|
# There's a series of callbacks associated with #destroy. If the
|
|
|
|
# <tt>before_destroy</tt> callback throws +:abort+ the action is cancelled
|
|
|
|
# and #destroy returns +false+.
|
|
|
|
# See ActiveRecord::Callbacks for further details.
|
2010-05-08 19:06:05 -04:00
|
|
|
def destroy
|
2016-08-30 09:44:06 -04:00
|
|
|
_raise_readonly_record_error if readonly?
|
2011-05-31 10:43:19 -04:00
|
|
|
destroy_associations
|
2015-02-01 17:20:36 -05:00
|
|
|
self.class.connection.add_transaction_record(self)
|
2016-12-01 17:39:15 -05:00
|
|
|
@_trigger_destroy_callback = if persisted?
|
|
|
|
destroy_row > 0
|
|
|
|
else
|
|
|
|
true
|
|
|
|
end
|
2010-05-08 19:06:05 -04:00
|
|
|
@destroyed = true
|
|
|
|
freeze
|
|
|
|
end
|
|
|
|
|
2012-06-05 02:35:05 -04:00
|
|
|
# Deletes the record in the database and freezes this instance to reflect
|
|
|
|
# that no changes should be made (since they can't be persisted).
|
|
|
|
#
|
2014-12-15 01:10:15 -05:00
|
|
|
# There's a series of callbacks associated with #destroy!. If the
|
|
|
|
# <tt>before_destroy</tt> callback throws +:abort+ the action is cancelled
|
|
|
|
# and #destroy! raises ActiveRecord::RecordNotDestroyed.
|
|
|
|
# See ActiveRecord::Callbacks for further details.
|
2012-06-05 02:35:05 -04:00
|
|
|
def destroy!
|
`destroy` shouldn't raise when child associations fail to save
Deep down in the association internals, we're calling `destroy!` rather
than `destroy` when handling things like `dependent` or autosave
association callbacks. Unfortunately, due to the structure of the code
(e.g. it uses callbacks for everything), it's nearly impossible to pass
whether to call `destroy` or `destroy!` down to where we actually need
it.
As such, we have to do some legwork to handle this. Since the callbacks
are what actually raise the exception, we need to rescue it in
`ActiveRecord::Callbacks`, rather than `ActiveRecord::Persistence` where
it matters. (As an aside, if this code wasn't so callback heavy, it
would handling this would likely be as simple as changing `destroy` to
call `destroy!` instead of the other way around).
Since we don't want to lose the exception when `destroy!` is called (in
particular, we don't want the value of the `record` field to change to
the parent class), we have to do some additional legwork to hold onto it
where we can use it.
Again, all of this is ugly and there is definitely a better way to do
this. However, barring a much more significant re-architecting for what
I consider to be a reletively minor improvement, I'm willing to take
this small hit to the flow of this code (begrudgingly).
2015-07-24 11:13:20 -04:00
|
|
|
destroy || _raise_record_not_destroyed
|
2012-06-05 02:35:05 -04:00
|
|
|
end
|
|
|
|
|
2010-08-12 11:04:16 -04:00
|
|
|
# Returns an instance of the specified +klass+ with the attributes of the
|
|
|
|
# current record. This is mostly useful in relation to single-table
|
|
|
|
# inheritance structures where you want a subclass to appear as the
|
|
|
|
# superclass. This can be used along with record identification in
|
|
|
|
# Action Pack to allow, say, <tt>Client < Company</tt> to do something
|
2012-10-23 07:02:34 -04:00
|
|
|
# like render <tt>partial: @client.becomes(Company)</tt> to render that
|
2010-06-16 13:38:14 -04:00
|
|
|
# instance using the companies/company partial instead of clients/client.
|
2010-05-08 19:06:05 -04:00
|
|
|
#
|
2010-08-12 11:04:16 -04:00
|
|
|
# Note: The new instance will share a link to the same attributes as the original class.
|
2015-04-27 09:53:36 -04:00
|
|
|
# Therefore the sti column value will still be the same.
|
|
|
|
# Any change to the attributes on either instance will affect both instances.
|
2015-07-08 06:16:16 -04:00
|
|
|
# If you want to change the sti column as well, use #becomes! instead.
|
2010-05-08 19:06:05 -04:00
|
|
|
def becomes(klass)
|
|
|
|
became = klass.new
|
|
|
|
became.instance_variable_set("@attributes", @attributes)
|
2015-10-02 09:35:30 -04:00
|
|
|
became.instance_variable_set("@mutation_tracker", @mutation_tracker) if defined?(@mutation_tracker)
|
2015-06-10 12:03:44 -04:00
|
|
|
became.instance_variable_set("@changed_attributes", attributes_changed_by_setter)
|
2010-11-28 10:55:48 -05:00
|
|
|
became.instance_variable_set("@new_record", new_record?)
|
2010-05-08 19:06:05 -04:00
|
|
|
became.instance_variable_set("@destroyed", destroyed?)
|
2015-12-03 13:18:57 -05:00
|
|
|
became.errors.copy!(errors)
|
2011-09-14 11:32:31 -04:00
|
|
|
became
|
|
|
|
end
|
|
|
|
|
2015-07-08 06:16:16 -04:00
|
|
|
# Wrapper around #becomes that also changes the instance's sti column value.
|
2011-09-14 11:32:31 -04:00
|
|
|
# This is especially useful if you want to persist the changed class in your
|
|
|
|
# database.
|
|
|
|
#
|
|
|
|
# Note: The old instance's sti column value will be changed too, as both objects
|
|
|
|
# share the same set of attributes.
|
|
|
|
def becomes!(klass)
|
|
|
|
became = becomes(klass)
|
2014-01-13 09:04:23 -05:00
|
|
|
sti_type = nil
|
|
|
|
if !klass.descends_from_active_record?
|
|
|
|
sti_type = klass.sti_name
|
|
|
|
end
|
|
|
|
became.public_send("#{klass.inheritance_column}=", sti_type)
|
2010-05-08 19:06:05 -04:00
|
|
|
became
|
|
|
|
end
|
|
|
|
|
2012-08-25 21:54:55 -04:00
|
|
|
# Updates a single attribute and saves the record.
|
|
|
|
# This is especially useful for boolean flags on existing records. Also note that
|
|
|
|
#
|
|
|
|
# * Validation is skipped.
|
2015-07-08 06:16:16 -04:00
|
|
|
# * \Callbacks are invoked.
|
2012-08-25 21:54:55 -04:00
|
|
|
# * updated_at/updated_on column is updated if that column is available.
|
|
|
|
# * Updates all the attributes that are dirty in this object.
|
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# This method raises an ActiveRecord::ActiveRecordError if the
|
2013-04-17 05:54:07 -04:00
|
|
|
# attribute is marked as readonly.
|
2014-03-12 11:57:45 -04:00
|
|
|
#
|
2015-10-13 08:02:14 -04:00
|
|
|
# Also see #update_column.
|
2012-08-25 21:54:55 -04:00
|
|
|
def update_attribute(name, value)
|
|
|
|
name = name.to_s
|
|
|
|
verify_readonly_attribute(name)
|
2015-01-23 00:38:50 -05:00
|
|
|
public_send("#{name}=", value)
|
2016-09-23 05:50:39 -04:00
|
|
|
|
Deprecate the behavior of AR::Dirty inside of after_(create|update|save) callbacks
We pretty frequently get bug reports that "dirty is broken inside of
after callbacks". Intuitively they are correct. You'd expect
`Model.after_save { puts changed? }; model.save` to do the same thing as
`model.save; puts model.changed?`, but it does not.
However, changing this goes much farther than just making the behavior
more intuitive. There are a _ton_ of places inside of AR that can be
drastically simplified with this change. Specifically, autosave
associations, timestamps, touch, counter cache, and just about anything
else in AR that works with callbacks have code to try to avoid "double
save" bugs which we will be able to flat out remove with this change.
We introduce two new sets of methods, both with names that are meant to
be more explicit than dirty. The first set maintains the old behavior,
and their names are meant to center that they are about changes that
occurred during the save that just happened. They are equivalent to
`previous_changes` when called outside of after callbacks, or once the
deprecation cycle moves.
The second set is the new behavior. Their names imply that they are
talking about changes from the database representation. The fact that
this is what we really care about became clear when looking at
`BelongsTo.touch_record` when tests were failing. I'm unsure that this
set of methods should be in the public API. Outside of after callbacks,
they are equivalent to the existing methods on dirty.
Dirty itself is not deprecated, nor are the methods inside of it. They
will only emit the warning when called inside of after callbacks. The
scope of this breakage is pretty large, but the migration path is
simple. Given how much this can improve our codebase, and considering
that it makes our API more intuitive, I think it's worth doing.
2016-06-09 10:07:12 -04:00
|
|
|
if has_changes_to_save?
|
|
|
|
save(validate: false)
|
|
|
|
else
|
|
|
|
true
|
|
|
|
end
|
2012-08-25 21:54:55 -04:00
|
|
|
end
|
|
|
|
|
2010-07-14 11:42:48 -04:00
|
|
|
# Updates the attributes of the model from the passed-in hash and saves the
|
|
|
|
# record, all wrapped in a transaction. If the object is invalid, the saving
|
|
|
|
# will fail and false will be returned.
|
2013-01-02 11:46:58 -05:00
|
|
|
def update(attributes)
|
2010-07-14 11:42:48 -04:00
|
|
|
# The following transaction covers any possible database side-effects of the
|
|
|
|
# attributes assignment. For example, setting the IDs of a child collection.
|
2010-07-13 15:30:23 -04:00
|
|
|
with_transaction_returning_status do
|
2012-09-12 12:35:05 -04:00
|
|
|
assign_attributes(attributes)
|
2010-07-13 15:30:23 -04:00
|
|
|
save
|
|
|
|
end
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
2013-01-27 15:47:47 -05:00
|
|
|
|
2013-01-02 11:46:58 -05:00
|
|
|
alias update_attributes update
|
2010-05-08 19:06:05 -04:00
|
|
|
|
2015-07-08 06:16:16 -04:00
|
|
|
# Updates its receiver just like #update but calls #save! instead
|
2016-01-30 14:03:54 -05:00
|
|
|
# of +save+, so an exception is raised if the record is invalid and saving will fail.
|
2013-01-02 11:46:58 -05:00
|
|
|
def update!(attributes)
|
2010-07-14 11:42:48 -04:00
|
|
|
# The following transaction covers any possible database side-effects of the
|
|
|
|
# attributes assignment. For example, setting the IDs of a child collection.
|
2010-07-13 15:30:23 -04:00
|
|
|
with_transaction_returning_status do
|
2012-09-12 12:35:05 -04:00
|
|
|
assign_attributes(attributes)
|
2010-07-13 15:30:23 -04:00
|
|
|
save!
|
|
|
|
end
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
2013-01-27 15:47:47 -05:00
|
|
|
|
2013-01-02 11:46:58 -05:00
|
|
|
alias update_attributes! update!
|
2010-05-08 19:06:05 -04:00
|
|
|
|
2013-01-18 02:44:19 -05:00
|
|
|
# Equivalent to <code>update_columns(name => value)</code>.
|
2012-07-24 18:13:18 -04:00
|
|
|
def update_column(name, value)
|
|
|
|
update_columns(name => value)
|
|
|
|
end
|
|
|
|
|
2013-01-18 02:44:19 -05:00
|
|
|
# Updates the attributes directly in the database issuing an UPDATE SQL
|
|
|
|
# statement and sets them in the receiver:
|
2011-05-21 12:14:55 -04:00
|
|
|
#
|
2013-01-18 02:44:19 -05:00
|
|
|
# user.update_columns(last_request_at: Time.current)
|
|
|
|
#
|
|
|
|
# This is the fastest way to update attributes because it goes straight to
|
|
|
|
# the database, but take into account that in consequence the regular update
|
|
|
|
# procedures are totally bypassed. In particular:
|
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# * \Validations are skipped.
|
|
|
|
# * \Callbacks are skipped.
|
2013-01-18 02:44:19 -05:00
|
|
|
# * +updated_at+/+updated_on+ are not updated.
|
2015-12-05 02:22:19 -05:00
|
|
|
# * However, attributes are serialized with the same rules as ActiveRecord::Relation#update_all
|
2011-05-21 12:14:55 -04:00
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# This method raises an ActiveRecord::ActiveRecordError when called on new
|
2013-01-18 02:44:19 -05:00
|
|
|
# objects, or when at least one of the attributes is marked as readonly.
|
2011-05-21 12:14:55 -04:00
|
|
|
def update_columns(attributes)
|
2014-08-10 23:31:31 -04:00
|
|
|
raise ActiveRecordError, "cannot update a new record" if new_record?
|
|
|
|
raise ActiveRecordError, "cannot update a destroyed record" if destroyed?
|
2012-07-24 18:13:18 -04:00
|
|
|
|
|
|
|
attributes.each_key do |key|
|
2012-08-25 21:59:40 -04:00
|
|
|
verify_readonly_attribute(key.to_s)
|
2012-07-24 18:13:18 -04:00
|
|
|
end
|
|
|
|
|
2012-12-06 20:09:11 -05:00
|
|
|
updated_count = self.class.unscoped.where(self.class.primary_key => id).update_all(attributes)
|
2012-10-28 12:48:04 -04:00
|
|
|
|
2012-11-20 19:44:33 -05:00
|
|
|
attributes.each do |k, v|
|
|
|
|
raw_write_attribute(k, v)
|
2011-05-21 12:14:55 -04:00
|
|
|
end
|
2012-07-24 18:13:18 -04:00
|
|
|
|
2012-10-28 12:48:04 -04:00
|
|
|
updated_count == 1
|
2011-05-21 12:14:55 -04:00
|
|
|
end
|
|
|
|
|
2010-05-08 19:06:05 -04:00
|
|
|
# Initializes +attribute+ to zero if +nil+ and adds the value passed as +by+ (default is 1).
|
|
|
|
# The increment is performed directly on the underlying attribute, no setter is invoked.
|
|
|
|
# Only makes sense for number-based attributes. Returns +self+.
|
|
|
|
def increment(attribute, by = 1)
|
|
|
|
self[attribute] ||= 0
|
|
|
|
self[attribute] += by
|
|
|
|
self
|
|
|
|
end
|
|
|
|
|
2016-06-17 18:39:33 -04:00
|
|
|
# Wrapper around #increment that writes the update to the database.
|
|
|
|
# Only +attribute+ is updated; the record itself is not saved.
|
|
|
|
# This means that any other modified attributes will still be dirty.
|
2017-01-12 11:55:29 -05:00
|
|
|
# Validations and callbacks are skipped. Supports the `touch` option from
|
|
|
|
# +update_counters+, see that for more.
|
|
|
|
# Returns +self+.
|
|
|
|
def increment!(attribute, by = 1, touch: nil)
|
2015-10-03 09:36:49 -04:00
|
|
|
increment(attribute, by)
|
Deprecate the behavior of AR::Dirty inside of after_(create|update|save) callbacks
We pretty frequently get bug reports that "dirty is broken inside of
after callbacks". Intuitively they are correct. You'd expect
`Model.after_save { puts changed? }; model.save` to do the same thing as
`model.save; puts model.changed?`, but it does not.
However, changing this goes much farther than just making the behavior
more intuitive. There are a _ton_ of places inside of AR that can be
drastically simplified with this change. Specifically, autosave
associations, timestamps, touch, counter cache, and just about anything
else in AR that works with callbacks have code to try to avoid "double
save" bugs which we will be able to flat out remove with this change.
We introduce two new sets of methods, both with names that are meant to
be more explicit than dirty. The first set maintains the old behavior,
and their names are meant to center that they are about changes that
occurred during the save that just happened. They are equivalent to
`previous_changes` when called outside of after callbacks, or once the
deprecation cycle moves.
The second set is the new behavior. Their names imply that they are
talking about changes from the database representation. The fact that
this is what we really care about became clear when looking at
`BelongsTo.touch_record` when tests were failing. I'm unsure that this
set of methods should be in the public API. Outside of after callbacks,
they are equivalent to the existing methods on dirty.
Dirty itself is not deprecated, nor are the methods inside of it. They
will only emit the warning when called inside of after callbacks. The
scope of this breakage is pretty large, but the migration path is
simple. Given how much this can improve our codebase, and considering
that it makes our API more intuitive, I think it's worth doing.
2016-06-09 10:07:12 -04:00
|
|
|
change = public_send(attribute) - (attribute_in_database(attribute.to_s) || 0)
|
2017-01-12 11:55:29 -05:00
|
|
|
self.class.update_counters(id, attribute => change, touch: touch)
|
2015-10-03 09:36:49 -04:00
|
|
|
clear_attribute_change(attribute) # eww
|
|
|
|
self
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Initializes +attribute+ to zero if +nil+ and subtracts the value passed as +by+ (default is 1).
|
|
|
|
# The decrement is performed directly on the underlying attribute, no setter is invoked.
|
|
|
|
# Only makes sense for number-based attributes. Returns +self+.
|
|
|
|
def decrement(attribute, by = 1)
|
2015-10-03 09:36:49 -04:00
|
|
|
increment(attribute, -by)
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
2016-06-17 18:39:33 -04:00
|
|
|
# Wrapper around #decrement that writes the update to the database.
|
|
|
|
# Only +attribute+ is updated; the record itself is not saved.
|
|
|
|
# This means that any other modified attributes will still be dirty.
|
2017-01-12 11:55:29 -05:00
|
|
|
# Validations and callbacks are skipped. Supports the `touch` option from
|
|
|
|
# +update_counters+, see that for more.
|
|
|
|
# Returns +self+.
|
|
|
|
def decrement!(attribute, by = 1, touch: nil)
|
|
|
|
increment!(attribute, -by, touch: touch)
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Assigns to +attribute+ the boolean opposite of <tt>attribute?</tt>. So
|
|
|
|
# if the predicate returns +true+ the attribute will become +false+. This
|
|
|
|
# method toggles directly the underlying value without calling any setter.
|
|
|
|
# Returns +self+.
|
2015-11-20 21:20:07 -05:00
|
|
|
#
|
|
|
|
# Example:
|
|
|
|
#
|
|
|
|
# user = User.first
|
|
|
|
# user.banned? # => false
|
|
|
|
# user.toggle(:banned)
|
|
|
|
# user.banned? # => true
|
|
|
|
#
|
2010-05-08 19:06:05 -04:00
|
|
|
def toggle(attribute)
|
2015-01-23 00:38:50 -05:00
|
|
|
self[attribute] = !public_send("#{attribute}?")
|
2010-05-08 19:06:05 -04:00
|
|
|
self
|
|
|
|
end
|
|
|
|
|
2015-07-08 06:16:16 -04:00
|
|
|
# Wrapper around #toggle that saves the record. This method differs from
|
2015-10-13 08:02:14 -04:00
|
|
|
# its non-bang version in the sense that it passes through the attribute setter.
|
2010-05-08 19:06:05 -04:00
|
|
|
# Saving is not subjected to validation checks. Returns +true+ if the
|
|
|
|
# record could be saved.
|
|
|
|
def toggle!(attribute)
|
2012-08-25 21:54:55 -04:00
|
|
|
toggle(attribute).update_attribute(attribute, self[attribute])
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
2013-05-31 06:49:18 -04:00
|
|
|
# Reloads the record from the database.
|
|
|
|
#
|
2017-01-03 15:57:39 -05:00
|
|
|
# This method finds the record by its primary key (which could be assigned
|
|
|
|
# manually) and modifies the receiver in-place:
|
2013-10-02 00:14:58 -04:00
|
|
|
#
|
|
|
|
# account = Account.new
|
|
|
|
# # => #<Account id: nil, email: nil>
|
|
|
|
# account.id = 1
|
|
|
|
# account.reload
|
|
|
|
# # Account Load (1.2ms) SELECT "accounts".* FROM "accounts" WHERE "accounts"."id" = $1 LIMIT 1 [["id", 1]]
|
|
|
|
# # => #<Account id: 1, email: 'account@example.com'>
|
|
|
|
#
|
2013-10-02 04:18:02 -04:00
|
|
|
# Attributes are reloaded from the database, and caches busted, in
|
2015-04-24 08:29:33 -04:00
|
|
|
# particular the associations cache and the QueryCache.
|
2013-05-31 06:49:18 -04:00
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# If the record no longer exists in the database ActiveRecord::RecordNotFound
|
2013-05-31 06:49:18 -04:00
|
|
|
# is raised. Otherwise, in addition to the in-place modification the method
|
|
|
|
# returns +self+ for convenience.
|
|
|
|
#
|
|
|
|
# The optional <tt>:lock</tt> flag option allows you to lock the reloaded record:
|
|
|
|
#
|
|
|
|
# reload(lock: true) # reload with pessimistic locking
|
|
|
|
#
|
|
|
|
# Reloading is commonly used in test suites to test something is actually
|
|
|
|
# written to the database, or when some action modifies the corresponding
|
|
|
|
# row in the database but not the object in memory:
|
|
|
|
#
|
|
|
|
# assert account.deposit!(25)
|
|
|
|
# assert_equal 25, account.credit # check it is updated in memory
|
|
|
|
# assert_equal 25, account.reload.credit # check it is also persisted
|
|
|
|
#
|
2013-12-25 07:52:26 -05:00
|
|
|
# Another common use case is optimistic locking handling:
|
2013-05-31 06:49:18 -04:00
|
|
|
#
|
|
|
|
# def with_optimistic_retry
|
|
|
|
# begin
|
|
|
|
# yield
|
|
|
|
# rescue ActiveRecord::StaleObjectError
|
|
|
|
# begin
|
|
|
|
# # Reload lock_version in particular.
|
|
|
|
# reload
|
|
|
|
# rescue ActiveRecord::RecordNotFound
|
|
|
|
# # If the record is gone there is nothing to do.
|
|
|
|
# else
|
|
|
|
# retry
|
|
|
|
# end
|
|
|
|
# end
|
|
|
|
# end
|
|
|
|
#
|
2010-05-08 19:06:05 -04:00
|
|
|
def reload(options = nil)
|
2015-04-24 08:29:33 -04:00
|
|
|
self.class.connection.clear_query_cache
|
|
|
|
|
2012-04-29 13:10:43 -04:00
|
|
|
fresh_object =
|
2012-04-29 13:33:54 -04:00
|
|
|
if options && options[:lock]
|
2014-01-28 23:56:20 -05:00
|
|
|
self.class.unscoped { self.class.lock(options[:lock]).find(id) }
|
2012-04-29 13:10:43 -04:00
|
|
|
else
|
|
|
|
self.class.unscoped { self.class.find(id) }
|
|
|
|
end
|
|
|
|
|
2016-08-06 12:24:04 -04:00
|
|
|
@attributes = fresh_object.instance_variable_get("@attributes")
|
2014-07-04 10:45:04 -04:00
|
|
|
@new_record = false
|
2010-05-08 19:06:05 -04:00
|
|
|
self
|
|
|
|
end
|
|
|
|
|
2015-04-27 10:00:36 -04:00
|
|
|
# Saves the record with the updated_at/on attributes set to the current time
|
2015-02-16 01:30:41 -05:00
|
|
|
# or the time specified.
|
2014-03-14 18:44:07 -04:00
|
|
|
# Please note that no validation is performed and only the +after_touch+,
|
|
|
|
# +after_commit+ and +after_rollback+ callbacks are executed.
|
2010-08-02 10:16:02 -04:00
|
|
|
#
|
2015-02-16 01:30:41 -05:00
|
|
|
# This method can be passed attribute names and an optional time argument.
|
2014-03-20 07:08:22 -04:00
|
|
|
# If attribute names are passed, they are updated along with updated_at/on
|
2015-02-16 01:30:41 -05:00
|
|
|
# attributes. If no time argument is passed, the current time is used as default.
|
2014-03-20 07:08:22 -04:00
|
|
|
#
|
2015-02-16 01:30:41 -05:00
|
|
|
# product.touch # updates updated_at/on with current time
|
|
|
|
# product.touch(time: Time.new(2015, 2, 16, 0, 0, 0)) # updates updated_at/on with specified time
|
2014-03-20 07:08:22 -04:00
|
|
|
# product.touch(:designed_at) # updates the designed_at attribute and updated_at/on
|
2014-03-19 21:13:03 -04:00
|
|
|
# product.touch(:started_at, :ended_at) # updates started_at, ended_at and updated_at/on attributes
|
2010-08-24 10:21:58 -04:00
|
|
|
#
|
2015-07-08 06:16:16 -04:00
|
|
|
# If used along with {belongs_to}[rdoc-ref:Associations::ClassMethods#belongs_to]
|
|
|
|
# then +touch+ will invoke +touch+ method on associated object.
|
2010-08-24 10:21:58 -04:00
|
|
|
#
|
2010-08-24 18:22:53 -04:00
|
|
|
# class Brake < ActiveRecord::Base
|
2012-10-23 07:02:34 -04:00
|
|
|
# belongs_to :car, touch: true
|
2010-08-24 18:22:53 -04:00
|
|
|
# end
|
|
|
|
#
|
|
|
|
# class Car < ActiveRecord::Base
|
2012-10-23 07:02:34 -04:00
|
|
|
# belongs_to :corporation, touch: true
|
2010-08-24 18:22:53 -04:00
|
|
|
# end
|
|
|
|
#
|
|
|
|
# # triggers @brake.car.touch and @brake.car.corporation.touch
|
|
|
|
# @brake.touch
|
2013-02-25 01:07:19 -05:00
|
|
|
#
|
|
|
|
# Note that +touch+ must be used on a persisted object, or else an
|
|
|
|
# ActiveRecordError will be thrown. For example:
|
|
|
|
#
|
|
|
|
# ball = Ball.new
|
|
|
|
# ball.touch(:updated_at) # => raises ActiveRecordError
|
|
|
|
#
|
2015-03-13 13:14:55 -04:00
|
|
|
def touch(*names, time: nil)
|
2016-06-01 15:03:30 -04:00
|
|
|
unless persisted?
|
2016-07-03 13:40:16 -04:00
|
|
|
raise ActiveRecordError, <<-MSG.squish
|
2016-06-01 15:03:30 -04:00
|
|
|
cannot touch on a new or destroyed record object. Consider using
|
|
|
|
persisted?, new_record?, or destroyed? before touching
|
2016-07-03 13:40:16 -04:00
|
|
|
MSG
|
2016-06-01 15:03:30 -04:00
|
|
|
end
|
2013-02-18 20:07:05 -05:00
|
|
|
|
2015-03-13 13:14:55 -04:00
|
|
|
time ||= current_time_from_proper_timezone
|
2010-08-12 11:04:16 -04:00
|
|
|
attributes = timestamp_attributes_for_update_in_model
|
2014-03-19 21:13:03 -04:00
|
|
|
attributes.concat(names)
|
2010-11-27 05:14:26 -05:00
|
|
|
|
2010-09-24 13:35:35 -04:00
|
|
|
unless attributes.empty?
|
2010-08-24 09:56:26 -04:00
|
|
|
changes = {}
|
2010-08-12 11:04:16 -04:00
|
|
|
|
2010-08-24 09:56:26 -04:00
|
|
|
attributes.each do |column|
|
2012-03-03 00:10:39 -05:00
|
|
|
column = column.to_s
|
2015-02-16 01:30:41 -05:00
|
|
|
changes[column] = write_attribute(column, time)
|
2010-08-24 09:56:26 -04:00
|
|
|
end
|
2010-08-12 11:04:16 -04:00
|
|
|
|
2010-08-24 09:56:26 -04:00
|
|
|
primary_key = self.class.primary_key
|
2015-04-19 17:14:08 -04:00
|
|
|
scope = self.class.unscoped.where(primary_key => _read_attribute(primary_key))
|
2015-04-16 10:40:52 -04:00
|
|
|
|
|
|
|
if locking_enabled?
|
|
|
|
locking_column = self.class.locking_column
|
|
|
|
scope = scope.where(locking_column => _read_attribute(locking_column))
|
|
|
|
changes[locking_column] = increment_lock
|
|
|
|
end
|
|
|
|
|
2016-09-14 11:07:15 -04:00
|
|
|
clear_attribute_changes(changes.keys)
|
2015-04-16 10:40:52 -04:00
|
|
|
result = scope.update_all(changes) == 1
|
|
|
|
|
|
|
|
if !result && locking_enabled?
|
|
|
|
raise ActiveRecord::StaleObjectError.new(self, "touch")
|
|
|
|
end
|
|
|
|
|
2016-12-01 17:39:15 -05:00
|
|
|
@_trigger_update_callback = result
|
2015-04-16 10:40:52 -04:00
|
|
|
result
|
2014-03-14 21:20:13 -04:00
|
|
|
else
|
|
|
|
true
|
2010-08-24 09:56:26 -04:00
|
|
|
end
|
2010-08-02 10:16:02 -04:00
|
|
|
end
|
|
|
|
|
2010-05-08 19:06:05 -04:00
|
|
|
private
|
2011-05-31 10:43:19 -04:00
|
|
|
|
2011-07-24 17:04:52 -04:00
|
|
|
# A hook to be overridden by association modules.
|
2011-05-31 10:43:19 -04:00
|
|
|
def destroy_associations
|
|
|
|
end
|
|
|
|
|
2012-03-30 09:39:55 -04:00
|
|
|
def destroy_row
|
|
|
|
relation_for_destroy.delete_all
|
|
|
|
end
|
|
|
|
|
|
|
|
def relation_for_destroy
|
2015-01-14 17:08:03 -05:00
|
|
|
self.class.unscoped.where(self.class.primary_key => id)
|
2012-03-30 09:39:55 -04:00
|
|
|
end
|
|
|
|
|
2014-12-27 18:17:57 -05:00
|
|
|
def create_or_update(*args)
|
2016-08-30 09:44:06 -04:00
|
|
|
_raise_readonly_record_error if readonly?
|
2014-12-27 18:17:57 -05:00
|
|
|
result = new_record? ? _create_record : _update_record(*args)
|
2010-05-08 19:06:05 -04:00
|
|
|
result != false
|
|
|
|
end
|
|
|
|
|
|
|
|
# Updates the associated record with values matching those of the instance attributes.
|
|
|
|
# Returns the number of affected rows.
|
2014-06-07 11:55:28 -04:00
|
|
|
def _update_record(attribute_names = self.attribute_names)
|
2013-04-30 07:27:18 -04:00
|
|
|
attributes_values = arel_attributes_with_values_for_update(attribute_names)
|
|
|
|
if attributes_values.empty?
|
2016-12-01 17:39:15 -05:00
|
|
|
rows_affected = 0
|
|
|
|
@_trigger_update_callback = true
|
2012-11-20 19:44:33 -05:00
|
|
|
else
|
2016-12-01 17:39:15 -05:00
|
|
|
rows_affected = self.class.unscoped._update_record attributes_values, id, id_in_database
|
|
|
|
@_trigger_update_callback = rows_affected > 0
|
2012-11-20 19:44:33 -05:00
|
|
|
end
|
2016-12-01 17:39:15 -05:00
|
|
|
rows_affected
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
|
|
|
|
|
|
|
# Creates a record with values matching those of the instance attributes
|
|
|
|
# and returns its id.
|
2014-06-07 11:55:28 -04:00
|
|
|
def _create_record(attribute_names = self.attribute_names)
|
2012-09-28 12:55:35 -04:00
|
|
|
attributes_values = arel_attributes_with_values_for_create(attribute_names)
|
2010-05-08 19:06:05 -04:00
|
|
|
|
2011-03-22 12:18:01 -04:00
|
|
|
new_id = self.class.unscoped.insert attributes_values
|
2011-10-05 13:11:25 -04:00
|
|
|
self.id ||= new_id if self.class.primary_key
|
2010-05-08 19:06:05 -04:00
|
|
|
|
2010-11-28 10:55:48 -05:00
|
|
|
@new_record = false
|
2010-05-08 19:06:05 -04:00
|
|
|
id
|
|
|
|
end
|
2012-08-25 21:55:03 -04:00
|
|
|
|
|
|
|
def verify_readonly_attribute(name)
|
|
|
|
raise ActiveRecordError, "#{name} is marked as readonly" if self.class.readonly_attributes.include?(name)
|
|
|
|
end
|
`destroy` shouldn't raise when child associations fail to save
Deep down in the association internals, we're calling `destroy!` rather
than `destroy` when handling things like `dependent` or autosave
association callbacks. Unfortunately, due to the structure of the code
(e.g. it uses callbacks for everything), it's nearly impossible to pass
whether to call `destroy` or `destroy!` down to where we actually need
it.
As such, we have to do some legwork to handle this. Since the callbacks
are what actually raise the exception, we need to rescue it in
`ActiveRecord::Callbacks`, rather than `ActiveRecord::Persistence` where
it matters. (As an aside, if this code wasn't so callback heavy, it
would handling this would likely be as simple as changing `destroy` to
call `destroy!` instead of the other way around).
Since we don't want to lose the exception when `destroy!` is called (in
particular, we don't want the value of the `record` field to change to
the parent class), we have to do some additional legwork to hold onto it
where we can use it.
Again, all of this is ugly and there is definitely a better way to do
this. However, barring a much more significant re-architecting for what
I consider to be a reletively minor improvement, I'm willing to take
this small hit to the flow of this code (begrudgingly).
2015-07-24 11:13:20 -04:00
|
|
|
|
|
|
|
def _raise_record_not_destroyed
|
|
|
|
@_association_destroy_exception ||= nil
|
|
|
|
raise @_association_destroy_exception || RecordNotDestroyed.new("Failed to destroy the record", self)
|
|
|
|
ensure
|
|
|
|
@_association_destroy_exception = nil
|
|
|
|
end
|
2015-12-06 16:35:05 -05:00
|
|
|
|
|
|
|
def belongs_to_touch_method
|
|
|
|
:touch
|
|
|
|
end
|
2016-08-30 09:44:06 -04:00
|
|
|
|
|
|
|
def _raise_readonly_record_error
|
|
|
|
raise ReadOnlyRecord, "#{self.class} is marked as readonly"
|
|
|
|
end
|
2010-05-08 19:06:05 -04:00
|
|
|
end
|
2010-06-30 07:14:09 -04:00
|
|
|
end
|