StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14221171
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-01-08T17:56:57.107
FavoriteCount
0
LastActivityDate
2013-01-08T17:56:57.107
LastEditDate
LastEditorUserId
0
OwnerUserId
252228
ParentId
14219852
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I don't know the ruby syntax so I am not sure whether indentation or whitespace matters but with the stylesheet <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:acs="http://www.example.com/xsds" exclude-result-prefixes="acs"> <xsl:output method="text"/> <xsl:strip-space elements="*"/> <xsl:template match="acs:acronym_list"> Module <xsl:value-of select="local-name()"/> def self.included(other) include SAXMachine SAXMachine.configure(other) do |c| <xsl:apply-templates select="acs:item/acs:*" mode="config"/> end end <xsl:apply-templates select="acs:item/acs:*" mode="class"/> end </xsl:template> <xsl:template match="acs:item/acs:*" mode="config"> c.element :<xsl:value-of select="local-name()"/>, :class => <xsl:value-of select="local-name()"/> </xsl:template> <xsl:template match="acs:item/acs:*" mode="class"> class <xsl:value-of select="local-name()"/> include SAXMachine <xsl:apply-templates mode="class"/> end </xsl:template> <xsl:template match="acs:item/acs:*/acs:*" mode="class"> c.element :<xsl:value-of select="local-name()"/> </xsl:template> </xsl:stylesheet> </code></pre> Saxon 6.5.5 tansforms the input <pre><code><acronym_list xmlns="http://www.example.com/xsds" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.example.com/xsds http://www.example.com/xsds/acronyms.xsd"> <item> <metadata> <release>...</release> <id>...</id> <checkdigit>...</checkdigit> <status>...</status> <date_added>...</date_added> <date_modified>...</date_modified> <language>...</language> <license_url>...</license_url> </metadata> <info> <name>...</name> </info> </item> </acronym_list> </code></pre> into the output <pre><code>Module acronym_list def self.included(other) include SAXMachine SAXMachine.configure(other) do |c| c.element :metadata, :class => metadata c.element :info, :class => info end end class metadata include SAXMachine c.element :release c.element :id c.element :checkdigit c.element :status c.element :date_added c.element :date_modified c.element :language c.element :license_url end class info include SAXMachine c.element :name end end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT: Transform nested XML into Ruby Code
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMartin Honnen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POXSLT: Transform nested XML into Ruby Code
 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. COThis is awesome. Thanks! If I wanted to make the processing of the item element generic (i.e. I have one file with acronym_item and another with asset_item), can I take a similar approach with modes, like you've done above?
 singulars
 PostPostId
 PO
 UserUserId
 USMatt Rogers
2. COWell in the sample you have posted there is an `acronym_list` element, but no `acronym_item` so I am not sure where `asset_item` would appear. And it's not clear which output you want. If nothing changes in terms of the wanted output structure then it should suffice to simply provide an enumeration of match patterns for the templates e.g. `<xsl:template match="acs:acronym_list | acs:asset_list">...</xsl:template>`. Modes are helpful to process a node several times i.e. the first time for outputting in one way in a certain way using the first mode, the second time for outputting in a second way
 singulars
 PostPostId
 PO
 UserUserId
 USMartin Honnen

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.