StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8017001
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2011-11-04T23:41:29.277
FavoriteCount
0
LastActivityDate
2013-08-06T02:50:56.847
LastEditDate
2013-08-06T02:50:56.847
LastEditorUserId
980833
OwnerUserId
980833
ParentId
8016636
PostTypeId
2
Score
9
ViewCount
0
LastEditorDisplayName
text
Body
Edit of 2013-08-05 Using <code>sapply()</code> instead of <code>lapply()</code>, simplifies this considerably: <pre><code>foo4 <- function(a=1, b=5, h='coconut') { frm <- formals(sys.function()) sapply(names(frm), get, envir=sys.frame(sys.parent(0)), simplify=FALSE) } foo4(b=0, h='mango') </code></pre> This, though, without <code>sapply()</code> or <code>lapply()</code> might be the more elegant solution: <pre><code>foo5 <- function(a=1, b=5, h='coconut') { modifyList(formals(sys.function()), as.list(match.call())[-1]) } foo5(b=0, h='mango') </code></pre> <hr> Original post (2011-11-04) After casting about a bit, this looks to be the best solution. <pre><code>foo <- function(a=1, b=5, h='coconut') { frm <- formals(foo) parms <- lapply(names(frm), get, envir=sys.frame(sys.parent(0))) names(parms) <- names(frm) return(parms) } foo(b=0, h='mango') # $a # [1] 1 # $b # [1] 0 # $h # [1] "mango" </code></pre> There's some subtle stuff going on here with the way that <code>lapply</code> scopes/evaluates the calls that it constructs. The details are hidden in a call to <code>.Internal(lapply(X, FUN))</code>, but for a taste, compare these two calls: <pre><code># With function matched by match.fun, search in sys.parent(0) foo2 <- function(a=1, h='coconut') { lapply(names(formals()), get, envir = sys.parent(0)) } # With anonymous function, search in sys.parent(2) foo3 <- function(a=1, h='coconut') { lapply(names(formals()), FUN = function(X) get(X, envir = sys.parent(2))) } foo4(a=0, h='mango') foo5(a=0, h='mango') </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing get inside lapply, inside a function
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJosh O'Brien
UserOwnerUserId
1. USJosh O'Brien
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing get inside lapply, inside a function
 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
 VTAcceptedByOriginator
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

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.