6. When defining the Foreign Key constraint (see the partial code given below), why we only specify "ON DELETE" and/or "

Business, Finance, Economics, Accounting, Operations Management, Computer Science, Electrical Engineering, Mechanical Engineering, Civil Engineering, Chemical Engineering, Algebra, Precalculus, Statistics and Probabilty, Advanced Math, Physics, Chemistry, Biology, Nursing, Psychology, Certifications, Tests, Prep, and more.
Post Reply
answerhappygod
Site Admin
Posts: 899603
Joined: Mon Aug 02, 2021 8:13 am

6. When defining the Foreign Key constraint (see the partial code given below), why we only specify "ON DELETE" and/or "

Post by answerhappygod »

6 When Defining The Foreign Key Constraint See The Partial Code Given Below Why We Only Specify On Delete And Or 1
6 When Defining The Foreign Key Constraint See The Partial Code Given Below Why We Only Specify On Delete And Or 1 (108.96 KiB) Viewed 45 times
6. When defining the Foreign Key constraint (see the partial code given below), why we only specify "ON DELETE" and/or "ON UPDATE" but do not specify "ON INSERT"? Explain. [1 mark] CREATE TABLE EMPLOYEE ( FOREIGN KEY(Dno) REFERENCES DEPARTMENT(Dnumber) ON DELETE SET DEFAULT ON UPDATE CASCADE) ;
Join a community of subject matter experts. Register for FREE to view solutions, replies, and use search function. Request answer by replying!
Post Reply