RE: RE: Can you do this in SQL

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: David Morris
>
> I think we agree that SQL is a shoehorn. I also think that
> opnqryf is a shoehorn. So far, I think I am the only one to
> propose a strait RPG method so since you ask, I think
> it is likely to be as good or better than any solution involving
> SQL or OPNQRYF.

Why is OPNQRYF a shoehorn?  It's a way to dynamically create a logical view
for those situations where you don't want a permanent view.  Think of it
this way: by far the easiest solution to implement would be to have a
logical on the file in descending dollar amount.  If there happened to be
such a logical file, you could skip the OPNQRYF.  However, if there isn't
one, OPNQRYF is an excellent tool.  There is nothing kludgy or shoehorn
about the ability to create a temporary logical based on runtime values.

I fail to see why a one-line OPNQRYF and four lines of RPG is a bad thing.
I mean, having opinions is one thing, but please, back them up with some
sort of concrete argument.  Lines of code would be good.  Simplicity would
be good.  Performance would be good.  "I don't like OPNQRYF" isn't a valid
reason.  The fact that programmers think it's okay to use their favorite
tool rather than the right tool is one of the reasons so much bad code gets
written.

It's just my opinion, and if you don't like it, you're in popular companys.
Hey, that's why my boss is such a jerk.

Joe Pluta
President
Pluta Brothers Design