How to Create and Use MySQL Views

Reading Time: 6 minutes

What is a MySQL View?

A MySQL view is simply an ordinary database object that can save SQL query writers a lot of time when used correctly. A view is a stored query that a user can reference just like a table. Many times users will find themselves using the same base query over and over to solve multiple problems. Views are a way of quickly saving that query and referencing it later.  

What are the Advantages of Using Views?

Views have several advantages. First, views appear to the MySQL user just like a table. The SELECT clause can reference a view precisely like it would a table. Another advantage is that when the underlying tables referenced by a view change, the view’s results also change. A third advantage is that a view takes up very little space on the server. The view’s SQL results are calculated every time it is accessed, so they are not stored on the server until they are accessed.

Tables for this Exercise

For this article, a database will be created containing information about a fictional car racing season featuring three drivers, four tracks, and one race on each track. In this database, there are four tables.

  • Drivers
  • Tracks
  • Races
  • Finishes    

The structure for the tables is as outlined below.


create table drivers
(
  id int auto_increment,
  name varchar(64) not null,
  car_number int not null,
  constraint drivers_pk
     primary key (id)
);
create table tracks
(
  id int auto_increment,
  name varchar(64) not null,
  location varchar(64) not null,
  constraint track_pk
     primary key (id)
);
create table races
(
  id int auto_increment,
  name varchar(64) not null,
  track int not null,
  distance int not null,
  constraint races_pk
     primary key (id)
);


create table finishes
(
  id int auto_increment,
  driver int not null,
  race int not null,
  position int not null,
  constraint finishes_pk
     primary key (id)
);

Drivers

Now, in our next step, we will insert three drivers and their car numbers into a table.

  • Buddy Baker 28
  • Dale Earnhardt Jr. 8
  • Ricky Rudd 88
insert into drivers (name,car_number) values
  ('Buddy Baker',28),
  ('Dale Earnhardt Jr.',8),
  ('Ricky Rudd',88);

Our results will now show the following output.

IDNameCar Number
1Buddy Baker28
2Dale Earnhardt Jr.8
3Ricky Rudd88

Racetracks

Next, we add four racetracks and their location.

  • Talladega Superspeedway – Lincoln, AL
  • Daytona International Speedway – Daytona Beach, FL
  • Indianapolis Motor Speedway – Speedway, IN
  • Michigan International Speedway – Brooklyn, MI
insert into tracks (name,location) values
  ('Talladega Superspeedway','Lincoln, AL'),
  ('Daytona International Speedway','Daytona Beach, FL'),
  ('Indianapolis Motor Speedway','Speedway, IN'),
  ('Michigan International Speedway','Brooklyn, MI');

Our results will now show the following output.

IDNameLocation
1Talladega SuperspeedwayLincoln, AL
2Daytona International SpeedwayDaytona Beach, FL
3Indianapolis Motor SpeedwaySpeedway, IN
4Michigan International SpeedwayBrooklyn, MI

Races

Now, four races, along with the distance for each, are entered.

  • Daytona 500 ,2,500
  • Talladega 500,1,500
  • Brickyard 400,3, 400
  • Michigan 400 ,4, 400
insert into races (name,track,distance) values
  ('Daytona 500',2,500),
  ('Talladega 500',1,500),
  ('Brickyard 400',3,400),
  ('Michigan 400',4,'400');

Our results will now show the following output.

IDNameTrackDistance
1Talladega 5002500
2Daytona 5001500
3Brickyard 4003400
4Michigan 4004400

Results

Finally, the tables for the beginning of the season are now created.

In the first race at the Daytona 500:

  • Ricky Rudd finishes first
  • Dale Earnhardt Jr finishes second 
  • Buddy Baker finishes third. 
insert into finishes (driver, race, position) values
  (1,1,3),
  (2,1,2),
  (3,1,1);

Compiled Data

First Data Input

Now there is actual data to query. If we run a query to look at all driver results with their corresponding tracks and races, it is a bit complicated as there are several joins. 

select d.name as driver,
     r.name as race,
     t.name as track,
     t.location as location,
     f.position as position
  from finishes f
  left join races r
     on f.race = r.id
  left join tracks t
     on r.track = t.id
  left join drivers d
     on d.id = f.driver;

Our results now show the following output.

DriverRaceTrackLocationPosition
Buddy BakerDaytona 500Daytona International SpeedwayDaytona Beach, FL3
Dale Earnhardt Jr.Daytona 500Daytona International SpeedwayDaytona Beach, FL2
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1

Second Data Input

As the second race, the Talladega 500, data is added, the query could be written again, the same as the earlier query. In this race, Dale Earnhardt comes in first, and Buddy Baker comes in second.

