Re: SQL select via logicals

[DAsmussen <DAsmussen@xxxxxxx>]

Vernon,

In a message dated 97-12-01 16:30:57 EST, you write:

> >> > You're safe here. Even though QQQQuery might use a different access
path
>  >>  > to improve performance, it will only return rows that are included in
>  >>  > the access path that you specify, and the columns that are returned
will
>  >>  > always be based on the view that you specify.
>  >
>  >Sorry, but I must disagree.  Interactive SQL against files to prove
queries
>  >has proven otherwise...
>  
>  To what do you disagree, the bit about rows, or the bit about columns, or
>  both? The return of rows is limited, I believe, by any S/O specs. The
>  columns available are only those that are in the logical, right?

I don't know about the columns, we have all of them specified in all logical
files.  Security in the latter instance is determined by program access.  I
disagree with the ROWS statement.  I believe that it is possible for SQL to
choose a logical other than the one specified, thus invalidating all row
selection assumptions.

>  I've not looked at Interactive SQL in a while. Do all the fields of the
>  physical appear when you prompt the SELECT clause, or only those of the
>  logical you've named?

Don't know, as I don't ever prompt for this.  IMHO, you ought to either know
enough about the database to specify certain fields, or use SELECT *...

Regards,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"If you look like your passport photo, you're too ill to travel." -- Will
Kommen
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---