StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20063887
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-19T05:28:59.143
FavoriteCount
0
LastActivityDate
2013-11-19T05:28:59.143
LastEditDate
LastEditorUserId
0
OwnerUserId
128421
ParentId
20063081
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Here's how computers look at the strings and compare them. If we look at the first characters of each word it'll help a little, because we know how the alphabet orders letters: <pre><code>%w[hello my time here is long].map{ |s| s[0] }.sort # => ["h", "h", "i", "l", "m", "t"] </code></pre> But that doesn't really help visualize it, so here's a look at each word's letters as a computer sees them: <pre><code>%w[time tome].each do |w| puts w.chars.map(&:ord).join(', ') end # >> 116, 105, 109, 101 # >> 116, 111, 109, 101 </code></pre> Each letter has a value. Over the years there have been many different ways of ordering letters for a computer, which caused the character to value mapping to change. <a href="http://en.wikipedia.org/wiki/EBCDIC" rel="nofollow">EBCDIC</a> and <a href="http://en.wikipedia.org/wiki/ASCII" rel="nofollow">ASCII</a> have been the most popular but have different orders. We're usually dealing with ASCII, or a derivative, which is set by the OS. Look at how the characters in the words are represented by the values in the following output. It should make it easy to understand what the computer is doing then. <pre><code>%w[he hello help holler hollow].sort.each do |w| puts '"%6s": %s' % [ w, w.chars.map(&:ord).join(', ') ] end # >> " he": 104, 101 # >> " hello": 104, 101, 108, 108, 111 # >> " help": 104, 101, 108, 112 # >> "holler": 104, 111, 108, 108, 101, 114 # >> "hollow": 104, 111, 108, 108, 111, 119 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to analyze the "max" method
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USthe Tin Man
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.