| Bug #43497 | wrong migration of MSSQL unqiueidentifier | ||
|---|---|---|---|
| Submitted: | 9 Mar 2009 10:20 | Modified: | 17 Apr 2009 13:50 |
| Reporter: | peter hansen | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Migration Toolkit | Severity: | S3 (Non-critical) |
| Version: | OS: | Windows | |
| Assigned to: | CPU Architecture: | Any | |
[17 Mar 2009 13:50]
MySQL Verification Team
Thank you for the bug report. Could you please provide a SQL Server create table statement which presents the behavior reported and the SQL Server version?. Thanks in advance.
[17 Apr 2009 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".
Description: MSSQL uniqueidentifier is migrated as varchar(64) an UID (MS) is stored on MSSQL as 'C5F74E7D-0260-4609-99AA-E10D60D58E22' but a query in MS Administrator returns (and if you use UUIDs in you query) '{C5F74E7D-0260-4609-99AA-E10D60D58E22}' now if the UID is migrated as varchar, its saved in mySQL as 'C5F74E7D-0260-4609-99AA-E10D60D58E22' this isnt a problem, but you cant use the winapi StringFromCLSID(GUID, P) to create an query because this api returns '{C5F74E7D-0260-4609-99AA-E10D60D58E22}' a string'{C5F74E7D-0260-4609-99AA-E10D60D58E22}' (returned by API) is different from 'C5F74E7D-0260-4609-99AA-E10D60D58E22' (saved in MYSQL) so you dont get any result in MSSQL its still the same and you get some results How to repeat: see description Suggested fix: in my opinion the ms datatype uniqueidentifier 'C5F74E7D-0260-4609-99AA-E10D60D58E22' has to be migrated as mysql varchar '{C5F74E7D-0260-4609-99AA-E10D60D58E22}'