Update Operations/Dealing with Constraint Violations 

Sir?

Could u mention them here? for the sake of learning :)

@@amwalonline yeahh even I think so ...how empid could be same... won't it be a violate referential integrity

@@hrdyasham7330 No it won't, because Emp id and Pno are the keys not only the Emp id so there's no violation.

I think it violates only Key Constraints not Referential Integrity Constraints.

Maybe conflicting values since 1331 will now refer to two tuples which are supposed to be unique too

because there is already a tuple that contains the id 1330 in the foreign key so if we change the value 1330 in the key attribute to any other number, the number 1330 would not exist which violates the referential integrity and at the same the key constraint is violated because we cannot have double values in the key attribute since she attempted to modify 1330 to 1331 so we will have two tuples with the same value in the primary key which obviously violates the key constraint

In primary key it I'd not same

oh its a composite primary key of both emp_id and pno