Bug #48548 Please reopen Bug #46429
Submitted: 4 Nov 2009 21:40 Modified: 5 Nov 2009 19:27
Reporter: Werner Wolf Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:6.1.2 OS:Windows
Assigned to: CPU Architecture:Any
Tags: DELIMITER, mysqlscript

[4 Nov 2009 21:40] Werner Wolf 
Description:
We use Connector .NET 6.1.2, Visual Studio 2005, .NET 2.0 SP1
Same problem with MySqlCommand and MySqlScript
This was also a former, closed, bug: Bug#46429
Is there a workaround for this problem?

This is a serious problem to us, any comments are very welcome!

How to repeat:
See Bug#46429
[5 Nov 2009 7:08] Tonci Grgin 
Werner, I'll recheck on Bug#46429 now.
[5 Nov 2009 19:27] Werner Wolf 
Wonderfull, thank you.

Any knowledge in the meantime?
[20 Nov 2009 22:45] Sergei Shirokov 
The same problem. Version 6.1.3
[20 Nov 2009 23:37] Sergei Shirokov 
Disassembly of BreakIntoStatements

Attachment: MySqlScript.BreakIntoStatements.cs (text/plain), 2.11 KiB.
[20 Nov 2009 23:40] Sergei Shirokov 
Bug in the line # 35, exactly in the "startIndex = num3 + this.delimiter.Length;"
Here should be sentence without 'this.', i.e. local 'delimiter' variable.

Workarround is simple: use one character delimiter, like following:

DELIMITER ?
CREATE PROCEDURE XYZ()
BEGIN
  ...
END?
[23 Nov 2009 8:20] Tonci Grgin 
Sergei, please post your comments to Bug#46429 and not here.

As I said (in other report) I am unable to reproduce this behavior using latest sources from trunk.
[23 Nov 2009 8:52] Tonci Grgin 
Sergei, this appears to be old code, please see new code in http://lists.mysql.com/commits/79499 and make sure you're not referencing some old c/NET driver.

Patch was merged as rev. 714 on 2009-07-29 but I think it made it to 6.1.3 and not 6.1.2.
[25 Nov 2009 14:17] Sergei Shirokov 
As You suggested I wrote my comment to the http://bugs.mysql.com/bug.php?id=46429. Thanks!
[25 Nov 2009 14:23] Sergei Shirokov 
BTW I surely have version 6.1.3, and, as I see patch difference, the bug I found was before, and still stays there after the patch.