Re: & Removal in Expressions

Gene Wirchenko wrote:
> Bernhard Sander <****hs@[EMAIL PROTECTED]
> wrote:
> 
>>>       select . . .
>>>       where;
>>>        wostatus="B" and &dateexpwo and . . .
> 
>> I think, don't worry about the & in an SQL statement. It is evaluated
only once 
>> for the whole SQL statement, not for every row examined.
>>
>> You should only worry, if you have a (fox-) loop and inside the loop
you build 
>> lots of such SQL statements which return really small result sets. Only
then the 
>> over all execution time may be affected by the &
> 
>      I sometimes have loops with SQL like this in them.
> 
>      I just wrote a re****t program that takes a little over two
> minutes to crunch the data for one test case.  Two minutes is a long
> time.  I tried a couple of likely optimisations, but there was little
> difference in execution time.
> 
>      I do not like writing ugly code, but I want my code to not be
> slow.
> 
How much data are you working with?  And how many queries?  I do find 
that it does seem to work better if I build the entire string then macro 
substitute but it looks like that is what your doing.

-- 
Cy Welch
89 Camaro RS 5.0 TBI
03 Malibu