According to the spec, the query results may appear in hollow,
persistent-nontransactional, or persistent-clean, at the choice of the
implementation. What state does datanucleus choose?
On Feb 3, 1:01 pm, datanucleus wrote:
> Obviously the state has a general rule; the JDO spec.
> Just that you
Obviously the state has a general rule; the JDO spec.
Just that you can use JDOHelper.getObjectState to tell you what is the
rule, since it follows the spec
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, sen
Thx. Can the state only be determined at runtime, or there is a
general rule? I appreciate if you can let me know whether each match
is retrieved in an independent transaction.
Thx again.
On Feb 2, 12:04 am, datanucleus wrote:
> JDOHelper.getObjectState(obj) ?
--
You received this message beca
JDOHelper.getObjectState(obj) ?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsub
Can anyone help, plz?
On Feb 1, 3:43 pm, Brandon wrote:
> Hi,
>
> I am using JDO. I know that when querying a class of objects residing
> in different entity group, the query should not be executed inside a
> transaction.
>
> So, what are the state of the objects in the query result (persistent
>
