Re: Best Practices

[Paul Haninger <phaninge@COLUMBUS.RR.COM>]

I'll add one thought, when using table aliases
select
a.emplid
from ps_job a

use more descriptive alias names like ...

select job.emplid
from ps_job job

or...

select bp.emplid
from ps_bas_partic bp

It makes identifying where a colum variable came from deep inside an sqr
much easier to understand and debug.

Great idea for a topic!

Paul

-----Original Message-----
From: Richard McCutcheon <Richard_McCutcheon@HCM.HONDA.COM>
To: Multiple recipients of list SQR-USERS <SQR-USERS@list.iex.net>
Date: Sunday, January 31, 1999 1:13 AM
Subject: Re: Best Practices


>This is a great topic.
>
>I agree with everything that has been said so far;  descriptive variables,
>comments at the top of each SQR, and before each change, common structure
>between SQRs, use of a skeleton, etc.
>
>The only thing I can think of to add right now is that I personally like to
>use a least
>one blank line between procedures (maybe even 2 if I'm feeling up to
>it......).  I find
>that this really makes a program much easier to read.  If a program is
>easier to
>read that is a great start to being able to break it down and understand it
>better.
>
>Later.
>Richard McCutcheon
>PeopleSoft Support
>Honda of Canada MFG.