StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3442348
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-09T17:02:28.627
FavoriteCount
0
LastActivityDate
2010-09-23T10:50:19.517
LastEditDate
2010-09-23T10:50:19.517
LastEditorUserId
207241
OwnerUserId
207241
ParentId
3221745
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Besides the admin page inlines, other reason for the <code>ForeignKey</code> solution is that it allows you to use the correct, default DB manager when objects are accessed with a reverse relation. Consider example from this <a href="http://djangosnippets.org/snippets/1037/" rel="noreferrer">subclasses manager snippet</a>. Let's say that the <code>Post</code> class definition from the example looks like this: <pre><code>class Post(ParentModel): title = models.CharField(max_length=50) onetoone = models.ForeignKey(SomeModel, unique=True) children = ChildManager() objects = models.Manager() </code></pre> By calling <code>somemodel_instance.post_set.all()[0]</code>, you get the desired subclasses objects of the <code>Post</code> class as indicated by defining the first (default) manager as a <code>ChildManager</code>. On the other hand, with <code>OneToOneField</code>, by calling <code>somemodel_instance.post</code> you get the <code>Post</code> class instance. You can always call <code>somemodel_instance.post.subclass_object</code> and get the same result, but the default manager could do any other sort of tricks and the <code>FK</code> solutions hides them nicely. If you own and can modify the custom manager code you can use the <a href="http://docs.djangoproject.com/en/dev/topics/db/managers/#manager-types" rel="noreferrer"><code>use_for_related_fields</code></a> attribute instead of using FK in place of legitimate 1to1 field, but even that can fail because of some not-known to me nuisances of the automatic managers. As far as I remember it will fail in the above example.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODjango: When extending User, better to use OneToOneField(User) or ForeignKey(User, unique=True)?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStrybik
UserOwnerUserId
1. UStrybik
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.