RE: SQL VS QUERY

[Evan Harris <spanner@xxxxxxxxxx>]

Hi Matt

you wrote

<SNIP>
>         It has been posted on this list about a query eating up a system.
> True, basic users cannot kill data using QUERY/400, but there is by default
> nothing to prevent them from chewing up all the remaining resources with a
> bad selection condition set.
</SNIP>

this is one of those statements I see from time to time that I like to
challenge :)

If someone wrote a query that outputs to a file with a production file name
and replace member *yes specified they could certainly "kill" data.

Of course an adequate security scheme would prevent this but I'd hazard a
guess that this might be a vulnerability on just a few systems

regards
Evan Harris


> You still need SQL to create views in order to give ad-hoc report users
> better reporting data in QUERY/400.  You should not expect a user outside of
> IT to know which tables to join and how to join them.
>
> Plus, since it comes with in the development package for the 400 why not use
> it.
>
> IMO, QUERY/400 is not a tool to give to end-users without putting
> restrictions on them via system parameters and objects.
>
> Thank you,
> Matt Tyler