RE: Matching Records

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Wednesday, November 07, 2007 9:31 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Matching Records

actually you don't even need the correlation clause, this works too:
select file1.*, file2.*
from file1, file2

I figured that not every field would need to be printed in
the report.
I thought "select *" was generally thought to be bad form for
production queries, as it does not insulate from file layout changes.

True, in fact you'll find posts from me advocating that very position. <grin>

On the other hand, for examples or interactive testing "select *" is a lot less typing.

I just wanted to pass along the tip just in case you're weren't aware as I usually wouldn't have taken
the time to type out file1.field1, file1.field2....,file1.fieldN, file2.field1,
file2.field2....,file2.fieldN
in an example.

(In fact I didn't take the time to time the above, I copied and pasted it :)

Charles


This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.