StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5350167
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-18T09:35:36.070
FavoriteCount
0
LastActivityDate
2011-03-18T14:16:59.323
LastEditDate
2011-03-18T14:16:59.323
LastEditorUserId
482623
OwnerUserId
482623
ParentId
4921674
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I have same issue when running my app on emulator Android 2.1. Although for 2.2 it works perfectly. The version of the dom4j lib I am using is v1.6. As you can see from the following extract all attribute names are replaced with the name of the first attribute in my xml file: <pre><code><?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ncx PUBLIC "-//NISO//DTD ncx 2005-1//EN" "http://www.daisy.org/z3986/2005/ncx-2005-1.dtd"><ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1"> <head> <meta version="dtb:uid" version="6efac3c8-0d51-46bd-b125-58dae01bf92e"/> <meta version="dtb:depth" version="4"/> <meta version="dtb:totalPageCount" version="0"/> <meta version="dtb:maxPageNumber" version="0"/> </head> <docTitle> <text>Book</text> </docTitle> <navMap> <navPoint version="navPoint-1" version="1"> <navLabel> <text>Header1</text> </navLabel> <content version="Text/Section0001.xhtml"/> <navPoint version="navPoint-2" version="2"> </code></pre> When the actual xml is : <pre><code><?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ncx PUBLIC "-//NISO//DTD ncx 2005-1//EN" "http://www.daisy.org/z3986/2005/ncx-2005-1.dtd"> <ncx xmlns="http://www.daisy.org/z3986/2005/ncx/" version="2005-1"> <head> <meta name="dtb:uid" content="6efac3c8-0d51-46bd-b125-58dae01bf92e"/> <meta name="dtb:depth" content="4"/> <meta name="dtb:totalPageCount" content="0"/> <meta name="dtb:maxPageNumber" content="0"/> </head> <docTitle> <text>Book</text> </docTitle> <navMap> <navPoint id="navPoint-1" playOrder="1"> <navLabel> <text>Header1</text> </navLabel> <content src="Text/Section0001.xhtml"/> <navPoint id="navPoint-2" playOrder="2"> </code></pre> It seems that xml document is parsed incorrectly. Here is my source code: <pre><code>inputStream = new FileInputStream(ncfPath); SAXReader reader = new SAXReader(); // dom4j SAXReader Document document = reader.read(inputStream); String xml = document.asXML(); </code></pre> Let me know if you have found solution for this issue. EDIT: same issue for the dom4j 2.0 alpha 2 EDIT2: finally I've found a solution. The problem indeed in dom4j source code. Here is the <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=2789052&group_id=16035&atid=116035#" rel="nofollow">link</a> to the issue recorded almost two years(!) ago. To fix it you need correct following method in \dom4j-1.6.1\src\java\org\dom4j\tree\NamespaceStack.java: <pre><code>public QName getAttributeQName(String namespaceURI, String localName, String qualifiedName) { // Fix: qualifiedName is empty on Android 2.1 // refer to https://sourceforge.net/tracker/index.php?func=detail&aid=2789052&group_id=16035&atid=116035# if (qualifiedName == null || qualifiedName.length() == 0) { qualifiedName = localName; } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid 1.5 and dom4j - attributes names parsed incorrectly
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDenys Nikolayenko
UserOwnerUserId
1. USDenys Nikolayenko
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.