per page, with , order by , clip by
Results of 1 - 10 of about 16 for naming (0.003 sec.)
Django 1.11.5 リリースノート — Django 6.1 ドキュメント 13152
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.5 リリースノート ¶ September 5, 2017 Django 1.11.5 fixes a security issue and several bugs in 1.11.4. CVE-2017-12794: Possible XSS in tr ... lect widget rendering when option values are tuples ( #28502 ). Django 1.11 inadvertently changed the sequence and trigger naming scheme on Oracle. This causes errors on INSERTs for some tables if 'use_returning_into': False is in the OPTIONS part of D ... ATABASES . The pre-1.11 naming scheme is now restored. Unfortunately, it necessarily requires an update to Oracle tables created with Django 1.11.[1-4]. ... Use the upgrade script in #28451 comment 8 to update sequence and trigger names to use the pre-1.11 naming scheme. Added POST request support to LogoutView , for equivalence with the function-based logout() view ( #28513 ). Omitt ...
https://man.mtool.work/django/6.1/releases/1.11.5.html
Django 1.11.5 リリースノート — Django 6.1 ドキュメント 12823
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.11.5 リリースノート ¶ September 5, 2017 Django 1.11.5 fixes a security issue and several bugs in 1.11.4. CVE-2017-12794: Possible XSS in tr ... lect widget rendering when option values are tuples ( #28502 ). Django 1.11 inadvertently changed the sequence and trigger naming scheme on Oracle. This causes errors on INSERTs for some tables if 'use_returning_into': False is in the OPTIONS part of D ... ATABASES . The pre-1.11 naming scheme is now restored. Unfortunately, it necessarily requires an update to Oracle tables created with Django 1.11.[1-4]. ... Use the upgrade script in #28451 comment 8 to update sequence and trigger names to use the pre-1.11 naming scheme. Added POST request support to LogoutView , for equivalence with the function-based logout() view ( #28513 ). Omitt ...
https://man.mtool.work/django/6.1/releases/1.11.5.html
Django 4.0 リリースノート — Django 6.1 ドキュメント 9340
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.0 リリースノート ¶ 2021年12月7日 Django 4.0 へようこそ! このリリースノートでは、 バージョン 4.0 の新機能 と、Django 3.2 以前からアップグレー ... tion logic in delete() handlers should be moved to form_valid() , or a shared helper method, if required. Table and column naming scheme changes on Oracle ¶ Django 4.0 inadvertently changed the table and column naming scheme on Oracle. This causes erro ... rs for models and fields with names longer than 30 characters. Unfortunately, renaming some Oracle tables and columns is required. Use the upgrade script in 33789 to generate RENAME statements to change naming ... yMiddleware no longer sets the X-XSS-Protection header Migrations autodetector changes DeleteView changes Table and column naming scheme changes on Oracle その他 Features deprecated in 4.0 Use of pytz time zones Time zone support Localization その他 Fe ...
https://man.mtool.work/django/6.1/releases/4.0.html
Django 4.0 リリースノート — Django 6.1 ドキュメント 9340
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.0 リリースノート ¶ 2021年12月7日 Django 4.0 へようこそ! このリリースノートでは、 バージョン 4.0 の新機能 と、Django 3.2 以前からアップグレー ... tion logic in delete() handlers should be moved to form_valid() , or a shared helper method, if required. Table and column naming scheme changes on Oracle ¶ Django 4.0 inadvertently changed the table and column naming scheme on Oracle. This causes erro ... rs for models and fields with names longer than 30 characters. Unfortunately, renaming some Oracle tables and columns is required. Use the upgrade script in 33789 to generate RENAME statements to change naming ... yMiddleware no longer sets the X-XSS-Protection header Migrations autodetector changes DeleteView changes Table and column naming scheme changes on Oracle その他 Features deprecated in 4.0 Use of pytz time zones Time zone support Localization その他 Fe ...
https://man.mtool.work/django/6.1/releases/4.0.html
JavaScript code — Django 6.1 ドキュメント 8543
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... tion and whitespace issues. Most of the JavaScript files use 4 spaces for indentation, but there are some exceptions. When naming variables, use camelCase instead of underscore_case . Different JavaScript files sometimes use a different code style. Ple ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
JavaScript code — Django 6.1 ドキュメント 8387
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... tion and whitespace issues. Most of the JavaScript files use 4 spaces for indentation, but there are some exceptions. When naming variables, use camelCase instead of underscore_case . Different JavaScript files sometimes use a different code style. Ple ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
Migrating email to mailers — Django 6.1 ドキュメント 7919
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... omes "password" in "OPTIONS" . EMAIL_HOST_USER becomes "username" in "OPTIONS" . (Note "username" doesn't quite follow the naming pattern for the other deprecated settings.) EMAIL_PORT becomes "port" in "OPTIONS" . It can be omitted if the connection u ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 7919
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... omes "password" in "OPTIONS" . EMAIL_HOST_USER becomes "username" in "OPTIONS" . (Note "username" doesn't quite follow the naming pattern for the other deprecated settings.) EMAIL_PORT becomes "port" in "OPTIONS" . It can be omitted if the connection u ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... vor ¶ django.contrib.localflavor.usa has been renamed to django.contrib.localflavor.us . This change was made to match the naming scheme of other local flavors. To migrate your code, all you need to do is change the imports. セッション ¶ Getting a new ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 7745
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... vor ¶ django.contrib.localflavor.usa has been renamed to django.contrib.localflavor.us . This change was made to match the naming scheme of other local flavors. To migrate your code, all you need to do is change the imports. セッション ¶ Getting a new ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
PREV 1 2 NEXT