Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     WARNING: Oracle JOIN LEFT_OUTER does not allow MISSING test on target.

Read-Only Read-Only Topic
Go
Search
Notify
Tools
WARNING: Oracle JOIN LEFT_OUTER does not allow MISSING test on target.
 Login/Join
 
hammo1j
Master
posted
If you have tables A and B and common field FLD and want to find cases where no B exists for A then

JOIN LEFT_OUTER FLD IN A TO FLD IN B AS J1
TABLE FILE A
PRINT A.FLD
WHERE B.FLD EQ MISSING
END

does not work.

What happens is that the wf adapter reasons that any WHERE test on B does not require an outer join since the missing value retrieved will always fail the test.

This is almost true but it will pass the IS NULL test above!!!

SET ALL=PASS to get round this. (This also makes INNER JOINs into OUTER JOINs!)


Again this seems to be an unholy compromise of the original FOCUS behaviour and rdbms behaviour. This is the single most confusing element and I would say that this is a great deal of the feeling that the core product does not work.

What's needed is something like
SET JOINBEHAVIOUR=RDBMS|FOCUS
SET NULLBEHAVIOUR=RDBMS|FOCUS

Where the whole of wf table behaves in an RDBMS way!

WF is the better more logical way but there are more RDBMS's out there.

<<< End of Rant >>>


Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
Tony A
Expert
posted Hide Post
John,

Better still use SQL passthru to achieve exactly what you want without having to go around the WF code limitations. Make the RDBMS do all the work and control the environment.

T


In FOCUS
since 1986		WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10 
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     WARNING: Oracle JOIN LEFT_OUTER does not allow MISSING test on target.

Copyright © 1996-2020 Information Builders