Databases
StackOverflow2013
Postsdbo
PODjango user-profile creation code is running twice - why?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango user-profile creation code is running twice - why?
    primarykey
    data
    text
    <p>Using Django 1.2, I'm running the <em>django-registration</em> application, and creating a User Profile object after registration created the user - using code that came from some other Questions:</p> <pre><code># models.py def create_player_profile(sender, instance, created, **kwargs): signals.post_save.disconnect(create_player_profile, sender = User) # added. if created: print "creating profile." profile, created = PlayerProfile.objects.get_or_create(user = instance) print "profile %s created = %s" % (str(profile), str(created)) else: print "problems creating profile." signals.post_save.connect(create_player_profile, sender = User) </code></pre> <p>And it works fine :) The only problem is, I get two sets of output, indicating that the code is running <em>twice</em>. I suspect that for some reason, the signal is getting sent twice.</p> <p>My first thought is that the file is getting <em>imported</em> twice, setting up two identical signals. Which makes me wonder if maybe <em>django-registration</em> is doing something automatically? Or something else I don't yet understand about Django. :)</p> <p>So why is the code running twice? Are two signals being sent, and if so, why?</p> <p><strong>Update</strong> Just noticed <a href="https://stackoverflow.com/questions/1478630/django-signal-emitting-once-received-twice-why/1480174#1480174">this Answer</a> explained how to avoid duplicate signals. And it worked, somewhat :) My output went from:</p> <blockquote> <p>creating profile.<br> creating profile.<br> problems creating profile<br> problems creating profile </p> </blockquote> <p>to:</p> <blockquote> <p>creating profile.<br> problems creating profile </p> </blockquote> <p>I don't know if that means my code was originally running <em>four times</em>? And dropped down to only two times? I'm so confused. :)</p> <p>Update 2 - added the <em>signals.disconnect</em> line. I figured deleting the signal would prevent the function from executing twice. Alas, I was wrong - <em>create-player-profile</em> is <em>still</em> running twice... I have no clue why it would, if the signal was immediately deleted.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USJohn C
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango user-profile creation code is running twice - why?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango user-profile creation code is running twice - why?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODjango user-profile creation code is running twice - why?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you show how did you change your code after reading the answer explaining how to avoid duplicate signals? Btw, this is the [official link](http://docs.djangoproject.com/en/dev/topics/signals/#preventing-duplicate-signals) about that.
      singulars
      1. PODjango user-profile creation code is running twice - why?
      1. USPaolo
    2. COI did what both links suggested, adding *dispatch_uid = "foo"* to the signal-creation, I just didn't re-edit the code above. But the problem is solved (or non-problem, as the case may be).
      singulars
      1. PODjango user-profile creation code is running twice - why?
      1. USJohn C
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload