What happens if you change @Persistent to @Persistent(defaultFetchGroup =
true)
?
Tito George wrote:
Enviornment: Local
I have a Text field in one Persistent capable object,
@Persistent
private com.google.appengine.api.datastore.Text event_Description;
I am sure that i am not setting
Great, thanks. I added it to the correct one this time, with your comments.
datanucleus wrote:
Make sure it's on this issue tracker
http://code.google.com/p/datanucleus-appengine/issues/list
(for the plugin), rather than the main one for GAE/J.
You could also mention that
Maybe he forgot to precede it with the usual if
(em.getTransaction().isActive())?
David Fuelling wrote:
Hi Max,
I asked this question in the comments of your blog post, but I'll post
it here as well for the group folks:
Why is the transaction rolled-back at the end of the each
Ok, thanks. No need to get defensive; I wasn't blaming detachAllOnCommit or
DataNucleus, which is why I posted the question here rather than the
DataNucleus forums.
I'll add an issue to the googleappengine Issue Tracker about this.
datanucleus wrote:
So ask the question (of Google) why is
I'm trying to figure out the best way to manage root objects that are used with
different objects. For a semi concrete example, suppose you have a web page
with a drop down list of Favorite Foods, and a User object may have a reference
to a FavoriteFood, and other objects will have references
in the datastore.
2009/11/1 Rusty Wright rwright.li...@gmail.com
mailto:rwright.li...@gmail.com
I'm trying to figure out the best way to manage root objects that
are used with different objects. For a semi concrete example,
suppose you have a web page with a drop down list
1) In the case of result.isEmpty(), I don't see where you're adding the new
UserStats to the result list.
2) When you do pm.makePersistent( stats ) I think you're going to have a
problem adding the new stats to the ListUserStats, because that
makePersistent is going make a new stats a
Whoops, sorry; ignore my remark about UserStats not being persistable; I looked
again at your code and saw that it has a key. I was confused and thinking that
you're persisting the List, not an item in the List. But I think the problem
with it becoming a root object still remains.
Rusty
Any suggestions for how to fix this problem? I get the following stack trace
when I use makePersistent() on a class. It goes away if I add serialized to
one of its field's annotation; i.e., change the annotation from
@Persistent(defaultFetchGroup = true, mappedBy = facility)
private
Whoops; my mistake. I had been looking at the DataNucleus documentation rather
than the Google and I was using an unsupported Calendar when I should have been
using a Date.
Rusty Wright wrote:
Any suggestions for how to fix this problem? I get the following stack
trace when I use
Ok, thanks. That is helpful to know.
leszek wrote:
I ported my Open Source EJB3/JPA application to Google App Engine many
months ago and almost at the beginning it was obvious that I had to
split my entity classes to two versions: Google App Engine and non
Google App Engine. Impossible to
I've come up with a solution to my problems with data store integration tests.
I don't know if this is a good solution; feedback is welcome.
The problem, as much as my feeble brain can grasp, is that when Spring provides
you with a PersistenceManager, you need to use transactions so that, at
The name initially confused me because it made me think of
http://www.opends.org/
Nacho Coloma wrote:
Hi all,
We have been developing a persistence framework for the AppEngine
Datastore based on the raw DatastoreService API. For our (simple)
persistence case, both JDO and JPA were a
Peter, it was gratifying to hear you say detach/attach is also problematic
when dealing with caching and transactions because I've been banging my head
against the wall trying to write integration tests with GAE's datastore, using
JDO and Spring's transactions.
I either get the is managed by
:21 AM, Rusty Wright rwright.li...@gmail.com
mailto:rwright.li...@gmail.com wrote:
Here's my code; the first call on the persistence manager,
getObjectsById (note plural Objects) fails. But then later down it
iterates over the Keys and that succeeds. The log output is below
101 - 115 of 115 matches
Mail list logo
