Django 设计模型 创建模型 享用便捷的 API 动态生成的管理页面：并非徒有其表 规划 URL 编写视图 设计模板 这只是冰山一角 Django 最初被设计用于具有快速开发需求的新闻类站点，目的是要实现简单快捷的网站开发。以下 内容简要介绍了如何使用 Django 实现一个数据库驱动的 Web 应用。 为了让您充分理解 Django 的工作原理，这份文档为您详细描述了相关的技术细节，不过这并不是 Python 代码会在使用标签时在后台运行。 Django 使用了“模板继承”的概念。这就是 {% extends “base.html” %} 的作用。它的含义 是“先加载名为 base 的模板作为基类，并且用下面的标记块对模板中定义的标记块进行填充”。简 而言之，模板继承可以使模板间的冗余内容最小化：每个模板只需包含与其他文档有区别的内容。 下面是 base.html 可能的样子，它使用了静态文件： 简而言之，它定义了这个网站的外观（还有网站的 logo），并且给子模板们挖好了可以填的坑。这 也让网站的改版变得简单无比——你只需更改这个base基类模板文件即可。 它也可以用来创建网站的多个版本，多个基类模板可以重用同一套子模板。Django 的创始人就用这 种技术建立了网站的移动端适配版——只需建立一个新的基类模板。 注意，你并不是非得使用 Django 的模板系统，你可以使用其他你喜欢的模板系统。尽管 Django

JSON 等格式，以便于在 API 中进行传输。同时，它也可以将传入的 JSON 数据反序列化为数据对象，便于在后端进行 处理。 视图：DRF 提供了各种视图类，用于处理 API 请求，并返回适当的响应。包括基于 函数的视图和基于类的视图，还有通用视图和视图集等。 路由：DRF 提供了灵活的路由功能，用于将 API 请求映射到相应的视图处理函数上。 认证和权限：DRF 支持各种认证和权限控制方式，可以保护

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem. LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem. LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends. locmem.LocMemCache". For example: CACHES

database query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES