manage.py loaddata doesn't update table sequence numbers under Postgres
|Reported by:||russellm||Owned by:||russellm|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
If you are using Postgres and you dump the contents of a database, then load it again using loaddata, the sequence numbers for the dumped table are reset. For some reason, saving the objects as a result of the loaddata doesn't appear to update the sequence numbers.
This manifests as the following error:
ERROR: duplicate key violates unique constraint "myproj_myapp_pkey" INSERT INTO "myproj_myapp"
being raised when you add the first new object after loading the database contents.
Change History (3)
comment:1 Changed 9 years ago by russellm
- Needs documentation unset
- Needs tests unset
- Owner changed from jacob to russellm
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted