Consider the database schema below. Fruit (ID: integer, Name: String (unique)) Vitamin (FruitID: Integer, VitaminName: String, VitaminPercentage (not null)) A Vitami can have unknown VitaminPercentage ? Yes. No, violates referential integrity constraint. No, violates domain constraints. No, violates entity Integrity constraint No, violates key constraint.

Consider the database schema below. Fruit (ID: integer, Name: String (unique)) Vitamin (FruitID: Integer, VitaminName: String, VitaminPercentage (not null)) A Vitami can have unknown VitaminPercentage ? Yes. No, violates referential integrity constraint. No, violates domain constraints. No, violates entity Integrity constraint No, violates key constraint.

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

Create and upload a relational schema (using ERDPlus) for a database that covers the following rules: 1. Each student is advised by one faculty, and each faculty has many student advisees 2. Each faculty is affiliated with multiple departments, and a department have many faculty affiliates (note the change from class) 3. Each student is registered with many departments and each department has many registered students 4. Each department is chaired by one faculty, and any one faculty can chair only department 5. Each course is listed under one department 6. Each faculty can teach many course offerings, and each course offering can be taught by one faculty 7. Each student can take many course offerings, and each course offering will have many students
1):-In a dependant table, a__ key refrences the master table _ key a) foreign, primary b) primary, foreign c) artificial, primary d) primary, artificial 2):-When a table has no suitable _ key, the database designer speciiesa(n)__ a) primary, foreign b) foreign, primary c) primary, artificial d) artificial, primary 3):-Distinguish independant and dependent entities is a(n) __ process a) one time b) physical design c) iterative d) logical design 4):- In some ER modelling conventions, _ enities are called strong and __ entites are called weak. a) dependant, independent b) independent, dependent c) master, dependent d) dependent, master
DATABSE
QUESTION 6 Consider the database schema below. Fruit (ID: integer, Name: String (unique)) Vitamin (FruitID: Integer, VitaminName: String, VitaminPercentage) A Fruit have unknown ID? O Yes. No, violates referential integrity constraint. No, violates entity Integrity constraint No, violates domain constraints. No, violates key constraint.
QUESTION 5 Consider the following database schema for a library. Book (BookID:int, BookTitle:string(unique), Author:string, publisher:string) Borrowing-Record (BookID: int, CustomerCPR: int, Date: date, Time: time, Price: double) Customer (CPR:int, name: String) Is it possible to have two different books (with different ID) to have the same title? No, violates referential integrity constraint. Yes. No, violates domain constraints. No, violates entity Integrity constraint. No, violates key constraint. O O
QUESTION 2 Consider the database schema below. Fruit (ID: integer, Name: String (unique)) Vitamin (FruitID: Integer, VitaminName: String, VitaminPercentage) Different values VitaminPercentage can be used in two records for the same (FruitID, VitaminName ). Yes. No, violates key constraint. No, violates referential integrity constraint. No, violates entity Integrity constraint No, violates domain constraints.
QUESTION 15 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), CountrylD: Integer, CityName: String, Population: integer) A city can have unknown serialNo? O Yes. No, violates domain constraints. O No, violates key constraint. O No, violates referential integrity constraint.
Swing Jazz Club ERD Problem Follow the Simple Procedure for ERD diagramming to design an ERD using the following user provided information. Remember the ERD will eventually turn into the design for a database from a top down view. Make sure you resolve any many to many conflicts. Label an identifier or primary key and all pertinent attributes given. If an attribute is not readily apparent from the user information, then make one up that makes sense for the particular entity. Therefore, all entities should end up with at least an identifier and another attribute that makes sense. You may use any of the approaches shown by the book, though the ER-Model and Crow’s foot are the most common. Make sure you show entities, relationships, cardinality, and optionality. Swing Jazz Club The Swing Jazz Club teaches swing and jazz dancing and offers both private and group lessons. Swing Jazz charges $60 dollars per hour for a private lesson and $10 dollars per hour for a group lesson.…
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 4 Consider the following database schema for a library. Book (BookID:int, BookTitle:string(unique), Author:string, publisher:string) Borrowing-Record (BookID: int, CustomerCPR: int, Date: date, Time: time, Price: double) Customer (CPR:int, name: String) In Borrowing-Record, there are three primary keys? O True False