They should just play this in my lectures at university! It would have saved them 2 hours of us all wanting to fall to sleep. Thank you for explaining this in an easier-to-understand and not-so-boring way.
OMG, I took ER Diagrams from 2 years at college and I used to hate them so much. However, I started to refresh about them because of SQL and well ah I love them now. Strange how people from different parts of the world can have the same Experience! Thank you buddy for the Great Explanation!
Kudos on explaining an actual ER diagram instead of those confusing data model lookalikes most people choose (which are less abstract, and a lot of people prefer that, but easily lead to mistakes). I personally prefer listing attributes separately, beneath the ER diagram, to make it cleaner since ER is mostly about relationships and because attributes aren't really crucial for the ER part. p.s. I also hated these (on my first year), but on my fourth year when I got a serious db project, I finally understood them and started to love, well... appreciate, them.
+slothc Appreciation is good enough :) Regarding the attributes being listed separately, I wouldn't disagree with you. Especially because in the real world, the list of attributes can be enormous and muck up the visual model. Thanks for the kudos!
This was so useful, I'll never be the first one to say it but going around you-tube looking for technical minded videos can be a nightmare even when the videos really are there with the best of intent. The explanations were clear and simple,each slide was nicely separated so it never felt as though there was too much going on at any one point the voice over that was giving the explanation of the video was clear, engaged and associable *when I say this, I'm criticizing the countless videos that go on with dry, highly scripted lines that just feel abominable to listen to without breaking your own sanity(
if I understand it correctly, in the diagram at 8:00 I thnk there is a typo in the relation "has", a course has multiple lectures (it can participate in multiple "has" reln instance) but a lecture belongs to 1 course, (a lecture can be seen at most one reln instance in the "has" reln set). so, the connection labels 1 and n are not in the correct places, they should be replaced.
I'm coming from a Maths background, so bare in mind I'm new to this and could be wrong. However, in Maths it would be convention to label them differently due to them being different sets. You could have a different number of courses and users, but still have multiple of each. Therefore we are clarifying that these numbers can be different, where as if we just had both of them as M, there could be an implication that they are the same number.
@Louise cris -- UA-cam won't let me reply to your comment! Grr! In short, these diagrams are put together long before we start to worry about IDs and keys. We would start to use those concepts when creating a logical (or even physical) data model.
How many database tables do you need if you have an ER diagram of: user studies course? Do I only have a user and course table with their attributes, or do I need a 3rd table called study?
+meesie1 hello friend, I'm studying computer science probably just as you and what we do is we have 3 tables for an entity - relationship - entity it is a little expensive in the database however this system is used to know exactly what could be the worst scenario for our database if we use a relational system and how much memory we need to assign to the database
Sorry - missed your question somehow! Just like Jean said, there is a third table. In this case, it might be called UserCourseMappings or something similar. And the mapping table just contains a column for the UserId and a column for the CourseId. Together those two columns comprise a composite primary key. I believe that's the most common practice. This third table also could be used if you have attributes of the relationship itself (just make additional columns in the mappings table).
i have an entity (staff). each of the staff members are managed by zero or one staff members, except Jane Thomas who does not have a manager. The staff members may manage zero or more staff members. Attributes for the staff are (ID, Names, Sex and Age)
@ 2:50- wasn't that an example of many-to-one? many-to-one isn't listed among the types of cardinality. Can someone please help me understand this part better?
Small correction: since each course can have a varying number of lectures i.e. Kn, then under the "Lecture" entity box instead of n it should say Kn, and to the left of the "Lecture" entity box instead of n it should say (n x Kn) - since every user can watch a maximum of all the lectures in the n courses.
Hi, it's Don Hussey, the instructor. We don't use attributes on relationships nearly as often as we do on entities. But they're the same concept -- descriptors or data elements that are attached to the relationship. One example... Look at the ERD in 7:53. See the "Watches" relationship at the top-left of the diagram? Now imagine an attribute coming out of that called "In One Sitting". And for our purposes we can assume that's a Yes/No attribute that tells whether or not the User watches the Lecture in one sitting. It's an attribute of the *relationship* because it's not an attribute of the user. Neither is it an attribute of the lecture... It's an attribute of the interaction between the two. Let me know if this doesn't make sense. They're kind of wacky and seldom used.
"And we connect them to whatever Entity or Attribute they are an Attribute of" Uhh.. Did you mean Relationship? I'm taking notes so i wanted to get everything right..
I was from biology, physics, chemistry and math group in my school. I took the Information Technology course in university. No one explained this ER diagram very well and I used to hate it. I agree with this coach. I now understand it better. Thanks for the good video.
Hello guys i am going to draw an Entity relationship diagram for my website admin panel..I have only one entity in my project that is admin itself.now e.g i want to show process like admin can sends email? then how can i show this process in Entity relationship diagram? Because email is not an entity so i am little bit confuse about that.thanks
For the situation you're describing, an ER diagram won't work well. They don't illustrate processes at all. You will probably want a simple (or swim lane) flow chart.
No, but I'm sure they're out there on the Googles somewhere. Instead of thinking about flowcharts for the admin panel itself. Try to figure out what functions the admin panel enables -- those are likely going to be the processes you need to diagram in the flows.
If only there were more quality videos on UA-cam like this! Well paced, easy to understand and well narrated.
David, thanks for your kind words!
@@NorwalkAberdeen make more tutorial vids please
SOOOOOOOO helpful! You sir just summed up an entire chapter of my textbook in less than 9 minutes.
+John Hurley Awesome. Glad it's helpful!
@@NorwalkAberdeen can you help me
They should just play this in my lectures at university! It would have saved them 2 hours of us all wanting to fall to sleep. Thank you for explaining this in an easier-to-understand and not-so-boring way.
Crazy how I found this video before following Coursera's recommendation to this video! I will binge watch the rest of this!
Completely newbie here! Although it looks very complex, analogy is very simple. Everything makes sense right now. Thank you for your time!
I'm late to the party on this, but a great instructional video on UA-cam always deserves praise! Thanks a ton!
OMG, I took ER Diagrams from 2 years at college and I used to hate them so much. However, I started to refresh about them because of SQL and well ah I love them now. Strange how people from different parts of the world can have the same Experience! Thank you buddy for the Great Explanation!
THANK YOU!!!! Finally a video that makes sense and properly explains an entity-relationship diagram! Very well done!
Kudos on explaining an actual ER diagram instead of those confusing data model lookalikes most people choose (which are less abstract, and a lot of people prefer that, but easily lead to mistakes).
I personally prefer listing attributes separately, beneath the ER diagram, to make it cleaner since ER is mostly about relationships and because attributes aren't really crucial for the ER part.
p.s. I also hated these (on my first year), but on my fourth year when I got a serious db project, I finally understood them and started to love, well... appreciate, them.
+slothc Appreciation is good enough :) Regarding the attributes being listed separately, I wouldn't disagree with you. Especially because in the real world, the list of attributes can be enormous and muck up the visual model. Thanks for the kudos!
so much better and well-explained than my databases professor. thanks for making this video, appreciate it! :)
This was so useful, I'll never be the first one to say it but going around you-tube looking for technical minded videos can be a nightmare even when the videos really are there with the best of intent.
The explanations were clear and simple,each slide was nicely separated so it never felt as though there was too much going on at any one point the voice over that was giving the explanation of the video was clear, engaged and associable *when I say this, I'm criticizing the countless videos that go on with dry, highly scripted lines that just feel abominable to listen to without breaking your own sanity(
Great! Glad it's helpful!
Who else came here from the "SQL for Data Sciene" course. Week 1, additional studies.
Meee😊
@@geraldineorieoma7169 That's nice, good luck with the studies 😊
what you guys doing now ! I just started studying
Me😂
The video was very simple, clear and easy to understand. Great Job!!
exactly what i needed to hear and see to make things simpler. thanks for everything
This is soo helpful, hoping you make your videos. Your explanation is just very easy to understand
LOL, yeah, Don has a good nerd laugh. Glad you like it.
amazingly intuitive and simple to follow. Thank you. You are an extraordinary teacher.
if I understand it correctly, in the diagram at 8:00 I thnk there is a typo in the relation "has", a course has multiple lectures (it can participate in multiple "has" reln instance)
but a lecture belongs to 1 course, (a lecture can be seen at most one reln instance in the "has" reln set). so, the connection labels 1 and n are not in the correct places, they should be replaced.
Very clear and concise explanation, thank you!!
Thank you sir, This video made me understand what my prof tried to explain.
I dont even know how i made it to this video but i just learned something. Great info
I spent one hour to see some one good
But you are fantastic 🤩
Thx a lot it helps me ❤️
Thank you, dear author, you literally saved my life!
Ne za chto!
OK, you have to explain as this sounds like an amazing story.... or did you just use literally incorrectly?
Awesome. I was pretty confused in lecture about the ER Diagram. Great video.
Great! Thanks for the feedback. :)
Thank you so much. You have made it so easy to understand.
4:55 still confuses me, I mean, can we just use 'm' for both sides? Cause it still means multiple, right?
I'm coming from a Maths background, so bare in mind I'm new to this and could be wrong. However, in Maths it would be convention to label them differently due to them being different sets. You could have a different number of courses and users, but still have multiple of each. Therefore we are clarifying that these numbers can be different, where as if we just had both of them as M, there could be an implication that they are the same number.
@Louise cris -- UA-cam won't let me reply to your comment! Grr!
In short, these diagrams are put together long before we start to worry about IDs and keys. We would start to use those concepts when creating a logical (or even physical) data model.
I want to thank you a lot for this explanation.
5:37 That Laugh LOOOOOL!! its a great video though, Really helped. Thumbs up
How many database tables do you need if you have an ER diagram of: user studies course? Do I only have a user and course table with their attributes, or do I need a 3rd table called study?
+meesie1 hello friend, I'm studying computer science probably just as you and what we do is we have 3 tables for an entity - relationship - entity it is a little expensive in the database however this system is used to know exactly what could be the worst scenario for our database if we use a relational system and how much memory we need to assign to the database
Sorry - missed your question somehow!
Just like Jean said, there is a third table.
In this case, it might be called UserCourseMappings or something similar. And the mapping table just contains a column for the UserId and a column for the CourseId. Together those two columns comprise a composite primary key. I believe that's the most common practice. This third table also could be used if you have attributes of the relationship itself (just make additional columns in the mappings table).
Sweet video hopefully it will make my pass my database exam :)
Good luck!
Great video. This explains a lot.
Thank you very much sir, you really helped me on my assignment.
Clear and concise. Thank you sir!
I got so curious from the comments I had to skip forward to hear the laugh before I could concentrate lol.
Me too lol
thanks brother! Plain english is VERY helpful. BTW anyone ever tell you you sound like topher grace (eric from that 70's show)!
Glad it's helpful! And ha, no, I've never heard that until now :)
Thank you! I got over the hate significantly after watching this video😇
Is GPT right in saying it does not matter if you write M:N or N:M?
Simple and great explanation. Thanks
Wow thanks for the easy explanation !
i have an entity (staff). each of the staff members are managed by zero or one staff members, except Jane Thomas who does not have a manager. The staff members may manage zero or more staff members. Attributes for the staff are (ID, Names, Sex and Age)
not bad this sums up my first week in 9 minutes
Which books should I read to gain this kind of knowledge.
Chen style takes u- a lot of diagram space by having attributes in individual ovals, and relationships in diamonds instead of just plain lines.
That is true, and they can give the impression that the relationships are entities rather than just descriptors. Couple things to watch out for.
Thank you so much! This was exactly what I needed!
@ 2:50- wasn't that an example of many-to-one? many-to-one isn't listed among the types of cardinality. Can someone please help me understand this part better?
Anyone else here from the Coursera link?
This is a great video!
Explained in the simplest way, glad I found your video for ER diagrams.
This is really good, I'm surprise on the low number of videos
Thank you sir very imformative and clearly explained the symbols
Thank you! It was very informative and easy to understand.
very nice video. thank you for the recomendations from learn sql from data science coursera course
Much liked your method in actually identifying the Cardinality. Thanks : )
i finally understand these THANK YOU
Superb video, thank you so much.
great tutorial man, kudos!
im having trouble with the n and m what side do i use wich
Why use "n" when it can be represent as "m" ? N and M both mean "more than one" right?
Small correction: since each course can have a varying number of lectures i.e. Kn, then under the "Lecture" entity box instead of n it should say Kn, and to the left of the "Lecture" entity box instead of n it should say (n x Kn) - since every user can watch a maximum of all the lectures in the n courses.
Thats a very helpful explanation. Thanks so much!
Great Video.... So helpful....Thanks.................Seventh Morning LLC
easily understood .. thanks sir
i have followe you explanation but may you please clarify on how to list assumptions and how to write a data documentation for the ER diagram
Very helpful for A level, thank you
What about Mandatory and Optional relationships?
Simply amazing!
what about the unique identifier or primary key of each entity?
Really helpful , thank you
Can you please explain the attributes, that belong to relationships?
Hi, it's Don Hussey, the instructor.
We don't use attributes on relationships nearly as often as we do on entities. But they're the same concept -- descriptors or data elements that are attached to the relationship.
One example... Look at the ERD in 7:53. See the "Watches" relationship at the top-left of the diagram? Now imagine an attribute coming out of that called "In One Sitting". And for our purposes we can assume that's a Yes/No attribute that tells whether or not the User watches the Lecture in one sitting.
It's an attribute of the *relationship* because it's not an attribute of the user. Neither is it an attribute of the lecture... It's an attribute of the interaction between the two.
Let me know if this doesn't make sense. They're kind of wacky and seldom used.
Seventh Morning LLC Thank you very much,you really helped me a lot...
Thank you this is really clear!
Which geomatric shape is used to represent entity relationship in er diargram ?????
Many thanks, it helped me alot :)
you saved my day ...brilliant
What is the difference between m and n, why is there n in one place and m in the other?
"I actually used to hate these"😂😂
merci beacoup de votre explication claire monsieur.
Life saving :) much thanks
I know it's an old video, but does anyone know how to show a foreign key in chen notation
Good job!
What are primary and foreign keys?
you make me love them , thx bro ^_^
Awesome!
it was very good sir...thanks...
Hi. Is there many to one? Thanks.
It's same as one to many. Both are same.
Good video, thanks.
"And we connect them to whatever Entity or Attribute they are an Attribute of"
Uhh.. Did you mean Relationship? I'm taking notes so i wanted to get everything right..
good video should redo the voice when not having a cold, jea im subscribed very good content .
Excellent, thank you!
I have this shit on school, thanks for making things clear. Still very much in period of hating these tho :p
I was from biology, physics, chemistry and math group in my school. I took the Information Technology course in university. No one explained this ER diagram very well and I used to hate it. I agree with this coach. I now understand it better. Thanks for the good video.
MY 9minits not wasted
Oh my LORD, my teacher taught this badly
Thank you!
Thank You
Hello guys i am going to draw an Entity relationship diagram for my website admin panel..I have only one entity in my project that is admin itself.now e.g i want to show process like admin can sends email? then how can i show this process in Entity relationship diagram?
Because email is not an entity so i am little bit confuse about that.thanks
For the situation you're describing, an ER diagram won't work well. They don't illustrate processes at all. You will probably want a simple (or swim lane) flow chart.
yup..thnx bro...do u have any ERD or swim lane diagrame for website admin panel bro?
No, but I'm sure they're out there on the Googles somewhere. Instead of thinking about flowcharts for the admin panel itself. Try to figure out what functions the admin panel enables -- those are likely going to be the processes you need to diagram in the flows.
yes bro..thnxx again..
Thanks a lot
very helpful
Thanks
Thanks !
Coursera?
that soundtrack at the beginning woke me up
you sounded like Haymitch in the Hunger Game movie. hehe
OMG i got itttt