Should I use the CASCADE DELETE rule? [duplicate]

by

ON DELETE CASCADE is fine, but only when the dependent rows are really a logical extension of the row being deleted. For example, it’s OK for DELETE ORDERS to delete the associated ORDER_LINES because clearly you want to delete this order, which consists of a header and some lines. On the other hand, DELETE CUSTOMER should not delete the associated ORDERS because ORDERS are important in their own right, they are not just attributes of a customer.

One way to think about this is: if I issue DELETE X and it also deletes Y, will I be happy or unhappy? And if I issue DELETE X and am told “cannot delete X because Y exists” will I be glad of the protection, or irritated at the inconvenience?

More Related Contents:

  1. SQL Server: drop table cascade equivalent?
  2. How can I list all foreign keys referencing a given table in SQL Server?
  3. SQL query to select dates between two dates
  4. What is the benefit of using “SET XACT_ABORT ON” in a stored procedure?
  5. is there an advantage to varchar(500) over varchar(8000)?
  6. Split function equivalent in T-SQL?
  7. How to find all connected subgraphs of an undirected graph
  8. SQL query to split column data into rows
  9. Calculating number of full months between two dates in SQL
  10. How to drop SQL default constraint without knowing its name?
  11. Replacing NULL with 0 in a SQL server query
  12. Is it possible to delete from multiple tables in the same SQL statement?
  13. Months between two dates
  14. Dynamic update statement with variable column names
  15. Why can’t I use alias in a count(*) “column” and reference it in a having clause?
  16. How to return the output of stored procedure into a variable in sql server
  17. A way to extract from a DateTime value data without seconds
  18. How to select only the first rows for each unique value of a column?
  19. SQL Server (TSQL) – Is it possible to EXEC statements in parallel?
  20. How to find third or nᵗʰ maximum salary from salary table?
  21. Difference of two date time in sql server
  22. Modify Default value in SQL Server
  23. Unordered results in SQL
  24. Using PIVOT in SQL Server 2008
  25. Produce DISTINCT values in STRING_AGG
  26. sql group by only rows which are in sequence
  27. Function in SQL Server 2008 similar to GREATEST in mysql?
  28. ORDER BY items must appear in the select list if SELECT DISTINCT is specified
  29. Query times out from web app but runs fine from management studio
  30. How do I compare 2 rows from the same table (SQL Server)?

Leave a Comment