Query Builder dynamicly change the request

Question

Hello,
I use VS2010 with ODT 11.2.0.1.1 and I have strange behaviour with the "Query Builder"...
When I enter this request:
SELECT ARTICLE_PCH.AP_CODE ....ARTICLE_SAP.AS_USAGE_UNIQUE
FROM ARTICLE_SAP, ARTICLE_PCH
WHERE ARTICLE_SAP.AS_NUMERO = ARTICLE_PCH.AS_NUMERO ( + ) AND (ARTICLE_SAP.AS_CIRCUIT = 'SAD') AND (ARTICLE_SAP.AS_SUPRESSION IS NULL) AND
(ARTICLE_SAP.AS_FAMILLE 'ZEPS') AND (ARTICLE_PCH.AP_CODE IS NULL)
ORDER BY ARTICLE_SAP.AS_LIB_40
The query builder add a ( + ) before the "IS NULL"
Like This
SELECT ARTICLE_PCH.AP_CODE ....ARTICLE_SAP.AS_USAGE_UNIQUE
FROM ARTICLE_SAP, ARTICLE_PCH
WHERE ARTICLE_SAP.AS_NUMERO = ARTICLE_PCH.AS_NUMERO ( + ) AND (ARTICLE_SAP.AS_CIRCUIT = 'SAD') AND (ARTICLE_SAP.AS_SUPRESSION IS NULL) AND
(ARTICLE_SAP.AS_FAMILLE 'ZEPS') AND (ARTICLE_PCH.AP_CODE ( + ) IS NULL)
ORDER BY ARTICLE_SAP.AS_LIB_40
And then the request return a wrong result. When I test with sqlplus the request without the ( + ) return the good result. But I can't enter the request because the query builder automaticaly modify my request...
Did someone have the same problem with this beta of ODT ?
With the previous version of ODT I don't have the problem.
Thanks in advance
Jeff

Answer 1

Hi Jeff,
Our engineers are looking into this. Right now, it appears this change is being done by Query Builder itself (eg there may be nothing we can do to stop it). This did not happen in VS2008.
However if you change your original query to the equivalent using the "LEFT OUTER JOIN" keywords, you can avoid this problem entirely:
For example:
From:
SELECT EMP.ENAME, EMP.JOB, EMP.MGR, DEPT.DNAME, DEPT.LOC
FROM EMP, DEPT
WHERE EMP.DEPTNO = DEPT.DEPTNO (+) AND (DEPT.DNAME IS NULL)
ORDER BY EMP.ENAME
To:
SELECT EMP.ENAME, EMP.JOB, EMP.MGR, DEPT.DNAME, DEPT.LOC
FROM EMP LEFT OUTER JOIN
DEPT ON EMP.DEPTNO = DEPT.DEPTNO
WHERE (DEPT.DNAME IS NULL)
ORDER BY EMP.ENAME
Can you try this with your query? We will follow up with MS to find out if there is anything we can do to stop Querybuilder from changing the query in VS2010.
Thanks,
Christian