StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8478385
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-12T17:36:48.683
FavoriteCount
0
LastActivityDate
2012-09-10T08:37:28.037
LastEditDate
2012-09-10T08:37:28.037
LastEditorUserId
289572
OwnerUserId
289572
ParentId
8477868
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
As the structure of the <code>ul</code> is consistent, you can simply get each column individually (using only base R): <pre><code>section <- vapply(ul, function(x) as.numeric(x[[1]][2]), 0) field <- vapply(ul, function(x) as.numeric(x[[2]][2]), 0) final_answer <- vapply(ul, function(x) as.numeric(x[[3]][2]), 0) points <- vapply(ul, function(x) as.numeric(x[[4]][2]), 0) </code></pre> (Note, I use <code>vapply</code> instead of <code>sapply</code> as it is faster and reliably returns a vector, which is needed here). Then you can simply put it all together: <pre><code>> data.frame(section, field, final_answer, points) section field final_answer points 1 1 1 1.000 0 2 1 2 1.000 1 3 1 3 0.611 1 </code></pre> Note that I transformed everything into <code>numeric</code>. If you want to retain everything as characters, delete the <code>as.numeric</code> and exchange <code>0</code> with <code>""</code> in each call to <code>vapply</code>. <hr> Late update: There is actually a nice oneliner that extracts the complete data: <pre><code>do.call("rbind", lapply(ul, function(x) as.numeric(vapply(x, "[", i = 2, "")))) </code></pre> which gives: <pre><code> [,1] [,2] [,3] [,4] [1,] 1 1 1.000 0 [2,] 1 2 1.000 1 [3,] 1 3 0.611 1 </code></pre> to get the <code>colnames</code> use: <pre><code>> vapply(ul[[1]], "[", i = 1, "") param param param param "Section" "field" "final answer" "points" </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POList of lists to dataframe in R
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHenrik
UserOwnerUserId
1. USHenrik
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.