Bug #43764 | Row size too large error message when set parameter is multilanguage | ||
---|---|---|---|
Submitted: | 20 Mar 2009 8:01 | Modified: | 16 Oct 2009 12:17 |
Reporter: | William Castro | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S2 (Serious) |
Version: | 1.1.16 | OS: | Windows (xp pro sp3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | CHECKED |
[20 Mar 2009 8:01]
William Castro
[20 Mar 2009 12:33]
MySQL Verification Team
Thank you for the bug report. Could you please provide a small *.mdb file which contents a table and records which presents the behavior reported. Thanks in advance.
[21 Mar 2009 3:46]
William Castro
this is the sample file..this is just a portion and i hope to preserve everything
Attachment: bug data Bug #43764.zip (application/x-zip-compressed, text), 38.96 KiB.
[31 Mar 2009 8:36]
William Castro
Hi Miguel, Thanks for replying to my post. May I know if you have any updates regarding my bug report? I'm really looking forward to migrate my tables to MySql for it's currently causing me a lot of headaches. Thanks!
[31 Mar 2009 9:26]
Susanne Ebrecht
Which encoding is used for your database? Please send us output of: SHOW VARIABLES LIKE '%char%'; and output from: SHOW CREATE TABLE <your_table>;
[31 Mar 2009 9:57]
William Castro
Hi Susanne, I have my defaults as utf-8. I used MySQL Migration toolkit to migrate the MS Access file. Chose multilingual in both schema and table which is utf-8. Output: Nothing. Error: Row size too large error message when set parameter is multilanguage Note: The sample file I uploaded contains 25 records only(I think)
[31 Mar 2009 17:57]
MySQL Verification Team
Thank you for the feedback. Could you please try with last released version 1.1.17. I could not repeat the behavior reported. Thanks in advance. -------------------------------------------------------------------------------- -- MySQL Migration Toolkit Report -- -- -- -- Title: Summary Of The Migration Process -- -- Date: 2009-03-31 14:54 -- -------------------------------------------------------------------------------- 1. Schema Migration ------------------- Number of migrated schemata: 1 Schema Name: test - Tables: 1 - Views: 0 - Routines: 0 - Routine Groups: 0 - Synonyms: 0 - Structured Types: 0 - Sequences: 0 Details: - Tables `test`.`test` ------------- - Views - Routines - Routine Groups - Synonyms - Structured Types - Sequences 2. Data Bulk Transfer --------------------- `test`.`test` ------------- 48 row(s) transfered. End of report. --------------------------------------------------------------------------------
[1 Apr 2009 9:02]
William Castro
Hi, I installed 1.1.17 but I still get the error. Miguel, can you kindly guide me on what you did in creating the table and where you able to preserve the Chinese characters in the table?
[1 Apr 2009 12:41]
MySQL Verification Team
Sorry I was expecting to get the error message and didn't checked if the Chinese characters were migrated correctly and now checking I verified they were migrated wrongly (?? symbols) , so changing the status to verified.
[1 Apr 2009 13:11]
William Castro
Hi Miguel, Yes if you do the import as generic with Latin you will be able to successfully create a table but the foreign characters are replaced with question marks. If you change the preferences to multilingual (utf-8) during upload you might get the error I posted.. Please keep me updated. Thanks in advance!
[16 Oct 2009 12:17]
Susanne Ebrecht
I re-analysed this. Unfortunately, MySQL only support 3 byte utf8. The characters you are using have 4 bytes. Also they seem not to be utf8. It looks like they are utf16. You need to convert them first into utf8 before you can import them into MySQL.