Xavier CAMIER wrote : > >Good morning, > >Here starts the second part of my trigger tale. I have to manage datas >and I want it to be done by MaxDB. Here is a scheme of what I >want to do > >----> > > --------------- -------------- > | 'A' Storage | -- | 'C' Storage | ... > / -------------- -------------- >-------------- / >| Component | --------------- >-------------- \ | 'D' Storage | ... > \ -------------- / -------------- > | 'B' Storage | / > -------------- \ -------------- > \ | 'E' Storage >| ... > -------------- > > >* There is a trigger on the update event of the Component table >* There is a trigger on the update event of the Storage table >* A component is updated ==> the Component_Trigger updates 'A' Storage >and 'B' Storage. As there's a trigger on the Storage table, >'A' Storage >updates 'C' Storage and 'B' Storage updates 'D' and 'E' Storage. > >There is no infinite loop but MaxDB returns an generic error when >updating Component (it works when I disable the Storage_Trigger). The >MaxDB doc says that one of the reasons of an update statement >failure is >the failure of the trigger. That's seems beeing what's happening. > >The question are : is cascade triggering forbidden ? Are triggers >threaded or queued ? if cascade triggering is not forbidden, >where could >be my mistake ? > >Thanks for having read that long post. >Best regards, Xavier. > >--
Cascade triggering is not forbidden. Internally these cascading requests are queued. It therefore would be very interesting to know the sql error code which has been returned by the trigger. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