insert into finishes (driver, race, position) values
  (1,2,2),
  (2,2,1),
  (3,2,3);

The results of the above query would look like this.

DriverRaceTrackLocationPosition
Buddy BakerDaytona 500Daytona International SpeedwayDaytona Beach, FL3
Dale Earnhardt Jr.Daytona 500Daytona International SpeedwayDaytona Beach, FL2
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Buddy BakerTalladega 500Talladega SuperspeedwayLincoln, AL2
Dale Earnhardt, Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1
Ricky RuddTalladega 500Talladega SuperspeedwayLincoln, AL3

Create View

Now that there are multiple races in the database, there are new ways of looking at the results.  Queries can be written for “Best Finish” and “Most Wins.” These queries would all begin with the same underlying data of what drivers finished in each race’s position. To simplify the process of developing these queries, a view can be created with the “create or replace view as” a clause. This clause is followed by the SQL that is to be saved. In this case, it is added before the previous query that we showed above.

create or replace view all_finishes as
select d.name as driver,
     r.name as race,
     t.name as track,
     t.location as location,
     f.position as position
  from finishes f
  left join races r
     on f.race = r.id
  left join tracks t
     on r.track = t.id
  left join drivers d
     on d.id = f.driver;

The result is a powerful feature of SQL. This result is now something that looks like a table but will change when new information is added to any underlying table. Let’s run this query.

select * from all_finishes;
DriverRaceTrackLocationPosition
Buddy BakerDaytona 500Daytona International SpeedwayDaytona Beach, FL3
Dale Earnhardt Jr.Daytona 500Daytona International SpeedwayDaytona Beach, FL2
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Buddy BakerTalladega 500Talladega SuperspeedwayLincoln, AL2
Dale Earnhardt, Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1
Ricky RuddTalladega 500Talladega SuperspeedwayLincoln, AL3

The results are identical to the last time we ran this query:

The difference is that now the view can be queried like a table. A query that shows the winners of each race.

select * from all_finishes where position = 1;

The query provides these results.

DriverRaceTrackLocationPosition
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Dale Earnhardt, Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1

A query can also be written to display the leader based on average finish.

select avg(position) as finish,
  driver
from all_finishes
  group by driver
     order by finish;

Which shows Dale Earnhardt in the lead so far for the season:

FinishDriver
1.5Dale Earnhardt, Jr.
2.0Ricky Rudd
2.5Buddy Baker

Because views can reference other views, more extensive views can be created with these queries.

create view standings_leader as
select avg(position) as finish,
  driver
from all_finishes
  group by driver
     order by finish;

The results of the above query would look like this.

FinishDriver
1.5Dale Earnhardt, Jr.
2.0Ricky Rudd
2.5Buddy Baker

As well as:

create view race_winners as
select * from all_finishes where position = 1;

Which provides us the same results.

DriverRaceTrackLocationPosition
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Dale Earnhardt, Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1

Adding Data

The most potent part of views is that when we add more data like these race finishes where Buddy Baker wins the Brickyard 400 and the Michigan 400, we can just query our views to get the same results. 

insert into finishes (driver, race, position) values
  (1,3,1),
  (2,3,3),
  (3,3,2);

insert into finishes (driver, race, position) values
  (1,4,1),
  (2,4,2),
  (3,4,3);

Now we can see all finishes with this query.

select * from all_finishes;\

The results of the above query would look like this.

DriverRaceTrackLocationPosition
Buddy BakerDaytona 500Daytona International SpeedwayDaytona Beach, FL3
Dale Earnhardt Jr.Daytona 500Daytona International SpeedwayDaytona Beach, FL2
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Buddy BakerTalladega 500Talladega SuperspeedwayLincoln, AL2
Dale Earnhardt Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1
Ricky RuddTalladega 500Talladega SuperspeedwayLincoln, AL3
Buddy BakerBrickyard 400Indianapolis Motor SpeedwaySpeedway, IN1
Dale Earnhardt Jr.Brickyard 400Indianapolis Motor SpeedwaySpeedway, IN3
Ricky RuddBrickyard 400Indianapolis Motor SpeedwaySpeedway, IN2
Buddy BakerMichigan 400Michigan International SpeedwayBrooklyn, MI1
Dale Earnhardt Jr.Michigan 400Michigan International SpeedwayBrooklyn, MI2
Ricky RuddMichigan 400Michigan International SpeedwayBrooklyn, MI3

We can also run:

select * from race_winners;

Which gives us:

DriverRaceTrackLocationPosition
Ricky RuddDaytona 500Daytona International SpeedwayDaytona Beach, FL1
Dale Earnhardt Jr.Talladega 500Talladega SuperspeedwayLincoln, AL1
Buddy BakerBrickyard 400Indianapolis Motor SpeedwaySpeedway, IN1
Buddy BakerMichigan 400Michigan International SpeedwayBrooklyn, MI1

