[CMT2][BUG] The data migration from decimal, number to number is different in migration from oracle and mysql

Details

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

    CMT2.0.0.5258

Description

1 When migrated from mysql.
source target
decimal(13,2) character varying(13)

It will pop it will lost data.

2 When migrated from oracle.
source target
decimal(13,2) character varying(13)

It won't pop any warning.

Additional
The regular of from Numeric to vchar is as follows:
if s=0，the last length of target is p+1;
if p>s，the last length of target is p+1+1（包括小数点和符号）
if p=s，the last length of target is p+1+1+1（如decimal(3,3),可能会-0.999）。

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
高艳铭 added a comment -

There is the bug from int to varchar too.

Show
高艳铭 added a comment - There is the bug from int to varchar too.
Hide
Permalink
高艳铭 added a comment -

There is bug from int to numeric

Show
高艳铭 added a comment - There is bug from int to numeric
Hide
Permalink
付雷 (Inactive) added a comment - - edited

number to varchar
if s=0，the last length of target is p+1;
if p>s，the last length of target is p+1+1
if p=s，the last length of target is p+1+1+1
if scale < 0 and |scale|+ |Precision| > 38 convert it to varchar(|scale|+ |Precision|+1)
if scale > Precision and scale > 38 convert it to varchar(|scale| + 3)

int to number(p,s)
p should = 38

int to varchar ( n)
n should >= 127

Show
付雷 (Inactive) added a comment - - edited number to varchar if s=0，the last length of target is p+1; if p>s，the last length of target is p+1+1 if p=s，the last length of target is p+1+1+1 if scale < 0 and |scale|+ |Precision| > 38 convert it to varchar(|scale|+ |Precision|+1) if scale > Precision and scale > 38 convert it to varchar(|scale| + 3) int to number(p,s) p should = 38 int to varchar ( n) n should >= 127
Hide
Permalink
高艳铭 added a comment - - edited

Q1 if scale < 0 and |scale|+ |Precision| > 38 convert it to varchar(|scale|+ |Precision|+1)

It need to change if scale < 0 convert it to varchar(|scale|+ |Precision|1).If the length is less than |scale| |Precision|+1, need warning

ok

Q2 if scale > Precision and scale > 38 convert it to varchar(|scale| + 3)
The length is only the min length. The data in oracle maybe is long than the length.

if scale > Precision and scale > 38 convert it to varchar(|scale| + 3) is right.

Q3 int to varchar ( n)
n should >= 127
It only need >=126

it is >=127

Show
高艳铭 added a comment - - edited Q1 if scale < 0 and |scale|+ |Precision| > 38 convert it to varchar(|scale|+ |Precision|+1) It need to change if scale < 0 convert it to varchar(|scale|+ |Precision| 1).If the length is less than |scale| |Precision|+1, need warning ok Q2 if scale > Precision and scale > 38 convert it to varchar(|scale| + 3) The length is only the min length. The data in oracle maybe is long than the length. if scale > Precision and scale > 38 convert it to varchar(|scale| + 3) is right. Q3 int to varchar ( n) n should >= 127 It only need >=126 it is >=127
Hide
Permalink
高艳铭 added a comment -

Fixed in version CMT8.4.1.0001 20120120

Show
高艳铭 added a comment - Fixed in version CMT8.4.1.0001 20120120

People

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

Dates

  • Due:
    Created:
    Updated:
    Resolved: