Homework Help is Here – Start Your Trial Now!
Engineering
Computer Engineering
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

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

Computer Networking: A Top-Down Approach (7th Edition)
Computer Networking: A Top-Down Approach (7th Edition)
7th Edition
ISBN:9780133594140
Author:James Kurose, Keith Ross
Publisher:James Kurose, Keith Ross
Chapter1: Computer Networks And The Internet
Section: Chapter Questions
Problem R1RQ: What is the difference between a host and an end system? List several different types of end...
See similar textbooks
icon
Related questions
Question

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.

  1. Adding a new Professor
  2. Changing a specific Professor's Professor_Name
  3. Removing a Flub by ID
  4. Show a portfolio of the Flubs by a Professor in reverse chronological order
  5. Show how many Bounces and how many Citations a Flub of particular ID has
  6. Show a portfolio of all Flubs and Bounces (the Flubs bounced) by all of a Professor's Colleagues in reverse chronological order

(Should run in MySQL.)

The diagram is an Entity-Relationship (ER) diagram representing the relationships between different entities related to academic publications and collaborations in a university setting. Below is a detailed explanation of the components in the diagram: ### Entities 1. **Professor** - **Attributes:** - `Professor_ID` PK: The primary key uniquely identifying each professor. - `Professor_Name`: The name of the professor. - `Field`: The field of expertise or department the professor belongs to. - `College`: The college or institution associated with the professor. - `Phd_Date`: The date the professor obtained their PhD. 2. **Flub** - **Attributes:** - `Flub_ID` PK: The primary key uniquely identifying each "flub." - `Purpose`: The purpose of the flub. - `Content`: The content or subject matter. - `Moment`: The time or occasion for the flub. - `Inventor`: The creator or initiator of the flub. ### Relationships 1. **Shares** - Professors share information (possibly research papers or findings). 2. **Creates** - Professors create flubs, indicating a generative relationship between professors and their work or projects. 3. **Cite** - Represents the citing process where a professor’s work (flub) is cited, likely by other professors or in academic papers. 4. **Bounce** - Involves the entities Professor and Flub, suggesting a possible interaction or feedback loop related to academic sharing or discussion. 5. **Citations** - A concrete relationship where a professor’s work is formally cited, with references between professors and their associated flubs. 6. **Refer** - Indicates a referencing process, possibly where flubs are used as references in academic discourse. 7. **Send** - Suggests that information or work is sent, possibly indicating publication or communication between professors or institutions. ### Diagram Layout - The entities are depicted as rectangles with their respective attributes. - Diamonds represent relationships between the entities. - Lines connect entities and their relationships, illustrating the flow and interaction of information between professors and their work. - PK: Denotes primary key attributes that uniquely identify each entity in the database. This ER diagram provides a structured overview of academic interactions, focusing on the roles of professors and their contributions to academic content or "flubs." It highlights the processes of creation,
Transcribed Image Text:The diagram is an Entity-Relationship (ER) diagram representing the relationships between different entities related to academic publications and collaborations in a university setting. Below is a detailed explanation of the components in the diagram: ### Entities 1. **Professor** - **Attributes:** - `Professor_ID` PK: The primary key uniquely identifying each professor. - `Professor_Name`: The name of the professor. - `Field`: The field of expertise or department the professor belongs to. - `College`: The college or institution associated with the professor. - `Phd_Date`: The date the professor obtained their PhD. 2. **Flub** - **Attributes:** - `Flub_ID` PK: The primary key uniquely identifying each "flub." - `Purpose`: The purpose of the flub. - `Content`: The content or subject matter. - `Moment`: The time or occasion for the flub. - `Inventor`: The creator or initiator of the flub. ### Relationships 1. **Shares** - Professors share information (possibly research papers or findings). 2. **Creates** - Professors create flubs, indicating a generative relationship between professors and their work or projects. 3. **Cite** - Represents the citing process where a professor’s work (flub) is cited, likely by other professors or in academic papers. 4. **Bounce** - Involves the entities Professor and Flub, suggesting a possible interaction or feedback loop related to academic sharing or discussion. 5. **Citations** - A concrete relationship where a professor’s work is formally cited, with references between professors and their associated flubs. 6. **Refer** - Indicates a referencing process, possibly where flubs are used as references in academic discourse. 7. **Send** - Suggests that information or work is sent, possibly indicating publication or communication between professors or institutions. ### Diagram Layout - The entities are depicted as rectangles with their respective attributes. - Diamonds represent relationships between the entities. - Lines connect entities and their relationships, illustrating the flow and interaction of information between professors and their work. - PK: Denotes primary key attributes that uniquely identify each entity in the database. This ER diagram provides a structured overview of academic interactions, focusing on the roles of professors and their contributions to academic content or "flubs." It highlights the processes of creation,
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps with 2 images

SEE SOLUTIONCheck out a sample Q&A here
Blurred answer
Similar questions
Recommended textbooks for you
Computer Networking: A Top-Down Approach (7th Edi…
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Concepts of Database Management
Concepts of Database Management
Computer Engineering
ISBN:
9781337093422
Author:
Joy L. Starks, Philip J. Pratt, Mary Z. Last
Publisher:
Cengage Learning
Prelude to Programming
Prelude to Programming
Computer Engineering
ISBN:
9780133750423
Author:
VENIT, Stewart
Publisher:
Pearson Education
Sc Business Data Communications and Networking, T…
Sc Business Data Communications and Networking, T…
Computer Engineering
ISBN:
9781119368830
Author:
FITZGERALD
Publisher:
WILEY
SEE MORE TEXTBOOKS