| Bug #43822 | Sybase "Date" datatype conversion fails | ||
|---|---|---|---|
| Submitted: | 24 Mar 2009 7:29 | Modified: | 16 Oct 2009 11:41 |
| Reporter: | Viswanath G | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Migration Toolkit | Severity: | S3 (Non-critical) |
| Version: | 1.1.16 | OS: | Windows (XP) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | CHECKED, migration, sybase | ||
[2 Apr 2009 6:58]
Susanne Ebrecht
Verified as described
[16 Oct 2009 11:41]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't fix this in foreseeable future. Timestamp, Date, Datetime, Time is always a problem on migrations. Every RDBMS implemented their own logic here and you can't catch all of this. On migration it always needs manual work to transfer Timestamp, Time, Date, Datetime values. More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/
Description: A values from date column in Sybase(verion 15.0.2) isn't converted correctly to MySQL datetime or date. For example: "2009-01-02" in Sybase, becomes: "2009-01-01" in MySQL after conversion. Also the insert statement saved by the migration wiz, is also wrong, it shows as "2009-01-01 23:59:59" I'm using MySQL 5.0.45 version. How to repeat: 1. In sybase, create a table "mydate" in sybase with "mydate date not null" table column. 2. Then, insert into mydate values('2009-01-02'). 3. Using Migration tool kit with "sybase driver" migrate the table. Note : In "Detailed Object Mapping" page, selected mydate column and changes "Migration of type GRT Object's" Method as "sybase default" and paramter option as "User defined" as "forceDatatypeName=DATE"