How to Design a Database for Harry Potter

Подписаться 56 тыс.

Просмотров 6 тыс.

50% 1

📝 Get my free SQL Cheat Sheets: www.databasestar.com/get-sql-...
🎓 Learn how to design an effective database and create it using SQL: databasestar.mykajabi.com/edd...
The world of Harry Potter and Hogwarts is fascinating and is a great example of a topic we can use to design a database.
In this video, we’ll look at the world of Harry Potter and Hogwarts and design a database that captures a range of concepts, such as students, teachers, houses, quidditch, and more.
We’ll go through each of the concepts step-by-step, creating an Entity Relationship Diagram to represent them and see how they relate to each other, to help you learn about database design and table relationships.
Timestamps:
00:00 The world of Harry Potter
00:38 Student
01:25 Teacher and subject
02:53 House
04:34 Classes
05:11 House Cup
05:59 Quidditch
09:06 Other characters
10:09 Final design and possible enhancements

Наука

Опубликовано:

26 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 31

@t3ntube357 2 года назад

I stumbled upon your channel this week, and you don't know how much it helps me, I can't thank you enough.♥

@DatabaseStar 2 года назад

I’m glad you like it! Thanks for watching my videos!

@carthai4590 Месяц назад

really good thanks for everything

@DatabaseStar Месяц назад

You're very welcome!

@PSAGrader 2 года назад

This is a fantastic resource for showing newcomers how to model a transactional database. You should follow this up with an analytical database example (facts/dimensions) using Star and snowflake schema.

@DatabaseStar 2 года назад

Thanks, I'm glad you like it! That's a good idea, I can create a video on an analytical database example.

@Olenka152 Год назад

this is absolutely amazing !!!!

@DatabaseStar Год назад

Thanks! Glad you like it

@wukaiwen3894 2 года назад

Very good example, thank you

@DatabaseStar 2 года назад

You are welcome!

@nazim9639 6 месяцев назад

Top tier content, subbed

@DatabaseStar 6 месяцев назад

Thanks!

@koko-nl5tp Год назад

Amazing!!! thank you.

@DatabaseStar Год назад

Glad you liked it!

@Adhithya2003 Год назад

Thank you good sir. Love it.

@DatabaseStar Год назад

Thanks!

@budmonk2819 9 месяцев назад

That was fun !

@DatabaseStar 9 месяцев назад

Glad you liked it!

@Millequattro Год назад

Your channel is greatly underrated

@DatabaseStar Год назад

Thanks!

@ckafrouni Год назад

Hi, really engaging video there! Is it intentional that all arrows are the same (is it one-to-many?) ?

@DatabaseStar Год назад

Thanks! Yeah that’s intentional and actually quite common. I don’t see a lot of one to one relationships in database (they can be useful but not that common) and many to many are better broken down into two one-to-many relationships.

@foureyedronin Год назад

Thank you so much for making these helpful videos. I have a question though, for the house_points is it really necessary to have an ID? If so could you please explain why?

@DatabaseStar Год назад

Thanks! Good question, no I don't think it's necessary. You could get away with not having an ID on this table.

@giakhiempham4057 8 месяцев назад

Can i have a question? why don't we add student_id to class table

@DatabaseStar 8 месяцев назад

Good question! The reason is because a student can be in many classes, and a class can have many students. If we add the student_id to the class table, then we can't store mutliple students in the same class.

@giakhiempham4057 8 месяцев назад

@@DatabaseStar Thank you a lots. I got it

@astorgadexterpelaez3502 10 месяцев назад

10 POINTS TO GRYFFINDOR!

@DatabaseStar 10 месяцев назад

Hahah!

@juanadearco6356 2 года назад

How would you fit gender and race records to such a system?

@DatabaseStar 2 года назад

For gender, I would have a separate table that lists all possible genders, and have a foreign key in the person table that links to it (e.g. person.gender_id). This is assuming a person has a single gender. For race, I would also have a separate table that lists all races. However, it depends on if we want to allow one race per person or multiple races per person. If it's multiple, we could have a joining table (called person_race or something) that stores each person_id and their races.