[CMT2][BUG] Migrate xml charset is not utf8, it will be error.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: CMT8.4.1
  • Fix Version/s: CMT8.4.1
  • Component/s: CUBRID Migration Toolkit
  • Labels:
    None
  • Environment:

    CMT2.0.0.4999

Description

1 Dump from mysql use "mysqldump data --default-character-set=gbk --xml -u root -p >c:\datagbk.xml"
2 Choose the xml, set charset to gbk, do migration,
3 Goto step3, only choose chartest table
4 Do migration,it will be error.

  1. XML File
    datagbk.xml
    20/Dec/11 3:58 AM
    1.16 MB
    高艳铭
  1. migrationerror.PNG
    25 kB
    20/Dec/11 3:58 AM

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
曹轶麟 added a comment -

Actually the file' encoding is still utf8.

Show
曹轶麟 added a comment - Actually the file' encoding is still utf8.
Hide
Permalink
孙泽玺 added a comment -

this file of "datagbk.xml" can be converted to the file whose char set is GBK using the command:iconv -t gbk -f utf-8 -c datagbk.xml > datagbk_iconv.xml.

Show
孙泽玺 added a comment - this file of "datagbk.xml" can be converted to the file whose char set is GBK using the command:iconv -t gbk -f utf-8 -c datagbk.xml > datagbk_iconv.xml.

People

  • Assignee:
    高艳铭
    Reporter:
    高艳铭
Vote (0)
Watch (0)

Dates

  • Due:
    Created:
    Updated:
    Resolved: