Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, some time passed since 2008 and it's time for some fresh answer. Since Django 1.5 you will be able to create custom User class. Actually, at the time I'm writing this, it's already merged into master, so you can try it out.</p> <p>There's some information about it in <a href="https://docs.djangoproject.com/en/dev/topics/auth/customizing/#a-full-example">docs</a> or if you want to dig deeper into it, in <a href="https://github.com/django/django/commit/70a0de37d132e5f1514fb939875f69649f103124">this commit</a>.</p> <p>All you have to do is add <code>AUTH_USER_MODEL</code> to settings with path to custom user class, which extends either <code>AbstractBaseUser</code> (more customizable version) or <code>AbstractUser</code> (more or less old User class you can extend).</p> <p>For people that are lazy to click, here's code example (taken from <a href="https://docs.djangoproject.com/en/dev/topics/auth/#a-full-example">docs</a>):</p> <pre><code>from django.db import models from django.contrib.auth.models import ( BaseUserManager, AbstractBaseUser ) class MyUserManager(BaseUserManager): def create_user(self, email, date_of_birth, password=None): """ Creates and saves a User with the given email, date of birth and password. """ if not email: raise ValueError('Users must have an email address') user = self.model( email=MyUserManager.normalize_email(email), date_of_birth=date_of_birth, ) user.set_password(password) user.save(using=self._db) return user def create_superuser(self, username, date_of_birth, password): """ Creates and saves a superuser with the given email, date of birth and password. """ u = self.create_user(username, password=password, date_of_birth=date_of_birth ) u.is_admin = True u.save(using=self._db) return u class MyUser(AbstractBaseUser): email = models.EmailField( verbose_name='email address', max_length=255, unique=True, ) date_of_birth = models.DateField() is_active = models.BooleanField(default=True) is_admin = models.BooleanField(default=False) objects = MyUserManager() USERNAME_FIELD = 'email' REQUIRED_FIELDS = ['date_of_birth'] def get_full_name(self): # The user is identified by their email address return self.email def get_short_name(self): # The user is identified by their email address return self.email def __unicode__(self): return self.email def has_perm(self, perm, obj=None): "Does the user have a specific permission?" # Simplest possible answer: Yes, always return True def has_module_perms(self, app_label): "Does the user have permissions to view the app `app_label`?" # Simplest possible answer: Yes, always return True @property def is_staff(self): "Is the user a member of staff?" # Simplest possible answer: All admins are staff return self.is_admin </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POExtending the User model with custom fields in Django
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USOndrej Slinták
    1. USOndrej Slinták
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe create_user function doesn't seem to store the username, how so?!
      singulars
      1. PO
      1. USOrca
    2. COBecause in this example, `email` is the username.
      singulars
      1. PO
      1. USOndrej Slinták
    3. COPerfect, this is the right way to make the extend!!!.
      singulars
      1. PO
      1. USpjl
 

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