... 1.8.12 リリースノート 関連キーワード MySQL SQLite リリースノート fixes several bugs バグ 修正 Fixed TimeField microseconds round tripping Restored conversion empty saving values GenericIPAddressField クイック検索 Last update: 2026年10月09日 « previous ... ... リリースノート 関連キーワード Django MySQL SQLite リリースノート fixes several bugs バグ 修正 Fixed TimeField microseconds round tripping Restored conversion empty string null saving 関連するページ Django 1.10.2 リリースノート Django 1.11.8 リリースノ ... ... ssertRedirects() because Django 1.9 no longer converts redirects to absolute URIs ( #26428 ). Fixed TimeField microseconds round-tripping on MySQL and SQLite ( #26498 ). Prevented makemigrations from generating infinite migrations for a model field th ... d support relative path client SimpleTestCase assertRedirects because longer converts absolute URIs TimeField microseconds round クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... lt = 1 , y__radians__lt = 1 ) Random ¶ class Random ( ** extra ) [ソース] ¶ 0.0 ≤ x < 1.0 の範囲のランダムな値を返します。 Round ¶ class Round ( expression , precision = 0 , ** extra ) [ソース] ¶ 数値フィールドまたは式を precision (整数でなければなりま ... す。半分の値を切り上げるか切り下げるかはデータベースによって異なります。 使用例: >>> from django.db.models.functions import Round >>> Vector . objects . create ( x = 5.4 , y =- 2.37 ) >>> vector = Vector . objects . annotate ( x_r = Round ( "x" ), y_r ... = Round ( "y" , precision = 1 )) . get () >>> vector . x_r , vector . y_r (5.0, -2.4) トランスフォームとして登録することもできます ... ... lt = 1 , y__radians__lt = 1 ) Random ¶ class Random ( ** extra ) [ソース] ¶ 0.0 ≤ x < 1.0 の範囲のランダムな値を返します。 Round ¶ class Round ( expression , precision = 0 , ** extra ) [ソース] ¶ 数値フィールドまたは式を precision (整数でなければなりま ... す。半分の値を切り上げるか切り下げるかはデータベースによって異なります。 使用例: >>> from django.db.models.functions import Round >>> Vector . objects . create ( x = 5.4 , y =- 2.37 ) >>> vector = Vector . objects . annotate ( x_r = Round ( "x" ), y_r ... = Round ( "y" , precision = 1 )) . get () >>> vector . x_r , vector . y_r (5.0, -2.4) トランスフォームとして登録することもできます ... ... ask is raised. See defining tasks for usage examples. Task ¶ class Task [ソース] ¶ Represents a Task to be run in the background. Tasks should be defined using the task() decorator. Attributes of Task cannot be modified. See modifying Tasks for detail ... [ソース] ¶ Enqueues the Task to the Task backend for later execution. Arguments are passed to the Task 's function after a round-trip through a json.dumps() / json.loads() cycle. Hence, all arguments must be JSON-serializable and preserve their type a ... fter the round-trip. If the Task is not valid according to the backend, InvalidTask is raised. See enqueueing Tasks for usage examples. a ... ... ssertRedirects() because Django 1.9 no longer converts redirects to absolute URIs ( #26428 ). Fixed TimeField microseconds round-tripping on MySQL and SQLite ( #26498 ). Prevented makemigrations from generating infinite migrations for a model field th ... ... ask is raised. See defining tasks for usage examples. Task ¶ class Task [ソース] ¶ Represents a Task to be run in the background. Tasks should be defined using the task() decorator. Attributes of Task cannot be modified. See modifying Tasks for detail ... [ソース] ¶ Enqueues the Task to the Task backend for later execution. Arguments are passed to the Task 's function after a round-trip through a json.dumps() / json.loads() cycle. Hence, all arguments must be JSON-serializable and preserve their type a ... fter the round-trip. If the Task is not valid according to the backend, InvalidTask is raised. See enqueueing Tasks for usage examples. a ... ... responses. For some functionality, it may be beneficial to run code outside the request-response cycle. That's where background Tasks come in. Background Tasks can offload work to be run outside the request-response cycle, to be run elsewhere, potent ... or service. Given that, a task backend capable of executing tasks on that service should be evaluated and configured. Background Task fundamentals ¶ When work needs to be done in the background, Django creates a Task , which is stored in the Queue Sto ... ther is not specified in your settings file. The ImmediateBackend runs enqueued Tasks immediately, rather than in the background. This allows background Task functionality to be slowly added to an application, before the required infrastructure is ava ... ... responses. For some functionality, it may be beneficial to run code outside the request-response cycle. That's where background Tasks come in. Background Tasks can offload work to be run outside the request-response cycle, to be run elsewhere, potent ... or service. Given that, a task backend capable of executing tasks on that service should be evaluated and configured. Background Task fundamentals ¶ When work needs to be done in the background, Django creates a Task , which is stored in the Queue Sto ... ther is not specified in your settings file. The ImmediateBackend runs enqueued Tasks immediately, rather than in the background. This allows background Task functionality to be slowly added to an application, before the required infrastructure is ava ... 2026年10月08日