The following tables form part of a database held in a Relational Database Management System for a printing company that
Posted: Thu Jun 02, 2022 7:52 am
company that handles printing jobs for book publishers: Publisher BookJob (publD, pubName, street, city, postcode, telNo, creditCode) (jobID, publD, jobDate, description, job Type) Purchase Order (jobID, polD, poDate) POltem (jobID, polD, itemID, quantity) Item (itemID, description, onHand, price) contains publisher details and pubID is the key. CreditCode refers to CR for Credit, CA for Cash, CH for Check) contains details of the printing jobs (books or part books) and jobID is the key. A printing job requires the use of materials, such as paper and ink, which are assigned to a job via purchase orders. This table contains details of the purchase orders for each job and the key is jobID/polD. Each printing job may have several purchase orders assigned to it. Each purchase order (PO) may contain several PO items. This table contains details of the PO items and jobID/polD/itemID form the key. contains details of the materials which appear in POltem, and the key is itemID. List all publishers in alphabetical order of name. List all printing jobs for the publisher 'Gold Press'. List the names and phone numbers of all publisher who have a rush job (jobType = 'R'). List the dates of all the purchase orders for the publisher 'PressMan'. (Assume that you have a publisher 'PressMan'). How many publisher fall into each credit code category? List all job type's with at least three printing jobs. List the average price of all items. List all items with a price below the average price of an item. Where: Publisher BookJob PurchaseOrder POltem Item Instructions: Formulate the following queries using SQL: (i) (ii) (iii) (iv) (v) (vi) (vii) (viii)
The following tables form part of a database held in a Relational Database Management System for a printing