StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POPersistence Strategy for Standalone Desktop Java Application
primarykey
Id
9515511
data
AcceptedAnswerId
9517392
AnswerCount
3
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-03-01T11:41:04.770
FavoriteCount
1
LastActivityDate
2012-03-02T12:42:33.227
LastEditDate
2017-05-23T10:24:24.453
LastEditorUserId
-1
OwnerUserId
329028
ParentId
0
PostTypeId
1
Score
3
ViewCount
1231
LastEditorDisplayName
text
Body
(Only managed to find one other question on this - <a href="https://stackoverflow.com/questions/393948/object-persistence-strategy-for-desktop-application">Object persistence strategy for desktop application</a>) I have a basic Java Swing application - which needs to access / persist a few thousand POJOs. I may need to run basic queries on these. Originally I looked at JPA-Hibernate + HSQLDB, but this slows app start-up time and I figured it was overkill for my query requirements. I simplified my data model and started looking at Document DBs - mongodb is great but it isnt really suited for non-server environments; starting up and shutting down the mongod process from Java (using ProcessBuilder) is fiddly and I really want an embedded solution. I really want a fast, lightweight persistence tool with basic query functions that can be embedded in a Java app. Are these the only options? <ul> <li><a href="http://prevayler.org/" rel="nofollow noreferrer">http://prevayler.org/</a></li> <li>Java Embedded Database (HSQL) without ORM</li> <li>Java Serialization to filesystem</li> <li>JSON persisted to flat files?</li> <li>XStream (and XBird? - <a href="http://code.google.com/p/xbird/" rel="nofollow noreferrer">http://code.google.com/p/xbird/</a>)</li> <li>OODB</li> <li>JCR Implementation ?</li> </ul> Can anyone offer any other advice / suggestions? At what point would serializing a large List of POJO's start to really hurt performance? Thanks edit: Just found this post - <a href="https://stackoverflow.com/questions/2825491/are-there-any-embeddable-document-database-engines-for-java-something-similar-t">https://stackoverflow.com/questions/2825491/are-there-any-embeddable-document-database-engines-for-java-something-similar-t</a> recommending Orient - <a href="http://code.google.com/p/orient/" rel="nofollow noreferrer">http://code.google.com/p/orient/</a>
Tags
<java><swing><persistence>
Title
Persistence Strategy for Standalone Desktop Java Application
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USAndrew B
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
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
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POPersistence Strategy for Standalone Desktop Java Application
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POPersistence Strategy for Standalone Desktop Java Application
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POPersistence Strategy for Standalone Desktop Java Application
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.