Also, this results in the series champion:

select * from standings_leader;

Which results in:

FinishDriver
2Buddy Baker
2Dale Earnhardt, Jr.
2Ricky Rudd

Conclusion

When we save a query in our database server (more specifically in the database catalog) and give it a name, this newly named query is called a database view, or, more simply, a view. MySQL Views are a powerful way to save vital and reuseable queries that can help us speed the retrieval of important information. Because these save views can reference other views, more detailed views can be created with these substantial queries.

Rate Us!

We pride ourselves on being The Most Helpful Humans In Hosting™!

Our Support Teams are filled with experienced Linux technicians and talented system administrators who have intimate knowledge of multiple web hosting technologies, especially those discussed in this article.

Should you have any questions regarding this information, we are always available to answer any inquiries with issues related to this article, 24 hours a day, 7 days a week 365 days a year.

If you are a Fully Managed VPS server, Cloud Dedicated, VMWare Private Cloud, Private Parent server, Managed Cloud Servers, or a Dedicated server owner and you are uncomfortable with performing any of the steps outlined, we can be reached via phone @800.580.4985, a chat or support ticket to assisting you with this process.

Was this article helpful? Let us know!

Running SQL Queries on a Database with PhpMyAdmin

Reading Time: 2 minutes

In this tutorial, we will explore how to run SQL queries on a database within PhpMyAdmin. SQL stands for Structured Query Language. SQL statements or queries are used to perform database tasks such as searching, updating, or retrieving data from a database.

Continue reading “Running SQL Queries on a Database with PhpMyAdmin”

How to Enable Remote MySQL Connections in cPanel

Reading Time: 2 minutesRemote MySQL connections are disabled by default in cPanel servers because they are considered a potential security threat. Using the tools in the Web Host Manager (WHM) and the domain-level cPanel interface (usually http://domainname.com/cpanel) remote hosts can be added which the server allows connecting to the MySQL service.

Before using either of the following techniques, you will need to open up port 3306 in your server’s firewall.

Continue reading “How to Enable Remote MySQL Connections in cPanel”

How to Display (List) All Jobs in Cron / Crontab

Reading Time: 2 minutesServers can automatically perform tasks that you would otherwise have to perform yourself, such as running scripts. On Linux cloud dedicated servers or VPS servers, the cron utility is the preferred way to automate the running of scripts. In this article, we’ll cover how to view the jobs scheduled in the crontab list. For an introduction to Cron check-out our KB: How To: Automate Server Scripts With Cron. Knowing how to set up crontab is an important skill, but even if you’re not editing these knowing how to view them is important as well. Continue reading “How to Display (List) All Jobs in Cron / Crontab”

How To: Automate Server Scripts With Cron

Reading Time: 2 minutesServers can automatically perform tasks that you would otherwise have to perform yourself, such as running scripts. On Linux servers, the cron utility is the preferred way to automate the running of scripts.
Continue reading “How To: Automate Server Scripts With Cron”

How To: Create a cPanel Account in WHM

Reading Time: 5 minutesRunning your first webserver can be daunting. Even if you are familiar with running a cPanel account, there is much to learn regarding Web Host Manager (WHM). The first step to successfully running WHM is creating a cPanel account.
Continue reading “How To: Create a cPanel Account in WHM”

Digging Into Exim Mail Logs With Exigrep

Reading Time: 3 minutesPerhaps a particular domain on your cPanel server has stopped receiving e-mail. Or, an address on your domain is able to receive e-mail, except from your supplier. Maybe you can receive e-mail just fine, but are receiving error message bounce-backs from Yahoo. How are you going to get the fine-grained information you need to figure out just what is going on?

The answers you seek can be found in exim’s logs.

Continue reading “Digging Into Exim Mail Logs With Exigrep”

Updating an A record in cPanel

Reading Time: 2 minutesDomain Name System, or DNS, is a complex system to understand, but cPanel has simplified the administration of DNS by adding it to the WHM interface. One of the most common tasks involved with administrating DNS is updating an A record. A records are one of the most common DNS entries, and cPanel makes updating them easy.
This article assumes that you are running BIND on a Linux server, that you already have an understanding of what DNS is, the different types of DNS entries, and how DNS works. Please note: The incorrect editing of your zone file can take your site offline. All editing must be done on the authoritative nameservers for the given domain.

Continue reading “Updating an A record in cPanel”

Apache Error: “semget: No space left on device”

Reading Time: < 1 minuteIf Apache fails, and will not successfully start again, check the error log. If you see an error similar to the following, it could indicate that your server has run out of semaphores.

Continue reading “Apache Error: “semget: No space left on device””