Function-based vs class-based decision in Django - When to Use Which

The Big Idea

Discover how a simple switch in your Django views can save hours of repetitive coding!

The Scenario

Imagine building a web app where you write separate functions for every page and action, then manually handle all the details like HTTP methods and data processing.

The Problem

Writing everything as separate functions can get messy and repetitive. It's easy to forget to handle some HTTP methods or duplicate code, making your app harder to maintain and grow.

The Solution

Django's class-based views organize related actions together in one place. They provide built-in tools to handle common tasks, so you write less code and keep your app clean and easy to update.

Before vs After

✗ Before

def my_view(request):
    if request.method == 'GET':
        # handle GET
    elif request.method == 'POST':
        # handle POST

✓ After

from django.views import View

class MyView(View):
    def get(self, request):
        # handle GET
    def post(self, request):
        # handle POST

What It Enables

You can build scalable, maintainable web apps faster by organizing code logically and reusing common behaviors.

Real Life Example

When creating a blog, class-based views let you easily add features like showing posts, creating new posts, and editing posts without repeating code.

Key Takeaways

Function-based views are simple but can get repetitive and hard to manage.

Class-based views group related actions, reducing code duplication.

Choosing the right approach helps keep your Django app clean and easy to grow.

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