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

Working with stored procedures

Stored procedures are the workhorses of your MySQL database. Similar to UDFs, they can run multiple SQL statements, contain the logic flow, and return the results. Stored procedures are used for situations where you want to store queries that will need to be run multiple times. For example, if a set of queries need to be run daily, they can be created as stored procedures. Where UDFs return a single result, stored procedures can return a single result, or they can return entire record sets. They are ideal for moving extensive processing tasks to a MySQL server. Imagine that you are working in a sales application that's connected to a MySQL database and you need to record a sale. Your application would record a sale by doing the following:

  • Determining the total payment amount to confirm payment:
    • Calculating the sale value (sales cost * item value)
    • Calculating the sales tax that applies to the sale
  • Subtracting the item from the inventory...