StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POStoring XML Files in Database
primarykey
Id
4216478
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-18T15:30:32.007
FavoriteCount
0
LastActivityDate
2010-11-18T17:07:23.977
LastEditDate
LastEditorUserId
0
OwnerUserId
145354
ParentId
0
PostTypeId
1
Score
0
ViewCount
1500
LastEditorDisplayName
text
Body
I have to create a desktop application in Java 6. Program should be able to communicate with other system using XML files (sending/receiving). Every single XML file is connected with its XSD, tags describing its content, username and status of the document. Application should provide such functionality as searching, modyfying etc. XML content. The question is: how should I store all these information retaining logical connections? I came up with an idea to store it using XML database - BaseX. In other words, storing XML files with information connected to them in one big XML (database) file. Sample database: <code><?XML VERSION="1.0"?></code> <code><mySampleRecord id="1"></code> <code><XMLcontent> // Content of XML file (...) </XMLcontent></code> <code><XMLschema> // Content of XSD file (...) </XMLschema></code> <code><tags>j2ee java xml</tags></code> <code><username>File Owner</username></code> <code><status>received</status></code> <code></mySampleRecord></code> <code><mySampleRecord id="2"></code> <code><XMLcontent> // Content of XML file (...) </XMLcontent></code> <code><XMLschema> // Content of XSD file (...) </XMLschema></code> <code><tags>doc xls mdb</tags></code> <code><username>Admin</username></code> <code><status>sent</status></code> <code></mySampleRecord></code> I was also wondering if it's possible BaseX to read <code><XMLContent></code> node and then treat its content as XML enabling me to perform XQuery operations. Hope its understandable ;) Thanks for any hints and suggestions.
Tags
<java><xml><database><xml-database>
Title
Storing XML Files in Database
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmonczek
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.