OK, but why would this behavior be happening inconsistently across his
(and probably others) application?
On Sep 5, 7:06 pm, Max Ross maxr+appeng...@google.com wrote:
Key is not in the default fetch group because it is an appengine-specific
class. The JDO spec doesn't know anything about app
I think it makes sense now. I did see more exceptions related to
incorrect transaction handling (e.g. updating multiple entities from
different entity groups) that didn't happen prior to 1.2.5. It seems
that it was the upgrade to datanucleus 1.1.5 that triggered these
exceptions. I am not
Key is not in the default fetch group because it is an appengine-specific
class. The JDO spec doesn't know anything about app engine so there's no
way that Key could be included in the list of types that are automatically
included in the default fetch group.
Max
On Fri, Sep 4, 2009 at 1:32 PM,
Just so you know, I think I have solved the problem by setting
defaultFetchGroup=true on the Key property:
@Persistent(defaultFetchGroup=true)
private Key text;
Might have something to do with the recently closed issue #58 Queries
don't respect fetch groups:
