Opened 9 years ago

Closed 9 years ago

#3915 closed (duplicate)

manage.py loaddata doesn't update table sequence numbers under Postgres

Reported by: Russell Keith-Magee Owned by: Russell Keith-Magee
Component: Core (Serialization) Version: master
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

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 Russell Keith-Magee

Needs documentation: unset
Needs tests: unset
Owner: changed from Jacob to Russell Keith-Magee
Patch needs improvement: unset
Triage Stage: UnreviewedAccepted

comment:3 Changed 9 years ago by Russell Keith-Magee

Resolution: duplicate
Status: newclosed

Duplicate of #3790.

Note: See TracTickets for help on using tickets.
Back to Top