Mysql Views How To Create View From Tables With Examples

WHERE

“CREATE VIEW view_name” tells MySQL server to create a view object in the database named view_name

“AS SELECT statement” is the SQL statements to be packed in the MySQL Views. It can be a SELECT statement can contain data from one table or multiple tables.

How to Create Views in MySQL

Following is a step by step process to create view in MySQL: Step 1: Create our first view using the “myflixdb” Let’s now create our first view using the “myflixdb” we will create a simple view that restricts the columns seen in the members table. Suppose authorization requirements state that the accounts department can only see member’s number , name and gender from the member’s table. To achieve this you can create a VIEW – Step 2: Expanding the views node Executing the above script in MySQL workbench against the myflixdb and expanding the views node in the database explorer gives us the following results.

Note the accounts_v_members object is now visible in the database views objects. Step 3: Execute a SELECT statement Let’s now execute a SELECT statement that selects all the fields from the view as shown in the below MySQL create view example. Step 4: Execute a script Executing the above script in MySQL workbench against myflixdb gives us the following results shown below. Only the authorized columns for accounts department have been returned. Other details found in the members table have been hidden . If we want to see the SQL statements that make up a particular view, we can use the script shown below to do that. Executing the above script gives you the view name and the SQL SELECT statements used to create the view.

Joins and Views in MySQL

Let’s now look at a fairly complex example which involves multiple tables and uses joins. We will package the JOIN created that gets information from three (3) tables namely members, movies and movie rentals. Below is the script that helps us to achieve that. Executing the above scripts creates the view named general_v_movie_rentals in our myflixdb Let’s now select all the fields from a table named general_v_movie_rentals. Executing the above script in MySQL workbench against the myflixdb gives us the following results shown below. Note we didn’t have to write the complex JOIN query to get information about members, movies and movie rental details. We simply used the view in a regular SELECT statement as any other ordinary table. The view can be called from anywhere in the application system running on top of the myflixdb.

Dropping Views in MySQL

The DROP command can be used to delete a view from the database that is no longer required. The basic syntax to drop a view is as follows. Why use views? You may want to use views primarily for following 3 reasons

	Ultimately , you will use your SQL knowledge , to create applications , which will use a  database for data requirements. It’s recommended that you use VIEWS of the original table structure in your application instead of using the tables themselves. This ensures that when you refactor your DB, your legacy code will see the orignal schema via the view without breaking the application.

	VIEWS increase re-usability. You will not have to create complex queries involving joins repeatedly. All the complexity is converted into a single line of query use VIEWS. Such condensed code will be easier to integrate in your application. This will eliminates chances of typos and your code will be more readable.

	VIEWS help in data security. You can use views to show only authorized information to users and hide sensitive data like credit card numbers.

Summary

	Views are virtual tables; they do not contain the data that is returned. The data is stored in the tables referenced in the SELECT statement.

	Views improve security of the database by showing only intended data to authorized users. They hide sensitive data.

	Views make life easy as you do not have write complex queries time and again.

	It’s possible to use INSERT, UPDATE  and DELETE on a VIEW. These operations will change the underlying tables of the VIEW.  The only consideration is that VIEW should contain all NOT NULL columns of the tables it references. Ideally, you should not use VIEWS for updating.