Skip to content

Commit

Permalink
Merge pull request #35509 from willnet/fix-typo-in-persistence
Browse files Browse the repository at this point in the history
[ci skip]Fix typo:  constaint -> constraint
  • Loading branch information
kamipo committed Mar 7, 2019
2 parents 2170338 + 6c797d6 commit 2beb0b4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions activerecord/lib/active_record/persistence.rb
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ def insert(attributes, returning: nil, unique_by: nil)
# record or pass <tt>returning: false</tt> to omit the clause.
#
# [:unique_by]
# (Postgres and SQLite only) In a table with more than one unique constaint or index,
# (Postgres and SQLite only) In a table with more than one unique constraint or index,
# new records may considered duplicates according to different criteria. By default,
# new rows will be skipped if they violate _any_ unique constraint/index. By defining
# <tt>:unique_by</tt>, you can skip rows that would create duplicates according to the given
Expand Down Expand Up @@ -218,7 +218,7 @@ def upsert(attributes, returning: nil, unique_by: nil)
# record or pass <tt>returning: false</tt> to omit the clause.
#
# [:unique_by]
# (Postgres and SQLite only) In a table with more than one unique constaint or index,
# (Postgres and SQLite only) In a table with more than one unique constraint or index,
# new records may considered duplicates according to different criteria. For MySQL,
# an upsert will take place if a new record violates _any_ unique constraint. For
# Postgres and SQLite, new rows will replace existing rows when the new row has the
Expand Down

0 comments on commit 2beb0b4

Please sign in to comment.