Difference between On Delete Cascade & On Update Cascade in mysql

A very good thread on this subject is to be found here and also here. The definitive guide for MySQL is, of course, the documentation, to be found here.

In the SQL 2003 standard there are 5 different referential actions:

1. CASCADE
2. RESTRICT
3. NO ACTION
4. SET NULL
5. SET DEFAULT

To answer the question:

1. CASCADE

   • ON DELETE CASCADE means that if the parent record is deleted, any child records are also deleted. This is not a good idea in my opinion. You should keep track of all data that's ever been in a database, although this can be done using TRIGGERs. (However, see caveat in comments below).

   • ON UPDATE CASCADE means that if the parent primary key is changed, the child value will also change to reflect that. Again in my opinion, not a great idea. If you're changing PRIMARY KEYs with any regularity (or even at all!), there is something wrong with your design. Again, see comments.

   • ON UPDATE CASCADE ON DELETE CASCADE means that if you UPDATE OR DELETE the parent, the change is cascaded to the child. This is the equivalent of ANDing the outcomes of first two statements.

2. RESTRICT

   • RESTRICT means that any attempt to delete and/or update the parent will fail throwing an error. This is the default behaviour in the event that a referential action is not explicitly specified.

     For an ON DELETE or ON UPDATE that is not specified, the default action is always RESTRICT`.

3. NO ACTION

   • NO ACTION: From the manual. A keyword from standard SQL. In MySQL, equivalent to RESTRICT. The MySQL Server rejects the delete or update operation for the parent table if there is a related foreign key value in the referenced table. Some database systems have deferred checks, and NO ACTION is a deferred check. In MySQL, foreign key constraints are checked immediately, so NO ACTION is the same as RESTRICT.

4. SET NULL

   • SET NULL - again from the manual. Delete or update the row from the parent table, and set the foreign key column or columns in the child table to NULL. This is not the best of ideas IMHO, primarily because there is no way of "time-travelling" - i.e. looking back into the child tables and associating records with NULLs with the relevant parent record - either CASCADE or use TRIGGERs to populate logging tables to track changes (but, see comments).

5. SET DEFAULT

   • SET DEFAULT. Yet another (potentially very useful) part of the SQL standard that MySQL hasn't bothered implementing! Allows the developer to specify a value to which to set the foreign key column(s) on an UPDATE or a DELETE. InnoDB and NDB will reject table definitions with a SET DEFAULT clause.

As mentioned above, you should spend some time looking at the documentation, here.

These two are actions to be performed, respectively, when the referenced record on the parent table changes its id and when it gets deleted.

If you execute:

UPDATE parent SET id = -1 WHERE id = 1;

And there is at least one record on child with parent_id = 1, 1) will fail; in cases 2) and 3), all records with parent_id = 1 are updated to parent_id = -1.

If you execute:

DELETE FROM parent WHERE id = 1;

And there is at least one record on child with parent_id = 1, 2) will fail; in cases 1) and 3), all records with parent_id = 1 are deleted.

3) is syntactically correct.

Full documentation can be found on the manual.

I don't have enough reputation to comment on the previous answers. So I thought I'd elaborate a bit.

1) ON DELETE CASCADE means if the parent record is deleted, then any referencing child records are also deleted. ON UPDATE defaults to RESTRICT, which means the UPDATE on the parent record will fail.

2) ON DELETE action defaults to RESTRICT, which means the DELETE on the parent record will fail. ON UPDATE CASCADE will update all referencing child records when the parent record is updated.

3) See the CASCADE actions in 1) and 2) above.

On using parent record IDs as foreign keys (in child tables) -- experience says a) if the IDs are auto-generated sequence numbers, then DO NOT use them as foreign keys. Use some other unique parent key instead. b) if the IDs are GUIDs, then it's ok to use them as foreign keys. You'll see the wisdom in this suggestion when you export and import the records or copy records to another database. It's too cumbersome to deal with auto-generated sequence numbers during data migration when they are referenced as foreign keys.