Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My experience of <code>XmlReader</code> is that it's very easy to accidentally read too much. I know you've said you want to read it as quickly as possible, but have you <em>tried</em> using a DOM model instead? I've found that LINQ to XML makes XML work much <em>much</em> easier.</p> <p>If your document is particularly huge, you can combine <code>XmlReader</code> and LINQ to XML by creating an <code>XElement</code> from an <code>XmlReader</code> for each of your "outer" elements in a streaming manner: this lets you do most of the conversion work in LINQ to XML, but still only need a small portion of the document in memory at any one time. Here's some sample code (adapted slightly from <a href="http://blogs.msdn.com/xmlteam/archive/2007/03/24/streaming-with-linq-to-xml-part-2.aspx" rel="noreferrer">this blog post</a>):</p> <pre><code>static IEnumerable&lt;XElement&gt; SimpleStreamAxis(string inputUrl, string elementName) { using (XmlReader reader = XmlReader.Create(inputUrl)) { reader.MoveToContent(); while (reader.Read()) { if (reader.NodeType == XmlNodeType.Element) { if (reader.Name == elementName) { XElement el = XNode.ReadFrom(reader) as XElement; if (el != null) { yield return el; } } } } } } </code></pre> <p>I've used this to convert the StackOverflow user data (which is enormous) into another format before - it works very well.</p> <p>EDIT from radarbob, reformatted by Jon - although it's not quite clear which "read too far" problem is being referred to...</p> <p>This should simplify the nesting and take care of the "a read too far" problem.</p> <pre><code>using (XmlReader reader = XmlReader.Create(inputUrl)) { reader.ReadStartElement("theRootElement"); while (reader.Name == "TheNodeIWant") { XElement el = (XElement) XNode.ReadFrom(reader); } reader.ReadEndElement(); } </code></pre> <p>This takes care of "a read too far" problem because it implements the classic while loop pattern:</p> <pre><code>initial read; (while "we're not at the end") { do stuff; read; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POReading Xml with XmlReader in C#
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsdgfsdh
    1. USJon Skeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReading Xml with XmlReader in C#
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCalling XNode.ReadFrom reads the element and goes to the next one, then the following reader.Read() reads the next one again. You'd essentially miss an element if they happen to have the same name and be consecutive.
      singulars
      1. PO
      1. USpbz
    2. CO@pbz: Thanks. I'm not sure I trust myself to edit it correctly (that's how much I dislike XmlReader :) Are you able to edit it correctly?
      singulars
      1. PO
      1. USJon Skeet
    3. CO@Jon: :-) I ended up doing something like Paul Alexander (below) recommended. Using a label (yuk) and making it jump to the first instruction in the "while" loop, and thus skipping an extra "read" "should" work, I think :-)
      singulars
      1. PO
      1. USpbz
 

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