Consider the following three relations. Column domain specifications are omitted for brevity. TABLE account (act# ,branch# ,owner-s sn, TABLE checking(act#,branch#,fee, balance, PRIMARY KEY(act, branch#)); PRIMARY FOREIGN KEY KEY (act, branch#), (act, branch#) REFERENCES account); TABLE savings(act, branch#, interest,minBalance, PRIMARY KEY (act#, branch) FOREIGN KEY (act#,branch#) REFERENCES account): Although not written above, you can assume that all foreign key constraints are followed by ON DELETE CASCADE and ON UPDATE CASCADE. ** One of the integrity constraints in this domain is that every account is either a savings or a checking account.** I. (a) Express this as a general SQL _assertion_ constraint. /* mySQL does not support constraint checking so you won't be able to test this * Consider the following three relations. Column domain specifications are omitted for brevity. TABLE account (act# ,branch# ,owner-s sn, TABLE checking(act#,branch#,fee, balance, PRIMARY KEY(act, branch#)); PRIMARY FOREIGN KEY KEY (act, branch#), (act, branch#) REFERENCES account); TABLE savings(act, branch#, interest,minBalance, PRIMARY KEY (act#, branch) FOREIGN KEY (act#,branch#) REFERENCES account): Although not written above, you can assume that all foreign key constraints are followed by ON DELETE CASCADE and ON UPDATE CASCADE. ** One of the integrity constraints in this domain is that every account is either a savings or a checking account.** I. (a) Express this as a general SQL _assertion_ constraint. /* mySQL does not support constraint checking so you won't be able to test this *