StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
729979
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-04-08T13:22:58.577
FavoriteCount
0
LastActivityDate
2011-11-08T10:20:31.233
LastEditDate
2017-05-23T10:31:20.830
LastEditorUserId
-1
OwnerUserId
56285
ParentId
729621
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
For what it's worth, here's a solution I came up with using the <a href="http://dom4j.sourceforge.net/" rel="nofollow noreferrer">dom4j</a> library. (I did check that it works.) Read the XML fragment into a <code>org.dom4j.Document</code> (note: all the XML classes used below are from org.dom4j; see Appendix): <pre><code> String newNode = "<node>value</node>"; // Convert this to XML SAXReader reader = new SAXReader(); Document newNodeDocument = reader.read(new StringReader(newNode)); </code></pre> Then get the Document into which the new node is inserted, and the parent Element (to be) from it. (Your org.w3c.dom.Document would need to be converted to org.dom4j.Document here.) For testing purposes, I created one like this: <pre><code> Document originalDoc = new SAXReader().read(new StringReader("<root><given></given></root>")); Element givenNode = originalDoc.getRootElement().element("given"); </code></pre> Adding the new child element is very simple: <pre><code> givenNode.add(newNodeDocument.getRootElement()); </code></pre> Done. Outputting <code>originalDoc</code> now yields: <pre><code><?xml version="1.0" encoding="utf-8"?> <root> <given> <node>value</node> </given> </root> </code></pre> Appendix: Because your question talks about <code>org.w3c.dom.Document</code>, here's how to convert between that and <code>org.dom4j.Document</code>. <pre><code>// dom4j -> w3c DOMWriter writer = new DOMWriter(); org.w3c.dom.Document w3cDoc = writer.write(dom4jDoc); // w3c -> dom4j DOMReader reader = new DOMReader(); Document dom4jDoc = reader.read(w3cDoc); </code></pre> (If you'd need both kind of <code>Document</code>s regularly, it might make sense to put these in neat utility methods, maybe in a class called <code>XMLUtils</code> or something like that.) Maybe there are better ways to do this, even without any 3rd party libraries. But out of the solutions presented so far, in my view this is the easiest way, even if you need to do the dom4j <-> w3c conversions. Update (2011): before adding dom4j dependency to your code, note that <a href="https://stackoverflow.com/questions/831865/what-java-xml-library-do-you-recommend-to-replace-dom4j">it is not an actively maintained project, and has some other problems too</a>. Improved version 2.0 has been in the works for ages, but there's only an alpha version available. You may want to consider an alternative, like XOM, instead; read more in the question linked above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConvert String XML fragment to Document Node in Java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJonik
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. 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.