StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15538800
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-21T03:11:53.287
FavoriteCount
0
LastActivityDate
2013-03-21T03:11:53.287
LastEditDate
LastEditorUserId
0
OwnerUserId
2008506
ParentId
15534365
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
First of all, obviously I want each user to be able to track their own progress and not have any other users be able to see it. In the template, you can do like this <pre><code> User: {{ user.username }} squats: {{ user.userprofile.squats }} lunges: {{ user.userprofile.lunges }} Skip Stairs: {% if user.userprofile.skipStairs %} Yes {% else %} No {% endif %} Stair: {{ user.userprofile.stairDaysCount }}} Week Completed: {% if user.userprofile.weekOneComplete %} Yes {% else %} In-Progress {% endif %} </code></pre> How does accessing each user's data work once this relationship is defined? For example, if I wanted to create an addSquats function. To access user data, <pre><code>user = UserProfile(user=request.user) user.weekOne.squats += 5 user.weekOne.save() user.save() </code></pre> Second, every time a user makes a change to their progress (i.e., adds a squat or lunge), I want to check if all of the fields have met a certain a benchmark. If they have, I want to set weekOneComplete to true. Under your UserProfile model, create check updates function. <pre><code>class UserProfile(models.Model): user = models.OneToOneField(User) weekOne = models.ForeignKey(WeekOne) def check_updates(self): check = WeekOne.object.get(id=self.weekOne) if check.skipStairs and \ check.squats == 1000 and \ check.lunges == 250 and \ check.stairDaysCount == 3: check.weekOneComplete = True check.save() </code></pre> So every time you update the data for that user, just call the method like this: <pre><code>user = UserProfile.objects.get(user=request.user) user.check_updates() </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POProperly Defining Relationships in Django DB
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UScatherine
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POProperly Defining Relationships in Django DB
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.