Just a quick addition: you actually have something in between an
owned and unowned one-to-many
because you're holding on to object references to your many.
The unowned one-to-many would use Set childrenKeys, for example.
On Jun 6, 2:38 am, mscwd01 wrote:
> To add to my last comment I could do:
To add to my last comment I could do:
pm.deletePersistentAll(children)
to delete all Child objects in the Parents children Set, however as
the method deletePersistentAll has a void return type how do you
ensure all Child objects have been deleted before I delete the Parent
entity?
On Jun 6, 10:1
Thanks for the replies.
@Didier - I have considered this, and I guess I will have to manually
delete each entity if I cant find a more elegant solution, however
going by what the documentation says it should just work. I'd like to
find out why this exception is occurring if possible.
@Nichole - I
You might want to use @Persistent(mappedBy = "parent") for your Parent
entity declaration in your Child entity.
Owned one-to-many
http://code.google.com/appengine/docs/java/datastore/jdo/relationships.html#Owned_One_to_Many_Relationships
On Jun 5, 9:27 pm, Didier Durand wrote:
> Hi,
>
> As a wor
Hi,
As a workaround, why don't you delete each entity in the set in a loop
by yourself before deleting the entity which the set is part of ?
regards
didier
On Jun 6, 1:48 am, mscwd01 wrote:
> Hey,
>
> I have a "parent" entity which has a Set of "child" entities, as
> follows:
>
> class Parent
