RE: [U2] broken up SELECTS

2004-11-11 Thread Adrian Matthews
It's something I've always done over the last twenty years. The select processor in theory should apply optimisiation but I always break my statements down to reduce the working record set and to increase readability. Makes very little difference on smaller amount of records but makes a huge

RE: [U2] broken up SELECTS

2004-11-11 Thread Pingilley, Ron
statements made more sense. --Ron P. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adrian Matthews Sent: Thursday, November 11, 2004 9:27 AM To: [EMAIL PROTECTED] Subject: RE: [U2] broken up SELECTS It's something I've always done over the last twenty

RE: [U2] broken up SELECTS

2004-11-11 Thread Timothy Snyder
Adrian Matthews [EMAIL PROTECTED] wrote on 11/11/2004 10:26:48 AM: It's something I've always done over the last twenty years. The select processor in theory should apply optimisiation but I always break my statements down to reduce the working record set and to increase readability. Makes

Re: [U2] broken up SELECTS

2004-11-11 Thread Results
Ron, I frequently break up selects for readability by whomsoever will follow after me. I've managed to avoid awkward AND and OR logic - or at least limit it - by cascading selects. - Charles Readability Barouch Pingilley, Ron wrote: The UV keyword REQUIRE.SELECT makes this a possibility. On

RE: [U2] broken up SELECTS

2004-11-11 Thread Stevenson, Charles
: Thursday, November 11, 2004 7:27 AM To: [EMAIL PROTECTED] Subject: RE: [U2] broken up SELECTS It's something I've always done over the last twenty years. The select processor in theory should apply optimisiation but I always break my statements down to reduce the working record set and to increase