Bugs item #1056004, was opened at 2004-10-28 13:42 Message generated for change (Settings changed) made by loubyansky You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1056004&group_id=22866
Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Vladimir Stefanyuk (kletchatey) >Assigned to: Alexey Loubyansky (loubyansky) Summary: batch-cascade-delete problem Initial Comment: I have 4 entities: Client Project Order OrderLine Order has a NOT-NULL foregin key reference to Client. Order has a NULL-ABLE foreign key reference to Project. OrderLine has NOT-NULL foreign key reference to Order. Between Order and Client, Order and Project, OrderLine and Order are 1:M relations. For OrderLine-Order relation <cascade-delete/> is specified in ejb-jar.xml. To prevent from UDATING to NULL orderId in OrderLine, <batch-cascade-delete/> is specified in jbosscmp- jdbc.xml. The problem is, that when Order is deleted, an attempt is made to UPDATE Order NOT-NULL foreign keys to NULL values. In case if <batch-cascade-delete/> is not specified this problem doesn't appear, but of course problem with updating OrderLine orderId field appear. Note: This updating is doing only for foreign-keys that contains NOT-NULL values. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1056004&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development