Oracle 5.0 Reference Manual page 1865

Figure 20.26. Function Stepping (2 of 2)
• To step into the code of a condition handler, the condition must be triggered in the rest of the MySQL
routine.
• The next statement to be executed is highlighted in yellow.
• To continue stepping, you can choose between Step Into (by pressing F11), Step Out (by pressing
F10) or Step Over (by pressing Shift+F11).
• You can step out of any of functions, triggers or stored procedures. If you step from the main routine,
it will run that routine to completion and finish the debug session.
• You can step over stored procedure calls, stored functions, and triggers. (To step over a trigger, step
over the statement that would cause the trigger to fire.)
• When stepping into a single statement, the debugger will step into each individual function invoked
by that statement and each trigger fired by that statement. The order in which they are debugged is
the same order in which the MySQL server executes them.
• You can step into triggers triggered from INSERT, DELETE, UPDATE, and
• Also, the number of times you enter into a stored function or trigger depends on how many rows are
evaluated by the function or affected by the trigger. For example, if you press F11 (Step Into) into
an statement that modifies three rows (calling a function for a column in the
UPDATE
thus invoking the function for each of the three rows), you will step into into that function three times
in succession, once for each of the rows. You can accelerate this debug session by disabling any
breakpoints defined in the given stored function and pressing Shift+F11 to step out. In this example,
the order in which the different instances of the stored function are debugged is server-specific: the
same order used by the current MySQL server instance to evaluate the three function invocations.
Breakpoints
Connector/Net Visual Studio Integration
1845
statements.
REPLACE
clause,
SET