David, The columns for the IN/NOT IN are NOT indexed because they both have many occurrences of the code numbers they contain. I've always thought that sort of usage was not good for indexes but I'll give it a go.
The view _should_ be straightforward enough as it effectively limits the driving table to certain rows and looks up some names - no complicated computations or conditions - but, again, I'll check it. Thanks & regards, Alastair. ----- Original Message ----- From: "David Blocker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, April 20, 2002 4:09 AM Subject: Re: Problem with select statement > Alastair > > This looks like a straightforward query, so the first place I'd check is for > problems with indexes. Are the two columns you're using for the IN and NOT > IN conditions indexed? if so, try a PACK KEYS command to rebuild indexes > and see if it helps. If they're not indexed, try indexing them and see what > happens. > > The next place I'd look is a the view definition itself. What is it? > > David Blocker > > ----- Original Message ----- > From: "Mike Young" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, April 19, 2002 7:01 PM > Subject: Re: Problem with select statement > > > > Alastair, > > > > One more thought on this. Perhaps there is some kind of limit > > on the number of items in the IN part (althought the documentation > > does not state there is). Try taking some out and see if that makes > > a difference. I don't see anything wrong with what you are doing > > though it is just longer than others that I have constructed. > > > > Best regards, > > Mike Young > > > > On Fri, 19 Apr 2002 23:24:54 +0100, Alastair Burr wrote: > > > > >Yes, Mike, they are integers and I've already tried quotes which, rather > > >surprisingly, DIDN'T fail on syntax which I expected when comparing > integer > > >to text. > > > > > >Didn't give me what I wanted either!! > > > > > >Thanks & regards, Alastair. > > > > > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
