per page, with , order by , clip by
Results of 1 - 10 of about 217 for default (0.012 sec.)
PostgreSQL 固有の集計関数 11406
PostgreSQL 固有の集計関数 これらの機能は、 django.contrib.postgres.aggregates モジュールから利用可能です。これらについての詳細は、 PostgreSQLドキュメント に記載されています。 注釈 すべての関数はデフォルトのエイリアスを持たないので、明示的に ... field" )) {'arr': [0, 1, 2]} 一般的な集計オプション すべての集計関数は、 filter キーワード引数を持ち、ほとんどの集計関数は default キーワード引数も持っています。 汎用的な集計関数 ArrayAgg class ArrayAgg ( expression , distinct = False , filter = None , ... default = None , order_by = () , ** extra ) null を含む値のリストを配列に連結して返すか、値がない場合は default を返す。 distinct オプションの真偽値引数で、配列の値を区別するかどうかを指定する。デフォルトは False です。 order_by 結果リ ... ield" ) ArrayAgg ( "a_field" , order_by = F ( "some_field" ) . desc ()) BitAnd class BitAnd ( expression , filter = None , default = None , ** extra ) すべての非 null 入力値のビットごとの AND を返し、すべての値が null の場合は default を返します。 バージ ...
https://man.mtool.work/django/6.1/ref/contrib/postgres/aggregates.html
Django 3.2 リリースノート 9382
Django 3.2 リリースノート April 6, 2021 Django 3.2 へようこそ! このリリースノートでは、 バージョン 3.2 の新機能 と、Django 3.1 以前からアップグレードする際に注意すべき、 後方互換性のない変更 について説明します。また、 一部の機能を非推奨 とし ... omatic AppConfig discovery Most pluggable applications define an AppConfig subclass in an apps.py submodule. Many define a default_app_config variable pointing to this class in their __init__.py . When the apps.py submodule exists and defines a single A ... ppConfig subclass, Django now uses that configuration automatically, so you can remove default_app_config . default_app_config made it possible to declare only the application's path in INSTALLED_APPS (e.g. 'django.co ... , with the intent to switch the ecosystem to the latter, but the switch didn't happen. With automatic AppConfig discovery, default_app_config is no longer needed. As a consequence, it's deprecated. See アプリケーションを設定する for full details. Custom ...
https://man.mtool.work/django/6.1/releases/3.2.html
メールを送信する 9382
メールを送信する Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework also supports swapping in different delivery mechanisms: you can direct email to the console ... ive ( html_content , "text/html" ) msg . send () Configuring email New Django projects are not configured to send email by default. Instead, email is printed to the console as a development aid (for projects created with startproject ) or results in a M ... g to tell Django how to send email. For example, to send through an SMTP server running on the local machine: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : { "host" : "localhost" , }, }, } Django abstr ... ve been sent. 開発用にメールを設定する discusses some other approaches. Changed in Django 6.1: In earlier releases, Django defaulted to sending email through an SMTP server running on localhost, using the now-deprecated EMAIL_BACKEND and related setting ...
https://man.mtool.work/django/6.1/topics/email.html
Migrating email to mailers 8701
Migrating email to mailers Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduced mail.mailers for obtaining configured email backend instances, replacing mail.get_connectio ... needed to migrate to mailers is updating email-related settings. In your project's settings, define a MAILERS dict with a "default" entry matching the earlier EMAIL_* settings: MAILERS = { "default" : { "BACKEND" : ... , # value of EMAIL_BACKEND setting ... IL_USE_TLS = True EMAIL_PORT = 587 EMAIL_HOST_USER = "user@example.net" EMAIL_HOST_PASSWORD = "password" use: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : { "host" : "mail.example.net" , "use_tls" : T ... rue , # port is not needed: it defaults to 587 with use_tls True. "username" : "user@example.net" , "password" : "password" , }, }, } The complete list of deprec ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Django 6.1 release notes 8387
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 changes you'll want to be aware of when upgrading from Django 6.0 or earlier. We've begun the ... ngo fetches data from the database when an unfetched field is accessed. Django provides three fetch modes: FETCH_ONE , the default, fetches the missing field for the current instance only. This mode represents Django's existing behavior. FETCH_PEERS fet ... ns for ForeignKey.on_delete ForeignKey.on_delete now supports database-level delete options: DB_CASCADE DB_SET_NULL DB_SET_DEFAULT These options handle deletion logic entirely within the database, using the SQL ON DELETE clause. They are thus more effic ... ckends with different options, similar to existing mechanisms for CACHES , DATABASES , STORAGES , and TASKS : MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : { "host" : "smtp.example.com" , "use_tls" : T ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 6.0 release notes 8282
Django 6.0 release notes December 3, 2025 Welcome to Django 6.0! These release notes cover the new features , as well as some backwards incompatible changes you should be aware of when upgrading from Django 5.2 or earlier. We've begun the d ... nd support Django-provided constants for clarity and safety. For example: from django.utils.csp import CSP SECURE_CSP = { "default-src" : [ CSP . SELF ], "script-src" : [ CSP . SELF , CSP . NONCE ], "img-src" : [ CSP . SELF , "https:" ], } The resulting ... Content-Security-Policy header would be set to: default-src 'self'; script-src 'self' 'nonce-SECRET'; img-src 'self' https: To get started, follow the CSP how-to guide . For in-d ... y, both levels shared the same appearance as messages.SUCCESS . Given that ModelAdmin.message_user() uses messages.INFO by default, set the level to messages.SUCCESS to keep the previous icon and styling. django.contrib.auth The default iteration count ...
https://man.mtool.work/django/6.1/releases/6.0.html
Django's Tasks framework 8229
Django's Tasks framework New in Django 6.0: For older Django versions, the django-tasks backport is available. For a web application, there's often more than just turning HTTP requests into HTTP responses. For some functionality, it may be ... gs file. Whilst most applications will only need a single backend, multiple are supported. Immediate execution This is the default backend if another is not specified in your settings file. The ImmediateBackend runs enqueued Tasks immediately, rather th ... red infrastructure is available. To use it, set BACKEND to "django.tasks.backends.immediate.ImmediateBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.immediate.ImmediateBackend" }} The ImmediateBackend may also be useful in tests, t ... be used during development and testing. To use it, set BACKEND to "django.tasks.backends.dummy.DummyBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.dummy.DummyBackend" }} The results for enqueued Tasks can be retrieved from the ba ...
https://man.mtool.work/django/6.1/topics/tasks.html
設定 8082
設定 警告 設定を上書きするとき、特にデフォルト値が空でないリストや辞書の場合、例えば STATICFILES_FINDERS などは、注意してください。Djangoの使用したい機能に必要なコンポーネントを保持するようにしてください。 コアの設定 ここでは、Django の cor ... きのみ有効です。詳しくは see ミドルウェア (Middleware) を参照。また PREPEND_WWW も参照してください。 CACHES デフォルト値: { "default" : { "BACKEND" : "django.core.cache.backends.locmem.LocMemCache" , } } Django で使用されるすべてのキャッシュの設定を含む辞 ... キャッシュのエイリアスを個々のキャッシュのオプションを含む辞書にマッピングする内容のネストされた辞書です。 CACHES 設定では、 default キャッシュを設定する必要があります。追加で任意の数のキャッシュを指定することもできます。ローカルメモリキャッシュ以外のキャ ... ed path to a function (or any callable) that defines how to compose a key, prefix, and version into a final cache key. The default function converts the components to strings and joins them with colons, as shown in the cache documentation . 好きなキー関 ...
https://man.mtool.work/django/6.1/ref/settings.html
Django 1.6 リリースノート 7611
Django 1.6 リリースノート 注釈 Dedicated to Malcolm Tredinnick On March 17, 2013, the Django project and the free software community lost a very dear friend and developer. Malcolm was a long-time contributor to Django, a model community mem ... version will be 2.7. Python 3.4 is not supported, but support will be added in Django 1.7. Django 1.6 の新機能 Simplified default project and app templates The default templates used by startproject and startapp have been simplified and modernized. The ... admin is now enabled by default in new projects; the sites framework no longer is. clickjacking prevention is now on and the database defaults to SQLite. ... If the default templates don't suit your tastes, you can use custom project and app templates . Improved transaction management Django's ...
https://man.mtool.work/django/6.1/releases/1.6.html
モデルフィールドリファレンス 7453
モデルフィールドリファレンス このドキュメントには、Django が提供するフィールドオプション field options とフィールド型 field types を含む、 Field のすべての API リファレンスが記載されています。 注釈 フィールドは django.db.models.fields に定義 ... ior" , GRADUATE : "Graduate" , } year_in_school = models . CharField ( max_length = 2 , choices = YEAR_IN_SCHOOL_CHOICES , default = FRESHMAN , ) def is_upperclass ( self ): return self . year_in_school in { self . JUNIOR , self . SENIOR } モデルクラスの ... 。データベース API ドキュメントの get_FOO_display() を参照してください。 Unless blank=False is set on the field along with a default then a label containing "- Select an option -" will be rendered with the select box. To override this behavior, add a tupl ... , you can use an empty string instead of None where this makes sense - such as on a CharField . Changed in Django 6.1: The default blank label was changed from "---------" to "- Select an option -" . 列挙型 さらに Django には、選択肢を簡潔に定義するため ...
https://man.mtool.work/django/6.1/ref/models/fields.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT