per page, with , order by , clip by
Results of 1 - 10 of about 76 for Apply (0.003 sec.)
Djangoアプリケーションを削除する — Django 6.1 ドキュメント 11802
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Djangoアプリケーションを削除する ¶ Django は、一連の機能を アプリケーション と呼ばれる Python パッケージとしてグループ化する機能を提供しています。要 ... 更新するために必要とされる他のマイグレーションを生成します。 他のアプリのマイグレーション内のアプリへの参照を squash する。 Apply migrations locally, run tests, and verify the correctness of your project. 更新された Django プロジェクトをデプロイ/リリー ... 一連 パッケージ グループ 提供 要件 変化 安全 import 外部 キー models makemigrations 関連 テーブル 接続 リレーション squash Apply migrations locally クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/howto/delete-app.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 11082
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... e only way that a custom header of this nature can be added is with XMLHttpRequest. Therefore, for ease of use, we did not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framew ... produce a proof-of-concept demonstrating the same vulnerability in Django's CSRF handling. To remedy this, Django will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 11082
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... e only way that a custom header of this nature can be added is with XMLHttpRequest. Therefore, for ease of use, we did not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framew ... produce a proof-of-concept demonstrating the same vulnerability in Django's CSRF handling. To remedy this, Django will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
Django 1.2.5 リリースノート — Django 6.1 ドキュメント 10001
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.5 リリースノート ¶ Django 1.2.5 へようこそ! This is the fifth "bugfix" release in the Django 1.2 series, improving the stability and perf ... e only way that a custom header of this nature can be added is with XMLHttpRequest. Therefore, for ease of use, we did not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framew ... produce a proof-of-concept demonstrating the same vulnerability in Django's CSRF handling. To remedy this, Django will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but ...
https://man.mtool.work/django/6.1/releases/1.2.5.html
Django 1.2.5 リリースノート — Django 6.1 ドキュメント 9641
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2.5 リリースノート ¶ Django 1.2.5 へようこそ! This is the fifth "bugfix" release in the Django 1.2 series, improving the stability and perf ... e only way that a custom header of this nature can be added is with XMLHttpRequest. Therefore, for ease of use, we did not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framew ... produce a proof-of-concept demonstrating the same vulnerability in Django's CSRF handling. To remedy this, Django will now apply full CSRF validation to all requests, regardless of apparent AJAX origin. This is technically backwards-incompatible, but ...
https://man.mtool.work/django/6.1/releases/1.2.5.html
Django 1.10 リリースノート — Django 6.1 ドキュメント 8921
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.10 リリースノート ¶ 2016年8月1日 Django 1.10 へようこそ! このリリースノートでは、 バージョン 1.10 の新機能 と、Django 1.9 以前からアップグレ ... dels.User.username is included. If you have a custom user model inheriting from AbstractUser , you'll need to generate and apply a database migration for your user model. We considered an increase to 254 characters to more easily allow the use of emai ... f request . user . is_authenticated is True : ... Custom manager classes available through prefetch_related must define a _apply_rel_filters() method ¶ If you defined a custom manager class available through prefetch_related() you must make sure it de ... fines a _apply_rel_filters() method. This method must accept a QuerySet instance as its single argument and return a filtered version of ...
https://man.mtool.work/django/6.1/releases/1.10.html
Django 1.10 リリースノート — Django 6.1 ドキュメント 8921
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.10 リリースノート ¶ 2016年8月1日 Django 1.10 へようこそ! このリリースノートでは、 バージョン 1.10 の新機能 と、Django 1.9 以前からアップグレ ... dels.User.username is included. If you have a custom user model inheriting from AbstractUser , you'll need to generate and apply a database migration for your user model. We considered an increase to 254 characters to more easily allow the use of emai ... f request . user . is_authenticated is True : ... Custom manager classes available through prefetch_related must define a _apply_rel_filters() method ¶ If you defined a custom manager class available through prefetch_related() you must make sure it de ... fines a _apply_rel_filters() method. This method must accept a QuerySet instance as its single argument and return a filtered version of ...
https://man.mtool.work/django/6.1/releases/1.10.html
Django 5.2.16 release notes — Django 6.1 ドキュメント 8561
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.16 release notes ¶ July 7, 2026 Django 5.2.16 fixes three security issues with severity "low" in 5.2.15. CVE-2026-48588: Potential exposu ... en the request already carried an unrelated cookie (such as a language or theme preference cookie), the protection did not apply, allowing a response that sets a session or other sensitive cookie to be stored in Django's shared cache. This issue has s ...
https://man.mtool.work/django/6.1/releases/5.2.16.html
Djangoアプリケーションを削除する — Django 6.1 ドキュメント 8201
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Djangoアプリケーションを削除する ¶ Django は、一連の機能を アプリケーション と呼ばれる Python パッケージとしてグループ化する機能を提供しています。要 ... 更新するために必要とされる他のマイグレーションを生成します。 他のアプリのマイグレーション内のアプリへの参照を squash する。 Apply migrations locally, run tests, and verify the correctness of your project. 更新された Django プロジェクトをデプロイ/リリー ...
https://man.mtool.work/django/6.1/howto/delete-app.html
Django 5.2.16 release notes — Django 6.1 ドキュメント 8201
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 5.2.16 release notes ¶ July 7, 2026 Django 5.2.16 fixes three security issues with severity "low" in 5.2.15. CVE-2026-48588: Potential exposu ... en the request already carried an unrelated cookie (such as a language or theme preference cookie), the protection did not apply, allowing a response that sets a session or other sensitive cookie to be stored in Django's shared cache. This issue has s ...
https://man.mtool.work/django/6.1/releases/5.2.16.html
PREV 1 2 3 4 5 6 7 8 NEXT