[CMT][BUG]Migrate decimal data type to CUBRID, the target data type is error

Details

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

    In CMT 1.5.5.4336

Description

1 Goto Migration/preferences/Mysql to CUBRID. Can see decimal(p,s) to numeric(p,s)
2 When create one table
CREATE TABLE testa(
n numeric(6,0)
);
CREATE TABLE testb(
n numeric(63,0)
);
3 Do migration, goto step5, can see
testa decimal(6,0) change to numeric(6,0)
testb decimal(63,0) change to numeric(65,0)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Isaiah Choe added a comment -

This is two problem.

1.
The CUBRID are not support numeric type that a precision is more than 38.

2.
Previous code changed force with varchar type. Because of no.1 problem.

I fixed this issue.
It will change numeric(38) if it has a overflowed numeric data type.
And then, if you click next button in step 5, you will see some alert message dialog.

Show
Isaiah Choe added a comment - This is two problem. 1. The CUBRID are not support numeric type that a precision is more than 38. 2. Previous code changed force with varchar type. Because of no.1 problem. I fixed this issue. It will change numeric(38) if it has a overflowed numeric data type. And then, if you click next button in step 5, you will see some alert message dialog.
Hide
Permalink
高艳铭 added a comment -

Fixed on version CMT1.5.5.4354

Show
高艳铭 added a comment - Fixed on version CMT1.5.5.4354

People

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

Dates

  • Due:
    Created:
    Updated:
    Resolved: