From: SourceForge.net <no...@so...> - 2010-09-12 04:35:28
|
Bugs item #3064605, was opened at 2010-09-11 22:35 Message generated for change (Tracker Item Submitted) made by s1kevin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3064605&group_id=132863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Benton (s1kevin) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL Driver unable to handle "DELIMITER" changes Initial Comment: When an SQL file contains a DELIMITER change, ESE doesn't sense it and react appropriately. For example, when defining a stored function, procedure or trigger (routine), it is very common to need to use DELIMITER so that the interpreter knows when to stop defining the stored routine. DELIMITER $$ CREATE PROCEDURE foo ... BEGIN -- some code goes here END $$ DELIMITER ; In code I've written that parses files then sends them through to the system like this, I've had to pre-parse the file to divide statements up by delimiter while stripping the delimiter changes out of the file because mysqld doesn't understand delimiter changes (that's just the mysql command-line client handling it for us). Today, I ran a few hundred lines of code from ESE that wouldn't execute code successfully with delimiter changes embedded in the code that the MySQL command-line client handled flawlessly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=725495&aid=3064605&group_id=132863 |