Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

SQL entries with duplicate primary keys

Hello,
The SQL database I'm working with is behaving strangely. There are a couple of issues, but the main one I want to ask about is what appears to be duplicate entries. I have two tables, order_items and riders. The primary key for the order_items is porder_item, and it is meant to be unique. When I query the database for results from order_items for a particular porder_item, I get one result. When I query for results from order_items inner joined with riders, I get two results, with the same porder_item. The new result row appears to be taken in part from a row that has a different porder_item value when querying the order_items table alone. I've checked my code, and porder_item is never explicitly set, just auto incremented. My first question is: Is this more likely to mean that the data is being inserted incorrectly somehow, or that it's OK but being retrieved incorrectly? My second question is: is this a symptom of a larger problem with the database, or is it more likely to be a code error somewhere?
0
bucky42
Asked:
bucky42
  • 5
  • 2
  • 2
1 Solution
 
CMYScottCommented:
the results of the joined query are normal IF you have two rows in riders that have the same porder_item value (or are linked to the same row that contains that porder_item value)

Given that the results are correct for the database (that does not mean you are getting what you WANT - but that you are getting what you are asking SQL for) - I don't believe its an indication of anything wrong with your database.
0
 
fesnyngCommented:
>>My first question is: Is this more likely to mean that the data is being inserted incorrectly somehow, or that it's OK but being retrieved incorrectly?<<

Most likely your JOIN is causing the dup.

The following should confirm if you have duplicate Primary Keys on porder_item.  If you see anything other than 1 for xcnt, then you have duplicate porder_item keys.

SELECT porder_item., count(*) as xcnt from dbo.d
GROUP BY porder_item.
ORDER BY xcnt DESC
0
 
bucky42Author Commented:
The query above returns 1, so it appears that there isn't a dup in the database. But how can an inner join produce a dup result?

If this is my query

SELECT * FROM Rider r INNER JOIN Order_Item o ON r.fk_category=o.fk_category WHERE o.porder_item=XXXX;

where does that extra result come from?

0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
CMYScottCommented:
your join is going to bring back all combinations of rows where Rider.fk_category and Order_Item.fk_category have the same value.

so if you have one row in Order where fk_category has a value of 1000
but you have 2 rows in Rider where where fk_category has a value of 1000

the inner join is going to return
-- the combination of the single-row result in Order with the FIRST row-result in Rider
AND
 -- the combination of the single-row result in Order with the SECOND row-result in Rider


0
 
fesnyngCommented:
CMYScoot is on it.

You can determine which rows in by changing the above query a little.

BTW, if you have not guessed, I use the query below exactly for the purpose of figuring out why I have dup rows in a join when there are not "supposed" to be any dups. (And thanks for catching my copy & paster error in the earlier version).

SELECT fk_category., count(*) as xcnt from Rider
GROUP BY fk_categorym.
ORDER BY xcnt DESC
0
 
bucky42Author Commented:
Aaah, so I need to join on a column which is unique for both tables to get a unique result. That makes sense.
0
 
bucky42Author Commented:
or where the WHERE clause eliminates any unwanted rows; so there must be a WHERE clause acting on any column of a table that has multiple values for something being joined on.
0
 
bucky42Author Commented:
No, scratch that last part. The WHERE clause has to be on something OTHER than the column with multiple rows in the join, since obviously all those rows would satisfy the WHERE clause if it were on them.
0
 
bucky42Author Commented:
Thanks! This revealed a major flaw in my understanding of inner joins.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now