StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7569314
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-27T12:43:34.980
FavoriteCount
0
LastActivityDate
2017-04-13T09:29:31.077
LastEditDate
2017-04-13T09:29:31.077
LastEditorUserId
498276
OwnerUserId
254307
ParentId
7568819
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
In my humble opinion, tail and head are more familiar with people with a functional background. When you start passing functions around, they are incredible useful, that's why most functional languages have them implemented and even have shortcut notation to refer to them, like in haskell or even in scala (even if it's not THAT functional, I know) In the "(almost) everything is an object but methods are made in a procedural way" java world, when passing around functions is at least hard and always awkward, head/tail methods are not so useful. For example, check this haskell implementation of quicksort: <pre><code>quicksort :: Ord a => [a] -> [a] quicksort [] = [] quicksort (p:xs) = (quicksort lesser) ++ [p] ++ (quicksort greater) where lesser = filter (< p) xs greater = filter (>= p) xs </code></pre> It relies, among other things, on the ability to easily separate head and tail, but also on being able to filter a collection using a predicate. A java implementation (check <a href="http://www.vogella.de/articles/JavaAlgorithmsQuicksort/article.html" rel="nofollow noreferrer">http://www.vogella.de/articles/JavaAlgorithmsQuicksort/article.html</a>) looks totally different, it is way lower level, and doesn't rely on separating head and tail. Note: The next sentence is totally subjective and based on my personal experience and may be proven wrong, but I think it's true: Most algorithms in functional programming rely on head/tail, in procedural programming you rely on accessing an element in a given position
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy no tail() or head() method in List to get last or first element?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USwool.in.silver
UserOwnerUserId
1. USPablo Grisafi
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.