StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4568191
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-31T05:05:41.697
FavoriteCount
0
LastActivityDate
2010-12-31T05:05:41.697
LastEditDate
LastEditorUserId
0
OwnerUserId
201487
ParentId
4568123
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The way I learned to work these things out is to stop and make associations. In more object oriented languages (I'm assuming you're using PHP?) that force OO, you learn to think OO very quickly, which is sort of what you're after here. My workflow is like this: <ol> <li>Work out what data you need to store. (Customer name etc.)</li> <li>Work out the main objects you're working with (e.g. Customer, Order, Salesperson etc), and assign each of these a key (e.g. Customer ID).</li> <li>Work out which data connects to which objects. (Customer name belongs to a customer)</li> <li>Work out how the main objects connect to each other (Salesperson sold order to Customer)</li> </ol> Once you have these, you have a good object model of what you're after. The next step is to look at the connections. For example: <ul> <li>Each customer has only one name.</li> <li>Each product can be sold multiple times to anybody</li> <li>Each order has only one salesperson and one customer.</li> </ul> Once you've worked that out, you want to try something called <a href="http://en.wikipedia.org/wiki/Database_normalization" rel="noreferrer" title="Database Normalization - wikipedia">normalization</a>, which is the art of getting this collection of data into a list of tables, still minimizing redundancy. (The idea is, a one-to-one (customer name) is stored in the table with the customer ID, many to one, one to many and many to many are stored in separate tables with certain rules) That's pretty much the gist of it, if you ask for it, I'll scan an example sheet from my workflow for you.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOrganizing a MySQL Database
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLiam Dawson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POOrganizing a MySQL 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
 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
 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.