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 08:59:16 -0400 |
| commit | 4f1eb64ad0bcebfae4075486855eb6b63355cc5a (patch) | |
| tree | a0d046a323c63472b4284c0fdf3a2bf05179e09e /docs/ref/models/instances.txt | |
| parent | e36598f963ae492ea4f3afe73d4e70b5a097f93a (diff) | |
| download | django-4f1eb64ad0bcebfae4075486855eb6b63355cc5a.tar.gz | |
Fixed #18485 -- Doc'd behavior of PostgreSQL when manually setting AutoField.
Diffstat (limited to 'docs/ref/models/instances.txt')
| -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 31fde97d1e..c327b0e9e7 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -426,6 +426,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? --------------------------- |