Skip to content

Commit 7ff610e

Browse files
committed
Don't use ` in titles in docs
1 parent 05da67d commit 7ff610e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The major problem with this approach is possibility of race conditions. In betwe
4747

4848
In order to combat this, PostgreSQL added native upserts. Also known as [`ON CONFLICT DO ...`](https://www.postgresql.org/docs/9.5/static/sql-insert.html#SQL-ON-CONFLICT). This allows a user to specify what to do when a conflict occurs.
4949

50-
### `upsert`
50+
### upsert
5151
Attempts to insert a row with the specified data or updates (and overwrites) the duplicate row, and then returns the primary key of the row that was created/updated.
5252

5353
Upserts work by catching conflcits. PostgreSQL requires to know whichconflicts to react to. You have to specify the name of the column to which you want to react to. This is specified in the `conflict_target` parameter.
@@ -135,7 +135,7 @@ It also supports specifying a "unique together" constraint on HStore keys:
135135
)
136136
)
137137

138-
### `upsert_and_get`
138+
### upsert_and_get
139139
Does the same thing as `upsert`, but returns a model instance rather than the primary key of the row that was created/updated. This also happens in a single query using `RETURNING` clause on the `INSERT INTO` statement:
140140

141141
from django.db import models

0 commit comments

Comments
 (0)