StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14182550
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-01-06T13:22:48.740
FavoriteCount
0
LastActivityDate
2013-01-24T06:56:54.170
LastEditDate
2017-05-23T11:43:07.297
LastEditorUserId
-1
OwnerUserId
6309
ParentId
14178746
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Update January 24th, 2013: source "<a href="https://github.com/blog/1381-a-whole-new-code-search" rel="nofollow noreferrer">A Whole New Code Search</a>" The same query <a href="https://github.com/search?q=repo:OpeningDesign/OpeningDesign%20GET&p=1&ref=searchbar&type=Code&l=" rel="nofollow noreferrer"><code>repo:OpeningDesign/OpeningDesign GET</code></a> now returns result! The search index must have been updated when then new search engine has been deployed (<a href="http://www.elasticsearch.org/community/" rel="nofollow noreferrer">elasticsearch.org</a>) <hr> Original answer (January 6th, 2013) Considering that: <ul> <li>any request on the ruby/ruby repo works (as mentioned in "<a href="https://stackoverflow.com/questions/3616221/search-code-inside-a-github-project">Search code inside a Github project</a>")</li> <li>any request on <a href="https://github.com/OpeningDesign/OpeningDesign" rel="nofollow noreferrer"><code>OpeningDesign/OpeningDesign</code></a> doesn't work,</li> </ul> it seems to be an indexation issue. After their recent <a href="https://github.com/blog/1364-downtime-last-saturday" rel="nofollow noreferrer">fileservers issues</a>, this could be a side-effect. As Iven points out, <a href="https://github.com/contact" rel="nofollow noreferrer">GitHub support</a> should be able to clarify this. <hr> The support did clarify (07 January 2013): <blockquote> We have stopped adding newly pushed code into our codesearch index. The volume of code has outgrown our current search index, and we are working on moving to a more scalable search architecture. I'm sorry for the annoyance. We do not have an estimate for when this new search index will be up and running, but when it is ready a blog post will be published (<a href="https://github.com/blog" rel="nofollow noreferrer">GitHub blog</a>) </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POA public Github repo not found via search
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POA public Github repo not found via search
 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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.