per page, with , order by , clip by
Results of 1 - 10 of about 114 for within (0.005 sec.)
Django 1.8 リリースノート — Django 6.1 ドキュメント 11137
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... s built-in support for the Django template language and for Jinja2 . It supports rendering templates with multiple engines within the same project. Learn more about the new features in the topic guide and check the upgrade instructions in older version ... y() has also gained the ability to accept expressions. Conditional Expressions allow you to use if ... elif ... else logic within queries. A collection of database functions is also included with functionality such as Coalesce , Concat , and Substr . T ... he MyISAM storage engine, will still be able to run these tests but won't benefit from the improvements. Tests are now run within two nested atomic() blocks: one for the whole class and one for each test. The class method TestCase.setUpTestData() adds ...
https://man.mtool.work/django/6.1/releases/1.8.html
Django 1.8 リリースノート — Django 6.1 ドキュメント 11137
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... s built-in support for the Django template language and for Jinja2 . It supports rendering templates with multiple engines within the same project. Learn more about the new features in the topic guide and check the upgrade instructions in older version ... y() has also gained the ability to accept expressions. Conditional Expressions allow you to use if ... elif ... else logic within queries. A collection of database functions is also included with functionality such as Coalesce , Concat , and Substr . T ... he MyISAM storage engine, will still be able to run these tests but won't benefit from the improvements. Tests are now run within two nested atomic() blocks: one for the whole class and one for each test. The class method TestCase.setUpTestData() adds ...
https://man.mtool.work/django/6.1/releases/1.8.html
GIS QuerySet API リファレンス — Django 6.1 ドキュメント 10696
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » GIS QuerySet API リファレンス ¶ 空間のルックアップ (Spatial Lookup) ¶ このセクションの空間ルックアップは GeometryField と RasterField 用です。 For a ... します。 実装例: Zipcode . objects . filter ( poly__contained = geom ) バックエンド 等価なSQL PostGIS poly @ geom MariaDB MBRWithin(poly, geom) MySQL MBRWithin(poly, geom) SpatiaLite MbrWithin(poly, geom) contains ¶ 利用可能なDB : PostGIS , Oracle, Maria ... m) MariaDB ST_Touches(poly, geom) MySQL ST_Touches(poly, geom) Oracle SDO_TOUCH(poly, geom) SpatiaLite Touches(poly, geom) within ¶ 利用可能なDB : PostGIS , Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) ジオメトリフィールドが空間的にルックア ... ップジオメトリ内にあるかどうかをテストします。 実装例: Zipcode . objects . filter ( poly__within = geom ) バックエンド 等価なSQL PostGIS ST_Within(poly, geom) MariaDB ST_Within(poly, geom) MySQL ST_Within(poly, geom) Or ...
https://man.mtool.work/django/6.1/ref/contrib/gis/geoquerysets.html
GIS QuerySet API リファレンス — Django 6.1 ドキュメント 10696
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » GIS QuerySet API リファレンス ¶ 空間のルックアップ (Spatial Lookup) ¶ このセクションの空間ルックアップは GeometryField と RasterField 用です。 For a ... します。 実装例: Zipcode . objects . filter ( poly__contained = geom ) バックエンド 等価なSQL PostGIS poly @ geom MariaDB MBRWithin(poly, geom) MySQL MBRWithin(poly, geom) SpatiaLite MbrWithin(poly, geom) contains ¶ 利用可能なDB : PostGIS , Oracle, Maria ... m) MariaDB ST_Touches(poly, geom) MySQL ST_Touches(poly, geom) Oracle SDO_TOUCH(poly, geom) SpatiaLite Touches(poly, geom) within ¶ 利用可能なDB : PostGIS , Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) ジオメトリフィールドが空間的にルックア ... ップジオメトリ内にあるかどうかをテストします。 実装例: Zipcode . objects . filter ( poly__within = geom ) バックエンド 等価なSQL PostGIS ST_Within(poly, geom) MariaDB ST_Within(poly, geom) MySQL ST_Within(poly, geom) Or ...
https://man.mtool.work/django/6.1/ref/contrib/gis/geoquerysets.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 8934
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... e be aware that this security release is slightly different from previous ones. Both issues addressed here have been dealt with in prior security updates to Django. In one case, we have received ongoing reports of problems, and in the other we've chose ... s to Django's HTTP redirect classes, performing additional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a commo ... tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this functio ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 8934
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... e be aware that this security release is slightly different from previous ones. Both issues addressed here have been dealt with in prior security updates to Django. In one case, we have received ongoing reports of problems, and in the other we've chose ... s to Django's HTTP redirect classes, performing additional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a commo ... tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this functio ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 8720
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... e be aware that this security release is slightly different from previous ones. Both issues addressed here have been dealt with in prior security updates to Django. In one case, we have received ongoing reports of problems, and in the other we've chose ... s to Django's HTTP redirect classes, performing additional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a commo ... tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this functio ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 8720
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... e be aware that this security release is slightly different from previous ones. Both issues addressed here have been dealt with in prior security updates to Django. In one case, we have received ongoing reports of problems, and in the other we've chose ... s to Django's HTTP redirect classes, performing additional validation of the scheme of the URL to redirect to (since, both within Django's own supplied applications and many third-party applications, accepting a user-supplied redirect target is a commo ... tighter validation in response to reported problems (primarily with third-party applications, but to a certain extent also within Django itself). This comes in two parts: 1. A new utility function, django.utils.http.is_safe_url , is added; this functio ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 8494
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... 届きます。 Once you've submitted an issue via email, you should receive an acknowledgment from a member of the security team within 3 working days. After that, the security team will begin their analysis. Depending on the action to be taken, you may rece ... There is no need to chase the security team unless you discover new, relevant information. All reports aim to be resolved within the industry-standard 90 days. Confirmed vulnerabilities with a high severity level will be addressed promptly. 暗号化され ... are criteria used by the security team when evaluating whether a report requires a security release: The vulnerability is within a supported version of Django. The vulnerability does not depend on manual actions that rely on code external to Django. T ...
https://man.mtool.work/django/6.1/internals/security.html
Django のセキュリティポリシー — Django 6.1 ドキュメント 8280
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django のセキュリティポリシー ¶ Django の開発チームは、セキュリティ関連の問題の責任ある報告と開示に強くコミットしています。そのため、私たちはその理想 ... 届きます。 Once you've submitted an issue via email, you should receive an acknowledgment from a member of the security team within 3 working days. After that, the security team will begin their analysis. Depending on the action to be taken, you may rece ... There is no need to chase the security team unless you discover new, relevant information. All reports aim to be resolved within the industry-standard 90 days. Confirmed vulnerabilities with a high severity level will be addressed promptly. 暗号化され ... are criteria used by the security team when evaluating whether a report requires a security release: The vulnerability is within a supported version of Django. The vulnerability does not depend on manual actions that rely on code external to Django. T ...
https://man.mtool.work/django/6.1/internals/security.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT