CROSS JOIN
Isha only reaches for CROSS JOIN when student + marks has to stay correct in a report.
CROSS JOIN order — meaning → JOIN … ON s.roll = m.roll → one limit. Dumping ten features helps nobody.
Without CROSS JOIN, a report gets messy and student + marks is hard to trust.
Use CROSS JOIN when student + marks must stay clear. If a simpler SQL step works, use that instead.
Don’t do this with CROSS JOIN — missing ON → cartesian product. Interviewers spot it in ten seconds.
Place CROSS JOIN next to nearby SQL work — JOIN … ON s.roll = m.roll is the link.
Close CROSS JOIN with — “If I skip it, student + marks goes wrong like this: missing ON → cartesian product.”
students.id
=
marks.student_id
│
▼
one result rowFor CROSS JOIN: definition + a report + one failure.