Databases
StackOverflow2013
Postsdbo
PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
    primarykey
    data
    text
    <p>For various complicated reasons[1] I need to add extra properties to the Django User class.</p> <p>I can't use either Profile nor the "inheritance" way of doing this. (As in <a href="https://stackoverflow.com/questions/44109/extending-the-user-model-with-custom-fields-in-django">Extending the User model with custom fields in Django</a> )</p> <p>So what I've been doing is including the User class in my local_settings file. And adding the property to it there.</p> <p>This, perhaps surprisingly, seems to work in many cases. But not when I create a new User from UserManager.create_user(). So I need to patch an alternative to the UserManager.create_user() method. Looking at the source for this (in contrib.auth.models.py) I find that the class it uses to create the User is kept in a property called UserManager.model rather than referenced directly.</p> <p>The line is this : </p> <p>user = self.model(None, username, '', '', email.strip().lower(), 'placeholder', False, True, False, now, now)</p> <p>The problem is that this self.model (which I assume contains a reference to the User class) doesn't seem to be my patched version.</p> <p>So, does anyone know where this self.model is set-up in the case of UserManager? And whether I'm correct in assuming that at that point the code hasn't gone through local_settings so my patch to the User class isn't there? And if there's a better place to patch the class?</p> <p>cheers</p> <p>phil</p> <p>[1] To satisfy the cur ious. I need to make the User class use a different and existing table in the database, which has extra fields and constraints.</p> <p>Update : For future reference, it looks like Proxy Models are the way that Django's going to support what I need : <a href="http://code.djangoproject.com/ticket/10356" rel="nofollow noreferrer">http://code.djangoproject.com/ticket/10356</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USinterstar
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"Can't use Profile"? Mostly, that's a recipe for disaster. Profile works and is easy to use. It's difficult to image a situation in which Profile can't be used. Please provide some insight into why you can't use the standard, supported, simple solution.
      singulars
      1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
      1. USS.Lott
    2. COYes. I can't use Profile because in fact I've mapped User to a legacy table from another system. I have to add the extra field because of a constraint in that table.
      singulars
      1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
      1. USinterstar
    3. COAre you trying to get to some kind of Single Sign On by sharing a User table from another application? Are you talking about another authentication source? I'm not sure I understand your use case. http://docs.djangoproject.com/en/dev/topics/auth/#other-authentication-sources
      singulars
      1. PODjango : Adding a property to the User class. Changing it at runtime and UserManager.create_user
      1. USS.Lott
 

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