Why Function-based views basics in Django? - Purpose & Use Cases

The Big Idea

Discover how a few simple functions can transform your website building from chaos to clarity!

The Scenario

Imagine building a website where every page needs to show different content, and you have to write separate code to handle each page's request manually.

The Problem

Manually handling each request means repeating code, mixing logic with presentation, and making it hard to maintain or update your site as it grows.

The Solution

Function-based views let you write simple Python functions that handle web requests and return responses, keeping your code organized and easy to manage.

Before vs After

✗ Before

if request.path == '/home':
    return HttpResponse('Home page')
elif request.path == '/about':
    return HttpResponse('About page')

✓ After

from django.http import HttpResponse

def home_view(request):
    return HttpResponse('Home page')

def about_view(request):
    return HttpResponse('About page')

What It Enables

It makes building and maintaining web pages straightforward by separating each page's logic into clear, reusable functions.

Real Life Example

When you want to add a contact form page, you just create a new function-based view to handle the form submission and display, without touching other pages.

Key Takeaways

Manual request handling is repetitive and hard to maintain.

Function-based views organize code into simple, clear functions.

This approach makes your website easier to build and update.

Practice

1. What is the main purpose of a function-based view in Django?

easy

A. To handle web requests and return responses

B. To define database models

C. To style HTML pages with CSS

D. To manage user sessions automatically

Solution

1. Step 1: Understand the role of views in Django

   Views are responsible for processing web requests and returning responses.

2. Step 2: Identify the function-based view role

   Function-based views are simple Python functions that take a request and return a response.

3. Final Answer:

   To handle web requests and return responses -> Option A

4. Quick Check:

   Function-based views handle requests = A [OK]

Hint: Views handle requests and responses in Django [OK]

Common Mistakes:

• Confusing views with models
• Thinking views handle styling
• Assuming views manage sessions automatically

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

easy

A. def my_view(request): print('Hello')

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

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

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

Solution

1. Step 1: Check function signature for views

   A function-based view must accept a request parameter.

2. Step 2: Verify the return value

   The view must return an HttpResponse object, not just print or omit request.

3. Final Answer:

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

4. Quick Check:

   Function with request param and HttpResponse return = A [OK]

Hint: View functions need request param and return HttpResponse [OK]

Common Mistakes:

• Omitting the request parameter
• Using class syntax instead of function
• Printing instead of returning HttpResponse

3. Given this function-based view code, what will be the HTTP response content?

from django.http import HttpResponse

def greet(request):
    name = request.GET.get('name', 'Guest')
    return HttpResponse(f'Hello, {name}!')

medium

A. Hello, None!

B. Hello, Guest!

C. Hello, name!

D. Error: missing name parameter

Solution

1. Step 1: Understand request.GET.get usage

   The code tries to get 'name' from query parameters; if missing, defaults to 'Guest'.

2. Step 2: Determine response content when no name given

   If no 'name' parameter is in the URL, it uses 'Guest', so response is 'Hello, Guest!'.

3. Final Answer:

   Hello, Guest! -> Option B

4. Quick Check:

   Missing name defaults to Guest = B [OK]

Hint: GET.get with default returns default if param missing [OK]

Common Mistakes:

• Assuming missing param causes error
• Confusing string literal with variable name
• Expecting None instead of default value

4. Identify the error in this function-based view code:

from django.http import HttpResponse

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

medium

A. Return statement syntax is incorrect

B. HttpResponse is not imported

C. Missing request parameter in function definition

D. Function name is invalid

Solution

1. Step 1: Check function parameters for views

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

2. Step 2: Verify imports and syntax

   HttpResponse is imported correctly and return syntax is valid; function name is valid.

3. Final Answer:

   Missing request parameter in function definition -> Option C

4. Quick Check:

   View functions need request param = C [OK]

Hint: Always include request parameter in view functions [OK]

Common Mistakes:

• Omitting request parameter
• Forgetting to import HttpResponse
• Misnaming the function

5. You want to create a function-based view that returns a 404 error if a query parameter 'id' is missing. Which code snippet correctly implements this?

hard

A. def view(request):
if request.GET.get('id') is None:
return HttpResponse('Not found', status=404)
return HttpResponse('Found')

B. def view(request):
if request.GET['id'] is None:
return HttpResponse('Not found', status=404)
return HttpResponse('Found')

C. def view(request):
if request.GET.get('id') == '':
return HttpResponse('Not found', status=404)
return HttpResponse('Found')

D. def view(request):
if 'id' not in request.POST:
return HttpResponse('Not found', status=404)
return HttpResponse('Found')

Solution

1. Step 1: Check how to safely get query parameters

   Using request.GET.get('id') returns None if 'id' is missing, avoiding KeyError.

2. Step 2: Verify condition to return 404

   If get returns None, return HttpResponse with status=404; else return 'Found'.

3. Final Answer:

   def view(request): if request.GET.get('id') is None: return HttpResponse('Not found', status=404) return HttpResponse('Found') -> Option A

4. Quick Check:

   Use GET.get to check missing param safely = D [OK]

Hint: Use request.GET.get to avoid KeyError when checking params [OK]

Common Mistakes:

• Using request.GET['id'] without checking existence
• Checking for empty string instead of None
• Confusing request.GET with request.POST