| Summary: | OQL UNION clause problems | ||
|---|---|---|---|
| Product: | [Tools] MAT | Reporter: | Andrew Johnson <andrew_johnson> |
| Component: | Core | Assignee: | Andrew Johnson <andrew_johnson> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Andrew Johnson
There are two problems. The duplicate UNION clauses in the text is because the partial result has the full OQL query string, instead of the result without the union which is then combined with the union subresults. The ResultSet and ObjectResultSet need to be built with the correct sub query. The null pointer exception is because the first result has no objects so is null. The fix is to create an empty result when needed (i.e. when another sub result is not null). Fixed as described. |