| Bug #10347 | Delimiter error when creating a stored procedure | ||
|---|---|---|---|
| Submitted: | 3 May 2005 19:34 | Modified: | 4 May 2005 0:38 | 
| Reporter: | Guillaume Lebur | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S2 (Serious) | 
| Version: | 1.1.7 (mySQL 5.0.4) | OS: | Windows (Windows XP SP2) | 
| Assigned to: | CPU Architecture: | Any | |
   [3 May 2005 19:34]
   Guillaume Lebur        
  
 
   [4 May 2005 0:38]
   Jorge del Conde        
  Hi! This is the expected behavoiur in Query Browser. What happens is each query that's executed in query browser creates a new connection to mysqld, so when ever the stored procedure code is actually executed, mysqld never sees its corresponding "DELIMITER //" call. Please use the script mode for these types of queries.
   [5 May 2005 7:42]
   [ name withheld ]        
  No, this really doesn't work. The script below was produced by the interface when I right-clicked on "Test3" in the "Schemata" and chose "Edit Procedure". It doesn't execute when I choose "Execute" from the "Script" menu. As far as I can tell this is "script mode". What is going on? Perhaps you should attempt these steps? DELIMITER $$ DROP PROCEDURE IF EXISTS `vuetec`.`Test`$$ CREATE PROCEDURE `vuetec`.`Test`() SELECT COUNT(*) FROM config$$ DELIMITER ; Jaye.
   [5 May 2005 7:43]
   [ name withheld ]        
  Argh! Why the hell can't I attach a screenshot to this!

