Write the following constraints as tuple-based CHECK constraintson one of the relations of our running movies example: M o v ies(title , y ea r, len g th , genre, studioName, producerC#) StarsIn (m o v ieT itle, movieYear, starName) MovieStar(name, ad dress, gender, b irth d a te ) MovieExec(name, ad d ress, c e rt# ,netWorth) Studio(name, ad d ress, presC#) If the constraintactually involves two relations, then you should put constraints inboth relations so that whichever relation changes, the constraintwill be checked on insertions and updates. Assume no deletions; itis not always possible to maintain tuple-based constraints
OR
OR