RE: QUERY TO SQL

Sheesh, well I guess you answered my last question!  Would it really be that
hard for IBM to "enhance" RTVQMQRY to get the SQL right on joins?  After
all, isn't WRKQRY using SQL under the covers?

Dan Bale
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Vernon Hamberg
Sent: Tuesday, March 19, 2002 9:44 AM
To: midrange-l@midrange.com
Subject: RE: QUERY TO SQL


RTVQMQRY does not handle the various joins properly. Here is the text from
Query Management manual that pertains, from Chapter 12. Using Query/400
Definition Information in Query Management:

>If the acceptability of the Query/400 result depends on any of the
>following, the Query Management
>result will probably be unacceptable. Parenthesized phrases indicate the
>potentially unacceptable
>system action for each item:
>– Unmatched join with primary file (A matched join is performed)
>– Matched join with primary file (A matched join is performed)

It will never create a JOIN specification, only the older WHERE cluse
version for joins. But you can take the join criteria and convert it to the
appropriate JOIN, Query type 2 -> left outer join, type 3 -> exception join.