Data Modeler 3.0 EA2: Column type changes to unknown

Question

Drawing a relational model
Create table TABLE_1
add Column_1 - number - primary key
Create table TABLE_2
add Column_2 - varchar2 - primary key
create foreign key TABLE_2_TABLE_1_FK
Create unique constraint TABLE_2 for columns Column_2 , TABLE_1_Column_1
Create a foreign key TABLE_1_TABLE_2_FK
Change PK / UK Index from TABLE_2.TABLE_2_PK to TABLE_2.TABLE_2__UK
Select Associated Columns and select Child columns
Parent column           Child column
Column_2                 TABLE_2_Column_2
TABLE_1_Column_1       Column_1Press ok - and the column <B>TABE_2.TABLE_1_Column_1 datatype becomes UNKNOWN </B>. It was number.
Situation before problem happens looks like following. If the model is reverse engineered from this DDL the problem does not happen.
CREATE TABLE TABLE_1
     Column_1 NUMBER  NOT NULL
ALTER TABLE TABLE_1
    ADD CONSTRAINT TABLE_1_PK PRIMARY KEY ( Column_1 ) ;
CREATE TABLE TABLE_2
     Column_2 VARCHAR2  NOT NULL ,
     TABLE_1_Column_1 NUMBER  NOT NULL
ALTER TABLE TABLE_2
    ADD CONSTRAINT TABLE_2_PK PRIMARY KEY ( Column_2 ) ;
ALTER TABLE TABLE_2
    ADD CONSTRAINT TABLE_2__UN UNIQUE ( Column_2 , TABLE_1_Column_1 ) ;
ALTER TABLE TABLE_2
    ADD CONSTRAINT TABLE_2_TABLE_1_FK FOREIGN KEY
     TABLE_1_Column_1
    REFERENCES TABLE_1
     Column_1
;

Answer 1

Hi Rafu,
I logged bug for that.
Import of DDL is not the only way to get it working , just need to follow the steps in DDL. TABLE_1_Column_1 column is automatically created FK column when you work manually. If you create it before FK (set data type) and then select it as FK column you'll have the same behavior as in import of DDL.
Philip