Why Dropping and altering views in MySQL? - Purpose & Use Cases

The Big Idea

What if you could change your data summaries instantly without breaking anything?

The Scenario

Imagine you have a big spreadsheet with many tabs showing different summaries of your data. Now, you want to change one summary tab or remove it completely. Doing this by copying and pasting data every time is tiring and confusing.

The Problem

Manually updating or deleting these summary tabs means you risk mistakes, lose track of changes, and waste lots of time. It's easy to forget to update all places where the summary is used, causing errors and frustration.

The Solution

Using views in a database lets you create saved queries that act like these summary tabs. Dropping or altering views means you can quickly remove or change these summaries without touching the original data, keeping everything clean and consistent.

Before vs After

✗ Before

Copy data from table to new sheet; manually update formulas everywhere

✓ After

DROP VIEW view_name; CREATE OR REPLACE VIEW view_name AS SELECT ...;

What It Enables

You can easily update or remove complex data summaries without breaking anything else, saving time and avoiding errors.

Real Life Example

A sales manager changes the way monthly sales are calculated. Instead of recreating reports, they just alter the view, and all reports update automatically.

Key Takeaways

Manual updates of data summaries are slow and error-prone.

Views let you save and reuse queries like templates.

Dropping and altering views keeps data consistent and easy to maintain.

Practice

1. What does the DROP VIEW statement do in MySQL?

easy

A. Deletes an existing view from the database

B. Creates a new view in the database

C. Updates the data inside a view without deleting it

D. Renames an existing view

Solution

1. Step 1: Understand the purpose of DROP VIEW

   The DROP VIEW command is used to remove a view completely from the database.

2. Step 2: Differentiate from other commands

   Creating or updating views uses CREATE VIEW or ALTER VIEW, not DROP VIEW.

3. Final Answer:

   Deletes an existing view from the database -> Option A

4. Quick Check:

   DROP VIEW = delete view [OK]

Hint: DROP VIEW removes the view completely from the database [OK]

Common Mistakes:

• Confusing DROP VIEW with ALTER VIEW
• Thinking DROP VIEW updates data inside the view
• Assuming DROP VIEW renames the view

2. Which of the following is the correct syntax to drop a view named employee_view?

easy

A. DELETE VIEW employee_view;

B. DROP employee_view;

C. DROP VIEW employee_view;

D. REMOVE VIEW employee_view;

Solution

1. Step 1: Recall the correct DROP VIEW syntax

   The correct syntax to delete a view is DROP VIEW view_name;.

2. Step 2: Check each option

   DROP VIEW employee_view; matches the correct syntax exactly. Others use invalid keywords like DELETE or REMOVE.

3. Final Answer:

   DROP VIEW employee_view; -> Option C

4. Quick Check:

   DROP VIEW + view name = correct syntax [OK]

Hint: Use DROP VIEW followed by the view name to delete it [OK]

Common Mistakes:

• Omitting the VIEW keyword
• Using DELETE or REMOVE instead of DROP
• Adding extra semicolons inside the command

3. Given the view definition:

CREATE VIEW active_users AS SELECT id, name FROM users WHERE status = 'active';

What will be the result after running:

ALTER VIEW active_users AS SELECT id, name FROM users WHERE status = 'inactive';

and then querying SELECT * FROM active_users;?

medium

A. It will show users with status 'active'

B. It will cause a syntax error

C. It will show all users regardless of status

D. It will show users with status 'inactive'

Solution

1. Step 1: Understand ALTER VIEW effect

   The ALTER VIEW statement changes the view's query to the new SELECT statement.

2. Step 2: Analyze the new query condition

   The new view selects users where status = 'inactive', so querying the view returns inactive users.

3. Final Answer:

   It will show users with status 'inactive' -> Option D

4. Quick Check:

   ALTER VIEW changes query = shows inactive users [OK]

Hint: ALTER VIEW changes the view's query to the new SELECT statement [OK]

Common Mistakes:

• Assuming ALTER VIEW appends to the old query
• Expecting a syntax error from ALTER VIEW
• Thinking the view still shows old data after alteration

4. You try to run the command:

ALTER VIEW sales_summary AS SELECT product_id, SUM(quantity) FROM sales GROUP BY product_id;

but get an error. What is the most likely cause?

medium

A. You cannot use GROUP BY in a view

B. The view sales_summary does not exist

C. ALTER VIEW requires DROP VIEW first

D. The view name is invalid

Solution

1. Step 1: Check prerequisites for ALTER VIEW

   ALTER VIEW requires the specified view to already exist in the database.

2. Step 2: Rule out other causes

   GROUP BY is allowed in views, no need to DROP first, and sales_summary is valid.

3. Final Answer:

   The view sales_summary does not exist -> Option B

4. Quick Check:

   ALTER VIEW requires existing view [OK]

Hint: Ensure the view exists before ALTER VIEW [OK]

Common Mistakes:

• Thinking GROUP BY is not allowed in views
• Trying to ALTER VIEW without dropping it first
• Assuming view names cause this error

5. You have a view customer_orders that shows customer names and their order counts. You want to update it to also show the total order amount. Which sequence of commands correctly updates the view without losing it?

hard

A. ALTER VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name;

B. DROP VIEW customer_orders; CREATE VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name;

C. UPDATE VIEW customer_orders SET total_amount = SUM(amount);

D. MODIFY VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name;

Solution

1. Step 1: Identify how to update a view

   Use ALTER VIEW to change the view's query without dropping it.

2. Step 2: Check the options

   ALTER VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name; uses ALTER VIEW with the new SELECT statement including SUM(amount). DROP VIEW customer_orders; CREATE VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name; drops and recreates, which loses the view temporarily. The other options use invalid commands.

3. Final Answer:

   ALTER VIEW customer_orders AS SELECT name, COUNT(*), SUM(amount) FROM orders GROUP BY name; -> Option A

4. Quick Check:

   ALTER VIEW updates view query safely [OK]

Hint: Use ALTER VIEW to update view queries without dropping [OK]

Common Mistakes:

• Dropping view unnecessarily before recreating
• Using UPDATE or MODIFY which are invalid for views
• Not including GROUP BY when using aggregation