Consider the following relations for a database that keeps track of automobile sales in a car delarship (OPTION refers to some optional equipment installed on an automobile); CAR (Serialno, Model, Manufacturer, Price) OPTION (Serialno, optionname, Price) SALE (Salesperson_id, Serialno, Date, Sale_Price) SALESPERSON (Salespersn_id, Name, Phone)
First specify the foreign keys for this schema, stating any assumptions you make. Next, populate the relations with a few sample tuples, and then give an example of an insertion in the SALE and SALESPERSON relations that violates the referential integrity constraints and of another insertion that does not.
The foreign ids are Salesperson_id and Serialno in SALE table.
VIOLATING INSERTION:-
INSERT INTO SALESPERSON(Salesperson_id,'Name','Phone') VALUES(1,'Rajesh','9832511251');
INSERT INTO SALE(Salesperson_id,Serialno,'Date','Sale_price') VALUES(2,1,'2015-02-12','5000');
NON-VIOLATING INSERTION:-
INSERT INTO SALESPERSON(Salesperson_id,'Name','Phone') VALUES(1,'Rajesh','9832511251');
INSERT INTO SALE(Salesperson_id,Serialno,'Date','Sale_price') VALUES(1,1,'2015-02-12','5000');
REASON:- The reason is that the foreign key value must be a subset of the primary key values. The primary key values set can be either same as the foreign key values set or a superset of it for referential integrity constraints to hold true.
Consider the following relations for a database that keeps track of automobile sales in a car...
Consider the following relations for a database that keeps track of student enrollment in courses and books adopted for each course. -------------------------------------------------------------------------------------------------------- STUDENT(Ssn,Name,Major,Bdate) COURSE(Course#,Cname,Dept) ENROLL(Ssn,Course#,Quarter,Grade) TEXTBOOK(Book_isbn,Book_title,Publisher,Author) BOOK_ASSOC(Course#,Quarter,Book_isbn) ------------------------------------------------------------------------------------------------------------------------------- Having that a relation can have zero or more foreign keys and each foreign key can refer to different referenced relations. Specify the foreign keys for this schema.
2) Consider the following relations for an order processing database: CUSTOMER(Cust#, CustName, City) ORDER(Order#, OrdDate, Cust#, OrdAmount) ORDER_ITEM(Order#, Item#, Quantity) ITEM(Item#, UnitPrice) SHIPMENT(Order#, Warehouse#, ShipDate) WAREHOUSE (Warehouse#, City) Primary keys are underlined. OrdAmount is total dollar amount of an order. OrdDate is date the order was placed. ShipDate is date when order was shipped from the warehouse. An order can be shipped from several warehouses. Specify all foreign keys for this schema. For each foreign key specify referential integrity constraints...
(Taken from Exercise 5.15) Consider the following relations for a database that keeps track of student enrollment in courses and the books adopted for each course: STUDENT(SSN, Name, Major, Bdate) COURSE(Course#, Cname, Dept) ENROLL(SSN, Course#, Quarter, Grade) BOOK_ADOPTION(Course#, Quarter, Book_ISBN) TEXT(Book_ISBN, Book_Title, Publisher, Author) Draw a relational schema diagram specifying the foreign keys for this schema.
Question: Consider the following relations for a database that keeps track of student enrollment in courses and the books adopted for each course. 1- Draw an ER diagram of ONLINE COURSE REGISRATION database, that captures all the given below requirements. Specify key attribute(s) of each entity set. For each relationship set, specify structural constraints and participation constraints. a. For each USER, the portal maintains user ID, Name, E-mail. Each user has a unique ID. Name is a Composite attributes with Frame, Midname,...
Consider the following relations for course-enrollment database in a university: STUDENT(S-ID,S-Name, Department, Birth-date) COURSE(C-ID, C-Name, Department) ENROLL(S-ID, C-ID, Grade) TEXTBOOK(B-ISBN, B-Title, Publisher, Author) BOOK-ADOPTION(C-ID, B-ISBN) (a) Draw the database relational schema and show the primary keys and referential integrity constraints on the schema. (b) How many superkeys does the relation TEXTBOOK have? List ALL of them. (c) Now assume each COURSE has distinct C-Name. (i) If C-ID is a primary key, what are the candidate keys and the unique keys...
Consider the following relational database to manage concert and ticket sales. The relations are artist, concert, venue, seat, ticket, and fan. The schemas for these relations (with primary key attributes underlined) are: Artist-schema = (artistname, type, salary) Concert-schema = (artistname, date, venuename, artistfees) Venue-schema = (venuename, address, seating_capacity) Seat-schema=(venuename, row, seatnumber) Ticket-schema = (fanID, date, venuename, row, seatnumber) Fan-schema = (fanID, name, address, creditcardno) Where: • artistname is a unique name for the artist (because of trademark/copyright rules no two...
Suppose we have the following relation (R) that keeps track of car sales: R(car date_sold, salesperson#, comission_rate, discount) In addition to the functional dependency implied by the primary key (car#), assume the following functional dependencies: date_sold discount salesperson commission_rate Explain why this relation is not in Boyce-Codd Normal Form (BCNF). a. b. Show how you would normalize this relation to achieve Boyce-Codd Normal Form by drawing a new relational schema. Highlight all primary keys by underlining them and use arrows...
Assume that The Queen Anne Curiosity Shop designs a database with the following tables. CUSTOMER (CustomerID, LastName, FirstName, EmailAddress, EncyptedPassword, City, State, ZIP, Phone, ReferredBy) EMPLOYEE (EmployeeID, LastName, FirstName, Position, Supervisor, OfficePhone, EmailAddress) VENDOR (VendorID, CompanyName, ContactLastName, ContactFirstName, Address, City, State, ZIP, Phone, Fax, EmailAddress) ITEM (ItemID, ItemDescription, PurchaseDate, ItemCost, ItemPrice, VendorID) SALE (SaleID, CustomerID, EmployeeID, SaleDate, SubTotal, Tax, Total) SALE_ITEM (SaleID, SaleItemID, ItemID, ItemPrice) The referential integrity constraints are: ReferredBy in CUSTOMER must exist in CustomerID in CUSTOMER Supervisor...
Need help completing this schema below.
2. (3.14 Elmasri-6e)- Consider the following six relations for an order-processing database application in a company CUSTOMER (Cust#, Cnam City) ORDER (Orderf., Qdate Custf. QrdAmt ORDER ITEM (Order, Item#, Qty) ITEM Citen Unitaptice) SHIPMENT (Order Warehouse Ship. date) WAREHOUSE (Warehouses City) Here, Qrd Amt refers to total dollar amount of an order, Qdate is the date the order was placed; Ship.date is the date an order (or part of an order) is shipped from...
Given the following relational database schema (primary keys are bold and underlined). Answer questions 2.1 to 2.4 Orders(orderld, customerld, dateOrdered, dateRequired, status) Customer(customerld, customerLastName, customerStreet, customerCity, customerState, customer Lip OrderDetails(orderld.productld, quantity, lineNumber, amount) Products(productld, name, description, quantity, unitPrice) Account(accountNumber, customerld, dateOpened, creditCard, mailingStreet, mailingCity, mailingState, mailingZip) 2.1 (2 Points) List all possible foreign keys. For each foreign key list both the referencing and referenced relations. 2.2 (2 Points) Devise a reasonable database instance by filling the tables with data of...