Hi David and Matthew,
Thanks for the response. Regarding the design issues, I agree that it is
a Java problem. In jdo this problem becomes more evident. If I want to
delete an object in java, I need to set all references to null. In JDO I
need to set all references to null and actually delete
Hi,
I have a question regarding delete by query. In the JDO 2.0 spec 14.8 it
says:
...These methods delete the instances of affected classes that pass the
filter, and all dependent
instances To me it is not really clear what should be done in case
such instance contains a List attribute.
Hi David,
thanks for the reply! That would make sense to me as well. I indeed want
the entries in the PAGE table to remain there. I also thought there
should be no need in the .orm file to specify anything specific (like a
cascade delete) in order to have the corresponding entries in BOOK_PAGE
