Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I see a few possible problems. First of all, this:</p> <pre><code>@doc = Nokogiri::XML(sympFile) </code></pre> <p>will slurp the whole XML file into memory as some sort of libxml2 data structure and that will probably be larger than the raw XML file.</p> <p>Then you do things like this:</p> <pre><code>@doc.xpath(...).each </code></pre> <p>That may not be smart enough to produce an enumerator that just maintains a pointer to the internal form of the XML, it might be producing a copy of everything when it builds the <code>NodeSet</code> that <code>xpath</code> returns. That would give you another copy of most of the expanded-in-memory version of the XML. I'm not sure how much copying and array construction happens here but there is room for a fair bit of memory and CPU overhead even if it doesn't copy duplicate everything.</p> <p>Then you make your copy of what you're interested in:</p> <pre><code>symptomsList.push([signId, name]) </code></pre> <p>and finally iterate over that array:</p> <pre><code>symptomsList.each do |x| Symptom.where(:name =&gt; x[1], :signid =&gt; Integer(x[0])).first_or_create end </code></pre> <p>I find that <a href="http://nokogiri.org/Nokogiri/HTML/SAX.html" rel="nofollow">SAX parsers</a> work better with large data sets but they are more cumbersome to work with. You could try creating your own SAX parser something like this:</p> <pre><code>class D &lt; Nokogiri::XML::SAX::Document def start_element(name, attrs = [ ]) if(name == 'DisorderSign') @data = { } elsif(name == 'ClinicalSign') @key = :sign @data[@key] = '' elsif(name == 'SignFreq') @key = :freq @data[@key] = '' elsif(name == 'Name') @in_name = true end end def characters(str) @data[@key] += str if(@key &amp;&amp; @in_name) end def end_element(name, attrs = [ ]) if(name == 'DisorderSign') # Dump @data into the database here. @data = nil elsif(name == 'ClinicalSign') @key = nil elsif(name == 'SignFreq') @key = nil elsif(name == 'Name') @in_name = false end end end </code></pre> <p>The structure should be pretty clear: you watch for the opening of the elements that you're interested in and do a bit of bookkeeping set up when the do, then cache the strings if you're inside an element you care about, and finally clean up and process the data as the elements close. You're database work would replace the</p> <pre><code># Dump @data into the database here. </code></pre> <p>comment.</p> <p>This structure makes it pretty easy to watch for the <code>&lt;Disorder id="17601"&gt;</code> elements so that you can keep track of how far you've gone. That way you can stop and restart the import with some small modifications to your script.</p>
    singulars
    1. This table or related slice is empty.
    1. POParsing Large XML with Nokogiri
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmu is too short
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POParsing Large XML with Nokogiri
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen I get a moment, I will attempt this and edit this comment with the results.
      singulars
      1. PO
      1. USNight Train
    2. COCheck my response to my original post. While that solved my issue, I do see that a SAX parser makes more sense for a larger a file, and may end up changing it to that anyway, thank you for your effort in trying to help me.
      singulars
      1. PO
      1. USNight Train
    3. COAh, I missed the tree for the forest. You can convert that comment to an answer and accept your own answer (after a 24 hour delay AFAIK).
      singulars
      1. PO
      1. USmu is too short
 

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