Databases
StackOverflow2013
Postsdbo
POHow to filter node list based on the contents of another node list
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to filter node list based on the contents of another node list
    primarykey
    data
    text
    <p>I'd like to use XSLT to filter a node list based on the contents of another node list. Specifically, I'd like to filter a node list such that elements with identical id attributes are eliminated from the resulting node list. Priority should be given to one of the two node lists. </p> <p>The way I originally imagined implementing this was to do something like this:</p> <pre><code>&lt;xsl:variable name="filteredList1" select="$list1[not($list2[@id_from_list1 = @id_from_list2])]"/&gt; </code></pre> <p>The problem is that the context node changes in the predicate for $list2, so I don't have access to attribute @id_from_list1. Due to these scoping constraints, it's not clear to me how I would be able to refer to an attribute from the outer node list using nested predicates in this fashion.</p> <p>To get around the issue of the context node, I've tried to create a solution involving a for-each loop, like the following:</p> <pre><code> &lt;xsl:variable name="filteredList1"&gt; &lt;xsl:for-each select="$list1"&gt; &lt;xsl:variable name="id_from_list1" select="@id_from_list1"/&gt; &lt;xsl:if test="not($list2[@id_from_list2 = $id_from_list1])"&gt; &lt;xsl:copy-of select="."/&gt; &lt;/xsl:if&gt; &lt;/xsl:for-each&gt; &lt;/xsl:variable&gt; </code></pre> <p>But this doesn't work correctly. It's also not clear to me how it fails... Using the above technique, filteredList1 has a length of 1, but appears to be empty. It's strange behaviour, and anyhow, I feel there must be a more elegant approach.</p> <p>I'd appreciate any guidance anyone can offer. Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USjbeard4
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to filter node list based on the contents of another node list
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to filter node list based on the contents of another node list
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to filter node list based on the contents of another node list
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGood question (+1). See my one-liner solution. :)
      singulars
      1. POHow to filter node list based on the contents of another node list
      1. USDimitre Novatchev
 

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