Is it possible to have two orders for the same customer? O No, viðlates entity Integrity constraint O No, violates key constraint. O No, violates referential integrity constraint. O Yes. O No, violates domain constraints. QUESTION 8 Consider the following relational database schema. Book (BookNo, BookTitle, BookType) Orders (OrderNo, BookNo, CustomeriD, Price) Write SQL Query to Retrieve the list of customers' ID who have made at least one order for a book of type "Science", but never ordered books of type "Novel".

Is it possible to have two orders for the same customer? O No, viðlates entity Integrity constraint O No, violates key constraint. O No, violates referential integrity constraint. O Yes. O No, violates domain constraints. QUESTION 8 Consider the following relational database schema. Book (BookNo, BookTitle, BookType) Orders (OrderNo, BookNo, CustomeriD, Price) Write SQL Query to Retrieve the list of customers' ID who have made at least one order for a book of type "Science", but never ordered books of type "Novel".

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

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.
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 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 17 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) The same country name can be repeated with two different IDs in Country relation? No, violates key constraint. No, violates entity Integrity constraint No, violates domain constraints. No, violates referential integrity constraint. Yes.
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.
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.
Please answer the following relational database ques Given a relation schema R = {A, B, C, D, E} and a set of functional dependencies Σ = {CD->E, B->C, AE->B, D->AC}(1) Check if Σ implies BE->AC. Justify your answer.(2) Check if BD is a candidate key in R. Justify your answer.(3) Let Σ’ ={D->E, B->C, AE->B, D->AC}. Are Σ and Σ' equivalent? Justify your answer.
Given the following relational schema (Hint: the bold text represents a primary key), Professor(emp_num, emp_fname, emp_lname, emp_dob, dept_code, prof_ext)Class (class_code, course_code, class_section, class_time, class_room, emp_num)Course (course_code, course_name, crs_credits, dept_code) Write a relation algebra to find all "Database Design and Implementation" classes including section, time, room, and professor name (first name and last name). Hint: "Database Design and Implementation" is the course name
Subject: Database Management System Consider the following relations: PERSON(P_id,_F_name, L_name,Occupation, Salary, City) ORDER(O_id, P_id, Item, Quantity, Price, Order_date) The Primary Keys are P_id and O_id respectively. Express the following queries in SQL and Relational Algebra. a) Find the person's name and city whose name starts with S. b) Find the person with the highest salary. c) Find the average salary for each Occupation. d) Find the detail of the person who has ordered any item. e) Find the name of the person who has ordered in the same date. f) Find the game of the person who hasn't ordered any item. g) Find the highest ordered item. h) Find the detail of Item with lowest Price.
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?