Databases
StackOverflow2013
Postsdbo
POunique value field based on another field in django
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POunique value field based on another field in django
    primarykey
    data
    text
    <p>Preface: I am new to django and to db design.</p> <p>SUPEREDIT: I made some significant changes, so the answers before my changes may reference things not here. I apologize.</p> <p>I'll get right to the code: models.py:</p> <pre><code>class Player(models.Model): name = models.CharField() class Team(models.Model): name = models.CharField() members = models.ManyToManyField(Player, through='Membership') class Word(models.Model): word = models.CharField(unique=True) definition = models.CharField() ... class Ownership(models.Model): owner = models.ForeignKey(Player) team = models.ForeignKey(Team) word = models.ForeignKey(Word) class Membership(models.Model): team = models.ForeignKey(Team) player = models.ForeignKey(Player) </code></pre> <p>the Word table has been populated. In the admin I create a Player. I then create a team and add members to it. I've added Ownership to the admin. I create a new Ownership and I get to pick from players, from the teams, and from the words. I'd like to put a constraint where if a player owns a word for a given team, then players belonging to that team can not own the word within the team. They may own the word in other teams.</p> <p>The way it is now. I could have two different players on the same team own the same word. Bad. Basically I want the admin to say take all of the words owned within this team and not make them available in the drop down.</p> <p>How can I model this relationship? How can I get this functionality in the admin?</p> <p>EDIT: I added the membership model just to show that I am trying to solve a different problem. And as I said, this is a simplified example of what I am really working with. As you can see I've got the membership relationship done, I am trying to solve a separate problem of ownership.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDan.StackOverflow
    1. USDan.StackOverflow
    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. This table or related slice is empty.
    1. COYour schema is STILL wrong, and your edit doesn't change that. You did not ask whatsoever about the Ownership model pre-edit. Your question makes no sense. You still haven't explained the problem with Ownership, then.
      singulars
      1. POunique value field based on another field in django
      1. USjonwd7
    2. COI see no need for an Ownership model, if you were to actually change your schema to be correct. If the only thing Ownership indicates is associating a player with a number, that is absolutely incorrect, and instead the number should be part of the Membership model.
      singulars
      1. POunique value field based on another field in django
      1. USjonwd7
    3. COQuestion is very vague and confusing. Instead of showing your solution and making us guess the problem, describe the problem more instead.
      singulars
      1. POunique value field based on another field in django
      1. USdrozzy
 

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