compound primary key

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

I have this query

create table reservation(
customer_id int not null references customer(customer_id),
trip_id int not null references trip(trip_id),
seat_nb int not null
primary key(customer_id,trip_id))

where customer is a table that has customer_id as a primary key of it's own as same as trip table
now I want to make both foreign keys to stand for a primary key in reservation table
but the sql server gives this error message
"the insert statement conflict with foreign key constraint"

Posted 28-Apr-10 3:12am

fresh_girl

Updated 28-Apr-10 3:16am

Rama Krishna Vavilala

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Chris Meech · Answer 1 · 2010-04-28T04:29:00

Try the following instead

create table reservation(
  customer_id int not null references customer(customer_id)
 ,trip_id int not null references trip(trip_id)
 ,seat_nb int not null
 );

alter table reservation add primary key(customer_id,trip_id)
;

I had this work on Oracle. Should be same on SQLServer. :)