Hello
I am facing an issue in MySQL where a stored procedure using SELECT INTO inside an IF block sometimes fails to populate the variable; even though the query returns a row when executed independently. 
The problem occurs intermittently & the procedure runs without error but the output variables remain NULL. 
I suspect it’s either due to how MySQL handles variable scope within conditional logic / because of overlapping column names across joins. 
This is part of a migration from an older Oracle system where we used PL/SQL to conditionally assign variables inside blocks and the logic translated cleanly. But MySQL seems more sensitive to SELECT INTO behavior inside nested logic.
Are there hidden caveats when using SELECT INTO with IF/ELSE blocks in stored procedures? Does the query optimizer treat those differently compared to standalone SELECTs? I have checked https://dev.mysql.com/doc/refman/8.4/en/select-into.html guide for reference.
While debugging this; I also revisited the fundamentals of what is pl sql to better understand how MySQL’s procedural logic compares to Oracle’s. Any clarity on scoping / optimizer quirks with SELECT INTO would be very helpful especially in complex procedures with branching logic.
Thank you !! 