DELETE JOIN
Ananya only reaches for DELETE JOIN when student + marks has to stay correct in a report.
Do DELETE JOIN once by hand. JOIN … ON s.roll = m.roll. Change one input. Say the new result out loud.
Without DELETE JOIN, a report gets messy and student + marks is hard to trust.
Use DELETE JOIN when student + marks must stay clear. If a simpler SQL step works, use that instead.
DELETE JOIN trap — missing ON → cartesian product. Ananya loses marks for that every viva.
DELETE JOIN is not a lonely heading. Ananya ties it to student + marks.
One breath for DELETE JOIN, then student + marks, then missing ON → cartesian product. Sit down.
students.id
=
marks.student_id
│
▼
one result rowBoard: student + marks. Dry-run DELETE JOIN. Name the trap: missing ON → cartesian product.