Cascading delete for ODMG
-------------------------
Key: OJB-41
URL: http://issues.apache.org/jira/browse/OJB-41
Project: OJB
Type: New Feature
Components: ODMG-API
Reporter: Steve Clark
The docs for the ODMG API have always said that auto-delete must be set to
"false" in order for the ODMG API to work correctly. However, it has always
worked fine to go ahead and set auto-delete="link" or "object", and a cascading
delete configurable at the individual reference level has been unofficially
available.
With the rewrite of the ODMG layer, it appears that this unofficial cascading
delete has been removed, and has been replaced with bizarre and completely
useless solution based on the category of reference, with all 1:1 references
treated same, all 1:n treated the same, and all m:n treated the same. The
impact on our existing codebase is huge, as it requires us to go back and write
a complete OJB-aware cascading delete for every dataobject in our library.
Can we please have the old behavior back?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
