I am trying to migrate a large MSSQL 2000 database into MySQL 5.6. My MySQL database has fields allowing milliseconds, which appear for newly inserted records; but records imported via wbcopytables.exe lose their milliseconds (i.e. the records appear with datetime values ending in .000). This happens even if I CAST the field to a string value in the generated Workbench Table Data copy script .cmd file.
In looking at the source code, I find that /plugins/migration/copytable/copytable.cpp makes no provision for milliseconds in the case block for various date/time fields (lines 2073 to 2102 in 6.1.7-src).
So maybe some work needs to be done with that, but I'm not familiar with the source sufficiently to be sure I've isolated the right block of code.
Is there any existing means of importing my milliseconds without something inconvenient like an integer field that will later be used to adjust the datetime field. I have more tables and fields than I would want to do that for.
Thank you,
Jeremy
In looking at the source code, I find that /plugins/migration/copytable/copytable.cpp makes no provision for milliseconds in the case block for various date/time fields (lines 2073 to 2102 in 6.1.7-src).
So maybe some work needs to be done with that, but I'm not familiar with the source sufficiently to be sure I've isolated the right block of code.
Is there any existing means of importing my milliseconds without something inconvenient like an integer field that will later be used to adjust the datetime field. I have more tables and fields than I would want to do that for.
Thank you,
Jeremy