Bug #5461 | MySQL Query Browser fails to run stored procedure install scripts | ||
---|---|---|---|
Submitted: | 8 Sep 2004 9:20 | Modified: | 3 Nov 2004 12:47 |
Reporter: | Roger Wallace | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.0.5 alpha | OS: | Windows (Windows 2000) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[8 Sep 2004 9:20]
Roger Wallace
[8 Sep 2004 9:22]
Roger Wallace
Note that the script gives a similar error from at least one other GUI client: The Eclipse plugin - QuantumDB.
[3 Nov 2004 12:47]
Michael G. Zinner
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/
[14 Aug 2009 14:17]
moi meme
This bug still exists on v "1.2.17" . A script created with workbench, containing procedures, can't be executed. See sample line 2: DELIMITER // // CREATE PROCEDURE `SpotDatabaseTEST`.`GetModulePaths_Names` (IN moduleTypeParam VARCHAR(255), IN moduleNameParam VARCHAR(255), OUT importPathParam TEXT, OUT exportPathParam TEXT) BEGIN DECLARE idModuleVar VARCHAR(255) DEFAULT NULL; # Get the id of the module SELECT m.idModule INTO idModuleVar FROM TSpotModule m INNER JOIN TSpotModuleType mt ON mt.idModuleType = m.idModuleType INNER JOIN TConfModule mc ON m.idModule = mc.idModule WHERE mc.name = moduleNameParam AND mt.moduleTypeName = moduleTypeParam; CALL getModulePaths_ids(idModuleVar, importPathParam, exportPathParam); END//