Thank you, Andy, for this information!
I have upgraded to DataNucleus plugin 2.0.0-RC2 which solves the issue in
my development environment. Can I use this version (RC2) in the GAE
production environment as well? Can I use the same deployment procedure
from within Eclipse as with the DataNucleus p
@Rick,
JDO doesn't encourage you to do anything, nor impose it. Perhaps its
just that some will, upon using it, think in a particular way because
they used a similar API before, and they're used to their "good old"
RDBMS handling things for them so assume the same is true ... and it
isn't as you s
Many thanks, Andy, for the clarification.
I am still not sure which of the following statements describes the best
the behaviour I observe: it is (a) the intended behaviour, (b) not
intended, just happens to be like this or (c) a bug.
After regarding cache level: reading fleetingly through the JD
Many thanks, Rick, for bringing to my attention these apparently useful
alternatives! I hopefully will find time to try them.
Thanks,
Peter
On Mon, Jan 2, 2012 at 9:00 PM, Rick Mangi wrote:
> Do yourself a big favor and run away from JDO + GAE screaming as fast
> as you can. You're much better
Perhaps I am thinking of JDO and JPA as being more similar than I
should, but I've found that GAE doesn't really want you to think of
your datastore in an OO manner either. It's a collection of documents
and indexes. JDO (and JPA) encourage you to model your objects as you
would in any sane system
As for the problem of the original poster, evictAll is for the
*Level1* cache (which will not be of any use since you aren't using
transactions there). Calling addLabels is queued (doesn't go straight
to the DB in the version you use there), and you don't then start a
transaction. Simple thing to d
> JDO was designed for relational data models, GAE was designed for the
> opposite.
Please check your facts, perhaps by consulting people who actually
designed the JDO standard, or by actually reading the JDO spec. It was
designed to be datastore-agnostic. JPA on the other hand was not, with
RDBMS
Do yourself a big favor and run away from JDO + GAE screaming as fast
as you can. You're much better off using one of the thin wrappers
around the AppEngine Datastore like Objectify or Twig along with the
built in Memcache service.
JDO was designed for relational data models, GAE was designed for
