Book Image

The MySQL Workshop

By : Thomas Pettit, Scott Cosentino
5 (1)
Book Image

The MySQL Workshop

5 (1)
By: Thomas Pettit, Scott Cosentino

Overview of this book

Do you want to learn how to create and maintain databases effectively? Are you looking for simple answers to basic MySQL questions as well as straightforward examples that you can use at work? If so, this workshop is the right choice for you. Designed to build your confidence through hands-on practice, this book uses a simple approach that focuses on the practical, so you can get straight down to business without having to wade through pages and pages of dull, dry theory. As you work through bite-sized exercises and activities, you'll learn how to use different MySQL tools to create a database and manage the data within it. You'll see how to transfer data between a MySQL database and other sources, and use real-world datasets to gain valuable experience of manipulating and gaining insights from data. As you progress, you'll discover how to protect your database by managing user permissions and performing logical backups and restores. If you've already tried to teach yourself SQL, but haven't been able to make the leap from understanding simple queries to working on live projects with a real database management system, The MySQL Workshop will get you on the right track. By the end of this MySQL book, you'll have the knowledge, skills, and confidence to advance your career and tackle your own ambitious projects with MySQL.
Table of Contents (22 chapters)
1
Section 1: Creating Your Database
6
Section 2: Managing Your Database
11
Section 3: Querying Your Database
16
Section 4: Protecting Your Database

SQL queries to create indexes and foreign keys

When working in MySQL, we will often have multiple tables, containing multiple datasets. These datasets are often related to each other in some way, typically with a common field between them. For example, if we had a table of customers, each customer might have a customer ID. From here, we may have a table of orders that contains the customer ID of the person who ordered it. We can relate these two tables using the customer ID field that they both share.

This type of relationship is called a foreign key relationship. To help to define these relationships, MySQL allows us to specify them at the time of creating a table. This creates a relationship between the two tables. The main advantage of this is that we can enforce policies for the foreign keys. For example, suppose we wanted to change a customer ID in our customer table. It will, in turn, make sense that we want to update the same customer ID in every other table that it appears...