Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd like to expand on the solution by @thornomad. </p> <p>Extending Django's User class directly can cause all kinds of trouble with the internal django.auth mechanisms. What I've done in a similar situation is precisely what @thornomad suggests - I made my own UserProfile model linked one-to-one with the Django User model, in which I held additional user data and from which I inherited models for different types of users.</p> <p>Something to fit what you described:</p> <pre><code>class UserProfile(models.Model): user = models.OneToOneField(User, blank=True, related_name='profile') class Meta: abstract = True class PositionHolderUserProfile(UserProfile): first_name = models.CharField(max_length=30) last_name = models.CharField(max_length=30) landline = models.CharField(blank=True, max_length=20) mobile = models.CharField(blank=True, max_length=20) created_by = models.ForeignKey(PositionHolderUserProfile, editable=False, blank=True, related_name="created_users") modified_by = models.ForeignKey(PositionHolderUserProfile, editable=False, blank=True, related_name="modified_users") class Principal(PositionHolderUserProfile): branchoffice = models.ForeignKey(BranchOffice) class Administrator(PositionHolderUserProfile): superior = models.ForeignKey(Principal, related_name="subordinates") province = models.ForeignKey(Province) class Coordinator(PositionHolderUserProfile): superior = models.ForeignKey(Administrator, related_name="subordinates") class Company(UserProfile): name = models.CharField(max_length=50) class Product(models.Model): name = models.CharField(max_length=50) produced_by = models.ForeignKey(Company) class Buyer(UserProfile): first_name = models.CharField(max_length=30) last_name = models.CharField(max_length=30) products_bought = models.ManyToManyField(Product) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODjango Multi-Table Inheritance VS Specifying Explicit OneToOne Relationship in Models
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UStaleinat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODjango Multi-Table Inheritance VS Specifying Explicit OneToOne Relationship in Models
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat seems like a good implementation to me. But why have both the UserProfile class and the PositionHolderUserProfile class? Will it not be simpler to get rid of the latter and push everything in it to the former model?
      singulars
      1. PO
      1. USchefsmart
    2. COI thought it best to encapsulate data relevant to all position holders, e.g. Principal, Administrator and Coordinator, but not relevant to other users such as Buyer and Company. Such data could include which branch they work in, how long they've been employed, etc.
      singulars
      1. PO
      1. UStaleinat
    3. COThis doesn't seem to work with settings.AUTH_PROFILE_MODULE.
      singulars
      1. PO
      1. USCeasar Bautista
 

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