StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2047913
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-12T09:34:42.957
FavoriteCount
0
LastActivityDate
2010-01-12T09:54:33.790
LastEditDate
2010-01-12T09:54:33.790
LastEditorUserId
18771
OwnerUserId
18771
ParentId
2047020
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
To your questions: <blockquote> Is there any way to break the statement in for-each if condition is true ? </blockquote> No, and normally this is also unnecessary. XSLT is not an imperative programming language, and imperative approaches do not really work well here. What you seemingly want to do is expressing "find the first <code><LeafNode></code> where <code>@Type='ABC'</code>, and return true or false depending on whether there is one. The way to do this in traditional languages is like your approach: for each node, check condition, if condition satisfied then return. In XSLT you simply select the node with XPath: <pre><code>//RootNode/LeafNode[@Type='ABC'] </code></pre> either the result of this contains a node, or it does not. No need for a for-each at all. <blockquote> Can we use the value of Template variable or param from main calling routine ? </blockquote> No. Variables and params are strictly scoped. They go out of scope once processing leaves their parent element. They are also constant, once declared they cannot be changed. The way to do what you want here is making the template output the desired value and capture it in a variable: <pre><code><xsl:template> <xsl:variable name="returnValue"> <xsl:call-template name="TestTemplate" /> </xsl:variable> </xsl:template> <xsl:template name="TestTemplate">  <xsl:value-of select=" count(//RootNode/LeafNode[@Type='ABC']) gt; 0 " /> </xsl:template> </code></pre> Two last hints: <ul> <li>avoid the <code>'//'</code> operator at all costs. Most of the time its use is not necessary</li> <li>the first, top-most element in a document is not the "root node", it is the "document element"</li> </ul> This is an important distinction. The "root node" comes before the document element, so the XPath above should be more like this (semantically): <pre><code>/DocumentElement/LeafNode ^------ *this* slash represents the "root node" </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT: Use of template tag variable and break condition in for-each loop
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTomalak
UserOwnerUserId
1. USTomalak
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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.