Bug #37783 Importing a script created by export feature fails if datetime has default set
Submitted: 1 Jul 2008 19:08 Modified: 1 Aug 2008 21:49
Reporter: Eric Lyng Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.23 OS:Windows
Assigned to: CPU Architecture:Any

[1 Jul 2008 19:08] Eric Lyng
Description:
To migrate 3 databases created with MySqlWorkbench into a singe MySqlWorkbench project, I Exported each to a Script file. When importing that script file there were failures. After closer inspection of the script files I found that if I set the default of a datetime field to all zeros in the proper format the import errors out. Other problems were related to indexes where MySqlWorkbench would not allow me to delete the index to recreate it. So I deleted the whole table, fixed it in the script file, imported that table back into the MySqlWorkbench project, exported to script, then the import to the other project worked fine. Other than that, MySqlWorkbench is far superior than DBDesigner 4.

How to repeat:
set default of datetime field to all zeros
[1 Jul 2008 19:12] Eric Lyng
How to repeat:
set default of datetime field to all zeros, export, then import to another project and error occurs while parsing the script file when it hits the default datetime.
[1 Jul 2008 21:49] MySQL Verification Team
Thank you for the bug report. I can't repeat trying to follow your how to repeat instructions, could you please provide the model file projects (a test case)?. Thanks in advance.
[2 Jul 2008 13:05] Eric Lyng
Project1 trimmed down to just the offending table

Attachment: project1.mwb (application/x-zip-compressed, text), 5.31 KiB.

[1 Aug 2008 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".