Bug #22347 Problems with scripts from 1.2.2 then executing in 1.2.3 of Query Browser

• Submitted: 14 Sep 2006 14:08
• Modified: 15 Sep 2006 13:03
• Reporter: marc castrovinci (Basic Quality Contributor)
• Status: Duplicate
• Category: MySQL Query Browser
• Severity: S3 (Non-critical)
• Version: 1.2.2 then 1.2.3
• OS: Windows (XP PRO )
• CPU Architecture: Any
• Tags: execute, problem, query browser, script

[14 Sep 2006 14:08] marc castrovinci

Description:
I had a script that had stored procs and triggers that I had wrote in the Query Browswer 1.2.2. Well, this morning I decided to download the new pack with revisions. This upgrade the Browser to 1.2.3. So I try to execute my script, with no changes, and it brings up a TON of errors. So now i've got both running and it will execute fine on 1.2.2, but bring up errors on 1.2.3.

I don't know if this really counts as a bug, but it sure is going to keep me away from 1.2.3 now.

How to repeat:
create a stored proc in 1.2.2 execute, save the script. Open 1.2.3, and then load and try to execute the script.

[14 Sep 2006 19:26] Sveta Smirnova

Thank you for the report.

Could you please check if the problem is register of DELIMITER word as in bug #22330 and bug #22324?

[15 Sep 2006 12:51] marc castrovinci

It is the delimiter keyword problem. I had DELIMITER, now it executes fine with delimiter.

Thanks

[15 Sep 2006 13:03] Sveta Smirnova

Thank you for the feedback.

I mark this bug as duplicate of the bug #22324