StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13082002
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-26T06:39:29.223
FavoriteCount
0
LastActivityDate
2012-11-01T19:32:29.793
LastEditDate
2012-11-01T19:32:29.793
LastEditorUserId
136476
OwnerUserId
136476
ParentId
13081035
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
My advise would be to use something else than XML. Note that I don't have anything against XML in general; just want make that clear, since there are quite a few people out there who feel XML is not good for anything at all. Here are some of the anticipated consequences of using XML in this case: Lookup times It would make jumping to specific positions in your text always expensive. XML would offer you two ways to do it: <ol> <li>Read the entire document in a streaming way until you hit the fragment that you were looking for. Very slow.</li> <li>Read the entire document into an in-memory data structure, which would allow you to create an in memory index from some sort of location identifier to the actual text fragment. Very expensive in terms of memory consumption.</li> </ol> Compactness Turning the entire bible into an XML file would make it HUGE. Of course there solutions such as <a href="http://en.wikipedia.org/wiki/Fast_Infoset" rel="nofollow">Fast Infoset</a> and <a href="http://www.w3.org/XML/EXI/" rel="nofollow">Efficient XML</a> (both binary encodings of <a href="http://www.w3.org/TR/xml-infoset/" rel="nofollow">Infoset</a>, the data model behind XML). That would help a little, but perhaps not a lot. Gzip would probably reduce to approx. 1/3 of the original size, which again would help, but it would still be big. What to do instead? My advise would be to consider a binary encoding of your bible text; one that is optimized for fast lookups. Like, having an index inside the file, mapping the location (a verse) to the offset where that actual text fragment starts. And if you do it properly, there is even the bonus of having something that is way more compact than XML. Harder? It sounds much harder, but in reality, it might not. You might also consider looking at <a href="http://preon.github.com/" rel="nofollow">Preon</a>, since Preon has been used on Android as well, and allows you to declaratively map an in memory data structure into its binary encoded representation. The framework itself will figure out if there is an opportunity to load data lazily, from the input file.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to parse the Bible in Android
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWilfred Springer
UserOwnerUserId
1. USWilfred Springer
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.