Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!e56g2000cwe.googlegroups.com!not-for-mail
From: "Mark D Powell" <Mark.Powell@eds.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Index Range Scans....
Date: 3 Mar 2006 06:41:45 -0800
Organization: http://groups.google.com
Lines: 10
Message-ID: <1141396905.788823.290710@e56g2000cwe.googlegroups.com>
References: <1141391689.633706.102630@z34g2000cwc.googlegroups.com>
   <46r19kFc2r87U1@individual.net>
NNTP-Posting-Host: 192.85.50.1
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1141396911 10272 127.0.0.1 (3 Mar 2006 14:41:51 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 3 Mar 2006 14:41:51 +0000 (UTC)
In-Reply-To: <46r19kFc2r87U1@individual.net>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: e56g2000cwe.googlegroups.com; posting-host=192.85.50.1;
   posting-account=J7QqBQwAAABTieek3RP_669Gs2iATWzr
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:262696

Good eyes, Robert.  Failure to include all join keys is a common error
that can sometimes have interesting side effects.  Many queries because
of the where clause conditions will still return the right result set,
but do so slightly less efficiently than the query could if it was
coded correctly.  And then sometime you end up with a few extra rows
that do not get noticed in testing but eventually cause a problem that
has to be tracked down.

HTH -- Mark D Powell --