Real upsert for PostgreSQL 9.5+ and Rails 5 / ActiveRecord 5. Uses ON CONFLICT DO UPDATE.
- Does upsert on a single record using
ON CONFLICT DO UPDATE
- Updates timestamps as you would expect in ActiveRecord
- For partial upserts, loads any existing data from the database
-
PostgreSQL 9.5+
-
ActiveRecord ~> 5
-
For MRI: pg
-
For JRuby: No support
Add this line to your application's Gemfile:
gem 'active_record_upsert'
And then execute:
$ bundle
Or install it yourself as:
$ gem install active_record_upsert
Use ActiveRecord.upsert
or ActiveRecord#upsert
. ActiveRecordUpsert respects timestamps.
class MyRecord < ActiveRecord::Base
end
MyRecord.create(name: 'foo', wisdom: 1)
# => #<MyRecord id: 1, name: "foo", created_at: "2016-02-20 14:15:55", updated_at: "2016-02-20 14:15:55", wisdom: 1>
MyRecord.upsert(id: 1, wisdom: 3)
# => #<MyRecord id: 1, name: "foo", created_at: "2016-02-20 14:15:55", updated_at: "2016-02-20 14:18:15", wisdom: 3>
r = MyRecord.new(id: 1)
r.name = 'bar'
r.upsert
# => #<MyRecord id: 1, name: "bar", created_at: "2016-02-20 14:15:55", updated_at: "2016-02-20 14:18:49", wisdom: 3>
If you need to specify a condition for the update, pass it as an Arel query:
MyRecord.upsert({id: 1, wisdom: 3}, arel_condition: MyRecord.arel_table[:updated_at].lt(1.day.ago))
The instance method #upsert
can also take keyword arguments to specify a condition, or to limit which attributes to upsert
(by default, all changed
attributes will be passed to the upsert):
r = MyRecord.new(id: 1)
r.name = 'bar'
r.color = 'blue'
r.upsert(attributes: [:name], arel_condition: MyRecord.arel_table[:updated_at].lt(1.day.ago))
# will only update :name, and only if the record is older than 1 day;
# but if the record does not exist, will insert with both :name and :colors
If you want to create a record with the specific attributes, but update only a limited set of attributes,
similar to how ActiveRecord::Base.create_with
works, you can do the following:
existing_record = MyRecord.create(id: 1, name: 'lemon', color: 'green')
r = MyRecord.new(id: 1, name: 'banana', color: 'yellow')
r.upsert(attributes: [:color])
# => #<MyRecord id: 1, name: "lemon", color: "yellow", ...>
r = MyRecord.new(id: 2, name: 'banana', color: 'yellow')
r.upsert(attributes: [:color])
# => #<MyRecord id: 2, name: "banana", color: "yellow", ...>
# This is similar to:
MyRecord.create_with(name: 'banana').find_or_initialize_by(id: 2).update(color: 'yellow')
Upsert will perform validation on the object, and return false if it is not valid. To skip validation, pass validate: false
:
MyRecord.upsert({id: 1, wisdom: 3}, validate: false)
If you want validations to raise ActiveRecord::RecordInvalid
, use upsert!
:
MyRecord.upsert!(id: 1, wisdom: 3)
Or using the instance method:
r = MyRecord.new(id: 1, name: 'bar')
r.upsert!
It's possible to specify which columns should be used for the conflict clause. These must comprise a unique index in Postgres.
class Vehicle < ActiveRecord::Base
upsert_keys [:make, :name]
end
Vehicle.upsert(make: 'Ford', name: 'F-150', doors: 4)
# => #<Vehicle id: 1, make: 'Ford', name: 'Focus', doors: 2>
Vehicle.create(make: 'Ford', name: 'Focus', doors: 4)
# => #<Vehicle id: 2, make: 'Ford', name: 'Focus', doors: 4>
r = Vehicle.new(make: 'Ford', name: 'F-150')
r.doors = 2
r.upsert
# => #<Vehicle id: 1, make: 'Ford', name: 'Focus', doors: 2>
Make sure to have an upsert_test database:
bin/run_rails.sh db:create db:migrate DATABASE_URL=postgresql://localhost/upsert_test
Then run rspec
.
Bug reports and pull requests are welcome on GitHub at https://github.com/jesjos/active_record_upsert.
- Jesper Josefsson
- Jens Nockert
- Olle Jonsson
- Simon Dahlbacka
- Paul Hoffer
- Ivan (@me)
- Leon Miller-Out (@sbleon)
- Andrii Dmytrenko (@Antti)
- Alexia McDonald (@alexiamcdonald)