Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Django Design Patterns and Best Practices
  • Table Of Contents Toc
Django Design Patterns and Best Practices

Django Design Patterns and Best Practices

By : Ravindran
4.7 (7)
Buy this Book
close
close
Django Design Patterns and Best Practices

Django Design Patterns and Best Practices

4.7 (7)
By: Ravindran
Buy this Book

Overview of this book

If you want to learn how best to utilize commonly found patterns and learn best practices in developing applications with Django, this is the book for you. This book, like Django itself, is accessible to amateur and professional developers alike and assumes little in the way of prior experience. Although written for Python 3, the majority of the code in this book works in Python 2 or can be easily translated.
Table of Contents (14 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Django and Patterns
Icon
1. Django and Patterns
Icon
Why Django?
Icon
The story of Django
Icon
What is a Pattern?
Icon
Patterns in this book
Icon
Best practices
Icon
Summary
2
2. Application Design
Icon
2. Application Design
Icon
How to gather requirements
Icon
Are you a story teller?
Icon
HTML mockups
Icon
Designing the application
Icon
Before starting the project
Icon
SuperBook – your mission, should you choose to accept it
Icon
Summary
3
3. Models
chevron up
Icon
3. Models
Icon
M is bigger than V and C
Icon
The model hunt
Icon
Structural patterns
Icon
Retrieval patterns
Icon
Migrations
Icon
Summary
4
4. Views and URLs
Icon
4. Views and URLs
Icon
A view from the top
Icon
Class-based generic views
Icon
View mixins
Icon
Decorators
Icon
View patterns
Icon
Designing URLs
Icon
Summary
5
5. Templates
Icon
5. Templates
Icon
Understanding Django's template language features
Icon
Organizing templates
Icon
Using Bootstrap
Icon
Template patterns
Icon
Summary
6
6. Admin Interface
Icon
6. Admin Interface
Icon
Using the admin interface
Icon
Enhancing models for the admin
Icon
Admin interface customizations
Icon
Protecting the admin
Icon
Summary
7
7. Forms
Icon
7. Forms
Icon
How forms work
Icon
Displaying forms
Icon
Understanding CSRF
Icon
Form processing with Class-based views
Icon
Form patterns
Icon
Summary
8
8. Dealing with Legacy Code
Icon
8. Dealing with Legacy Code
Icon
Finding the Django version
Icon
Where are the files? This is not PHP
Icon
Starting with urls.py
Icon
Jumping around the code
Icon
Understanding the code base
Icon
Incremental change or a full rewrite?
Icon
Write tests before making any changes
Icon
Legacy databases
Icon
Summary
9
9. Testing and Debugging
Icon
9. Testing and Debugging
Icon
Why write tests?
Icon
Test-driven development
Icon
Writing a test case
Icon
Mocking
Icon
Pattern – test fixtures and factories
Icon
Learning more about testing
Icon
Debugging
Icon
The print function
Icon
Logging
Icon
The Django Debug Toolbar
Icon
The Python debugger pdb
Icon
Other debuggers
Icon
Debugging Django templates
Icon
Summary
10
10. Security
Icon
10. Security
Icon
Cross-site scripting (XSS)
Icon
A handy security checklist
Icon
Summary
11
11. Production-ready
Icon
11. Production-ready
Icon
Production environment
Icon
Hosting
Icon
Deployment tools
Icon
Monitoring
Icon
Performance
Icon
Summary
12
A. Python 2 versus Python 3
Icon
A. Python 2 versus Python 3
Icon
But I still use Python 2.7!
Icon
Python 3
Icon
Further information
13
Index
Icon
Index

Retrieval patterns

This section contains design patterns that deal with accessing model properties or performing queries on them.

Pattern – property field

Problem: Models have attributes that are implemented as methods. However, these attributes should not be persisted to the database.

Solution: Use the property decorator on such methods.

Problem details

Model fields store per-instance attributes, such as first name, last name, birthday, and so on. They are also stored in the database. However, we also need to access some derived attributes, such as full name or age.

They can be easily calculated from the database fields, hence need not be stored separately. In some cases, they can just be a conditional check such as eligibility for offers based on age, membership points, and active status.

A straightforward way to implement this is to define functions, such as get_age similar to the following:

class BaseProfile(models.Model):
    birthdate = models.DateField()
    #...
    def get_age...
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Django Design Patterns and Best Practices
End of Section 3
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon