StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1347939
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-08-28T15:59:43.490
FavoriteCount
0
LastActivityDate
2009-08-28T15:59:43.490
LastEditDate
LastEditorUserId
0
OwnerUserId
4126
ParentId
1345003
PostTypeId
2
Score
-1
ViewCount
0
LastEditorDisplayName
text
Body
In your question: <blockquote> Can I send the <book> element to a function - within that function I want to process the nodes under book (<author>, <price> or <year>) </blockquote> and later comment: <blockquote> can i have a function which accepts the node as a parameter? </blockquote> ...you're asking for a function, but what i think you want is a <a href="http://www.w3schools.com/xsl/el_template.asp" rel="nofollow noreferrer"><code>template</code></a> for the <code>book</code> element. Of course, you could do this several ways--in a <a href="http://www.w3schools.com/xsl/el_for-each.asp" rel="nofollow noreferrer"><code>for-each</code></a> loop, actually sending the <code>book</code> node into a template using <a href="http://www.w3schools.com/xsl/el_with-param.asp" rel="nofollow noreferrer"><code>with-param</code></a>, etc.--but a simple <a href="http://www.w3schools.com/xsl/el_template.asp" rel="nofollow noreferrer"><code>template</code></a> should accomplish what you need. Whatever the template matches is the "parameter". <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="books"> <xsl:apply-templates select="book"/> </xsl:template> <xsl:template match="book"> author: <xsl:value-of select="author" /> price: <xsl:value-of select="price" /> year: <xsl:value-of select="year" /> </xsl:template> </xsl:stylesheet> </code></pre> If you want to do some further processing on the sub-elements (author, price, and year), you could look into creating templates for them too. Keep in mind that matching "year" will match all year elements, even for those you might have in date of births etc. (In these cases you would probably want to restrict the XPath in the match or just keep the <code>book/year</code> processing within the book template.) Say you want to do something extra with <code>year</code>. Your book processing might evolve into something like this (where you're now passing each <code>year</code> node as parameters into the year template): <pre><code><xsl:template match="book"> author: <xsl:value-of select="author" /> price: <xsl:value-of select="price" /> <xsl:apply-templates select="year" /> </xsl:template> <xsl:template match="year"> <xsl:choose> <xsl:when test="year &lt; '2000'"> from a prior century: <xsl:value-of select="." /> </xsl:when> <xsl:otherwise> from this century: <xsl:value-of select="." /> </xsl:otherwise> </xsl:choose> </xsl:template> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I send a node (any) to an xsl:function?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbill weaver
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. COI am looking for a XSLT function, which accepts a node (basically any node it may be) as a param to the XSLT function ? If yes can i have the syntax for the XSLT function ?
 singulars
 PostPostId
 PO
 UserUserId
 USLaxmikanth Samudrala

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.