Even 7 years later, and this is still very relevant. Thank you so much for making this detailed explanation about ERDs. This is by far one of the best explanation videos I have found about this subject.
Thanks to your clear tuto about relationships, I figured out the type I needed for my diagram. As far as I understand you are teaching, your students are lucky. Although, I kept moving my mouse throughout the course thinking the annoying cursor on the screen was mine LOL! :D
you are absolutely amazing at teaching Brian, thank you so much for the great tutorial I have learnt more from this tutorial than 3 months of going to the University and studying the same subject
I know NOTHING about databases (although I'll have to learn for work), and this was super useful and incredibly easy to follow. Great content, thank you!!
Excellent video. Shows a clear way to think about this topic along with glimpses into different notation options. Very easy to follow. I did get hung up briefly on “an employee can be in many departments”. That’s not true for anyplace I’ve worked - yet it only slowed me down briefly. The rest is a lucid intro that makes intuitive sense
Thanks you Brian !! I a love this video and it will be instrumental in my success in an exam which I will be taking on May the 25th, 2022 !!! :D :D :DDDDDDDD :D
Brian! Hi! It was an awesome material and I was searching for a full course on DB and found that you have organized by number. I assume you teach this in Universities or something like that. Is there any possibility to get access to that 365 course? Thanks for this material again!
Thank you! I do not have any OLAP lectures online yet... but it is something I have considered. Until now, the field has been a moving target for undergrad courses... but I think standard practices are starting to settle in.
Hello Brian, very useful video for the start of my Ph.D.! I would like to ask you about the diagram at 21:38. Would be correct to use for three of derived tables video, book, ans magazine the primary key (and simulatiously, foreign key) - mediaKey, wouldn't be? Thanks for your answer and regards from Germany!
Thanks for your informative video! I appreciate the diagrams, but I kept trying to move my cursor out of the way and realized it was yours, not mine. LOL
Class diagrams are not generally used for database design. The concept of behavior/method, visibility, stereotypes, etc. has no context in databases. However, persistent classes in UML class diagrams can inform the database design. Also, class diagrams are not typically normalized; when they are ported to relations, they need to be normalized. My UML class diagrams videos explain more about how class diagrams are used in systems analysis and design.
@@BrianGreenNJ True it’s how I modelled a system way back in 2000 in my degree. It covers Object Models, Classes,Use cases, Actors etc. The final design was used the next year for a project to build the database. This was still in use at least 3 years after it was built. So the Objects were built, the attributes stored, the use cases programmed etc. Of course as it was just the design and not the implementation model it had to be adapted to work in Java. It matched pretty well.
GOOD VIDEO: Speaking as a member of the Peoples Popular Front against the Vilification of 'nulls' ... Nulls can be legitimate when there is latency between creating an entity with a latency on getting the full data. The trick is normalise the data and treat nulls as data that is unknown, but pending. Defaults can be used if necessary
Hey maybe you stated it in wrong way or I'm not getting it at 24:14. Should not it be like this way "An employee can exist in one or many departments and a department can have one or many employees". Because if department have zero employee then that means that department does not exist. Please somebody clear it to me
I believed that’s addressed in this video. The physical database, if it’s relational, can not have many-to-many relationships. There is a section that shows how an additional table must be added to support logical many-to-many relationships.
