diff options
| author | Jacob Walls <jacobtylerwalls@gmail.com> | 2025-09-17 09:19:25 -0400 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-09-17 13:28:58 -0300 |
| commit | b931156c207f661406635d49e0e29a51cacc1ab8 (patch) | |
| tree | 4d9adccade76009e4d7e6c9927ec08eb8790b0b6 /docs/ref/settings.txt | |
| parent | 9334499f537e402ce5b92708209933045a8c5e7d (diff) | |
Refs #35859 -- Removed support for Task enqueuing on transaction commit.
This removes the ability to configure Task enqueueing via a setting,
since the proposed `ENQUEUE_ON_COMMIT` did not support multi-database
setups.
Thanks to Simon Charette for the report.
Follow-up to 4289966d1b8e848e5e460b7c782dac009d746b20.
Diffstat (limited to 'docs/ref/settings.txt')
| -rw-r--r-- | docs/ref/settings.txt | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 54957a726a..b0750d3a42 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -2806,20 +2806,6 @@ You can use a backend that doesn't ship with Django by setting :setting:`BACKEND <TASKS-BACKEND>` to a fully-qualified path of a backend class (i.e. ``mypackage.backends.whatever.WhateverBackend``). -.. setting:: TASKS-ENQUEUE_ON_COMMIT - -``ENQUEUE_ON_COMMIT`` -~~~~~~~~~~~~~~~~~~~~~ - -Default: ``True`` - -Whether to enqueue a Task only after the current transaction, if any, commits -successfully, instead of enqueueing immediately. - -This can also be configured on a per-Task basis. - -See :ref:`Task transactions <task-transactions>` for more information. - .. setting:: TASKS-QUEUES ``QUEUES`` |