Function-based vs class-based decision in Django - Quick Revision & Key Differences

Recall & Review

beginner

What is a function-based view (FBV) in Django?

A function-based view is a simple Python function that takes a web request and returns a web response. It is straightforward and easy to understand, suitable for simple logic.

beginner

What is a class-based view (CBV) in Django?

A class-based view is a Python class that provides methods to handle HTTP requests. It helps organize code better and supports reuse through inheritance and mixins.

intermediate

When should you choose a function-based view over a class-based view?

Choose a function-based view when your view logic is simple and straightforward, like a single action or small page, because it is easier to write and understand.

intermediate

What are the advantages of using class-based views?

Class-based views allow code reuse through inheritance, organize complex logic into methods, and provide built-in generic views for common tasks like displaying lists or forms.

intermediate

How does Django handle HTTP methods differently in FBVs and CBVs?

In FBVs, you check the request method inside the function (like if request.method == 'POST'). In CBVs, you define separate methods like get() and post() for each HTTP method, making code cleaner.

Which Django view type is best for simple, one-action pages?

A Function-based view

B Class-based view

C Template view

D Middleware

Function-based views are simpler and better for straightforward tasks.

In class-based views, how do you handle a POST request?

A Override the dispatch() method only

B Check request.method inside a function

C Use a decorator

D Define a post() method

Class-based views handle HTTP methods by defining methods like post() for POST requests.

What is a key benefit of class-based views over function-based views?

A No need to import Django modules

B Better code reuse through inheritance

C Easier to write for simple pages

D Automatically faster response time

Class-based views support inheritance, which helps reuse and organize code.

Which view type requires you to manually check request.method?

A Template view

B Class-based view

C Function-based view

D Generic view

In function-based views, you check request.method yourself to handle different HTTP methods.

When might you prefer a class-based view?

A When your view has multiple HTTP methods and complex logic

B For a simple 'Hello World' page

C When you want to avoid using classes

D When you want to write less code for a single action

Class-based views help organize complex logic and multiple HTTP methods better.

Explain the main differences between function-based and class-based views in Django.

Think about how each handles requests and organizes code.

Describe scenarios when you would choose a function-based view versus a class-based view.

Consider complexity and code reuse needs.

Practice

1. Which of the following is a key advantage of using class-based views (CBVs) over function-based views (FBVs) in Django?

easy

A. FBVs require less code for complex views.

B. CBVs are always faster than FBVs.

C. FBVs cannot handle POST requests.

D. CBVs allow reuse of common functionality through inheritance.

Solution

1. Step 1: Understand CBVs and inheritance

   Class-based views use classes, so they can inherit and reuse code easily.

2. Step 2: Compare with FBVs

   Function-based views are simple functions and do not support inheritance for reuse.

3. Final Answer:

   CBVs allow reuse of common functionality through inheritance. -> Option D

4. Quick Check:

   CBVs = reuse by inheritance [OK]

Hint: CBVs use classes, so they support inheritance and reuse [OK]

Common Mistakes:

• Thinking CBVs are always faster
• Believing FBVs can't handle POST
• Assuming FBVs are better for complex views

2. Which of the following is the correct way to define a simple function-based view in Django?

easy

A. def my_view(request): return HttpResponse('Hello')

B. class my_view(View): return HttpResponse('Hello')

C. def my_view(): return HttpResponse('Hello')

D. class my_view: def get(): return HttpResponse('Hello')

Solution

1. Step 1: Check function signature for FBV

   A function-based view must accept a request parameter.

2. Step 2: Validate return statement

   The function should return an HttpResponse object.

3. Final Answer:

   def my_view(request): return HttpResponse('Hello') -> Option A

4. Quick Check:

   FBV needs request param and returns HttpResponse [OK]

Hint: FBVs are functions with request parameter returning HttpResponse [OK]

Common Mistakes:

• Omitting the request parameter
• Using class syntax for FBV
• Not returning HttpResponse

3. Given this class-based view code, what will be the HTTP response content when a GET request is made?

from django.http import HttpResponse
from django.views import View

class HelloView(View):
    def get(self, request):
        return HttpResponse('Hello from CBV')

medium

A. HelloView object

B. Hello from CBV

C. Error: get method missing request

D. Empty response

Solution

1. Step 1: Identify the get method behavior

   The get method returns HttpResponse with 'Hello from CBV'.

2. Step 2: Understand request handling

   A GET request calls the get method and returns that response content.

3. Final Answer:

   Hello from CBV -> Option B

4. Quick Check:

   GET calls get() returning 'Hello from CBV' [OK]

Hint: GET calls get() method in CBV returning its HttpResponse [OK]

Common Mistakes:

• Confusing class name with response content
• Thinking get method lacks request parameter
• Expecting empty or error response

4. What is wrong with this function-based view code?

def my_view():
    return HttpResponse('Hi')

medium

A. Function name must be capitalized.

B. HttpResponse cannot be returned from a function.

C. Missing request parameter in function definition.

D. The return statement should be inside a class.

Solution

1. Step 1: Check function parameters

   Function-based views must accept a request parameter to receive HTTP requests.

2. Step 2: Validate function signature

   The given function lacks the required request parameter, causing errors.

3. Final Answer:

   Missing request parameter in function definition. -> Option C

4. Quick Check:

   FBV needs request param [OK]

Hint: FBVs always need request parameter [OK]

Common Mistakes:

• Ignoring missing request parameter
• Thinking HttpResponse can't be returned
• Believing function names must be capitalized

5. You want to create a Django view that handles GET and POST requests differently and also reuse some common code for multiple views. Which approach is best?

hard

A. Use class-based views with methods for GET and POST and inheritance for reuse.

B. Use class-based views but define all logic in a single method.

C. Use function-based views with if-else inside to check request method.

D. Use function-based views with decorators for GET and POST.

Solution

1. Step 1: Identify need for handling GET and POST separately

   Class-based views allow defining separate get() and post() methods for clarity.

2. Step 2: Consider code reuse

   CBVs support inheritance, so common code can be reused across multiple views easily.

3. Final Answer:

   Use class-based views with methods for GET and POST and inheritance for reuse. -> Option A

4. Quick Check:

   CBVs = separate methods + reuse [OK]

Hint: CBVs separate methods and support inheritance for reuse [OK]

Common Mistakes:

• Using FBVs with complex if-else for methods
• Putting all logic in one CBV method
• Ignoring inheritance benefits