Yes, of course there is a constraint there: the primary key, which of course I don't want to remove. Marty's solution was it. Thanks for the assistance.
On Mar 28, 12:50 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Fri, Mar 28, 2008 at 2:35 PM, makebelieve <[EMAIL PROTECTED]> wrote: > > I haven't added any unique contraints. It really seems as though > > django doesn't know > > about my existing data. If I obliterate the old data everything works > > fine, but > > that's not a possibility. > > At the database level there is some sort of constraint requiring > uniqueness; otherwise your DB would not be raising the error it's > raising. > > But you apparently have not made Django aware of this constraint, so > Django tries to insert duplicate data and you get an error. > > The solution is to make Django aware of the constraint. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
