StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3449768
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-10T14:02:47.697
FavoriteCount
0
LastActivityDate
2010-08-10T19:54:56.293
LastEditDate
2010-08-10T19:54:56.293
LastEditorUserId
70604
OwnerUserId
416206
ParentId
3444449
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
As you have found, you can disable the shared cache, see <a href="http://wiki.eclipse.org/EclipseLink/Examples/JPA/Caching" rel="noreferrer">http://wiki.eclipse.org/EclipseLink/Examples/JPA/Caching</a> or <a href="http://wiki.eclipse.org/EclipseLink/FAQ/How_to_disable_the_shared_cache%3F" rel="noreferrer">http://wiki.eclipse.org/EclipseLink/FAQ/How_to_disable_the_shared_cache%3F</a> There are also other options available in EclipseLink depending on your data and requirements. A list of option include: <ol> <li>Disable shared cache</li> <li>Enable cache coordination (see, <a href="http://www.eclipse.org/eclipselink/api/2.1/org/eclipse/persistence/config/PersistenceUnitProperties.html#COORDINATION_PROTOCOL" rel="noreferrer">http://www.eclipse.org/eclipselink/api/2.1/org/eclipse/persistence/config/PersistenceUnitProperties.html#COORDINATION_PROTOCOL</a>)</li> <li>Set a cache invalidation timeout (see, <a href="http://www.eclipse.org/eclipselink/api/2.1/org/eclipse/persistence/annotations/Cache.html#expiry%28%29" rel="noreferrer">http://www.eclipse.org/eclipselink/api/2.1/org/eclipse/persistence/annotations/Cache.html#expiry%28%29</a>)</li> <li>Enable optimistic locking, this will ensure that any stale object cannot be updated, when an update on stale data occurs it will fail, and EclipseLink will automatically invalidate the object in the cache.</li> <li>Investigate the Oracle TopLink integration of EclipseLink and Oracle Coherence to provide a distributed cache.</li> </ol> See also, <a href="http://en.wikibooks.org/wiki/Java_Persistence/Caching#Caching_in_a_Cluster" rel="noreferrer">http://en.wikibooks.org/wiki/Java_Persistence/Caching#Caching_in_a_Cluster</a> There is no perfect solution, the solution used normally depend on the data/class, normally an application has a set of read-only classes, read-mostly classes and write mostly classes. Personally I would enable the cache for the read-only with a 1 day timeout, enable the cache with cache coordination for the read-mostly, and disable the cache for the write mostly.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJPA with Multiple Servers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPascal Thivent
UserOwnerUserId
1. USJames
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJPA with Multiple Servers
 singulars
 PostTypePostTypeId
 PTQuestion
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.