Level2 cache might be what you want, but anyway, just to add to the
dialog, I tinkered
with what's available in datanucleus-core v1.1.5.
Choices in datanucleus are: none, soft, and weak
(jcache is not available in any version, but see below for
customization)
In addition to those, one can make a
Thanks for your help. I'll go with Ian's suggestion, storing arrays in the
memcache.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
use the level 2 cache?
property name=datanucleus.cache.level2.type value=javax.cache /
Objects are placed in the L2 cache when you commit() the transaction
of a PersistenceManager. This means that you only have datastore-
persisted objects in that cache. Also, if an object is deleted during
a
Hi Christian,
If Nichole's tip doesn't help you, then for your list view, you could
back it up with an array (in memcache?). Upon any create, edit, delete
operation, you will have to test the relevant entity (using logic
equivalent to your query) to see whether its entry in the array should
be
Hi Ian,
Thanks for sharing your strategy.. I am not sure if I understand exactly how
could I use your system to solve my problem. Actually, the memcache concept
is working nice solving similar, but simpler situations. I think I explained
poorly my situation. Here it is:
An application manages
