per page, with , order by , clip by
Results of 1 - 10 of about 60 for Replace (0.006 sec.)
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 14193
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 ... xlength to max_length ¶ Rename your maxlength argument to max_length (this was changed to be consistent with form fields): Replace __str__ with __unicode__ ¶ Replace your model's __str__ function with a __unicode__ method, and make sure you use Unicode ... n't have to worry about inline editing until you get to the admin section, below. For now, remove all references to core . Replace class Admin: with admin.py ¶ Remove all your inner class Admin declarations from your models. They won't break anything if ... ically, this means you'll need to rewrite all of your class Admin declarations. You've already seen in models above how to replace your class Admin with an admin.site.register() call in an admin.py file. Below are some more details on how to rewrite tha ...
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 ドキュメント 13335
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 ... xlength to max_length ¶ Rename your maxlength argument to max_length (this was changed to be consistent with form fields): Replace __str__ with __unicode__ ¶ Replace your model's __str__ function with a __unicode__ method, and make sure you use Unicode ... n't have to worry about inline editing until you get to the admin section, below. For now, remove all references to core . Replace class Admin: with admin.py ¶ Remove all your inner class Admin declarations from your models. They won't break anything if ... ically, this means you'll need to rewrite all of your class Admin declarations. You've already seen in models above how to replace your class Admin with an admin.site.register() call in an admin.py file. Below are some more details on how to rewrite tha ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
Migrating email to mailers — Django 6.1 ドキュメント 9088
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 ... ed mail.mailers for obtaining configured email backend instances, replacing mail.get_connection() . A new using argument replaces the earlier connection in Django functions that send email. This guide provides details on migrating existing projects to ... ailable. If not (and if there are no alternatives to that package), you will need to remove MAILERS from your settings and replace it with the equivalent deprecated email settings until the package has been updated. If those errors are coming from your ... other sections in this migration guide for recommended updates. Replacing get_connection() and connection arguments ¶ The replacements for the deprecated mail.get_connection() function and connection arguments to other mail functions depend on how and ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 9088
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 ... ed mail.mailers for obtaining configured email backend instances, replacing mail.get_connection() . A new using argument replaces the earlier connection in Django functions that send email. This guide provides details on migrating existing projects to ... ailable. If not (and if there are no alternatives to that package), you will need to remove MAILERS from your settings and replace it with the equivalent deprecated email settings until the package has been updated. If those errors are coming from your ... other sections in this migration guide for recommended updates. Replacing get_connection() and connection arguments ¶ The replacements for the deprecated mail.get_connection() function and connection arguments to other mail functions depend on how and ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Django 6.1 release notes — Django 6.1 ドキュメント 8521
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... ailers[alias] . See メールを送信する for more details. MAILERS is not yet enabled by default in existing projects. It will replace EMAIL_BACKEND and related EMAIL_* settings in Django 7.0. Until then, the older settings will continue to work but will is ... tag name as the first positional argument. The undocumented ChangeList.has_related_field_in_list_display() method has been replaced with ChangeList.get_select_related_fields() . django.contrib.auth ¶ Under ASGI, RemoteUserMiddleware no longer prefixes H ... PORT , EMAIL_USE_TLS , EMAIL_USE_SSL , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , and EMAIL_TIMEOUT settings are deprecated. Replace them with a MAILERS configuration dictionary as described in Migrating email to mailers . mail.get_connection() is depreca ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 6.1 release notes — Django 6.1 ドキュメント 8521
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... ailers[alias] . See メールを送信する for more details. MAILERS is not yet enabled by default in existing projects. It will replace EMAIL_BACKEND and related EMAIL_* settings in Django 7.0. Until then, the older settings will continue to work but will is ... tag name as the first positional argument. The undocumented ChangeList.has_related_field_in_list_display() method has been replaced with ChangeList.get_select_related_fields() . In order to improve accessibility, the admin's breadcrumbs are now rendered ... PORT , EMAIL_USE_TLS , EMAIL_USE_SSL , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , and EMAIL_TIMEOUT settings are deprecated. Replace them with a MAILERS configuration dictionary as described in Migrating email to mailers . mail.get_connection() is depreca ...
https://man.mtool.work/django/6.1/releases/6.1.html
データベース関数 — Django 6.1 ドキュメント 8230
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベース関数 ¶ The classes documented below provide a way for users to use functions provided by the underlying database as annotations, aggrega ... bjects . update ( name = Repeat ( "name" , 3 )) 1 >>> print ( Author . objects . get ( alias = "j" ) . name ) JohnJohnJohn Replace ¶ class Replace ( expression , text , replacement = Value('') , ** extra ) [ソース] ¶ expression 内で text を replacement ... の引数は大文字小文字を区別します。 使用例: >>> from django.db.models import Value >>> from django.db.models.functions import Replace >>> Author . objects . create ( name = "Margaret Johnson" ) >>> Author . objects . create ( name = "Margaret Smith" ) >>> ... Author . objects . update ( name = Replace ( "name" , Value ( "Margaret" ), Value ( "Margareth" ))) 2 >>> Author . objects . values ( "name" ) <QuerySet [{'name': 'M ...
https://man.mtool.work/django/6.1/ref/models/database-functions.html
データベース関数 — Django 6.1 ドキュメント 8230
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベース関数 ¶ The classes documented below provide a way for users to use functions provided by the underlying database as annotations, aggrega ... bjects . update ( name = Repeat ( "name" , 3 )) 1 >>> print ( Author . objects . get ( alias = "j" ) . name ) JohnJohnJohn Replace ¶ class Replace ( expression , text , replacement = Value('') , ** extra ) [ソース] ¶ expression 内で text を replacement ... の引数は大文字小文字を区別します。 使用例: >>> from django.db.models import Value >>> from django.db.models.functions import Replace >>> Author . objects . create ( name = "Margaret Johnson" ) >>> Author . objects . create ( name = "Margaret Smith" ) >>> ... Author . objects . update ( name = Replace ( "name" , Value ( "Margaret" ), Value ( "Margareth" ))) 2 >>> Author . objects . values ( "name" ) <QuerySet [{'name': 'M ...
https://man.mtool.work/django/6.1/ref/models/database-functions.html
Django 2.1.15 リリースノート — Django 6.1 ドキュメント 8230
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 2.1.15 リリースノート ¶ 2019年12月2日 Django 2.1.15 は 2.1.14 に含まれるセキュリティ脆弱性とデータ損失のバグを修正しています。 CVE-2019-19118 ... Django's safe by default philosophy. For the time being, developers whose applications are affected by this change should replace the use of inlines in read-only parents with custom forms and views that explicitly implement the desired functionality. I ...
https://man.mtool.work/django/6.1/releases/2.1.15.html
Submitting contributions — Django 6.1 ドキュメント 7954
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Submitting contributions ¶ We're always grateful for contributions to Django's code. Indeed, bug reports with associated contributions will get fixe ... ccurate, misleading, or fictitious content. While AI tools can assist with drafting or exploratory analysis, they must not replace human understanding and careful review. If you use AI tools while preparing a contribution, you must: Disclose which AI to ... ws (for example GitHub Copilot or similar tools) on pull requests submitted to the Django repository. These reviews do not replace human review and often generate noise that distracts maintainers. You are free to use such tools in your own fork before s ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/submitting...
PREV 1 2 3 4 5 6 NEXT