[appengine-java] Re: JPA Entities Queried Outside Transaction Carried Into Next Transaction

2010-01-26 Thread datanucleus
When running in non-tx mode objects will be put in the L1 cache, yes,
since you are in non-tx mode. All other DN supported datastores don't
have any issue with objects being reused, so that is a problem for GAE/
J. If you wanted to remove them from the L1 cache (to attempt to get
around their problem) then call pm.evictAll(...).

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.



[appengine-java] Re: JPA Entities Queried Outside Transaction Carried Into Next Transaction

2010-01-26 Thread lent
Thanks Andy for your quick response.  I'm using JPA (as mentioned in
the title) so I used the equivalent of pm.evictAll in JPA which I
think is entityManager.clear and it did the trick.  The entities were
removed from the level 1 cache and the following transaction had no
problems.

Thanks,
Len

On Jan 26, 7:55 am, datanucleus andy_jeffer...@yahoo.com wrote:
 When running in non-tx mode objects will be put in the L1 cache, yes,
 since you are in non-tx mode. All other DN supported datastores don't
 have any issue with objects being reused, so that is a problem for GAE/
 J. If you wanted to remove them from the L1 cache (to attempt to get
 around their problem) then call pm.evictAll(...).

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.