How to Design a Database for Harry Potter

[@t3ntube357]

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

[@DatabaseStar]

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

[@RedmondGamer]

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]

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

[@carthai4590]

really good thanks for everything

[@DatabaseStar]

You're very welcome!

[@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.

[@astorgadexterpelaez3502]

10 POINTS TO GRYFFINDOR!

[@DatabaseStar]

Hahah!

[@nam9338]

What application you used to draw the database diagram?

[@DatabaseStar]

I used Lucidchart

[@giakhiempham4057]

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

[@DatabaseStar]

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]

@@DatabaseStar Thank you a lots. I got it

[@wukaiwen3894]

Very good example, thank you

[@DatabaseStar]

You are welcome!

[@nazim9639]

Top tier content, subbed

[@DatabaseStar]

Thanks!

[@budmonk2819]

That was fun !

[@DatabaseStar]

Glad you liked it!

[@Olenka152]

this is absolutely amazing !!!!

[@DatabaseStar]

Thanks! Glad you like it

[@juanadearco6356]

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

[@DatabaseStar]

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.

[@Millequattro]

Your channel is greatly underrated

[@DatabaseStar]

Thanks!

[@Adhithya2003]

Thank you good sir. Love it.

[@DatabaseStar]

Thanks!

[@koko-nl5tp]

Amazing!!! thank you.

[@DatabaseStar]

Glad you liked it!

[@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.