Function vs procedure decision in SQL - Quick Revision & Key Differences

Recall & Review

beginner

What is the main difference between a function and a procedure in SQL?

A function returns a value and can be used in SQL expressions, while a procedure performs actions but does not return a value directly.

beginner

When should you choose a function over a procedure?

Choose a function when you need to return a single value and use it inside SQL queries or expressions.

intermediate

Can a procedure return multiple result sets or perform complex operations?

Yes, procedures can return multiple result sets and perform complex operations like modifying data or controlling transactions.

beginner

Is it possible to call a procedure inside a SELECT statement?

No, procedures cannot be called inside SELECT statements because they do not return a value directly.

intermediate

Why might you use a procedure instead of a function for data modification?

Procedures are better for data modification because they can execute multiple statements and control transactions, while functions are limited in side effects.

Which SQL object returns a value and can be used inside a SELECT statement?

A View

B Procedure

C Function

D Trigger

Functions return values and can be used inside SELECT statements, unlike procedures.

Which is true about procedures in SQL?

A They can perform multiple operations and do not return a value directly

B They must return a value

C They can only be used in SELECT statements

D They cannot modify data

Procedures can perform multiple operations and do not return a value directly.

When deciding between function and procedure, which is best for complex data changes?

A Procedure

B Function

C View

D Index

Procedures are best for complex data changes because they can execute multiple statements and control transactions.

Can a function have side effects like modifying database tables?

A Yes, always

B No, functions should not modify data

C Only if called inside a procedure

D Only in some SQL dialects

Functions should not modify data; they are meant to return values without side effects.

Which SQL object is typically used to encapsulate reusable logic that returns a value?

A Table

B Procedure

C Trigger

D Function

Functions encapsulate reusable logic that returns a value.

Explain when you would use a function instead of a procedure in SQL.

Think about whether you need a value back to use in a query.

Describe the advantages of using a procedure for database operations.

Consider complex tasks and data changes.

Practice

1. Which of the following is true about SQL functions compared to procedures?

easy

A. Functions return a value and can be used in SELECT queries.

B. Functions perform actions but do not return any value.

C. Procedures always return a value and can be used in WHERE clauses.

D. Procedures can be used inside SELECT statements like functions.

Solution

1. Step 1: Understand the purpose of functions

   Functions are designed to return a value and can be called within queries like SELECT.

2. Step 2: Compare with procedures

   Procedures perform tasks but do not return values directly and cannot be used inside SELECT statements.

3. Final Answer:

   Functions return a value and can be used in SELECT queries. -> Option A

4. Quick Check:

   Functions return values [OK]

Hint: Functions return values; procedures perform tasks [OK]

Common Mistakes:

• Thinking procedures return values like functions
• Using procedures inside SELECT queries
• Confusing function usage with procedure usage

2. Which of the following is the correct syntax to create a SQL function that returns an integer?

easy

A. CREATE PROCEDURE getCount() BEGIN RETURN 10; END;

B. CREATE PROCEDURE getCount() RETURNS INT BEGIN RETURN 10; END;

C. CREATE FUNCTION getCount() BEGIN RETURN 10; END;

D. CREATE FUNCTION getCount() RETURNS INT BEGIN RETURN 10; END;

Solution

1. Step 1: Identify function syntax

   Functions require specifying RETURNS type and a RETURN statement inside BEGIN...END.

2. Step 2: Check options for correctness

   CREATE FUNCTION getCount() RETURNS INT BEGIN RETURN 10; END; correctly declares a function with RETURNS INT and returns a value. Others either use PROCEDURE or miss RETURNS.

3. Final Answer:

   CREATE FUNCTION getCount() RETURNS INT BEGIN RETURN 10; END; -> Option D

4. Quick Check:

   Functions need RETURNS and RETURN [OK]

Hint: Functions need RETURNS and RETURN statements [OK]

Common Mistakes:

• Using PROCEDURE keyword for functions
• Omitting RETURNS clause in function
• Using RETURN in procedures incorrectly

3. Given the following SQL code, what will be the output of SELECT calculateTax(100); if calculateTax is a function that returns 10% of the input amount?

CREATE FUNCTION calculateTax(amount INT) RETURNS INT BEGIN RETURN amount * 0.1; END;

medium

A. 100

B. 0.1

C. 10

D. Error: Cannot multiply INT by decimal

Solution

1. Step 1: Understand function logic

   The function multiplies the input amount by 0.1 to calculate 10% tax.

2. Step 2: Calculate output for input 100

   100 * 0.1 = 10, so the function returns 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   100 * 0.1 = 10 [OK]

Hint: Multiply input by 0.1 to get 10% tax [OK]

Common Mistakes:

• Confusing 0.1 with 10
• Expecting decimal output when function returns INT
• Assuming error due to type mismatch

4. You wrote this procedure to update a user's email:

CREATE PROCEDURE updateEmail(userId INT, newEmail VARCHAR(100)) BEGIN UPDATE users SET email = newEmail WHERE id = userId; END;

When you try to call it with SELECT updateEmail(1, '[e-mail]');, you get an error. What is the problem?

medium

A. Procedures cannot be called inside SELECT statements.

B. The procedure is missing a RETURN statement.

C. The UPDATE statement syntax is incorrect.

D. The procedure parameters must be declared as OUT.

Solution

1. Step 1: Understand procedure usage

   Procedures perform actions but do not return values and cannot be called inside SELECT queries.

2. Step 2: Identify error cause

   Calling a procedure with SELECT causes error because procedures are invoked with CALL, not SELECT.

3. Final Answer:

   Procedures cannot be called inside SELECT statements. -> Option A

4. Quick Check:

   Use CALL for procedures, not SELECT [OK]

Hint: Call procedures with CALL, not SELECT [OK]

Common Mistakes:

• Trying to use SELECT to call procedures
• Expecting procedures to return values
• Misunderstanding parameter directions

5. You need to create a reusable SQL routine that calculates the discount price and also logs the discount application in a table. Which approach is best?

hard

A. Use a single function to calculate discount and log the discount inside it.

B. Use a function to calculate discount and a procedure to log the discount.

C. Use a procedure to calculate discount and return the discounted price.

D. Use a procedure only to calculate discount and log the discount.

Solution

1. Step 1: Separate calculation and action

   Functions should be used for calculations returning values; procedures for actions like logging.

2. Step 2: Apply best practice

   Use a function to return the discount price, and a procedure to perform the logging task separately.

3. Final Answer:

   Use a function to calculate discount and a procedure to log the discount. -> Option B

4. Quick Check:

   Functions calculate; procedures perform tasks [OK]

Hint: Calculate with functions; log with procedures [OK]

Common Mistakes:

• Trying to do logging inside functions
• Expecting procedures to return values
• Mixing calculation and side effects in one routine