Eve,
Best to keep threads on the list. Others may have better ideas, and future
readers may benefit.
The comparison
candidate.Location IN ('CA', 'California')
will match 'CA' and 'California', but will not match 'Cupertino, CA' because
it isn't either of those strings. To match that row as w
Eve,
From your earlier post, I see it should be
resume.Candidate_ID = candidate.Candidate_ID
===
I should also point out that there are several problems with your Location
matching. You have
candidate.Location LIKE '%CA%' OR 'California'
First, this evaluates as
(candidate.Location
Hi Eve,
You have made a very common mistake while using the "comma-join" method. I
think if I translate your implicit inner join to an explicit inner join
you will spot your own mistake:
SELECT resume.Section_Value, candidate.Location
FROM resume
INNER JOIN candidate
WHERE resume.Section_ID
You have a cartesian join because you do not have join criteria between the
resume and candidate tables.
-Original Message-
From: Eve Atley
To: [EMAIL PROTECTED]
Sent: 8/17/04 12:22 PM
Subject: Assistance with SQL syntax: pulling duplicates back
I think this is an easy question...I've s
You are joining two tables, resume and candidate. Without a join condition,
you get a Cartesian product, each row of the first table paired with each
and every row of the second table. (Some on this list would go so far as to
say that's not even a join.) You need to specify how rows in resume
