Bug #45761 Reverse Engineer does not import stored procedure correctly
Submitted: 25 Jun 2009 16:54 Modified: 25 Jun 2009 18:36
Reporter: jed davidow Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.2.1 OS:Windows (Vista SP2 and XP SP3)
Assigned to: CPU Architecture:Any
Tags: PROCEDURE, regression, reverse engineer

[25 Jun 2009 16:54] jed davidow 
Description:
I Reverse Engineered a DB with a stored procedure.  A procedure with the correct name was imported, but the argument declarations and body were missing.

I duplicated my efforts with 5.1.14 RC and it worked without issue.

How to repeat:
1) Opened WB 5.2.1
2) Reverse Engineer DB (tried both local and remote servers, both failed)
3) Connected, specified DB, used defaults to finish import
4) Checked procedure within WB and it is defined as:

    -- --------------------------------------------------------------------------------
    -- Routine DDL
    -- --------------------------------------------------------------------------------
    DELIMITER //

    CREATE PROCEDURE `cpv`.`addDarkIVCurve` ()
    BEGIN
      
    END//
[25 Jun 2009 16:56] jed davidow 
Example of my DB with SP

Attachment: db.sql (application/octet-stream, text), 11.92 KiB.
[25 Jun 2009 17:29] Valeriy Kravchuk 
Looks like a duplicate of bug #45704. Please, check.
[25 Jun 2009 18:04] jed davidow 
Re: Looks like #45704

Yes, it is.  I searched 5.2.1 "procedure" but that did not come up, so I posted it.

Sorry about that.
[25 Jun 2009 18:36] Valeriy Kravchuk 
Duplicate of bug #45704.