StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2224257
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-02-08T19:28:52.860
FavoriteCount
0
LastActivityDate
2010-02-08T19:59:14.543
LastEditDate
2010-02-08T19:59:14.543
LastEditorUserId
267080
OwnerUserId
267080
ParentId
2224019
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Just changing the order of the two lines won't cause an <code>xml_archive_parsing_error</code> exception. The <a href="http://www.boost.org/doc/libs/1_42_0/libs/serialization/doc/exceptions.html#xml_archive_parsing_error" rel="noreferrer">doc</a> you've linked says that itself: <blockquote> (...)This might be possible if only the data is changed and not the XML attributes and nesting structure is left unaltered.(...) </blockquote> You haven't changed attributes and the order change has kept the structure (still two fields on the first level of your XML). No exception will ever be thrown this way. Also, when reading a XML using the <code>make_nvp function</code>, the name parameter won't put any restriction on what is being read. It will just tell arbitrarily the name to be used with the new name-value pair. So, you can change the name of your XML tags on your input, as long you don't change your expected order i.e. you could rename <code>producer</code> and <code>producer_version</code> on your XML to <code>foo</code> and <code>bar</code> and still would read the serialized data correctly i.e.: <blockquote> <code><foo>XXX</foo></code> <code><bar>0.0.1</bar></code> </blockquote> And your printed answer would still be "XXX 0.0.1". Since this only formatting your serialized data as a XML, there is no interest in checking the tag names. They are only used for making your serialized output more readable.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy doesn't boost::serialization check for tag names in XML archives?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfogo
UserOwnerUserId
1. USfogo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy doesn't boost::serialization check for tag names in XML archives?
 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
 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
 VTAcceptedByOriginator
CommentsPostId
1. COKind of sad, but if that's the way it is. Thanks for the info (I found this doc paragraph particularly hard to read, due to overuse of negation and conditionals).
 singulars
 PostPostId
 PO
 UserUserId
 USF'x

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.