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
Answer:
1) ER-Diagram:-
Trending now
This is a popular solution!
Step by step
Solved in 3 steps with 3 images
