StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6421397
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-21T06:45:42.003
FavoriteCount
0
LastActivityDate
2011-06-21T06:45:42.003
LastEditDate
LastEditorUserId
0
OwnerUserId
57191
ParentId
6420647
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>There is a lot to your question, and it would help to have more information, but here are some of my thoughts:</p> <ul> <li>The language interfacing with the database is generally not a factor -- you should work as hard as possible to limit the number of connections and messages required (i.e. use join instead of communicating with PHP twice), but since good design is doing as much data selection/sorting work on the DB side as possible (because <a href="http://en.wikiquote.org/w/index.php?title=Thumb_Wars&section=2" rel="nofollow">that's what they're for</a>)</li> <li>If all of the tables have the same structure, then you're often better off with one table when dealing with massive selects -- <code>UNION</code>, at least in my experience, is generally a slow beast.</li> <li>If you're really concerned about accessing only a small subset of the data at once, then I would recommend keeping everything in fewer tables and create views.</li> <li><code>Don't care about table management and simplicity of database</code> is a bad policy. All of the best practices of programming are true for db design. Remember, someone who has no idea what you were thinking will inherit this project, and that might be you.</li> </ul> <p>Personally, I think that quite a few of us have had experience with the 1M line table, and I know that I, for one, would not have wanted to deal with that as a series of <code>UNION</code>s, <code>OR</code>s and <code>JOIN</code>s. At least, not when it was all the same table design.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFeasibility of dynamically increase in no. of tables and rows in a database
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UScwallenpoole
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFeasibility of dynamically increase in no. of tables and rows in a database
  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
  VTAcceptedByOriginator
2. 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.