StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19370591
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-10-14T22:57:09.167
FavoriteCount
0
LastActivityDate
2015-04-12T08:52:32.363
LastEditDate
2015-04-12T08:52:32.363
LastEditorUserId
2789308
OwnerUserId
2789308
ParentId
19367027
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>XPath in the version you are using matches nodes in order, which you cannot change.</p> <p>There are several ways to achieve it:</p> <h1>XSLT</h1> <p>One simple way is to perform an <a href="http://en.wikipedia.org/wiki/XSLT" rel="nofollow">XSL Transform</a></p> <p>Once you learn XSLT, it becomes really easy to do this sort of thing. Such as:</p> <pre><code><?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:template match="Operaciones"> <xsl:copy> <xsl:apply-templates select="Operacion"> <xsl:sort select="index-of(('Alta','Media','Baja'), @Prioridad)"/> </xsl:apply-templates> </xsl:copy> </xsl:template> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> <p>And then you can query all your <code>Operaciones</code> easily. If you do it the XSLT route, it means that you can upgrade your queries without having to recompile your software. It is probably the solution you wish to utilise.</p> <p><strong>Update: Mathias pointed out that we're not looking for an alphabetical sort. I will keep the solutions below for reference, but now I'd advise to go for the correct XSLT solution above.</strong></p> <h1>XPathDocument</h1> <p>The second way is more programatic, which utilises Microsoft's own features:</p> <p>Assuming <code>doc</code> is an <code>XmlDocument</code>, you can do the following to turn it into an <code>XPathDocument</code>:</p> <pre><code>XPathDocument xpathDoc = new XPathDocument(new XmlNodeReader(doc)); </code></pre> <p>Once you do that, you can run the following query:</p> <pre><code>XPathNavigator nav = xpathDoc.CreateNavigator(); XPathExpression expression = XPathExpression.Compile(@"//Operacion"); expression.AddSort(@"@Prioridad", XmlSortOrder.Ascending, XmlCaseOrder.None, "", XmlDataType.Text); XPathNodeIterator iterator = nav.Select(expression); foreach (XPathNavigator operation in iterator) { Console.WriteLine("Found priority '{0}'",operation.GetAttribute("Prioridad","")); } </code></pre> <h1>Linq</h1> <p>Third way, using Linq (you might want to check the syntax here):</p> <pre><code>XDocument xDoc = XDocument.Load(new XmlNodeReader(doc)); var operations = xDoc.Descendants("Operacion").OrderBy(s=>(string)s.Attribute("Prioridad")); foreach(var operation in operations) { Console.WriteLine("hey -> {0}", operation); } </code></pre> <p>I suggest you do it via Linq, but if you are transforming data, then go for XSLT every time.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to appens nodes using XPATH
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USScala William
UserOwnerUserId
1. USScala William
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to appens nodes using XPATH
  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
  VTAcceptedByOriginator
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.