StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17229069
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-21T06:37:01.717
FavoriteCount
0
LastActivityDate
2013-06-21T06:53:44.527
LastEditDate
2013-06-21T06:53:44.527
LastEditorUserId
128421
OwnerUserId
128421
ParentId
17194043
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> <p>...I've noticed that Firebug produces some xpath expressions that don't work well with Nokogiri (or its dependency). I'm having better luck with Chrome's Debug XPath output.</p> </blockquote> <p>The problem with Firebug, or many other XPath outputs from a browser, is they follow the HTML spec when generating the XPath and synthesize a <code><tbody></code> tag, even if the original source doesn't have one. The XPath reflects that. </p> <p>We pass the raw HTML to Nokogiri for parsing, along with the erroneous XPath, and Nokogiri can't find the <code><table><tbody><tr></code> chain. </p> <p>Here's a for instance. Starting with this HTML:</p> <pre><code><html> <body> <table> <tr> <td> foo </td> </tr> </table> </body> </html> </code></pre> <p>Save it to a file and open it in Firefox, Chrome or Safari, then view the source, and look at it in Firebug or its equivalent.</p> <p>You'll see something like this, which came from Firefox:</p> <pre><code><table> <tbody><tr> <td> foo </td> </tr> </tbody></table> </code></pre> <p>To fix this, don't rely on the XPath generated by the browser, and confirm the table's structure by looking at only the <em>RAW</em> HTML in a text editor. The "view source" option is useful for some things, but if you see any <code><tbody></code> tags be suspicious and revert to checking with the editor.</p> <p>Also, you don't need the entire chain of tags to reach an inner tag. Instead, look for some landmarks along the way that will help you find your target node(s). Most HTML pages these days have <code>class</code> and <code>id</code> parameters in important tags. ID parameters in particular are great because they have to be unique. If other parameters exist that are unique, those can work too. </p> <p>Sometimes you won't find an identifying tag immediately prior to the one you want, but there is something embedded in it. Then, locate that embedded tag and step up the chain until you find what you want. Using XPath you can use the <code>..</code> (parent), but with CSS you have to rely on Nokogiri::XML::Node's <code>parent</code> method because Nokogiri and CSS don't support a selector for the parent (yet).</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to parse inner_html inside for loop using XPath with nokogiri
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USthe Tin Man
UserOwnerUserId
1. USthe Tin Man
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
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.