Why Granting privileges in MySQL? - Purpose & Use Cases

The Big Idea

What if you could control who sees or changes your data with just one simple command?

The Scenario

Imagine you run a small library and you want to let your friends borrow books. You write down who can borrow which books on paper. Every time someone new wants to borrow, you have to update your notes manually.

The Problem

This manual method is slow and confusing. You might forget to update the notes or give someone access to books they shouldn't have. It's hard to keep track and easy to make mistakes.

The Solution

Granting privileges in a database lets you easily control who can do what. Instead of writing notes, you tell the database who can read, write, or change data. It keeps everything clear and safe.

Before vs After

✗ Before

Keep a notebook: "Alice can read books A and B; Bob can borrow book C"

✓ After

GRANT SELECT ON library.books TO 'alice';
GRANT INSERT ON library.books TO 'bob';

What It Enables

This lets you quickly and safely manage access, so the right people can do the right things without confusion or risk.

Real Life Example

A company database where only HR staff can see employee salaries, while sales staff can only see customer orders.

Key Takeaways

Manual access control is slow and error-prone.

Granting privileges automates and secures who can do what.

This keeps data safe and access clear for everyone.

Practice

1. What does the GRANT SELECT ON database.* TO 'user'@'host'; command do in MySQL?

easy

A. Allows the user to read data from all tables in the specified database.

B. Allows the user to modify data in all tables in the specified database.

C. Creates a new user with read access to the database.

D. Deletes all data from the specified database.

Solution

1. Step 1: Understand the GRANT command

   The GRANT command is used to give specific permissions to a user on a database or table.

2. Step 2: Analyze the SELECT privilege

   SELECT privilege allows reading data but not modifying it.

3. Final Answer:

   Allows the user to read data from all tables in the specified database. -> Option A

4. Quick Check:

   GRANT SELECT = read permission [OK]

Hint: SELECT privilege means read-only access [OK]

Common Mistakes:

• Confusing SELECT with UPDATE or DELETE privileges
• Thinking GRANT creates a user
• Assuming it deletes data

2. Which of the following is the correct syntax to grant all privileges on the shop database to user 'alice' connecting from any host?

easy

A. GRANT ALL PRIVILEGES ON shop.* TO 'alice'@'%';

B. GRANT ALL PRIVILEGES ON shop TO 'alice'@'%';

C. GRANT ALL ON shop.* TO 'alice';

D. GRANT ALL PRIVILEGES TO 'alice'@'%' ON shop.*;

Solution

1. Step 1: Check the database and user format

   The database must be followed by .* to specify all tables, and user must include host.

2. Step 2: Verify the correct order of clauses

   The syntax is: GRANT privileges ON database.* TO 'user'@'host';

3. Final Answer:

   GRANT ALL PRIVILEGES ON shop.* TO 'alice'@'%'; -> Option A

4. Quick Check:

   Correct syntax = GRANT ALL PRIVILEGES ON shop.* TO 'alice'@'%'; [OK]

Hint: Use database.* to grant on all tables [OK]

Common Mistakes:

• Omitting .* after database name
• Placing TO clause incorrectly
• Not specifying host with user

3. Given the commands:

GRANT SELECT, INSERT ON sales.* TO 'bob'@'localhost';
SHOW GRANTS FOR 'bob'@'localhost';

What will the SHOW GRANTS output include?

medium

A. GRANT ALL PRIVILEGES ON sales.* TO 'bob'@'localhost'

B. GRANT SELECT ON sales.* TO 'bob'@'localhost'

C. GRANT SELECT, INSERT ON sales.* TO 'bob'@'localhost'

D. No privileges granted

Solution

1. Step 1: Understand the GRANT command given

   The user 'bob' is granted SELECT and INSERT privileges on all tables in the sales database.

2. Step 2: Interpret SHOW GRANTS output

   SHOW GRANTS displays the exact privileges granted, so it will list SELECT and INSERT on sales.* for bob.

3. Final Answer:

   GRANT SELECT, INSERT ON sales.* TO 'bob'@'localhost' -> Option C

4. Quick Check:

   SHOW GRANTS matches granted privileges [OK]

Hint: SHOW GRANTS shows exact privileges granted [OK]

Common Mistakes:

• Assuming ALL PRIVILEGES are granted
• Ignoring INSERT privilege
• Thinking SHOW GRANTS returns no rows

4. Identify the error in the following command:

GRANT UPDATE, DELETE ON * TO 'carol'@'localhost';

medium

A. Host '%' must be used instead of 'localhost'

B. User name must be in double quotes

C. Privileges UPDATE and DELETE cannot be granted together

D. Missing database or table name after ON

Solution

1. Step 1: Check the ON clause syntax

   The ON clause requires a database or table name, e.g., database.* or database.table.

2. Step 2: Identify the missing part

   The command uses * alone, which is invalid syntax in MySQL for ON.

3. Final Answer:

   Missing database or table name after ON -> Option D

4. Quick Check:

   ON must specify database or table [OK]

Hint: ON must specify database or table, not just * [OK]

Common Mistakes:

• Using * alone without database name
• Using wrong quotes for user
• Assuming localhost is invalid host

5. You want to allow user 'dave' to create new tables only in the inventory database but not modify data. Which GRANT command is correct?

hard

A. GRANT ALL PRIVILEGES ON inventory.* TO 'dave'@'localhost';

B. GRANT CREATE ON inventory.* TO 'dave'@'localhost';

C. GRANT CREATE, INSERT ON inventory.* TO 'dave'@'localhost';

D. GRANT CREATE ON *.* TO 'dave'@'localhost';

Solution

1. Step 1: Identify the needed privilege

   To create tables, the CREATE privilege is required; INSERT or ALL PRIVILEGES would allow data changes.

2. Step 2: Scope the privilege to the inventory database

   Granting on inventory.* limits the permission to that database only.

3. Step 3: Check user and host format

   User 'dave'@'localhost' is correctly specified.

4. Final Answer:

   GRANT CREATE ON inventory.* TO 'dave'@'localhost'; -> Option B

5. Quick Check:

   CREATE only on inventory = GRANT CREATE ON inventory.* TO 'dave'@'localhost'; [OK]

Hint: Grant only CREATE on specific database for table creation [OK]

Common Mistakes:

• Granting ALL PRIVILEGES instead of just CREATE
• Including INSERT which allows data changes
• Granting on *.* instead of specific database