diff options
| author | François Freitag <mail@franek.fr> | 2017-06-17 20:17:15 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-06-19 09:25:32 -0400 |
| commit | 712ce47e1a55f7ebd96ac64201a4817ae4743216 (patch) | |
| tree | 42f610c907df804fa90a2e76a28a3e52c19e1db6 /docs/ref/models | |
| parent | a3b1319d5863600981e71fbaa452d7104715a9e7 (diff) | |
[1.11.x] Fixed #18485 -- Doc'd behavior of PostgreSQL when manually setting AutoField.
Backport of 4f1eb64ad0bcebfae4075486855eb6b63355cc5a from master
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/instances.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index 696e09ba57..4a63b016aa 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -437,6 +437,9 @@ happens. Explicitly specifying auto-primary-key values is mostly useful for bulk-saving objects, when you're confident you won't have primary-key collision. +If you're using PostgreSQL, the sequence associated with the primary key might +need to be updated; see :ref:`manually-specified-autoincrement-pk`. + What happens when you save? --------------------------- |