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 c
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
https://groups.google.com/d/msg/google-appengine-java/-
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 add
use the level 2 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 transaction then at commit it will be removed from the L2 cache i
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
Hi Cristian,
If I am correct (and I could be wrong), you want to update more than
one entity group in the datastore by performing a set of sequential
writes to the datastore. You may then want to read from the datastore.
The writes and subsequent read are to be delayed so that the datastore
write/
