Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA | swissarmyknife(*) |
| Priority | Low |
| Complexity | Unknown |
| Component | Tools - ER Modeler |
| Version | 14.0 |
When comparing two ER Diagrams, Table Constraints appear as top level objects. They should not, they should be objects within tables and not appear as top level in the comparison results.
See attached.
Constraints are now compared in the Table object in ER Model comparison. They are no longer shown as a top-level object.
Also, fixed the object types shown in the Type Filter list in the Compare Filter dialog to match the list of object types in the comparison results. We were hard-coding the object types to Table, View, and Index. For example, referring to the attached screenshot, since the comparison results contain Table and Index, the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list.
looks good in
looks good in
As per your comment "the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list".
We verified this issue in ADS Version 14.0.5 and ADS Version 14.0.6
In ADS Version 14.0.6, we still observed "View"object in Compare Filter dialog.
Please see attached screenshot(ERMODEL.png).
As per your comment "the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list".
We verified this issue in ADS Version 14.0.5 and ADS Version 14.0.6
In ADS Version 14.0.6, we still observed "View"object in Compare Filter dialog.
Please see attached screenshot(ERMODEL.png).
Raghvendra, please read the entire sentence to get the correct context of my comment.
For example, referring to the attached screenshot, since the comparison results contain Table and Index, the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list.
As stated in my comment, "referring to the attached screenshot", the screenshot dated Nov 13, 2013 shows that "View" is not in the compare results. Therefore, "View" is not included in the Type Filter list.
However, in your screenshot ERMODEL.png, "View" is in the compare results and it is correct that "View" appears in the Type Filter list. Therefore, your reason for reopening this issue is invalid.
I am closing this issue as "fixed" since the original problem was fixed correctly.
Raghvendra, please read the entire sentence to get the correct context of my comment.
For example, referring to the attached screenshot, since the comparison results contain Table and Index, the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list.
As stated in my comment, "referring to the attached screenshot", the screenshot dated Nov 13, 2013 shows that "View" is not in the compare results. Therefore, "View" is not included in the Type Filter list.
However, in your screenshot ERMODEL.png, "View" is in the compare results and it is correct that "View" appears in the Type Filter list. Therefore, your reason for reopening this issue is invalid.
I am closing this issue as "fixed" since the original problem was fixed correctly.
Issue #10760 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 14.0.5-1 |
| No time estimate |
Constraints are now compared in the Table object in ER Model comparison. They are no longer shown as a top-level object.
Also, fixed the object types shown in the Type Filter list in the Compare Filter dialog to match the list of object types in the comparison results. We were hard-coding the object types to Table, View, and Index. For example, referring to the attached screenshot, since the comparison results contain Table and Index, the Compare Filter dialog shows Table and Index only and View is not included in the Type Filter list.