per page, with , order by , clip by
Results of 1 - 10 of about 70 for fetch (0.004 sec.)
Fetch modes — Django 6.1 ドキュメント 14083
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Fetch modes ¶ New in Django 6.1. When accessing model fields that were not loaded as part of the original query, Django will fetch that field's data ... from the database. You can customize the behavior of this fetching with a fetch mode , making it more efficient or even blocking it. Use QuerySet.fetch_mode() to set the fetch mode for m ... odel instances fetched by a QuerySet : from django.db import models books = Book . objects . fetch_mode ( models . FETCH_PEERS ) Fetch modes ap ... rs Fields deferred with QuerySet.defer() or QuerySet.only() ジェネリックリレーション(汎用リレーション) Django copies the fetch mode of an instance to any related objects it fetches, so the mode applies to a whole tree of relationships, not just the ...
https://man.mtool.work/django/6.1/topics/db/fetch-modes.html
Fetch modes — Django 6.1 ドキュメント 13858
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Fetch modes ¶ New in Django 6.1. When accessing model fields that were not loaded as part of the original query, Django will fetch that field's data ... from the database. You can customize the behavior of this fetching with a fetch mode , making it more efficient or even blocking it. Use QuerySet.fetch_mode() to set the fetch mode for m ... odel instances fetched by a QuerySet : from django.db import models books = Book . objects . fetch_mode ( models . FETCH_PEERS ) Fetch modes ap ... rs Fields deferred with QuerySet.defer() or QuerySet.only() ジェネリックリレーション(汎用リレーション) Django copies the fetch mode of an instance to any related objects it fetches, so the mode applies to a whole tree of relationships, not just the ...
https://man.mtool.work/django/6.1/topics/db/fetch-modes.html
Django 6.1 release notes — Django 6.1 ドキュメント 10108
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 ... highly recommend , and only officially support, the latest release of each series. What's new in Django 6.1 ¶ Model field fetch modes ¶ The on-demand fetching behavior of model fields is now configurable with fetch modes . These modes allow you to co ... ntrol how Django 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 fetches a missing field for all instances that came from the same QuerySet . This mode works like an on-demand prefe ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 6.1 release notes — Django 6.1 ドキュメント 9910
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 ... highly recommend , and only officially support, the latest release of each series. What's new in Django 6.1 ¶ Model field fetch modes ¶ The on-demand fetching behavior of model fields is now configurable with fetch modes . These modes allow you to co ... ntrol how Django 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 fetches a missing field for all instances that came from the same QuerySet . This mode works like an on-demand prefe ...
https://man.mtool.work/django/6.1/releases/6.1.html
モデルインスタンスリファレンス — Django 6.1 ドキュメント 8374
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » モデルインスタンスリファレンス ¶ このドキュメントでは、 Model API の詳細を説明しています。 モデル と データベースクエリ ガイドにある説明を前提として ... e until it is reloaded . モデルの読み込みをカスタマイズする ¶ classmethod Model. from_db ( db , field_names , values , * , fetch_mode = None ) [ソース] ¶ from_db() メソッドを使うと、データベースから読み込むときのモデルインスタンス作成をカスタマイズでき ... won't appear in field_names . In that case, assign a value of django.db.models.DEFERRED to each of the missing fields. The fetch_mode argument contains the fetch mode of the query that loaded the instance, or None if it was loaded outside of a query. ... ing the new model, the from_db() method must set the adding and db flags in the new instance's _state attribute, and, when fetch_mode is not None , its fetch_mode attribute. 以下はデータベースから読み出されたフィールドの初期値をどのように保存しているの ...
https://man.mtool.work/django/6.1/ref/models/instances.html
Sprint quickstart guide — Django 6.1 ドキュメント 8317
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... the ticket claimed, create a branch for your work, replacing TicketNumber with the actual Trac ticket number: /  $ git fetch upstream $ git checkout -b ticket_TicketNumber upstream/main ...\> git fetch upstream ...\> git checkout -b ticket_TicketN ... . Run the following, replacing PRNumber and TicketNumber with the actual pull request and Trac ticket numbers: /  $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_TicketNumber $ git push origin ticket_TicketNumber . ... ..\> git fetch upstream pull/PRNumber/head:ticket_TicketNumber ...\> git checkout ticket_TicketNumber ...\> git push origin ticket_Ticket ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
Sprint quickstart guide — Django 6.1 ドキュメント 8317
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Sprint quickstart guide ¶ This document explains how to prepare to contribute to Django. It is intended for use during sprints, or by people who are ... the ticket claimed, create a branch for your work, replacing TicketNumber with the actual Trac ticket number: /  $ git fetch upstream $ git checkout -b ticket_TicketNumber upstream/main ...\> git fetch upstream ...\> git checkout -b ticket_TicketN ... . Run the following, replacing PRNumber and TicketNumber with the actual pull request and Trac ticket numbers: /  $ git fetch upstream pull/PRNumber/head:ticket_TicketNumber $ git checkout ticket_TicketNumber $ git push origin ticket_TicketNumber . ... ..\> git fetch upstream pull/PRNumber/head:ticket_TicketNumber ...\> git checkout ticket_TicketNumber ...\> git push origin ticket_Ticket ...
https://man.mtool.work/django/6.1/internals/contributing/sprint-quickstart.html
モデルインスタンスリファレンス — Django 6.1 ドキュメント 8275
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » モデルインスタンスリファレンス ¶ このドキュメントでは、 Model API の詳細を説明しています。 モデル と データベースクエリ ガイドにある説明を前提として ... e until it is reloaded . モデルの読み込みをカスタマイズする ¶ classmethod Model. from_db ( db , field_names , values , * , fetch_mode = None ) [ソース] ¶ from_db() メソッドを使うと、データベースから読み込むときのモデルインスタンス作成をカスタマイズでき ... won't appear in field_names . In that case, assign a value of django.db.models.DEFERRED to each of the missing fields. The fetch_mode argument contains the fetch mode of the query that loaded the instance, or None if it was loaded outside of a query. ... ing the new model, the from_db() method must set the adding and db flags in the new instance's _state attribute, and, when fetch_mode is not None , its fetch_mode attribute. 以下はデータベースから読み出されたフィールドの初期値をどのように保存しているの ...
https://man.mtool.work/django/6.1/ref/models/instances.html
データベースアクセスの最適化 — Django 6.1 ドキュメント 7894
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースアクセスの最適化 ¶ Djangoのデータベース層は、開発者がデータベースを最大限活用できるように、さまざまな方法を提供しています。このドキュメン ... doing many database queries, when only one is needed. Below are some techniques to combine queries for efficiency. Use the FETCH_PEERS fetch mode ¶ Use the FETCH_PEERS fetch mode to make on-demand field access more efficient with bulk-fetching. Enable ... it for all usage of your models with a custom manager . Using this fetch mode is easier than declaring fields to fetch with select_related() or prefetch_related() , especially when it's hard to p ... redict which fields will be accessed. QuerySet.select_related() や prefetch_related() を使用する ¶ When the FETCH_PEERS fetch mode is not appropriate or efficient enough, use select_related() and pr ...
https://man.mtool.work/django/6.1/topics/db/optimization.html
データベースアクセスの最適化 — Django 6.1 ドキュメント 7753
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースアクセスの最適化 ¶ Djangoのデータベース層は、開発者がデータベースを最大限活用できるように、さまざまな方法を提供しています。このドキュメン ... doing many database queries, when only one is needed. Below are some techniques to combine queries for efficiency. Use the FETCH_PEERS fetch mode ¶ Use the FETCH_PEERS fetch mode to make on-demand field access more efficient with bulk-fetching. Enable ... it for all usage of your models with a custom manager . Using this fetch mode is easier than declaring fields to fetch with select_related() or prefetch_related() , especially when it's hard to p ... redict which fields will be accessed. QuerySet.select_related() や prefetch_related() を使用する ¶ When the FETCH_PEERS fetch mode is not appropriate or efficient enough, use select_related() and pr ...
https://man.mtool.work/django/6.1/topics/db/optimization.html
PREV 1 2 3 4 5 6 7 NEXT