Am 06.04.2013 um 16:30 schrieb Shawn Milochik: > I've seen some situations where it looked like signals are received multiple > times. > > However, you can easily fix that by checking for the existence of the user in > your function, or a try/except that handles the integrity error.
or by usage of get_or_create() -> https://docs.djangoproject.com/en/dev/ref/models/querysets/#get-or-create just my two cents … > > Also, if you're starting a new project, consider upgrading to Django 1.5. > It's similar to 1.4 > (which I assume you're using based on the documentation link you provided), > but also has customizable user models. > > Although creating a profile model to be linked to the User model is still a > good idea, some fields make sense to have > in a custom User model: > https://docs.djangoproject.com/en/1.5/topics/auth/customizing/#auth-custom-user > > Shawn > > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
