Well, it looks like I was able to solve this particular problem. In the fixtures, I changed the order when loading the data. I now load the Profile first, and then the User. That works.
I guess writing the problem down helped me think of potential solutions. :P Still, I'm going to have to alter dumpdata manually everytime. On Feb 1, 12:22 am, stryderjzw <stryder...@gmail.com> wrote: > Hi! > > I did some searching, but I felt it's going nowhere, so here's the > question. > > I'm using Django 1.1 r9756, the one where tests are using > transactions. > > I have a user profile automatically created with signals, as below: > > def create_player(sender, instance=None, **kwargs): > if instance is None: > return > player, created = Player.objects.get_or_create(user=instance) > post_save.connect(create_player, sender=User) > > When I run multiple tests together, it gives me IntegrityError: > > IntegrityError: duplicate key value violates unique constraint > "agent_player_user_id_key" > > It seems like it's trying to create the player again, but can't > because its' already created. > > Anyone else run into this problem? > > Thanks! > Justin --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
