in line for one to one:

This relationship is one to one because you can't have more than 1 spouse. Right? So Spouse one can only have one spouse and spouse 2 can only have one spouse and that's all the spouses that they're allowed, so I guess that means it's one - to - one. Unless they're into that sort of thing. But for the most part, let's just assume that they aren't, and it isn't allowed. 

in line for many to many:

reflection:


What is a one-to-one database?

A: A one to one database is any database that has tables that are only relatable to another table. Just as a country can only have one capital city, a one to one relationship is when a table can only be related to another table. 


When would you use a one-to-one database? (Think generally, not in terms of the example you created).

A: A one to one database should be used whenever there's a table with unique data that needs to separated out and it doesn't make sense just to add another column. So if it looks better to move something out to a different table altogether for clarity, do it. 

What is a many-to-many database?

A many to many database is when tables can be related to more than one other table and are joined together by another table. 

When would you use a many-to-many database? (Think generally, not in terms of the example you created).

Many-to-many databases would be used if you have a table with many fields that would be relatable to another table's many fields. And then with all that overlapping, you would need a many to many database to keep track.

What is confusing about database schemas? What makes sense?

Database schemas are a little confusing when you're looking at complex ones with several tables that have different relationships but it makes sense once you stop and think about it as they're sofr of like venn diagarams or nested information. 
Add file for reflection for 8.5
Add file for reflection for 8.5
