Tiffany B. Brown

Relational database design explained … sort of


Click through for a larger version. The text:

It helps ensure data consistency and integrity. This may not seem important at first. But it becomes critical when you want to query or sort that data.

For example, we have three books by Toni Morrison in the database. if we stored author information in the same table, every time someone wanted to add a Toni Morrison book, they would have to type “Toni Morrison” in the author field.

That’s fine, as long as this person types well. But letters often get transposed, and some names are easy to misspell. If a user enters “Toni Morisson,” that book title won’t appear in a “Toni Morrison” search. We can help ensure data consistency with a separate authors table.

For D.

2 Responses to “Relational database design explained … sort of”

  1. Proof that I’m a nerd? This made me think back to the days when I was heavy into Access/SQL databases. And I thought, “Oh, I miss those days.” Oh boy. :D

  2. Mau says:

    Proof that I’m a nerd? Today I was daydreaming about the database(s) they probably use to track NFL games. I got caught up thinking about the “Plays” table, because so many things could happen. Multiple flags thrown – against both the offense and the defense. My conclusion was that I’d love to be a Data Analyst for an NFL Team. There. I said it. I’m a nerd.