StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14284740
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-11T18:49:40.357
FavoriteCount
0
LastActivityDate
2013-01-12T15:55:39.313
LastEditDate
2013-01-12T15:55:39.313
LastEditorUserId
315013
OwnerUserId
315013
ParentId
14284411
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
Note first that <code>last</code> is not particularly great on other grounds, since it is a partial function like <code>head</code>. If you are constantly using the tail end of the list, scrap it for <code>Data.Sequence</code> or <code>Data.Vector.Unboxed</code>: <pre><code>import Data.Sequence firstThing seq = case viewl seq of EmptyL -> error "no beginning" a :< as -> a lastThing seq = case viewr seq of EmptyR -> error "no end" as :> a -> a -- > lastThing (fromList "abc") -- 'c' -- > firstThing (fromList "abc") -- 'a' </code></pre> If you are using an unboxed type like <code>Int</code>, <code>Double</code>, <code>Char</code> etc. then you will get still better results with <code>Data.Vector.Unboxed</code> , see the documentation for remarks about the efficiency of <code>Data.Vector.Unboxed.head</code> and <code>Data.Vector.Unboxed.last</code> <a href="http://hackage.haskell.org/packages/archive/vector/0.10.0.1/doc/html/Data-Vector-Unboxed.html#g:4" rel="nofollow noreferrer">http://hackage.haskell.org/packages/archive/vector/0.10.0.1/doc/html/Data-Vector-Unboxed.html#g:4</a> In the special case where you are using lists of <code>Char</code>s use <code>Data.Text</code> wherever possible, this is emphatically the 'idiomatic' thing. Again see the documentation for <code>head</code> and <code>last</code> <a href="http://hackage.haskell.org/packages/archive/text/0.11.2.3/doc/html/Data-Text.html" rel="nofollow noreferrer">http://hackage.haskell.org/packages/archive/text/0.11.2.3/doc/html/Data-Text.html</a> If you are imagining a contrast between 'Haskell' lists and 'lists' in other languages, it is probably the contrast between 'Haskell' lists on the one hand, and vectors and arrays on the other; the latter are just as 'Haskelly' as lists.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGet last element from a list in an efficient way
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USapplicative
UserOwnerUserId
1. USapplicative
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.