MySQL Stored Procedure debugging tool trade and free

MySQL Stored Procedure debugging tool commercial and free MySQL Stored Procedure since its birth in MySQL 5.0, has been released because there is no rich debugging tool

MySQL Stored Procedure debugging tool commercial and free MySQL Stored Procedure since its birth in MySQL 5.0, has been released because there is no rich debugging tool

MySQL Stored Procedure debugging tools commercial and free
MySQL stored procedures have been criticized for lack of debugging tools since the birth of MySQL 5.0. Since its acquisition by SUN and ORACLE, MySQL products have experienced many improvements in both functionality and performance. However, in terms of stored procedures, MySQL 5.5 adds an Error Buffer acquisition method. MySQL 5.6 further expands the error buffer to store as many warnings and error messages as possible. Of course, these are only functions of the software. Now ORACLE has integrated the debugging of the stored procedure into Virtual Studio, which can easily debug the stored procedure from Virtual Studio, simplifying the subsequent maintenance of the stored procedure.


Of course, third-party commercial companies have also developed some tools FOR debugging stored procedures, such as dbforge studio for mysql. This tool can debug a small amount of code.
For example, the following stored procedure:

DELIMITER $$USE `t_girl`$$DROP PROCEDURE IF EXISTS `sp_vs2010`$$CREATE DEFINER=`root`@`localhost` PROCEDURE `sp_vs2010`(OUT p2 INT)BEGINDECLARE i INT DEFAULT 0;loop_label1:LOOPIF i > 10 THEN  LEAVE loop_label1;END IF;SET i = i + 1;END LOOP;SET p2 = i;END$$DELIMITER ;

Debugging of dbforge studio for mysql:

Virtual Studio For MySQL debugging.