0

I have a table employee in which PK is SSN and I want to make FK as Super_SSN which would refer to SSN. Before adding any data to my table, I was able to make Super_SSN as my FK, but I wasn't able to add data to Super_SSN other than the same value of SSN. Example I wanted the SSN to be 123456789, and I tried entering Super_SSN as 987654321. But I got FK constraint error. When I entered the same value for SSN and Super_SSN, it accepted it. Then, I removed the FK from Super_SSN and added data, after that I tried to add FK to Super_SSN, then I got error. Please help me with this!

Improve this question
1
  • Why would you want them to be the same? This does not make sense. Since the primary key always has to be unique why would you have a foreign key here? Unless there is something I am missing. Can you please post your tables. Commented Oct 15, 2015 at 23:22

2 Answers 2

Reset to default
1

SuperSSN has to refer to the SSN of an existing employee.

You should enter the employees in a correct order - in your example SSN 987654321 first, then SSN 123456789 with SuperSSN = 987654321.

Or enter all employees without specifying SuperSSN and update it to correct values in another command.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

You are getting the error because that FK is part of a recursive relationship. It means that an employee is related with another employee. If the second employee does not exist, then the FK constraint error appears. That's why you don't get an error when adding the same SSN. Posible solution: You can add a Super_SSN column as a simple field but not as a FK.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.