Meeting 3 Notes - Database Design

Database Design: Because Tables

Today, weประกalled upon the venerable Schema Decision, a crucial step in the database design process.

After careful deliberation, we decided to go with a relational design, because who needs simplicity?

Our database will feature:

• One table for users, with columns for name, email, and favorite color.
• Another table for pets, with columns for species, owner, and treats consumed.
• And a table for favorite foods, with columns for type and rating.

These tables will be connected by the power of SQL, because,chartInstance

We also discussed the merits of using Object-Relational Mapping versus Normalization Rules.

Next meeting: Data Modeling