Bug #17969 Exported SQL Create script does not import as-is with cli
Submitted: 6 Mar 2006 15:23 Modified: 6 Mar 2006 15:41
Reporter: Csaba Skultety Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Workbench Preview Severity:S3 (Non-critical)
Version:1.0.5 beta OS:Windows (Win2K SP4)
Assigned to: CPU Architecture:Any

[6 Mar 2006 15:23] Csaba Skultety 
Description:
The exported create script fails with syntax errors on import. Editing the script with a hex editor reveals a null byte (if I'm reading it correctly) as every other character in the file, not sure if the cli is expecting a single-byte character file or what. 

How to repeat:
Create a test table with a field on the canvas, go to File->Export->Export SQL Create Script... and export the file to your favorite location. Import that file using: mysql -uuser -p < filename.sql
[6 Mar 2006 15:41] MySQL Verification Team 
Thank you for the bug report. I was able to repeat.
[6 Apr 2006 9:48] Klaus Bensch 
One Problem is that the file is stored in "UCS-2 little Endian". Conversion into ANSI will make it readable for the shell on Windows machines. But there are additional bugs with the syntax.
1. VARCHAR: wrong COLLATE definition, ERROR 1064
2. DOUBLE(0, 0): ERROR 1064
3. foreign keys: missing datatype definition
Use my test file to verify.