Re: Outer join syntax

This is great news. IMHO in addition to supporting new ANSI syntax (which separates join conditions from filter conditions-- cleaner and clearer), it is more desireable, as well as easier, to avoid intermediate tables when using OUTER to do things like finding rows in a table that have no corresponding rows in a subservient. I'm glad to see Informix now turning their attention to updating the actual SQL component of their products. Informix SQL has seemed to be frozen in time. I've asked about some of these things at Informix Training classes, and invariably the instructors are unfamiliar with changes in SQL standards that have occurred during the last decade or so, and have had no information on Informix's plans to comply. Thanks for info, Art. Art, do you know whether there will be a general, wholesale updating of SQL? I'm thinking of other things than the new ANSI syntax, for instance enhancements to take advantage of new (well, within last 7 years or so) knowledge showing updateable views are much more practical than previously thought. It just seems that Informix SQL could stand some "freshening" and it sounds like Art is indicating that might be occurring. Bravo. David Grove State of Alaska Art S. Kagel wrote in message <3675462C.B15@bloomberg.net>... >BTW The new syntax will allow some interesting things to be done that >were impossible in a single SELECT statement before, like selecting >only those rows from the OUTER join result set where the subservient >table had no rows (ie find where no match). Current syntax requires >a sub-query or a temp table. > >Art S. Kagel