Bug #69620 nvarchar, national varchar field types are not supported
Submitted: 29 Jun 2013 11:45 Modified: 16 Jul 2013 12:23
Reporter: Ob Steel Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version: OS:Microsoft Windows (XP)
Assigned to: CPU Architecture:Any
Tags: national varchar, NVARCHAR

[29 Jun 2013 11:45] Ob Steel
MySQL Workbench does not have support for nvarchar and national varchar field types. For my project I need complete DB support for unicode charset and therefore these data types are needed urgently. I tried adding my own type but no success.

How to repeat:
add a field with datatype nvarchar(45) or national varchar(45)
[29 Jun 2013 11:49] Ob Steel
added MySQL Workbench Version
[29 Jun 2013 11:52] Ob Steel
workaround: change all "varchar" to "nvarchar" after generating sql script then run altered script
[29 Jun 2013 21:55] Alfredo Kojima
nvarchar in MySQL is just an alias for VARCHAR and CHARACTER SET utf8. If you set the default charset in your DB and/or tables to utf8 you should be fine with VARCHAR in your columns
[30 Jun 2013 11:15] Peter Laursen
@Alfredo.  Should not WB define the *COLUMN* as utf8 - in order to ensure proper import where server, database and/or table has a non-utf8/non-unicode default?

Peter Laursen
[16 Jul 2013 12:23] Alfredo Kojima
Verifying as a feature request.
[16 Jul 2013 12:24] Alfredo Kojima
@Peter, true, that would probably be safer in all situations