Union vs Join
Don’t start Union vs Join with jargon. Start with student + marks. That is the whole point.
Keep Union vs Join small. Vikram should finish student + marks in a few lines, not a 40-line dump.
Union vs Join exists so Vikram can keep student + marks correct in a report.
Use Union vs Join when student + marks must stay clear. If a simpler SQL step works, use that instead.
Union vs Join trap — missing ON → cartesian product. Vikram loses marks for that every viva.
Union vs Join is not a lonely heading. Vikram ties it to student + marks.
Viva for Union vs Join — what it is → JOIN … ON s.roll = m.roll → the mistake (missing ON → cartesian product).
students.id
=
marks.student_id
│
▼
one result rowSay Union vs Join in one breath, then JOIN … ON s.roll = m.roll, then missing ON → cartesian product.