StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7563768
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-27T03:04:35.037
FavoriteCount
0
LastActivityDate
2011-09-27T03:04:35.037
LastEditDate
LastEditorUserId
0
OwnerUserId
36305
ParentId
7563354
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p><strong>Your main problem, based on the XML and XSLT code provided, is that your code doesn't address at all the fact that the elements in the XML document are in a default namespace</strong>.</p> <p>How to process an XML document with a default namespace is a FAQ -- just search the xslt and xpath tags and you'll find numerous good answers.</p> <p><strong>Here is one possible solution</strong>:</p> <p><strong>This transformation</strong>:</p> <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:x="http://notreal.org/ns1" exclude-result-prefixes="x"> <xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/> <xsl:template match="/*"> <html> <head> <title>User</title> </head> <body> <p>Detailed Addresses</p> <table> <thead> <xsl:apply-templates select="x:address/@type"/> </thead> <tr> <xsl:apply-templates select="x:address/x:street"/> </tr> <tr> <xsl:apply-templates select="x:address/x:city"/> </tr> </table> </body> </html> </xsl:template> <xsl:template match="@type"> <th><xsl:value-of select="."/></th> </xsl:template> <xsl:template match="x:address/*"> <td><xsl:value-of select="."/></td> </xsl:template> </xsl:stylesheet> </code></pre> <p><strong>when applied on a complete and well-formed XML document that includes the XML fragment provided in the question</strong>:</p> <pre><code><user xmlns="http://notreal.org/ns1" xmlns:poi="http://notreal2.org/ns2"> <address type="primary"> <street>1031 Court St.</street> <city>Monhegan, NY</city> </address> <address type="secondary"> <street>203 Elm St.</street> <city>Pittsburgh, PA</city> </address> </user> </code></pre> <p><strong>produces (what seems to be) the wanted, correct result</strong>:</p> <pre><code><html> <head> <title>User</title> </head> <body> <p>Detailed Addresses</p> <table> <thead> <th>primary</th> <th>secondary</th> </thead> <tr> <td>1031 Court St.</td> <td>203 Elm St.</td> </tr> <tr> <td>Monhegan, NY</td> <td>Pittsburgh, PA</td> </tr> </table> </body> </html> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POxslt - can't access curent node with attribute selector
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDimitre Novatchev
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POxslt - can't access curent node with attribute selector
  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
  VTAcceptedByOriginator
CommentsPostId
1. CO@DanielBrockman: You are welcome.
  singulars
  PostPostId
  PO
  UserUserId
  USDimitre Novatchev

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.