| Summary: | Allow comparisons of trees as well as tables | ||
|---|---|---|---|
| Product: | [Tools] MAT | Reporter: | Andrew Johnson <andrew_johnson> |
| Component: | Core | Assignee: | Andrew Johnson <andrew_johnson> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | apupier |
| Version: | 1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 369047, 394222 | ||
|
Description
Andrew Johnson
I've made a first pass at the changes. A query is eligible as a compare query if all the IStructuredResult arguments are of a type which can hold all of the selected objects in the compare basket. Where do we need to update query names, query help, parameter names, HTML help etc. to reflect this change to allow trees? We should also allow the results of an OQL query to be compared. Should we allow more generic compares/queries of any IResult? E.g. for a query doing group by value on a column etc. Results from OQL queries can now be compared. I've experimented with adding IStructuredResult as arguments to ordinary queries. It's a modification to Policy and QueryContextMenu. I'm not sure whether to add this yet - I'd need to see some queries that could use it. If we want to allow an IStructuredResult as an argument to an ordinary query then we should raise a new bug, preferably with an example query that could use that facility. This bug is now fixed - the use of trees as well as tables is mentioned in the documentation. This results of an OQL query can also now be compared. |