Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Jack Chaffin
Courses Plus Student 4,462 PointsHow abstract should we get with normalization using foreign keys?
So, theoretically, you could have a separate table or each aspect of a given entry and enter them all into a more inclusive table as foreign keys. For instance, a deck of cards table with the columns of suite, color, value, etc. Each column could be filled with foreign keys here if you wanted, right? Would that be a good idea, or would it just make it hard to read?
2 Answers
Peter Vann
36,427 PointsHi Jack!
This might be a clearer and easier to understand slideshow than the previous one provided:
https://www.slideshare.net/PrateekParimal1/normalization-in-dbms
This one, too:
http://www2.cs.uh.edu/~paris/6340/PowerPoint/Normalization.ppt
I hope that helps.
Stay safe and happy coding!
Peter Vann
36,427 PointsHi Jack!
I could explain this, but I'd be reinventing the wheel.
Not only are these great explanations, but they also give graphic data to help you visualize the process better:
https://www.albany.edu/~goel/classes/fall2001/msi520/notes/normalization.ppt
https://beginnersbook.com/2015/05/normalization-in-dbms/
https://www.guru99.com/database-normalization.html
https://www.youtube.com/watch?v=xoTyrdT9SZI
https://www.youtube.com/watch?v=UrYLYV7WSHM
Overkill but great info on SQL in general:
https://www.youtube.com/watch?v=XqIk2PwP0To&t=16s
I hope that helps.
Stay safe and happy coding!