StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5041849
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-18T13:28:16.313
FavoriteCount
0
LastActivityDate
2011-02-18T13:28:16.313
LastEditDate
LastEditorUserId
0
OwnerUserId
267887
ParentId
5040978
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Why not create a table per user? Creating a db table per user is definitely not recommended. How would you create a table for every user? Raw SQL statements? As far as I know, you would break the main purpose of Django, it's ORM (object relational mapper) -- it's easy interface to SQL because it doesn't support automatically creating tables per user / knowing how to query it. Definitely, definitely use a table with a <code>ForeignKey</code> to the <code>User</code> table. Every table has a Primary Key field which is generally a number. One table can refer to another table via that Primary Key. For example <code>Entry 1 belongs to User ID 3</code>. Luckily, django abstracts the SQL layer and this is done via the <code>ForeignKey</code> field. <a href="http://docs.djangoproject.com/en/dev/ref/models/fields/#foreignkey" rel="nofollow">http://docs.djangoproject.com/en/dev/ref/models/fields/#foreignkey</a> <hr> As you are the one constructing queries for the database, only showing entries written by a specific user is a non-issue. You would simply only query the database for entries by the logged in user. As long as there are no loopholes for raw SQL to be input from outside your program, there's no way a user can access others data. <hr> To learn about best practice / ForeignKey's / querying etc, I suggest following the tutorial online. I think the documentation and tutorials are one of django's greatest assets. <a href="http://docs.djangoproject.com/en/dev/intro/tutorial01/" rel="nofollow">http://docs.djangoproject.com/en/dev/intro/tutorial01/</a> In the first tutorial they cover creating a <code>Poll</code> app, which includes a <code>Choices</code> model with a <code>ForeignKey</code> to <code>Poll</code> You can definitely apply this back to your model : )
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest practices: Good idea to create a new table for every user?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USYuji 'Tomita' Tomita
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
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.