Closed GoogleCodeExporter closed 8 years ago
Somebody!!!
I really need your help.
Thanks.
Original comment by kanic.a...@gmail.com
on 13 Aug 2010 at 11:57
A few things:
1) Does this ever happen locally?
2) Looking at the output of the log line isn't a good indication of whether or
not the child object is being saved since sometimes the child gets flushed
immediately and sometimes it gets flushed when the pm is closed. You can only
count on objects being persistent after you've closed the pm (or after you've
committed the txn, if you're using txns). Do you have some other indication
that the child object is not being saved?
3) The call to pm.makePersistent(dbOffer) isn't necessary - the object is
already persistent and all changes to that object should be "seen" by the
datastore.
4) You should really be using a list-ordering on your 1-Many relationships:
http://code.google.com/appengine/docs/java/datastore/relationships.html#Owned_On
e_to_Many_Relationships
Original comment by max.r...@gmail.com
on 16 Aug 2010 at 7:32
Max, many thanks.
My comments below:
1) Does this ever happen locally?
No, I can not reproduce this issue on my locally machine.
2) Do you have some other indication that the child object is not being saved?
Yes. We not see new child object in Datastore Viewer.
3) The call to pm.makePersistent(dbOffer) isn't necessary.
Thanks. I not catch this information.
4) You should really be using a list-ordering on your 1-Many relationships.
Ok. I will try to test this case. But in really we are not in need of ordering.
5) What SDK you are using?
We started with SDK 1.3.1. But now we are using SDK 1.3.5 with datanucleus
version 1.0.7
Original comment by kanic.a...@gmail.com
on 17 Aug 2010 at 3:55
gracias por el aporte, me sirvió de mucho. gracias por el ejemplo 1:N
Original comment by d...@aconsultores.com.mx
on 28 Jul 2011 at 3:45
Original comment by googleco...@yahoo.co.uk
on 21 Sep 2011 at 3:51
Can't reproduce this. Provide a testcase that demonstrates something and it
could be moved forward
Original comment by googleco...@yahoo.co.uk
on 1 Nov 2011 at 4:18
Original issue reported on code.google.com by
kanic.a...@gmail.com
on 11 Aug 2010 at 12:08