This content has been marked as final. Show 6 replies
thanks for feedback.
Data Type: VARCHAR2 (2000 BYTE ) <=> VARCHAR2 (2000)You can change it in "Preferences>Data Modeler>DDL>Show Char/Byte unit ...."
Data Type Kind: Logical Type(VARCHAR) <=> Domain (MEMO)has no effect when compare to database
LOV Constraint: 'Y','N' <=> Y,NI logged a bug for that, still you can remove those quotes yourself and there will be no problem.
thanks for your reply.
The solution was not to remove those quotes but to add them in "Tools / Domains Administration".
With your other hint now most of the virtual diffs are gone, but I still have one diff I cannot explain.
All my foreign Keys are having different Delete Rules .
In database it is "*NO ACTION*" and in model it shows "*RESTRICT*",
although when I navigate to Foreign Keys Properties it also shows NO ACTION in model.
Do you know how this can be solved?
The flag Use "Data Type Kind" Property seems to have no effect.
The property is used in comparison even if this flag is unchecked.
The solution was not to remove those quotes but to add them in "Tools / Domains Administration".Can you elaborate on that - there is no need to add quotes if data type is character - what type is used, what goes into generated DDL
The flag Use "Data Type Kind" Property seems to have no effect.It has no effect when compare to database because there are no such definitions there. It's used when compare to another model
Also you can try DM 3.3 and to check for problem with foreign keys. It's better to use 3.3 if you import from Designer repository.
I will test with 3.3 and come back with my findings.
This might take some time because I'm blocked for the next weeks.
switching to Version 220.127.116.114 was partly successful.
The bug with the LOV Constraint 'Y','N' still exists, the workaround from 3.1 is still working.
The bug with the Delete Rule (No Action versus Restrict) still exists.
All Foreign Keys are marked as "To Drop" and as "New Relation" with the same name.
Some (very view) Views are having the same problem like all Foreign Keys.
Materialized Views are showing no wrong Diffs any more.
Sequences are showing no wrong Diffs any more.
I hope, that in some future releases the remaining bugs gets also fixed.