imho it should not be a normal operation, a delete should be refused (with a clear error message) if it would leave orphans. Cascade deletes should only be available to dba / super-users. But then I don't think that raw add/update/delete should ever be exposed to end-user applications, you should write rock solid SP's for all user functions which /are/ exposed. You are then protected from clever or malicious users who find a way around the UI - they can still do that but you have the checking in the SP. Others may disagree <vbg> AndyD 8-)?
On 28/02/2012 20:22, Eurico Chagas Filho wrote: > Your opinion sirs... > > Should CASCADE delete be enforced within the database or in my code ? > > E. > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
