MySQL stored procedure controller not found creates a messy solution

Make a draft

Issue: For select var1 into var2, the result of a single select is null (null means no data found, not the value is null), the controller's not found is triggered

When the cursor is empty, the controller's not found is triggered

When there are multiple cursors in the program, select into and so on, the controller's not found may be triggered at an incorrect time, resulting in confusion in the program logic

Workaround:

Add the tag block and capture the not found within the tag block, without throwing it up, in the following format

Tag Block Name: BEGIN

The executed statement

END Tag Block name

MySQL stored procedure controller not found creates a messy solution