StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4976154
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-12T03:34:28.017
FavoriteCount
0
LastActivityDate
2011-02-12T03:34:28.017
LastEditDate
LastEditorUserId
0
OwnerUserId
613394
ParentId
4976065
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<p>I have mine organized something like the following:</p> <pre><code>/type(OS specific, website, application, script, etc) /sourcecode /snippets(sections of code that I use frequently in many different projects) /language(perl, java, batch, bash, etc) /version(either version number or completion date depending on the project) /test_code(very raw form, pieces from here may work or may complete trash) /language /version /dev_code(slightly more refined code, but still buggy) /language /version /pprd_code(code that is being tested prior to delivery to the production environment) /language /version /prod_code(code that is currently completed and is either being used in production or is fully ready to be placed in production) /language /version /patches(special patches that do not have their own specific version) /language /version /compiled_projects /test_apps(very raw form, applications here may work or may be junkers yet to be deleted) /language /version /dev_apps(slightly more refined applications, but still buggy) /language /version /pprd_apps(applications that are being tested prior to delivery to the production environment) /language /version /prod_apps(applications that are currently completed and are either being used in production or are fully ready to be placed in production) /language /version /patches(special patches that do not have their own specific version) /language /version /graveyard(I put all code or apps that I want to delete here for at least 6mo to a year just in case I may need something that I forgot about) /language /old_project_name_expected_deletion_date </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORecommendations on how to organize my various web projects (rails, asp.net, binaries and git repos)
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USEli
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.