Re: How to read and or statement

Unfortunately, you can't allow the first without allowing the second.

I think I can see why one might consider the second form
misleading...but IMHO it's only because the reader would be assuming
what the rest of the SELECT looked like from the first WHEN. I prefer
to look at the code of the entire SELECT before deciding what's going
on.

Charles

On Tue, Nov 16, 2010 at 9:17 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt

With good long names and proper usage of constants, I don't
see it as being harder to read.


Consider
   SELECT;
 WHEN Customer.Type = 'A';
   ...
 WHEN  (Customer.Type = 'B'
                 or Customer.Type = 'C'
                 or Customer.type = 'D')
         and Customer.isTaxable = 'Y'
   ...
 OTHER;
   ...
ENDSL;

Charles, I don't have a problem with your example. I've also done similar things, but...

Consider
   SELECT;
 WHEN Customer.Type = 'A';
   ...
 WHEN  Customer.isTaxable = 'Y';
   ...
 WHEN  (Customer.Type = 'B'
                 or Customer.Type = 'C'
                 or Customer.type = 'D')
   ...
 OTHER;
   ...
ENDSL;

coded this way, I find it misleading.