Question

I have a view which was working fine when I was joining my main table:

LEFT OUTER JOIN OFFICE ON CLIENT.CASE_OFFICE = OFFICE.TABLE_CODE.

However I needed to add the following join:

LEFT OUTER JOIN OFFICE_MIS ON CLIENT.REFERRAL_OFFICE = OFFICE_MIS.TABLE_CODE 

Although I added DISTINCT, I still get a “duplicate” row. I say “duplicate” because the second row has a different value.

However, if I change the LEFT OUTER to an INNER JOIN, I lose all the rows for the clients who have these “duplicate” rows.

What am I doing wrong? How can I remove these “duplicate” rows from my view?

---

Note:

This question is not applicable in this instance:

How can I remove duplicate rows?

Answer 1

DISTINCT won’t help you if the rows have any columns that are different. Obviously, one of the tables you are joining to has multiple rows for a single row in another table. To get one row back, you have to eliminate the other multiple rows in the table you are joining to.

The easiest way to do this is to enhance your where clause or JOIN restriction to only join to the single record you would like. Usually this requires determining a rule which will always select the ‘correct’ entry from the other table.

Let us assume you have a simple problem such as this:

Person:  Jane
Pets: Cat, Dog

If you create a simple join here, you would receive two records for Jane:

Jane|Cat
Jane|Dog

This is completely correct if the point of your view is to list all of the combinations of people and pets. However, if your view was instead supposed to list people with pets, or list people and display one of their pets, you hit the problem you have now. For this, you need a rule.

SELECT Person.Name, Pets.Name
FROM Person
  LEFT JOIN Pets pets1 ON pets1.PersonID = Person.ID
WHERE 0 = (SELECT COUNT(pets2.ID) 
             FROM Pets pets2
             WHERE pets2.PersonID = pets1.PersonID
                AND pets2.ID < pets1.ID);

What this does is apply a rule to restrict the Pets record in the join to to the Pet with the lowest ID (first in the Pets table). The WHERE clause essentially says “where there are no pets belonging to the same person with a lower ID value).

This would yield a one record result:

Jane|Cat

The rule you’ll need to apply to your view will depend on the data in the columns you have, and which of the ‘multiple’ records should be displayed in the column. However, that will wind up hiding some data, which may not be what you want. For example, the above rule hides the fact that Jane has a Dog. It makes it appear as if Jane only has a Cat, when this is not correct.

You may need to rethink the contents of your view, and what you are trying to accomplish with your view, if you are starting to filter out valid data.