4.0 EA3 import from designer and database leads to differences in compare models

Question

Hello,
I followed two ways to import a model in Data Modeler:
1 - an import from Oracle Designer
2 - an import from the database generated on basis from Oracle Designer
Then I compare the two models in Data Modeler, and found differences ...
One of the differences is in Table check constraints. The text is the same when viewing it in the compare model.
So I opened the corresponding XML files for the tables and compared the XML for the constraint text. And there are differences:
example:
<rule>(file_locatie is not null and file_naam_org is not null) or&lt;br/&gt;(file_locatie is null and file_naam_org is null)</rule>
<rule>(file_locatie is not null and file_naam_org is not null) or&lt;br&gt;(file_locatie is null and file_naam_org is null)</rule>    <<-- designer
the design imported from designer contains br, the databse imported version contains br/
This should not be considered during comparision, or better: boths imports should use the same way of formatting.
Joop

Answer 1

The Rule specification is not re-formatted in Data Modeler code; it is stored as extracted from the database.
For Oracle Database, the Rule is extracted using SQL of the form SELECT search_condition FROM dba_constraints/all_constraints WHERE constraint_type = 'C';
For Oracle Designer, the Rule is extracted using SQL like SELECT txt_text FROM rm_text_lines WHERE txt_type = 'CDWHCL';
Are you able to tell how your Table Check Constraint is represented (with respect to the 'br') in your Database and Designer?
Regards,
Tony