StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2441112
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-03-14T03:50:18.697
FavoriteCount
0
LastActivityDate
2017-07-13T19:00:23.037
LastEditDate
2017-07-13T19:00:23.037
LastEditorUserId
1103734
OwnerUserId
179972
ParentId
2439453
PostTypeId
2
Score
23
ViewCount
0
LastEditorDisplayName
text
Body
The Google Go docs <a href="http://golang.org/doc/go_tutorial.html#tmp_94" rel="nofollow noreferrer">state the following about passing arrays</a> - they say you usually want to pass a slice (instead of a pointer?): <h2>Updated:</h2> As indicated by @Chickencha's comment, array slices are references which is why they are efficient for passing. Therefore likely you will want to use the slice mechanism instead of "raw" pointers. From Google Effective Go doc <a href="http://golang.org/doc/effective_go.html#slices" rel="nofollow noreferrer">http://golang.org/doc/effective_go.html#slices</a> <blockquote> Slices are reference types, </blockquote> <hr> <h2>Original</h2> It's under the heading An Interlude about Types <blockquote> [...snip...] When passing an array to a function, you almost always want to declare the formal parameter to be a slice. When you call the function, take the address of the array and Go will create (efficiently) a slice reference and pass that. </blockquote> Editor's note: This is no longer the case Using slices one can write this function (from sum.go): <pre><code>09 func sum(a []int) int { // returns an int 10 s := 0 11 for i := 0; i < len(a); i++ { 12 s += a[i] 13 } 14 return s 15 } </code></pre> and invoke it like this: <pre><code>19 s := sum(&[3]int{1,2,3}) // a slice of the array is passed to sum </code></pre> <hr> Maybe pass the whole array as a slice instead. Google indicates Go deals efficiently with slices. This is an alternate answer to the question but maybe it's a better way.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing a pointer to array
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USollien
UserOwnerUserId
1. USJohn K
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. COI agree that this sounds like the way to go. A slice is basically a pointer to an array already and is the preferred way of passing an array by reference.
 singulars
 PostPostId
 PO
 UserUserId
 USEvan Shaw

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.