StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17809932
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-23T12:14:45.810
FavoriteCount
0
LastActivityDate
2013-07-23T12:14:45.810
LastEditDate
LastEditorUserId
0
OwnerUserId
2594491
ParentId
14906247
PostTypeId
2
Score
-1
ViewCount
0
LastEditorDisplayName
text
Body
Your XML has no target namespace. It's not an issue but you have to take it into account. You can specify which parser <code>XML::Simple</code> will use. Here is a code example, with <code>XML::Simple</code> that gets the result you expect. <pre><code>tvnshack$ ./a.pl Trying bugtrack.xml ... bugtrack.xml is indeed valid BugTrackID is: 57982 </code></pre> The code is bellow ... to be adjusted to your liking (it's based on some live code I use in production). <pre><code>#!/opt/perl/bin/perl -w use strict; use XML::Simple qw(:strict); use Data::Dumper; # Supported namespaces my $nspcBUGT = 'urn:alerts.symantec.com'; my $parsingfailed = 0; my $XMLdata; my $XMLfname = 'bugtrack.xml'; print STDOUT "Trying $XMLfname ... "; $XML::Simple::PREFERRED_PARSER = 'XML::SAX::Expat'; my $simpleCstr = XML::Simple->new( Cache => [ 'memshare' ], KeyAttr => [], ForceArray => 1, KeepRoot => 1, ContentKey => 'value', NSExpand => 1, NormaliseSpace => 1); eval { $parsingfailed++; # if the parsing fails, the module will terminate the process abruptly. $XMLdata = $simpleCstr->XMLin($XMLfname); # This line of code will not be executed, leaving $parsingfailed>0. $parsingfailed = 0; }; if ( $parsingfailed > 0) { print STDERR "Error: That XML file <$XMLfname> can not be read, does not exist or is not a valid XML file (possible wrong namespace too).\n"; } else { if (defined($XMLdata->{"Alerts"})) { print STDOUT "$XMLfname is indeed valid\n"; print STDOUT " BugTrackID is: " . $XMLdata->{'Alerts'}->[0]->{"{$nspcBUGT}AlertDocument"}->[0]->{"{$nspcBUGT}BugTraqID"}->[0] . "\n"; # print Dumper($XMLdata) . "\n"; } } __END__ </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParsing xml with namespace using Perl XML::Simple
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTVNshack
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
 VTDownMod
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.