StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9041371
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2012-01-27T23:19:54.297
FavoriteCount
0
LastActivityDate
2012-01-30T20:39:54.393
LastEditDate
2012-01-30T20:39:54.393
LastEditorUserId
592746
OwnerUserId
592746
ParentId
9041237
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Whitelist those elements: <pre><code><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="*[not(self::description or self::p or self::i or self::em or self::strong or self::b or self::ol or self::ul or self::li or self::a)]"/> </xsl:stylesheet> </code></pre> Note that this removes the undesired elements and anything below them. To just strip the <code>font</code> element itself, for example, but allow its children, modify the last template like this: <pre><code><xsl:template match="*[not(self::description or self::p or self::i or self::em or self::strong or self::b or self::ol or self::ul or self::li or self::a)]"/> <xsl:apply-templates/> </xsl:template> </code></pre> An equivalent (and slightly cleaner) solution: <pre><code><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="@*|node()" priority="-3"> <xsl:copy/> </xsl:template> <xsl:template match="description|p|i|em|strong|b|ol|ul|li|a"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="*"/> </xsl:stylesheet> </code></pre> The opposite approach is to blacklist the unwanted elements: <pre><code><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="font|span"/> </xsl:stylesheet> </code></pre> Again, add an <code>apply-templates</code> to the final template if you want to allow children of the skipped elements.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORemove unwanted tags with XSL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWayne Burkett
UserOwnerUserId
1. USWayne Burkett
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORemove unwanted tags with XSL
 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
 VTUpMod
CommentsPostId

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.