For the database created by prac8tables.sql, whose relation diagram (the 1st diagram there) is shown earlier on (in this prac when in the solution display mode), list enough functional dependencies implied by this relation diagram so that all the functional dependencies are either in this list or can be derived there.

1..1 VENDOR V_CODE V_NAME V_CONTACT VAREACODE V_PHONE V_STATE V_ORDER CUSTOMER CUS_CODE CUS UNAME CUS_FNAME CUS INITIAL CUS_AREACODE CUS_PHONE CUS_BALANCE 1..1 supplies CUS_ORDER ORDER_COOL CUS_CODE ORDDATETIME contains PRODUCT 9 P CODE P_DESCRIPT P_INDATETIME PLONHAND P MIN P PRICE P_DISCOUNT V _CODE 0.* ORDER_DETAIL ORDER_CODE PRODUCT_CODE QUANTITY {fk1} {fk2} L {fk } 0..* 1. * detailsin We note that the SQL script didn't directly link table CUS_ORDER with the table CUSTOMER, as the linkage was deliberately commented out. Some multiplicity constraints may not be unique due to the lack of specific business requirements at hand. Of course, w would expect the current design in the SQL script to be improved to having the missing foreign key, as roughly shown in the following diagram. VENDOR V_vode{PK} ORDER_DETAIL Order_code{PK,FK1) Product_code{PK,FK2} 1..1 PRODUCT P_code{PK} V_code{FK) CUS_ORDER Cus_order{PK) Cus_code FK} CUSTOMER Cus_code{PK} 1. 1