StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4184070
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-11-15T11:55:31.230
FavoriteCount
0
LastActivityDate
2010-11-15T11:55:31.230
LastEditDate
LastEditorUserId
0
OwnerUserId
454144
ParentId
4178082
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>Here is example of <code>XML::Twig</code> usage. The main advantage is that it is not holding whole file in memory, so processing is much faster. The code below is trying to emulate operation of script from question.</p> <pre><code>use XML::Twig; my %strings = (); XML::Twig->new( twig_handlers => { 'strings/string' => sub { $strings{ lc $_->first_child('name')->text } = $_->first_child('id')->text }, } )->parsefile('B.xml'); print "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<npc_templates xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:noNamespaceSchemaLocation=\"npcs.xsd\">\n"; XML::Twig->new( twig_handlers => { 'npc_client' => sub { my $nameid = eval { $strings{ lc $_->first_child('desc')->text } }; # calculate rank as needed my $hpgauge_level = eval { $_->first_child('hpgauge_level')->text }; $rank = $hpgauge_level >= 28 ? 'ERROR' : $hpgauge_level > 25 ? 'LEGENDARY' : $hpgauge_level > 21 ? 'HERO' : $hpgauge_level > 10 ? 'ELITE' : $hpgauge_level > 0 ? 'NORMAL' : $hpgauge_level; my $npc_id = eval { $_->first_child('id')->text }; my $name = eval { $_->first_child('name')->text }; my $tribe = eval { $_->first_child('tribe')->text }; my $scale = eval { $_->first_child('scale')->text }; my $race_type = eval { $_->first_child('race_type')->text }; print qq|\t<npc_template npc_id="$npc_id" name="$name" name_id="$nameid" height="$scale" rank="$rank" tribe="$tribe" race="$race_type" hp_gauge="$hpgauge_level"/>\n|; $_->purge; } } )->parsefile('A.xml'); print "</<npc_templates>"; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POParsing large XML files?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbvr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POParsing large XML files?
  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. CO+1 Thanks very informational learning stuff really appreciate for you going thru my trouble :)
  singulars
  PostPostId
  PO
  UserUserId
  USGuapo

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.