per page, with , order by , clip by
Results of 1 - 10 of about 96 for appropriate (0.003 sec.)
Django 1.4.11 リリースノート — Django 6.1 ドキュメント 11609
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.11 リリースノート ¶ April 21, 2014 Django 1.4.11 fixes three security issues in 1.4.10. Additionally, Django's vendored version of six, d ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.4.11.html
Django 1.4.11 リリースノート — Django 6.1 ドキュメント 11438
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.11 リリースノート ¶ April 21, 2014 Django 1.4.11 fixes three security issues in 1.4.10. Additionally, Django's vendored version of six, d ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.4.11.html
Django 1.5.6 リリースノート — Django 6.1 ドキュメント 11438
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.6 リリースノート ¶ April 21, 2014 Django 1.5.6 fixes several bugs in 1.5.5, including three security issues. Unexpected code execution us ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.5.6.html
Django 1.5.6 リリースノート — Django 6.1 ドキュメント 11267
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.6 リリースノート ¶ April 21, 2014 Django 1.5.6 fixes several bugs in 1.5.5, including three security issues. Unexpected code execution us ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.5.6.html
Django 1.6.3 リリースノート — Django 6.1 ドキュメント 10598
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.3 リリースノート ¶ April 21, 2014 Django 1.6.3 fixes several bugs in 1.6.2, including three security issues, and makes one backwards-inco ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.6.3.html
Django 1.6.3 リリースノート — Django 6.1 ドキュメント 10440
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.3 リリースノート ¶ April 21, 2014 Django 1.6.3 fixes several bugs in 1.6.2, including three security issues, and makes one backwards-inco ... o callable views, and Django's own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke. Django also provides a convenience function -- reverse() -- which performs this process in the opposite di ... the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur if the query itself had been manipulated. Django's ... ally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which allow the developer to supply raw SQL or SQL f ...
https://man.mtool.work/django/6.1/releases/1.6.3.html
チケットをトリアージする — Django 6.1 ドキュメント 7932
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 ... ld probably be fixed if possible. For new features, accepted tickets should only exist after the idea has gone through the appropriate process for suggesting new features and received community and Steering Council approval, or been accepted in a DEP. Needs ... his flag is used for tickets that relate to User Interface and User Experiences questions. For example, this flag would be appropriate for user-facing features in forms or the admin interface. Cc ¶ You may add your username or email address to this field to ... をチケットとして送ってしまうことがあります) などです。 wontfix (修正しない) Used when someone decides that the request isn't appropriate for consideration in Django. Sometimes a ticket is closed as "wontfix" with a request for the reporter to start a discussi ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 7932
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 ... ld probably be fixed if possible. For new features, accepted tickets should only exist after the idea has gone through the appropriate process for suggesting new features and received community and Steering Council approval, or been accepted in a DEP. Needs ... his flag is used for tickets that relate to User Interface and User Experiences questions. For example, this flag would be appropriate for user-facing features in forms or the admin interface. Cc ¶ You may add your username or email address to this field to ... をチケットとして送ってしまうことがあります) などです。 wontfix (修正しない) Used when someone decides that the request isn't appropriate for consideration in Django. Sometimes a ticket is closed as "wontfix" with a request for the reporter to start a discussi ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
データベースアクセスの最適化 — Django 6.1 ドキュメント 7433
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースアクセスの最適化 ¶ Djangoのデータベース層は、開発者がデータベースを最大限活用できるように、さまざまな方法を提供しています。このドキュメン ... elds will be accessed. QuerySet.select_related() や prefetch_related() を使用する ¶ When the FETCH_PEERS fetch mode is not appropriate or efficient enough, use select_related() and prefetch_related() . Understand their documentation thoroughly and apply the ... values() や values_list() を使用する ¶ When you only want a dict or list of values, and don't need ORM model objects, make appropriate usage of values() . These can be useful for replacing model objects in template code - as long as the dicts you supply hav ... if you do use them, the ORM will have to go and get them in a separate query, making this a pessimization if you use it inappropriately. プロファイリングなしに、あまり積極的にフィールドの遅延を行わないようにしてください。たとえ、いくつかのカラムしか使用しな ...
https://man.mtool.work/django/6.1/topics/db/optimization.html
データベースアクセスの最適化 — Django 6.1 ドキュメント 7433
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベースアクセスの最適化 ¶ Djangoのデータベース層は、開発者がデータベースを最大限活用できるように、さまざまな方法を提供しています。このドキュメン ... elds will be accessed. QuerySet.select_related() や prefetch_related() を使用する ¶ When the FETCH_PEERS fetch mode is not appropriate or efficient enough, use select_related() and prefetch_related() . Understand their documentation thoroughly and apply the ... values() や values_list() を使用する ¶ When you only want a dict or list of values, and don't need ORM model objects, make appropriate usage of values() . These can be useful for replacing model objects in template code - as long as the dicts you supply hav ... if you do use them, the ORM will have to go and get them in a separate query, making this a pessimization if you use it inappropriately. プロファイリングなしに、あまり積極的にフィールドの遅延を行わないようにしてください。たとえ、いくつかのカラムしか使用しな ...
https://man.mtool.work/django/6.1/topics/db/optimization.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT