StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15320961
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-10T09:55:59.673
FavoriteCount
0
LastActivityDate
2013-03-10T09:55:59.673
LastEditDate
LastEditorUserId
0
OwnerUserId
790387
ParentId
3834238
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I'll try to answer your actual problem, because what you are asking for in the question is a problem with your proposed solution, which as many have pointed out is not really ideal. In the comments you mention this: <blockquote> i'll try to explain.. So we have 2 models: User and Book. A User has a book called "Titanic" with some content. Now, another user wants a relation to that book too. But, the second user wants exactly the same book, but it should be called "Ship is going under".. I would copy the book, and rename it. - I know, i could also put the content of the book in another model - but my model is a little bit more complex. </blockquote> Looks like you have three things to track: <ol> <li>Users</li> <li>Their Books</li> <li>Some custom notes that users have about their "owned" book.</li> </ol> For each <code>Book</code>, store its common information, for example: <pre><code>class Author(models.Model): name = models.CharField(max_length=50) email = models.EmailField() def __unicode__(self): return unicode(self.name) class Book(models.Model): title = models.CharField(max_length=100) author = models.ManyToMany(Author) isbn = models.CharField(max_length=13) # and so on def __unicode__(self): return unicode(self.title) </code></pre> Now, you need to store Book -> User relation, such as one user can have many books, two users may own the same book, with their own meta information attached. <pre><code>class BookClub(models.Model): username = models.ForeignKey(User) book = models.ForeignKey(Book) comments = models.TextField() </code></pre> If you structure your models like that, you'll be able to do queries like: <ul> <li>"How many books does each member have?"</li> <li>"What is the most popular book?"</li> <li>"What is the least popular book?"</li> <li>"What is the most popular author?"</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCopy all fields of a django model instance
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBurhan Khalid
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. This table or related slice is empty.
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.