Based on the following Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors --------- Create the Relational Model for the Flubber database based upon your ER Diagram above, meeting all the same requirements. Include all necessary Primary Key and Foreign Key constraints. This should be syntactically correct to test in a MySQL database.

Based on the following Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors --------- Create the Relational Model for the Flubber database based upon your ER Diagram above, meeting all the same requirements. Include all necessary Primary Key and Foreign Key constraints. This should be syntactically correct to test in a MySQL database.

Oracle 12c: SQL

3rd Edition

ISBN:9781305251038

Author:Joan Casteel

Publisher:Joan Casteel

Chapter1: Overview Of Database Concepts

Section: Chapter Questions

Problem 3MC

See similar textbooks

Similar questions

Based on: Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Show the Relational Algebra AND Domain Relational Calculus formulas for each. Show a portfolio of the Flubs by a Professor Show a portfolio of all Flubs and Bounces (the Flubs bounced) by all of a Professor's Colleagues
Based on: Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Create the SQL for a single View called "Flubbergasting" of a Professor which includes all attributes from Entity-Relationship Diagram, as well as how many Flubs, the average number of Bounces the Flubs had, and total Citations across all Flubs by that professor.
Based on the following Entity-Relationship Diagram with the following requirements: There are Professors (ie users) with the changeable attributes Professor_Name, Field, College, PhD_Date There are Flubs (ie posts) with the unchangeable attributes Content, Purpose, Moment, Inventor (which is the creating Professor) There are Bounces (ie shares) where a Professor can share another Professor's Flub Add ID attributes as necessary Content of Flubs only needs to be a text of fixed length Professors can have/be Colleagues (ie friends/followers) A Flub can get Citations (ie likes) by other Professors Write the necessary SQL Queries for the following functions. Adding a new Professor Changing a specific Professor's Professor_Name Removing a Flub by ID Show a portfolio of the Flubs by a Professor in reverse chronological order Show how many Bounces and how many Citations a Flub of particular ID has Show a portfolio of all Flubs and Bounces (the Flubs bounced) by all of a Professor's…
Which of the following is a key part of conceptual design in an entity relationship model? This model uses column names instead of attributes. In this model, the characteristics such as location, path, and format are described. This model converts entities into tables. In this model, no primary keys are specified in the entities.
Construct Entity Relationship Diagram (ERD) for the scenario given. Include all the actual andassociative entities, attributes of each entity assuming the primary key, foreign key and not nullconstraints, relationship between the entities with cardinality constraints. Use Crow's FootNotation. State any assumptions necessary to support your design. Royal Oman Police inspects their vehicles for keeping them tuned up. Every vehicle isidentified by Vehicle Identification Number, make, model and engine capacity. There is apolice owner for all vehicles who drives vehicles. The police owner is identified by police ID,name, office location and mobile number. Each police will have one vehicle and every vehiclewill be driven by only one police. Some Vehicle requires to be inspected every year. Thedepartment requires to record the details of inspection with attributes inspectionID, date,and results. Each inspection will require atleast 1 inspector who will do different tasks oneach inspection.…
Illustrate an Entity-Relationship Diagram (ERD) model using Crow’s Foot notation Here we can have the following entities 1.patients:this entity will store the details of the patients and the attributes for this entity is id(which is unique for each patient and can be used as a primary key) name(this attribute will store the name of the patient and it is a composite attribute) address(this attribute will store the address of the patient and it is multi valued attribute. ) contact_num(this is also a multi valued attribute which will store the contact details of the patient). age(which is a derived attribute) 2.room:this entity will store the information about the details of the rooms. The attributes are. id(this is unique for each room and can be used as a primary key) room number(this will store the room number) Total_bed(this will store the total number of beds present in that room) 3. Bed:this entity will store the information regarding to each bed present in an room, and the…
Prepare a Crow’s Foot Entity Relationship Diagram for the application described in the following paragraph. Many-to-Many relationships should be broken into two 1-to-Many relationships using a bridge entity. Label PK attributes and FK when applicable. For each entity, you need to define a primary key. If there is a relationship between two entities make sure you define the corresponding foreign key in the child table. Seneca Sandlot Baseball is a recreational baseball league for Seneca students. The league has different divisions for different skill levels. Each player’s skills are evaluated and the player is assigned to a division. A team is made up of many players from the same division, and a coach. A player may play on only one team in the league. Each division is made up of many teams. A coach may coach teams in more than one division , but can only coach one team in each division. A coach may not play on any team in the league. A season is twelve weeks in length.…
An instructor has several phone numbers. When reducing the ER diagram down to a schema this must be addressed. Which of the following statements are true? a. an instructors phone is what is known as a multi-valued attribute b. a multi-valued attribute of an entity is expressed as a separate schema with attributes including the primary key of the original entity and the multi-valued attribute c. the instructor should have a column for each type of phone number d. multi-valued attributes must be flatted out to a separate attribute for each component
Develop ERD (Entity Relationship Diagram) for one of the following two scenarios. NOTE: No further details were provided by the professor. The diagram can be drawn by hand also if preferred. Option1: A customer who goes to a grocery shop generates one invoice each time s/he goes to the grocery. Customer data to capture includes ID, FirstName, LastName, City, State, CreditLimit. An invoice should capture the data on InvoiceID, SaleDate, SalesPerson, and Amount. Provide a conceptual ERD for this transaction scenario. Option 2: One sports team consists of many players, and one player can belong to one sports team at a time. Sports team data should have TeamID, TeamName, CoachName, memberNumbers, City, State, owner, TeamValue. Each player can be represented with PID, Name, Address, PhoneNo, Position, weight, height, Value, and Scores. Provide a conceptual ERD to develop a database.
When mapping generalisations and specialisations in enhanced entity relationship diagrams, which solution will deliver the least redundancy and allow representation of the most specialisation types. Select one: a. Multiple relations representing subclass entities only. b. A single relation containing a type attribute. c. Multiple relations representing both superclass and subclass entities. d. A single relation with multiple boolean type attributes.
Suppose that we wish to keep a genealogy. The information we wish to record about each person includes their name, date of birth, phone number, and degrees obtained . We also need to keep track of the mother, father, and children of each person. Draw a complete Entity-Relationship diagram. You must include all the details, sad as keys, weak entities (if any), cardinality constraints, etc. Your diagram must avoid redundancy.
Unified Modelling Language (UML) is often used as a notation when drawing Entity-RelationshipDiagrams (ERDs) since it is a notation that software developers are already familiar with. What is the difference between a binary relationship and a unary relationship?Provide an example of each as part of your answer. Draw an Entity Relationship Diagram (ERD) using Unified Modelling Language(UML) notation according to the below business rules. Your design should be atthe logical level – include primary and foreign key fields and remember toremove any many-to-many relationships.Legal system – business rules:• In the legal system, a judge hears many cases throughout their career.• Each case can be heard by multiple judges in some circumstances.• A case has a date and title that needs to be recorded in the database.• The name and surname of each judge needs to be stored.• A judge can have multiple qualifications (with minimum of one), and eachqualification is related to only one specific judge.•…