Working with Multiple Tables
All the commands so far have operated on a single table. A database has many tables because of a concept called normalization.
Consider the books we’ve been looking at so far. A book has a title, author, and a few other elements. But an author may write more than one book, and a book may have more than one author. (We conveniently ignore the book with multiple authors scenario.)
If the row containing the book also contains the author information, we have duplicated data:
This is inefficient especially when you have to track other items about the book and author. If the author changes his address, you need to update ...