per page, with , order by , clip by
Results of 1 - 10 of about 96 for below (0.006 sec.)
Django 1.2 リリースノート — Django 6.1 ドキュメント 11806
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... ch supports comparison operators. These are just the highlights; full details and a complete list of features may be found below . 参考 Django Advent covered the release of Django 1.2 with a series of articles and tutorials that cover some of the new ... me users, will be backwards-incompatible. The big changes are: Support for Python 2.3 has been dropped. See the full notes below. The new CSRF protection framework is not backwards-compatible with the old system. Users of the old system will not be af ... o the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware that a number of methods have had a change in prototype, detailed unde ...
https://man.mtool.work/django/6.1/releases/1.2.html
Django 1.2 リリースノート — Django 6.1 ドキュメント 11806
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.2 リリースノート ¶ 2010 年 5 月 17 日 Django 1.2 へようこそ! Nearly a year in the making, Django 1.2 packs an impressive list of new featur ... ch supports comparison operators. These are just the highlights; full details and a complete list of features may be found below . 参考 Django Advent covered the release of Django 1.2 with a series of articles and tutorials that cover some of the new ... me users, will be backwards-incompatible. The big changes are: Support for Python 2.3 has been dropped. See the full notes below. The new CSRF protection framework is not backwards-compatible with the old system. Users of the old system will not be af ... o the new CSRF protection framework requires a few important backwards-incompatible changes, detailed in CSRF Protection , below. Authors of custom Field subclasses should be aware that a number of methods have had a change in prototype, detailed unde ...
https://man.mtool.work/django/6.1/releases/1.2.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 10046
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... om argument on model fields. It's no longer valid and has been moved to the ModelAdmin class in admin.py . See the admin , below, for more details about changes to the admin. Remove core ¶ Remove the core argument from your model fields. It is no long ... d differently by the admin interface now. You don't have to worry about inline editing until you get to the admin section, below. For now, remove all references to core . Replace class Admin: with admin.py ¶ Remove all your inner class Admin declarati ... also won't do anything. To register apps with the admin you'll move those declarations to an admin.py file; see the admin below for more details. 参考 A contributor to djangosnippets has written a script that'll scan your models.py and generate a cor ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
Porting your apps from Django 0.96 to 1.0 — Django 6.1 ドキュメント 10046
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Porting your apps from Django 0.96 to 1.0 ¶ Django 1.0 breaks compatibility with 0.96 in some areas. This guide will help you port 0.96 projects and ... om argument on model fields. It's no longer valid and has been moved to the ModelAdmin class in admin.py . See the admin , below, for more details about changes to the admin. Remove core ¶ Remove the core argument from your model fields. It is no long ... d differently by the admin interface now. You don't have to worry about inline editing until you get to the admin section, below. For now, remove all references to core . Replace class Admin: with admin.py ¶ Remove all your inner class Admin declarati ... also won't do anything. To register apps with the admin you'll move those declarations to an admin.py file; see the admin below for more details. 参考 A contributor to djangosnippets has written a script that'll scan your models.py and generate a cor ...
https://man.mtool.work/django/6.1/releases/1.0-porting-guide.html
GIS QuerySet API リファレンス — Django 6.1 ドキュメント 9297
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » GIS QuerySet API リファレンス ¶ 空間のルックアップ (Spatial Lookup) ¶ このセクションの空間ルックアップは GeometryField と RasterField 用です。 For a ... bjects . filter ( poly__overlaps_above = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly |&> geom overlaps_below ¶ 利用可能なDB : PostGIS , PGRaster (Conversion) ジオメトリフィールドのバウンディングボックスがルックアップジオメトリのバウ ... ディングボックスと重なっているか、または下にあるかどうかをテストします。 実装例: Zipcode . objects . filter ( poly__overlaps_below = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly &<| geom strictly_above ¶ 利用可能なDB : PostGIS , PGRas ... bjects . filter ( poly__strictly_above = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly |>> geom strictly_below ¶ 利用可能なDB : PostGIS , PGRaster (Conversion) ジオメトリフィールドのバウンディングボックスが、ルックアップジオメトリのバ ...
https://man.mtool.work/django/6.1/ref/contrib/gis/geoquerysets.html
GIS QuerySet API リファレンス — Django 6.1 ドキュメント 9297
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » GIS QuerySet API リファレンス ¶ 空間のルックアップ (Spatial Lookup) ¶ このセクションの空間ルックアップは GeometryField と RasterField 用です。 For a ... bjects . filter ( poly__overlaps_above = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly |&> geom overlaps_below ¶ 利用可能なDB : PostGIS , PGRaster (Conversion) ジオメトリフィールドのバウンディングボックスがルックアップジオメトリのバウ ... ディングボックスと重なっているか、または下にあるかどうかをテストします。 実装例: Zipcode . objects . filter ( poly__overlaps_below = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly &<| geom strictly_above ¶ 利用可能なDB : PostGIS , PGRas ... bjects . filter ( poly__strictly_above = geom ) PostGIS では下記の SQL と同等です: SELECT ... WHERE poly |>> geom strictly_below ¶ 利用可能なDB : PostGIS , PGRaster (Conversion) ジオメトリフィールドのバウンディングボックスが、ルックアップジオメトリのバ ...
https://man.mtool.work/django/6.1/ref/contrib/gis/geoquerysets.html
How to release Django — Django 6.1 ドキュメント 9048
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... here are a lot of details, so please read on. Use the checklists app To generate a checklist compiling the tasks described below as relevant to the specific release(s) you are issuing, use the checklists app in the project admin . This populates a lot ... you want to use is not your default signing key, you'll need to add -u you@example.com to every GPG signing command shown below, where you@example.com is the email address associated with the key you want to use. A clean Python virtual environment (P ... y commit ). Update the version number in django/__init__.py for the release. Please see notes on setting the VERSION tuple below for details on VERSION ( example commit ). If this is a pre-release package also update the "Development Status" trove cla ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
How to release Django — Django 6.1 ドキュメント 9048
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up How to release Django ¶ このドキュメントでは、Django のリリース方法について説明しています。 これらの手順を変更した場合は、最新の情報を保ってください! ここでの ... here are a lot of details, so please read on. Use the checklists app To generate a checklist compiling the tasks described below as relevant to the specific release(s) you are issuing, use the checklists app in the project admin . This populates a lot ... you want to use is not your default signing key, you'll need to add -u you@example.com to every GPG signing command shown below, where you@example.com is the email address associated with the key you want to use. A clean Python virtual environment (P ... y commit ). Update the version number in django/__init__.py for the release. Please see notes on setting the VERSION tuple below for details on VERSION ( example commit ). If this is a pre-release package also update the "Development Status" trove cla ...
https://man.mtool.work/django/6.1/internals/howto-release-django.html
アグリゲーション (集計) — Django 6.1 ドキュメント 8299
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アグリゲーション (集計) ¶ Djangoのデータベース抽象API のトピックガイドでは、個別のオブジェクトの作成、取得、削除を行うDjangoのクエリの使い方を説明し ... SalamiPress>, ...]> >>> pubs [ 0 ] . num_books 73 # Each publisher, with a separate count of books with a rating above and below 5 >>> from django.db.models import Q >>> above_5 = Count ( "book" , filter = Q ( book__rating__gt = 5 )) >>> below_5 = Cou ... nt ( "book" , filter = Q ( book__rating__lte = 5 )) >>> pubs = Publisher . objects . annotate ( below_5 = below_5 ) . annotate ( above_5 = above_5 ) >>> pubs [ 0 ] . above_5 23 >>> pubs [ 0 ] . below_5 12 # The top 5 publish ...
https://man.mtool.work/django/6.1/topics/db/aggregation.html
アグリゲーション (集計) — Django 6.1 ドキュメント 8299
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アグリゲーション (集計) ¶ Djangoのデータベース抽象API のトピックガイドでは、個別のオブジェクトの作成、取得、削除を行うDjangoのクエリの使い方を説明し ... SalamiPress>, ...]> >>> pubs [ 0 ] . num_books 73 # Each publisher, with a separate count of books with a rating above and below 5 >>> from django.db.models import Q >>> above_5 = Count ( "book" , filter = Q ( book__rating__gt = 5 )) >>> below_5 = Cou ... nt ( "book" , filter = Q ( book__rating__lte = 5 )) >>> pubs = Publisher . objects . annotate ( below_5 = below_5 ) . annotate ( above_5 = above_5 ) >>> pubs [ 0 ] . above_5 23 >>> pubs [ 0 ] . below_5 12 # The top 5 publish ...
https://man.mtool.work/django/6.1/topics/db/aggregation.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT