per page, with , order by , clip by
Results of 1 - 10 of about 98 for start (0.007 sec.)
データベース関数 — Django 6.1 ドキュメント 15223
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベース関数 ¶ The classes documented below provide a way for users to use functions provided by the underlying database as annotations, aggrega ... 渡すことは禁止されています。 日時関連の関数 ¶ 各関数の例では、以下のモデルを使用します: class Experiment ( models . Model ): start_datetime = models . DateTimeField () start_date = models . DateField ( null = True , blank = True ) start_time = models . ... actYear(...) が使えます。 使用例: >>> from datetime import datetime >>> from django.db.models.functions import Extract >>> start = datetime ( 2015 , 6 , 15 ) >>> end = datetime ( 2015 , 7 , 2 ) >>> Experiment . objects . create ( ... start_datetime = ... start , start_date = start . date (), end_datetime = end , end_date = end . date () ... ) >>> # Add the experiment start year as a field ...
https://man.mtool.work/django/6.1/ref/models/database-functions.html
データベース関数 — Django 6.1 ドキュメント 15223
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » データベース関数 ¶ The classes documented below provide a way for users to use functions provided by the underlying database as annotations, aggrega ... 渡すことは禁止されています。 日時関連の関数 ¶ 各関数の例では、以下のモデルを使用します: class Experiment ( models . Model ): start_datetime = models . DateTimeField () start_date = models . DateField ( null = True , blank = True ) start_time = models . ... actYear(...) が使えます。 使用例: >>> from datetime import datetime >>> from django.db.models.functions import Extract >>> start = datetime ( 2015 , 6 , 15 ) >>> end = datetime ( 2015 , 7 , 2 ) >>> Experiment . objects . create ( ... start_datetime = ... start , start_date = start . date (), end_datetime = end , end_date = end . date () ... ) >>> # Add the experiment start year as a field ...
https://man.mtool.work/django/6.1/ref/models/database-functions.html
Unit tests — Django 6.1 ドキュメント 7670
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... sting applications. See テストを書いて実行する for an explanation of how to write new tests. Running the unit tests ¶ Quickstart ¶ First, fork Django on GitHub . Second, create and activate a virtual environment. If you're not familiar with how to do ... test dependencies. Running the tests requires a Django settings module that defines the databases to use. To help you get started, Django provides and uses a sample settings module that uses the SQLite database. See Using another settings module to l ... lazy_objects ...\> runtests.py --settings=path.to.settings i18n.tests.TranslationTests.test_lazy_objects You can run tests starting at a specified top-level module with --start-at option. For example: /  $ ./runtests.py --start-at = wsgi ...\> runt ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 7670
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... sting applications. See テストを書いて実行する for an explanation of how to write new tests. Running the unit tests ¶ Quickstart ¶ First, fork Django on GitHub . Second, create and activate a virtual environment. If you're not familiar with how to do ... test dependencies. Running the tests requires a Django settings module that defines the databases to use. To help you get started, Django provides and uses a sample settings module that uses the SQLite database. See Using another settings module to l ... lazy_objects ...\> runtests.py --settings=path.to.settings i18n.tests.TranslationTests.test_lazy_objects You can run tests starting at a specified top-level module with --start-at option. For example: /  $ ./runtests.py --start-at = wsgi ...\> runt ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
クエリ式 (Query Expression) — Django 6.1 ドキュメント 7291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » クエリ式 (Query Expression) ¶ クエリ式 (query expression) は、update、create、filter、order by、annotation、またはaggregateの一部として使用できる値ま ... ¶ ウィンドウフレームでは、範囲ベースの行のシーケンスか、通常の行のシーケンスのいずれかを選択できます。 class ValueRange ( start = None , end = None , exclusion = None ) [ソース] ¶ frame_type ¶ この属性は 'RANGE' に設定されています。 PostgreSQLは Valu ... があり、 CURRENT ROW や UNBOUNDED FOLLOWING のような標準的な開始点と終了点の使用しかサポートしていません。 class RowRange ( start = None , end = None , exclusion = None ) [ソース] ¶ frame_type ¶ この属性は 'ROWS' に設定されています。 どちらのクラスもテ ... ンプレートとともにSQLを返します: % ( frame_type ) s BETWEEN % ( start ) s AND % ( end ) s class WindowFrameExclusion [ソース] ¶ CURRENT_ROW ¶ GROUP ¶ TIES ¶ NO_OTHERS ¶ exclusion 引数は、サポー ...
https://man.mtool.work/django/6.1/ref/models/expressions.html
PostGIS のインストール — Django 6.1 ドキュメント 7291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » PostGIS のインストール ¶ PostGIS は、PostgreSQL に地理オブジェクトのサポートを追加し、それを空間データベースに変えます。PostGIS をビルドする前に、 G ... _topology 拡張機能をインストールすることもできます。 データベースの管理 ¶ データベースの管理には、pgAdmin III プログラム ( Start ‣ PostgreSQL X ‣ pgAdmin III ) または SQL Shell ( Start ‣ PostgreSQL X ‣ SQL Shell ) を使用できます。例えば、 geodjango 空 ... sycopg postgresql 方法 CreateExtension topology Shell GeoDjango operations import migrations Migration raster 管理 pgAdmin Start ユーザ 地理 クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/ref/contrib/gis/install/postgis.html
クエリ式 (Query Expression) — Django 6.1 ドキュメント 7291
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » クエリ式 (Query Expression) ¶ クエリ式 (query expression) は、update、create、filter、order by、annotation、またはaggregateの一部として使用できる値ま ... ¶ ウィンドウフレームでは、範囲ベースの行のシーケンスか、通常の行のシーケンスのいずれかを選択できます。 class ValueRange ( start = None , end = None , exclusion = None ) [ソース] ¶ frame_type ¶ この属性は 'RANGE' に設定されています。 PostgreSQLは Valu ... があり、 CURRENT ROW や UNBOUNDED FOLLOWING のような標準的な開始点と終了点の使用しかサポートしていません。 class RowRange ( start = None , end = None , exclusion = None ) [ソース] ¶ frame_type ¶ この属性は 'ROWS' に設定されています。 どちらのクラスもテ ... ンプレートとともにSQLを返します: % ( frame_type ) s BETWEEN % ( start ) s AND % ( end ) s class WindowFrameExclusion [ソース] ¶ CURRENT_ROW ¶ GROUP ¶ TIES ¶ NO_OTHERS ¶ exclusion 引数は、サポー ...
https://man.mtool.work/django/6.1/ref/models/expressions.html
チケットをトリアージする — Django 6.1 ドキュメント 7108
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 ... s, this attribute easily tells us what and who each ticket is waiting on. Since a picture is worth a thousand words, let's start there: We have four roles in this diagram. Maintainers (also known as Fellows) usually take part in all of them, but anyon ... (Accepted + No Flags) The ticket is valid, but no one has submitted a patch for it yet. Often this means you could safely start writing a fix for it. This is generally more true for the case of accepted bugs than accepted features. A ticket for a bug ... sn't appropriate for consideration in Django. Sometimes a ticket is closed as "wontfix" with a request for the reporter to start a discussion on the Django Forum if they feel differently from the rationale provided by the person who closed the ticket. ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
チケットをトリアージする — Django 6.1 ドキュメント 7108
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 ... s, this attribute easily tells us what and who each ticket is waiting on. Since a picture is worth a thousand words, let's start there: We have four roles in this diagram. Maintainers (also known as Fellows) usually take part in all of them, but anyon ... (Accepted + No Flags) The ticket is valid, but no one has submitted a patch for it yet. Often this means you could safely start writing a fix for it. This is generally more true for the case of accepted bugs than accepted features. A ticket for a bug ... sn't appropriate for consideration in Django. Sometimes a ticket is closed as "wontfix" with a request for the reporter to start a discussion on the Django Forum if they feel differently from the rationale provided by the person who closed the ticket. ...
https://man.mtool.work/django/6.1/internals/contributing/triaging-tickets.html
Django 0.96 リリースノート — Django 6.1 ドキュメント 6847
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 ... lve, it's ready for use for most common cases. We recommend that anyone new to form handling skip the old forms system and start with the new. For more information about django.newforms , read the newforms documentation . URLconf improvements ¶ You ca ... ll continue to be valid for the foreseeable future. テストフレームワーク ¶ Django now includes a test framework so you can start transmuting fear into boredom (with apologies to Kent Beck). You can write tests based on doctest or unittest and test you ... res" -- initial data, stored in any of the supported serialization formats , that will be loaded into your database at the start of your tests. This makes testing with real data much easier. See the testing documentation for the full details. Improvem ...
https://man.mtool.work/django/6.1/releases/0.96.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT