Django Tutorial

• Django Tutorial
• Django MTV And MVC
• Django ORM Module
• Django auth App Module
• Django View Functions
• Django Template System
• Django Routing System
• Django Middleware
• Django Cache System
• Django Development Environment
• Django Installation And Configuration
• Django FBV And CBV Mode

Django Create A Complete Project

• Django Create The First Project
• Django Start A Project
• settings.py Configuration File
• Configure The settings.py File
• Django Initializes The Project Environment
• Django Create The First Application
• Django ORM Advanced

Django Template

• Django Template Loading And Responding
• Django Template Variables
• Django if Tag
• Django for Tag
• Django Template Filter
• Django url Tag
• Django Custom Tags
• Django Other Template Tags
• Django Template Inheritance
• Django Custom Filter
• Django Route Reverse And Namespace
• Django Routing Path Method

Django Database Query

• Django Meta Class Attribute
• Django Model Inheritance
• Django Insert Data To DataTable
• Django Database Query Operation
• Django DataTable Relationship Mapping
• Django F/Q Object Query
• Django Aggregate Query And Group Query
• Django Reverse Query For An Association Relationship
• Django QuerySet Query API

Django Form

• Django Form System
• Cookies In Django
• Session In Django
• Django Form Implements User Login And Logout
• Django Form Field Properties And Methods
• Django Form API
• Django QueryDict Object
• Django Form Built-in Fields
• Django Form Custom Fields
• Django Form Custom Validation Rules
• Django Defines A Form Based On Model
• Django ModelForm
• How The Django Form System Works

Django Authentication and Permission Management

• Django Auth Users And User Groups
• Django Auth Application Implements User Authentication
• Django User Authentication System Permission Management
• Django Custom Permission Management And Permission Verification
• Django Custom Authentication Backend
• Verify User Identity And Permissions In Django Templates
• Django Auth App Defines A Login View
• Django Auth Decorator To Verify User Identity And Permissions

Django unittest

• Python Unit Test by unittest Module
• Django Write Unit Test Cases in Project
• Django unittest Test Framework
• Django Unit Test Database Configuration And Common Testing Tools

Django Advanced

• Django Paging Function
• Django EMail Sending
• Django Upload File And Download CSV File
• Django Cache Mechanism
• Django Custom Middleware
• Django Signal Mechanism
• Django Signal Mechanism Execution Process
• How Django's Signaling Mechanism Works

Difference Between Django MTV And MVC

Django uses a slightly modified version of the traditional Model-View-Controller (MVC) pattern, known as Model-View-Template (MTV). Both the MVC and MTV patterns follow the same fundamental principles of separating concerns in web applications, but they are structured differently.

Here's a breakdown of the components in each pattern:

MVC (Model-View-Controller)

1. Model: Represents the data structure, database schema, and the business logic. It communicates with the database and handles data manipulation and validation.
2. View: Handles the presentation and display of data. It's responsible for rendering the user interface, showing the data retrieved from the Model.
3. Controller: Acts as an intermediary between the Model and the View. It processes incoming requests, interacts with the Model to retrieve or modify data, and passes the data to the View for rendering.

MTV (Model-View-Template)

1. Model: Similar to the Model in MVC, it represents the data structure, database schema, and business logic. It communicates with the database and handles data manipulation and validation.
2. View: In Django's MTV, the View acts more like the Controller in the MVC pattern. It processes incoming requests and interacts with the Model to retrieve or modify data.
3. Template: Corresponds to the View in the MVC pattern. It's responsible for rendering the user interface and displaying the data passed by the View (controller-like in MTV).

The primary difference between the two patterns lies in how the View component is handled. In Django's MTV pattern, the View takes on the role of the Controller in the MVC pattern, while the Template handles the presentation and display of data.

In summary, both Django's MTV and the traditional MVC patterns aim to separate concerns in web application development, with the main difference being how the View component is used. Django's MTV pattern replaces the traditional View with the Template and reassigns the controller's responsibilities to the View.

1. Django MTV vs MVC comparison:

   Django follows the MTV (Model-Template-View) architecture, which is often compared with the traditional MVC (Model-View-Controller) pattern. The key components are organized differently in Django, providing a distinct approach to web development.

   # Django MTV example
   class Model:
       # Represents data structure
   
   class Template:
       # Handles presentation logic
   
   class View:
       # Manages user interactions and business logic