On 03 Oct 2013 13:32, Hoteltravelfundotcom wrote:
I removed the <ed: predicate T01.OHOSTC = > 'CL' in the WHERE but
this didn't help.
Interesting tho. I then removed the other <ed: predicate in the
WHERE-clause; T01.OHORDD >= 20120101> ( the date) and now it doesn't
fetch a bunch of columns.
Apologies for the last empty message... some unknown sequence of
accidental keystrokes caused my NewsReader client to send the message
The LEFT OUTER JOIN will generate the NULL value for the columns of
unmatched rows. That is its function; i.e. the /fetched/ data for those
columns was the NULL value that was generated.
Rob gave an example of a simplified query, in a prior message, that
uses a predicate specific to selecting the order-number of interest from
the primary file; that could replace the other predicates in the WHERE
clause to make a very specific test.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact