Hi, My setup is:
Django 1.0 (rev 9066) Postgresql v8.3 I recently encountered a situation where the sequence for the primary key of one of my models became out of sync, which caused the following error when trying to save a new model instance: IntegrityError ... 'duplicate key violates unique constraint "myapp_mymodel_pkey"' This is because the sequence was returning IDs that were already in use, so there was a conflict when trying to insert a new record with the same ID. I found the solution was to reset the sequence using the output from './manage.py sqlsequencereset <app>'. This solution eliminated the error, but I'm left a little perplexed. I was hoping that someone might have some explanation for why the sequence would be out of sync in the first place. My understanding is that this should only happen if manual insertion is done to the database where an ID is specified (perhaps as the result of a database restore from a dump). I haven't done anything like that, so I'm not sure what would have caused it in my case. I _have_ done database table schema changes - i.e. adding new columns, etc. Could this cause the sequence to reset? Has anyone else has similar issues? Has anyone come up with a more elegant solution than having to reset the sequence after the fact? Does anyone have any suggestions on how to prevent the sequence from going out of sync in the first place? Any advice would be greatly appreciated! Thanks, Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
