| Bug #90158 | MySQL Workbench ignores routines with "STACKED" diagnostics during model synch | ||
|---|---|---|---|
| Submitted: | 21 Mar 2018 10:22 | Modified: | 21 Mar 2018 11:42 |
| Reporter: | Laszlo Lieszkovszky | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 6.3.10 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[21 Mar 2018 11:42]
Chiranjeevi Battula
Hello Laszlo, Thank you for the bug report. Verified this behavior on MySQL Workbench in 6.3.10 version. Thanks, Chiranjeevi.

Description: When using "Synchronize Model" (or similar tools) in MySQL Workbench, any procedure in the database that includes the keyword "STACKED diagnostics" is ignored. "CURRENT diagnostics" does not raise this error. Setting the "Target MYSQL Version" in "Model Options" to 5.7 (which is the MySQL version where the "STACKED" keyword was introduced) has not effect. How to repeat: Create an empty database with a single routine like below, and create an empty Workbench model. Try to sync the two. During sync, the procedure is ignored (as if it didn't exist). DELIMITER // DROP PROCEDURE IF EXISTS sp_ignoredbyworkbench// CREATE DEFINER=`root`@`localhost` PROCEDURE `sp_ignoredbyworkbench`() LANGUAGE SQL NOT DETERMINISTIC CONTAINS SQL SQL SECURITY DEFINER COMMENT '' BEGIN DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN GET STACKED DIAGNOSTICS CONDITION 1 @sqlstate = RETURNED_SQLSTATE, @errno = MYSQL_ERRNO, @text = MESSAGE_TEXT; RESIGNAL; END; END