Database Design: StackOverflow (Q&A Site)

[@DatabaseStar]

Want to improve your database design skills? Get my Database Design project Guides here (diagrams, explanations, and SQL scripts): www.databasestar.com/dbdesign/?

[@blets3329]

You've by far the best database design content on UA-cam

[@DatabaseStar]

Thanks!

[@NotAllHeroesWearCapes-101]

this is super cool. Thanks I do recommend to add those missing features. Those adds complexities and are great for understanding deeper concepts.

[@DatabaseStar]

Thanks! Sure I’ll look at expanding this to add those concepts

[@chinmoykr]

In this diagram you can mark every posts as accepted answer, including a question because question is also a post. So it is better to create separate tables for question and answer. Also in stack overflow you can add tags to a question but not to an answer.

[@DatabaseStar]

That's a good point about having separate tables to solve that problem!

[@vishalpoddar]

should not the post and the accepted-answer-id have 1 - 1 relationship? 8:33

[@DatabaseStar]

Yes, that would probably work better, as a post can only have one accepted answer.

[@vishalpoddar]

@@DatabaseStar Thanks.

[@PitZza143]

I like the way you construct the relationship.

[@DatabaseStar]

Thanks!

[@falseloop]

Please Make A tutorial on social media website, I know you have a video on this but please make a detailed social media database design like reddit , Thank You

[@DatabaseStar]

Good idea!

[@shivanikowkuri7850]

Can you explain how to create a database of credit card management system,i got this project but got stucked in the middle... your videos helped me a lot in understanding database

[@DatabaseStar]

You can check out my other video on creating a database design from requirements or an idea. That should help get you started.

[@nanohetube]

cool

[@ShreeharshaV]

Thanks for the great video. I have a question wrt one of the requirement - "Users can add comments to questions and answers". Can we not design it this way : Comment Table : id (PK), commentText, createdDate, createdByUserId (FK) and then PostComment table : id, postId (FK), commentId (FK) and AnswerComment table : id, answerId (FK), commentID(FK). Let me know your thoughts on this if this is a wrong design. Thanks

[@ShreeharshaV]

Tried to have many to many relationship between comment and post, and then comment and answer.

[@DatabaseStar]

Thanks! Yes that design could work, however in the design in the video, a Post can be either a Question or an Answer, so having a separate AnswerComment table may not be ideal (you would have to somehow ensure it only links to posts that are answers).

[@codingSeller]

thanks, fantastic contents🥰

[@DatabaseStar]

You’re welcome 😊

[@khumbomunsaka]

Have you thought about creating a discord server?

[@DatabaseStar]

Yeah, I actually plan on creating a community for my Academy members a little later this year.

[@kx01]

@@DatabaseStar Can we have more DB design videos? :') Like Design a car rental system, movie ticket booking, hotel room booking etc. I am glad after searching through internet for db design I stumbled upon your channel and I must say it is good. I looked into youtube most of the contents are related to OOD, LLD, HLD or some of the videos talking about db design when discussing HLD but not into depth or no dedicated videos on DB design.
You are a gem sir