per page, with , order by , clip by
Results of 1 - 10 of about 46 for people (0.004 sec.)
マネージャ — Django 6.1 ドキュメント 13349
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » マネージャ ¶ class Manager [ソース] ¶ マネージャ (Manager) とは、Django のモデルに対するデータベースクエリの操作を提供するインターフェイスです。Djan ... 、クラス変数を定義します。たとえば、次のように書きます。 from django.db import models class Person ( models . Model ): # ... people = models . Manager () このモデル例を使うと、 Person.objects は AttributeError 例外を起こしますが、 Person.people.all() と書 ... ( max_length = 50 ) role = models . CharField ( max_length = 1 , choices = { "A" : _ ( "Author" ), "E" : _ ( "Editor" )}) people = models . Manager () authors = AuthorManager () editors = EditorManager () この例では、 Person.authors.all() 、 Person.ed ... itors.all() 、 Person.people.all() を指定でき、期待通りの結果が得られます。 デフォルトマネージャ ¶ Model. _default_manager ¶ カスタムの Manager オブジェ ...
https://man.mtool.work/django/6.1/topics/db/managers.html
マネージャ — Django 6.1 ドキュメント 12464
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » マネージャ ¶ class Manager [ソース] ¶ マネージャ (Manager) とは、Django のモデルに対するデータベースクエリの操作を提供するインターフェイスです。Djan ... 、クラス変数を定義します。たとえば、次のように書きます。 from django.db import models class Person ( models . Model ): # ... people = models . Manager () このモデル例を使うと、 Person.objects は AttributeError 例外を起こしますが、 Person.people.all() と書 ... ( max_length = 50 ) role = models . CharField ( max_length = 1 , choices = { "A" : _ ( "Author" ), "E" : _ ( "Editor" )}) people = models . Manager () authors = AuthorManager () editors = EditorManager () この例では、 Person.authors.all() 、 Person.ed ... itors.all() 、 Person.people.all() を指定でき、期待通りの結果が得られます。 デフォルトマネージャ ¶ Model. _default_manager ¶ カスタムの Manager オブジェ ...
https://man.mtool.work/django/6.1/topics/db/managers.html
アクセシビリティ — Django 6.1 ドキュメント 9824
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... make digital accessibility easier. サポート対象とテスト ¶ Beyond standards, we want to make sure Django actually works for people using a wide range of input devices and assistive technologies. This has benefits to make sure Django works better for eve ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
アクセシビリティ — Django 6.1 ドキュメント 9824
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... make digital accessibility easier. サポート対象とテスト ¶ Beyond standards, we want to make sure Django actually works for people using a wide range of input devices and assistive technologies. This has benefits to make sure Django works better for eve ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
チケットをトリアージする — Django 6.1 ドキュメント 9519
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... uest and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Mergers: people with commit access who make the final decision to merge a change. When we say anyone, we mean you! Our Trac system and Git ... and Steering Council approval, or been accepted in a DEP. Needs PR Review (Accepted + Has Patch) The ticket is waiting for people to review the supplied solution. This means downloading the patch and trying it out, verifying that it contains tests and ... ter reproducing and confirming the issue. Please don't promote your own tickets to "Ready for checkin". You may mark other people's tickets that you've reviewed as "Ready for checkin", but you should get at minimum one other community member to review ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 9519
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » チケットをトリアージする ¶ Django uses Trac for managing the work on the code base. Trac is a community-tended garden of the bugs people have found ... uest and working on a solution for a ticket. Reviewers: anyone can review pull requests and suggest improvements. Mergers: people with commit access who make the final decision to merge a change. When we say anyone, we mean you! Our Trac system and Git ... and Steering Council approval, or been accepted in a DEP. Needs PR Review (Accepted + Has Patch) The ticket is waiting for people to review the supplied solution. This means downloading the patch and trying it out, verifying that it contains tests and ... ter reproducing and confirming the issue. Please don't promote your own tickets to "Ready for checkin". You may mark other people's tickets that you've reviewed as "Ready for checkin", but you should get at minimum one other community member to review ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Working with Git and GitHub — Django 6.1 ドキュメント 8650
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... "topic branch" in Git parlance. You are free to rewrite the history of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also ... "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good examples of public branches are the main ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Django 0.96 リリースノート — Django 6.1 ドキュメント 8650
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.96 リリースノート ¶ Django 0.96 へようこそ! The primary goal for 0.96 is a cleanup and stabilization of the features introduced in 0.95. Th ... ace, so you no longer need to worry about working with hashed passwords in the admin. ありがとう ¶ Since 0.95, a number of people have stepped forward and taken a major new role in Django's development. We'd like to thank these people for all their har ...
https://man.mtool.work/django/6.1/releases/0.96.html
Working with Git and GitHub — Django 6.1 ドキュメント 8650
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Working with Git and GitHub ¶ This section explains how the community can contribute code to Django via pull requests. If you're interested in how m ... "topic branch" in Git parlance. You are free to rewrite the history of this branch, by using git rebase for example. Other people shouldn't base their work on such a branch, because their clone would become corrupt when you edit commits. There are also ... "public branches". These are branches other people are supposed to fork, so the history of these branches should never change. Good examples of public branches are the main ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/working-wi...
Django 0.96 リリースノート — Django 6.1 ドキュメント 8650
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 0.96 リリースノート ¶ Django 0.96 へようこそ! The primary goal for 0.96 is a cleanup and stabilization of the features introduced in 0.95. Th ... ace, so you no longer need to worry about working with hashed passwords in the admin. ありがとう ¶ Since 0.95, a number of people have stepped forward and taken a major new role in Django's development. We'd like to thank these people for all their har ...
https://man.mtool.work/django/6.1/releases/0.96.html
PREV 1 2 3 4 5 NEXT