Databases
StackOverflow2013
Postsdbo
PODOM navigation: eliminating the text nodes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODOM navigation: eliminating the text nodes
    primarykey
    data
    text
    <p>I have a js script that reads and parses XML. It obtains the XML from an XMLHttpRequest request (which contacts with a php script which returns XML). The script is supposed to receive 2 or more nodes under the first parentNode. The 2 nodes it requires have the name well defined, the other ones can be any name. The output from the php may be:</p> <pre><code>&lt;?xml version='1.0'?&gt; &lt;things&gt; &lt;carpet&gt; &lt;id&gt;1&lt;/id&gt; &lt;name&gt;1&lt;/name&gt; &lt;desc&gt;1.5&lt;/desc&gt; &lt;/carpet&gt; &lt;carpet&gt; &lt;id&gt;2&lt;/id&gt; &lt;name&gt;2&lt;/name&gt; &lt;height&gt;unknown&lt;/height&gt; &lt;/carpet&gt; &lt;/things&gt; </code></pre> <p>Here all carpets have 7 nodes.</p> <p>but it also may be:</p> <pre><code>&lt;?xml version='1.0'?&gt; &lt;things&gt; &lt;carpet&gt; &lt;id&gt;1&lt;/id&gt; &lt;name&gt;1&lt;/name&gt; &lt;desc&gt;1.5&lt;/desc&gt; &lt;/carpet&gt; &lt;carpet&gt;&lt;id&gt;2&lt;/id&gt;&lt;name&gt;2&lt;/name&gt;&lt;height&gt;unknown&lt;/height&gt;&lt;/carpet&gt; &lt;/things&gt; </code></pre> <p>Here the first carpet has 7 nodes, the 2nd carpet has 3 nodes. I want my javascript code to treat both exactly the same way in a quick and clean way. If possible, I'd like to remove all the text nodes between each tag. So a code like the one above would always be treated as:</p> <pre><code>&lt;?xml version='1.0'?&gt; &lt;things&gt;&lt;carpet&gt;&lt;id&gt;1&lt;/id&gt;&lt;name&gt;1&lt;/name&gt;&lt;desc&gt;1.5&lt;/desc&gt;&lt;/carpet&gt;&lt;carpet&gt;&lt;id&gt;2&lt;/id&gt;&lt;name&gt;2&lt;/name&gt;&lt;height&gt;unknown&lt;/height&gt;&lt;/carpet&gt;&lt;/things&gt; </code></pre> <p>Is that possible in a quick and efficient way? I'd like not to use any get function (getElementsByTagName(), getElementById, ...), if possible and if more efficient.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShakre
    1. USbrunoais
    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. PODOM navigation: eliminating the text nodes
      1. UStaudorf
      1. VTFavorite
    2. VO
      singulars
      1. PODOM navigation: eliminating the text nodes
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODOM navigation: eliminating the text nodes
      1. This table or related slice is empty.
      1. VTUpMod
    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.

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