Consider the following database schema for a library. Book (Book D:int, BookTitle:string(unique), Author:string, publisher:string) Borrowing-Record (Bookl D: int, CustomerCPR: int, Date: date, Time: time, Price: double) Customer (CPR:int, name: String) Is it possible to have exactly the same value for Author and publisher? No, violates referential integrity constraint. No, violates domain constraints. Yes. No, violates key constraint. O No, violates entity Integrity constraint

Consider the following database schema for a library. Book (Book D:int, BookTitle:string(unique), Author:string, publisher:string) Borrowing-Record (Bookl D: int, CustomerCPR: int, Date: date, Time: time, Price: double) Customer (CPR:int, name: String) Is it possible to have exactly the same value for Author and publisher? No, violates referential integrity constraint. No, violates domain constraints. Yes. No, violates key constraint. O No, violates entity Integrity constraint

Database Systems: Design, Implementation, & Management

11th Edition

ISBN:9781285196145

Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Publisher:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Chapter10: Transaction Management And Concurrency Control

Section: Chapter Questions

Problem 1P

See similar textbooks

Similar questions

QUESTION 4 Consider the database schema below: Company (CompnayID: integer, CompnayName: String (unique), address) Department (DepartmentID: Integer, DepartmentName: String, CompanyID: Integer) Employee (ID:integer; name:String, DepartmentID:intger (not null)) Is it valid in the department relation, that two different departments to have the same value of CompanyID?   No, violates domain constraints.   No, violates key constraint.   Yes.   No, violates referential integrity constraint.   No, violates entity Integrity constraint.
QUESTION 3 Consider the database schema below: Company (CompnayID: integer, CompnayName: String (unique), address) Department (DepartmentID: Integer, DepartmentName: String, CompanyID: Integer) Employee (ID:integer; name:String, DepartmentID:intger (not null)) Is it valid for an employee to work in two different departments?   No, violates entity Integrity constraint   No, violates key constraint.   Yes.   No, violates domain constraints.   No, violates referential integrity constraint.
QUESTION 6 Consider the database schema below: Company (CompnayID: integer, CompnayName: String (unique), address) Department (DepartmentID: Integer, DepartmentName: String, CompanyID: Integer) Employee (ID:integer; name:String, DepartmentID:intger (not null)) Is it valid in the employee relation to have the same value of DepartmentID for three different Employees?   No, violates Entity Integrity constraint   No, violates referential integrity constraint.   No, violates Key constraint.   Yes.   No, violated Domain Constraints
QUESTION 15 Consider the database schema below for hotels in countries. A country have many hotels, and the same hotel chain (name) are available in different countries. Country (ID: integer, Name: String (unique)) Hotel (CountryID: Integer, HotelName: String, ManagerID: Integer) A hotel can have unknown manager? No, violates key constraint. Yes. No, violates domain constraints. No, violates entity Integrity constraint No, violates referential integrity constraint.
QUESTION 5 Consider the database schema below: Company (ID: integer, Name: String (unique), Address) Department (No: integer (not null), CompanyID: Integer, DepartmentName: String) Is it valid for Department to have unknown No? No, violates key constraint. No, violates referential integrity constraint. Yes. No, violates entity Integrity constraint No, violates domain constraints.
Database QUESTION Consider the database schema below for cities in countries. A country have many cities, and the same city name can be found in different countries. Country (ID: integer, Name: String (unique)) City (serialNo: integer (unique, not null), CountryID: Integer, CityName: String, Population: integer) A city can have unknown CityName? No, violates domain constraints. Yes. No, violates entity Integrity constraint No, violates key constraint. No, violates referential integrity constraint.
QUESTION 7 Consider the database schema below: Company (ID: integer, Name: String (unique), Address) Department (No: integer, CompanyID: Integer, DepartmentName: String) Is it valid to have the same Company name to be repeated with two different IDs in Company relation? Yes. No, violates key constraint. No, violates entity Integrity constraint No, violates referential integrity constraint. No, violates domain constraints.
Consider the database schema below for cities in countries. A country have many cities, and the same city name can be found in different countries. Country (ID: integer, Name: String (unique)) City (serialNo: integer (unique, not null), CountryID: Integer, CityName: String, Population: integer) A city can have unknown CityName? No, violates domain constraints. Yes. No, violates entity Integrity constraint No, violates key constraint. No, violates referential integrity constraint.
QUESTION 14 Consider the database schema below for cities in countries. A country have many cities, and the same city name can be found in different countries. Country (ID: integer, Name: String (unique), SN: serialNumber (int)(unique)) City (serialNo: integer (unique, not null), CountryID: Integer, CityName: String, Population: integer) The same country (ID , name) can be added twice in Country relation with different SN? No, violates entity Integrity constraint No, violates referential integrity constraint. No, violates key constraint. Yes. No, violates domain constraints.
Consider the following relations in the relational schema for a database that keeps track of business trips of Sales Representatives in a sales office: salesperson(SSN, lName, startYear, deptNo) trip(tripID, SSN, fromCity, toCity, departureDate, returnDate) expense(tripID, accountNumber, amount) Part 1 Answer the Following 3 Questions. Places Your Answers in a Word Processor identify the primary key for each table. Identify the foreign keys in each table. Given the above foreign keys, list the order in which the tables could be successfully created. Write your Answers using a Word Processor Review the Relational Schema and other necessary material in this assignment to create the metadata document for the above relational schema. Write your Metadata using a Spreadsheet or a Word Processor. Submit the Final Version as a PDF Open up a text editor such as Visual Studio Code. Write the SQL SELECT Queries to respond to the following Information Requests Find…
Let us consider the following relational database. Students(stuID, lastName, firstName, major, gpa) Faculty(facID, name, deptName, rank) Classes(classNhmber, facID, schedule, room) Enrolls(stuID, classNumber, grade) The primary keys are underlined. The referential integrity constraints are as follows: The column facID of relation Classes that references table Faculty, The column of stuID of relation Enrolls that references table Students, and The column classNumber of relation Enrolls that references table Classes. The following SQL statement is intended to define the table Students. However, this statement does not work correctly. CREAT TABLE Students( lastName VARCHAR(20), firstName VARCHAR(20), major VARCHAR(40) gpa DECIMAL(3,2), PRIMARY KEY(stuID)); However, this statement does not work correctly. Briefly explain why and list the corrected SQL statement.
Consider the following relational database schema that contains information about employees and projects to which they are assigned. Emp (eid, lastname, gender, DOB) Assign (eid, pid, hours) Proj (pid, pname, budget, manager_eid) Answer the following questions. (a) Find two superkeys in the Proj table — both of these two superkeys should NOT be same as the primary key. You should use appropriate set notation if the superkey contains multiple attributes. (b) Suppose the Emp and Proj tables have been created appropriately. Define (i.e., create) the Assign table in SQL (Just create only one table.) You should follow all the requirements discussed in the class. (c) Suppose in the Proj table a project has changed pid from P06 to P07. From the perspective of integrity constraints, how should this modification be handled?

SEE MORE QUESTIONS

Recommended textbooks for you

Database Systems: Design, Implementation, & Manag…

Computer Science

ISBN:

9781285196145

Author:

Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel

Publisher:

Cengage Learning