Oracle backend: primary key sequences don't increment if you provide the primary key

[graham_king <graham@…>]

The trigger that the Oracle backend creates on every table only increments the sequence if you don't provide an ID yourself. If you pickle some objects out of one django project / database and unpickle them into another, they already have IDs, so the sequence doesn't move on. Next time you try to add an object (say through the admin interface), the save will fail with a unique primary key violation.

The workaround is the call "SELECT "+ mysequence +".nextval FROM DUAL" every time you save your unpickled object.

[graham_king <graham@…>]

For the workaround, I meant you run that SQL once for each object you insert that has it's own primary key, thereby incrementing the sequence by one each time. Your objects must have sequential IDs, which is the most common case. Apologies if that was not clear.

[Erin Kelly]

The solution to this is to use fixtures to load objects from an external source. The manage.py loaddata command will automatically reset the sequences to the max pk values after loading the fixture.

You can also reset the sequences manually using the SQL generated by manage.py sqlsequencereset.