[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-29 Thread boustanihani
This enhanced version works... I encourage you to use Keys as Encoded Strings so u may use the same EntityClasses also on the client side :) According to: http://code.google.com/intl/de-DE/appengine/docs/java/datastore/creatinggettinganddeletingdata.html#Keys If the app creates a new object and

[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-29 Thread boustanihani
P.S. no need to reinitialize the PersistenceManager ... you may delete this line = pm = PMF.get().getPersistenceManager(); I would be glad to hear your feedback ... -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this

[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-29 Thread datanucleus
Your Problem is due to a bug in DataNucleus described at No. That is a bug in Google's plugin, since that is their issue tracker you refer to. DataNucleus current version is at version 2.1, whereas what you use there is v 1.1.x -- You received this message because you are subscribed to the

[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-29 Thread boustanihani
Yes, I should have been more accurate :) ... Do you know when this will be fixed and what the best workaround is ? -- 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

[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-28 Thread boustanihani
Your Problem is due to a bug in DataNucleus described at: http://code.google.com/p/datanucleus-appengine/issues/detail?id=89 Summary = Updating children does not work for the moment! This will be fixed in DataNucleus Release-1.1.0 ... The current version is 1.0.4.1 RC2 ... So I hope it will be

[appengine-java] Re: Owned one to many relationship problem when parent was already existed.

2010-04-28 Thread ylmz
That was very helpful. Thank you for your answer. Now I can implement this without relationships until this bug is solved. On Apr 28, 12:42 pm, boustanihani boustanih...@googlemail.com wrote: Your Problem is due to a bug in DataNucleus described

[appengine-java] Re: owned one to many relationship problem

2010-04-27 Thread ylmz
unfortunately I still am having problem. if parent is already persisted it does not work. I have a different post for that one. http://groups.google.com/group/google-appengine-java/browse_thread/thread/a9955f8944a8c520 On Apr 19, 12:27 am, ylmz yilmazhuse...@gmail.com wrote: Hi every body. I

[appengine-java] Re: owned one to many relationship problem

2010-04-22 Thread Ian Marshall
Excellent. -- 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

[appengine-java] Re: owned one to many relationship problem

2010-04-19 Thread Ian Marshall
Because A is the entity group parent of B, the key of an instance of B must contain information about its entity group parent instance of A. Instead of using b.key.getId() in // We cannot retrieve this object. Why? B newB = pm.getObjectById(B.class,b.key.getId()); you might care to use the