Bug #55073 User Defined Types cannot used in SQL (Triggers, SP)
Submitted: 8 Jul 2010 10:33 Modified: 4 Apr 2014 16:50
Reporter: Oliver Mnzberg Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.25 OS:Any
Assigned to: CPU Architecture:Any
Tags: User defined types
Triage: Needs Triage: D3 (Medium)

[8 Jul 2010 10:33] Oliver Mnzberg
Description:
User Defined Types cannot be used in SQL (e.g. Triggers, SP)
In the Code Editor it will be marked as an error and will not be converted in SQL-script to the related DataType.
The predefined UserTypes work

How to repeat:
Create a "User Defined Type" lets say "MyDataType" as an "INT".

Add a new routine like this:
DELIMITER $$

CREATE PROCEDURE `mydb`.`routine1` ( IN MyData MyDataType )
BEGIN

END$$
[8 Jul 2010 10:52] Oliver Mnzberg
Testes on OSX with Same resolut
[8 Jul 2010 10:57] Valeriy Kravchuk
Thank you for the problem report.
[6 Sep 2011 14:23] Анатолий Кирсанов
The same problem in Workbench 5.2.34 CE Revision 7780 on Windows Vista SP2
[4 Apr 2014 13:53] Alfredo Kojima
Thank you for the feature request. User defined types are not a server feature, thus it cannot be made to work cleanly with triggers and SPs in Workbench.
[4 Apr 2014 16:50] Oliver Mnzberg
Hi Alfredo,

I never expect this to be a server feature.

Maybe you did not know WorkBench, but this User Defined Types are only known to WorkBench and are like macros and will be translated by WorkBench before sending to the server.

I can accept that this will never been fixed, but I am upset by your explanation why.
Seems to me you are trying to kidding me.

But do not take to much time in this, I have turned my back to MySQL long time ago.
Now I know it was the right choice ... keep on