StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3407067
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2010-08-04T15:24:17.347
FavoriteCount
0
LastActivityDate
2010-08-05T07:24:53.707
LastEditDate
2010-08-05T07:24:53.707
LastEditorUserId
385573
OwnerUserId
385573
ParentId
3406994
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Maybe he was refering to XML-serialization used in Webservices ? Having used those a few years ago, I remember that a Webservice returning a <code>List</code> object was difficult to connect to (at least I could not figure it out, probably because of the inner structure of <code>ArrayList</code>s and <code>LinkedList</code>s), although this was trivially done when a native array was returned. To adress Reddy's comment, <blockquote> But in any case (array or ArrayList) will get converted to XML, right? </blockquote> Yes they will, but the XML-serialization basically translated in XML all the data contained in the serialized object. For an array, that is a series of values. For instance, if you declare and serialize <pre><code>int[] array = {42, 83}; </code></pre> You will probably get an XML result looking like : <pre><code> <array>42</array> <array>83</array </code></pre> For an ArrayList, that is : <ul> <li>an array (obviously), which may have a size bigger than the actual number of elements</li> <li>several other members such as integer indexes (<code>firstIndex</code> and <code>lastIndex</code>), counts, etc</li> </ul> (you can find all that stuff in the <a href="http://www.docjar.com/html/api/java/util/ArrayList.java.html" rel="nofollow noreferrer">source for <code>ArrayList.java</code></a>) So all of those will get translated to XML, which makes it more difficult for the Webservice client to read the actual values : it has to read the index values, find the actual array, and read the values contained between the two indexes. The serialization of : <pre><code>ArrayList<Integer> list = new ArrayList<Integer>(); list.add(42); list.add(83); </code></pre> might end up looking like : <pre><code><firstIndex>0</firstIndex> <lastIndex>2</lastIndex> <E>42</E> <E>83</E> <E>0</E> <E>0</E> <E>0</E> <E>0</E> <E>0</E> <E>0</E> <E>0</E> <E>0</E> </code></pre> So basically, when using XML-serialization in Webservices, you'd better use arrays (such as <code>int[]</code>) than collections (such as <code>ArrayList<Integer></code>). For that you might find useful to convert Collections to arrays using <code>Collection#toArray()</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POArrays are more serializable than ArrayList?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAxel
UserOwnerUserId
1. USAxel
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

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.