StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7846821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-21T08:23:37.687
FavoriteCount
0
LastActivityDate
2011-10-21T09:12:33.073
LastEditDate
2011-10-21T09:12:33.073
LastEditorUserId
284969
OwnerUserId
284969
ParentId
7844889
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
To clarify a bit on what others have said, there are rougly three categories of stuff that are excluded, and git uses different exclude files for each category: <ol> <li>Stuff that everybody working on the project wants to exclude — e.g. <code>*.o</code>, the names of the generated executables, other build-generated files that you don't want to check in. For this case, you use <code>.gitignore</code> in the project directories (as you're doing). Since you want everybody working on the project to share these excludes, you should add the these <code>.gitignore</code> files using <code>git add</code> and commit them like source files.</li> <li>Stuff that you personally want to exclude for all your projects, but others working on the same projects may not. For instance, I use the Emacs editor, which creates backup files like <code>Foo.~1~</code>, so that's something I exclude personally for all my git checkouts For this case, you use a "personal" ignore file, conventionally in your home directory called something like <code>~/.gitignore</code>; the name of this file is actually set as a global git parameter, so for instance, you might do: <pre><code>git config --global core.excludesfile ~/.gitignore </code></pre> [As that's a global setting, you only need to do it once.] So for my Emacs backup files, I add a pattern like <code>*~</code> to <code>~/.gitignore</code>.</li> <li>Stuff that you want excluded "locally" in a specific working-tree, but maybe not for other working-trees. For this case, you should add exclude entries to the <code>.git/info/exclude</code> file. Since this file is underneath the magic <code>.git</code> directory, the status command will never show it as an untracked file (and you can't add it).</li> </ol> Git uses all these exclude files together to decide what's excluded.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO.gitignore shows up when I run git status
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsnogglethorpe
UserOwnerUserId
1. USsnogglethorpe
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
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
 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.