Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This option will give you a sorted <code>IOrderedEnumerable</code>, with the xml for each user, and the managerId separately. Variations of this should give you a lot of flexibility:</p> <pre><code>var sortedUsers = yourRootXElement.Element("users") .Elements() .Select(usr =&gt; new { managerId = usr.Element("manager") .Element("dn") .Value, user = usr }) .OrderBy(user =&gt; user.managerId); </code></pre> <p><strong>Update:</strong></p> <p>Based on a comment under one of the other answers, it seems you want to reorder this "recursively" (sort of). </p> <p>Initially, I don't that is very easy using Linq - Unless you have the option of manipulating your original XML, you might be better of writing a recursive algorithm for this. </p> <p>If however, you can add a field <code>depth</code> to each user in your XML, so that it would look something like this..: </p> <pre><code>&lt;syncdata&gt; &lt;users&gt; &lt;user&gt; &lt;dn&gt;User2&lt;/dn&gt; &lt;manager&gt;&lt;dn&gt;User1&lt;/dn&gt;&lt;/manager&gt; &lt;depth&gt;2&lt;/depth&gt; &lt;/user&gt; &lt;user&gt; &lt;dn&gt;User1&lt;/dn&gt; &lt;manager&gt;&lt;dn&gt;User5&lt;/dn&gt;&lt;/manager&gt; &lt;depth&gt;1&lt;/depth&gt; &lt;/user&gt; &lt;user&gt; &lt;dn&gt;User4&lt;/dn&gt; &lt;manager&gt;&lt;dn&gt;User1&lt;/dn&gt;&lt;/manager&gt; &lt;depth&gt;2&lt;/depth&gt; &lt;/user&gt; &lt;user&gt; &lt;dn&gt;User5&lt;/dn&gt; &lt;manager&gt;&lt;dn&gt;User3&lt;/dn&gt;&lt;/manager&gt; &lt;depth&gt;1&lt;/depth&gt; &lt;/user&gt; &lt;user&gt; &lt;dn&gt;User3&lt;/dn&gt; &lt;manager&gt;&lt;dn&gt;&lt;/dn&gt;&lt;/manager&gt; &lt;depth&gt;0&lt;/depth&gt; &lt;!-- Note: Root element in hierarchy! --&gt; &lt;/user&gt; &lt;/users&gt; &lt;/syncdata&gt; </code></pre> <p>...then you could perhaps order it as follows?:</p> <pre><code>var sortedUsers = yourRootXElement.Element("users") .Elements() .Select(usr =&gt; new { userId = usr.Element("dn").Value, managerId = usr.Element("manager") .Element("dn") .Value, depth = usr.Element("depth") .Value, userData = usr }) .OrderBy(user =&gt; user.depth) .ThenBy(user =&gt; user.managerId); </code></pre> <p><strong>Note:</strong> This should order them by their "reporting-levels" in the hierarchy, but will not show those under a manager listed under him - ie.: All those reporting to a top-level managers will be shown first, followed by all those reporting to a second-level managers, etc... </p>
    singulars
    1. This table or related slice is empty.
    1. POLinqToXml: reorder user nodes based on mangerial hierarchy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKjartan
    1. USKjartan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes i believe your right i need to stamp the user nodes with a depth via a recursive function and then i should be able to order. just trying to workout how i can do that
      singulars
      1. PO
      1. USTim
    2. CO@Tim If you could get the depth in the original XML, that would be best (I have no idea if LDAP can provide that for you..?). Otherwise, if you're going to use a recursive function anyway, I would assume you might as well list the data out directly from it, instead of just using it to generate a "depth stamp"? ;)
      singulars
      1. PO
      1. USKjartan
    3. COUnfortunately we cannot get the depth in the initial file, as its a format for importing users which supports LDAP and other sources. I can preprocess the file though and recursively increment a new depth value, I just need to workout how to do this ;)
      singulars
      1. PO
      1. USTim
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload