summaryrefslogtreecommitdiff
path: root/docs/releases/2.0.txt
diff options
context:
space:
mode:
authorDavid Smith <smithdc@gmail.com>2025-07-25 10:24:17 +0100
committernessita <124304+nessita@users.noreply.github.com>2025-08-25 10:51:10 -0300
commitf81e6e3a53ee36e3f730a71aa55a5744982dd016 (patch)
tree44a4fdd64e2d1489d80b1af8bd1ac3c7af3ad0dd /docs/releases/2.0.txt
parent4286a23df64f6ce3b9b6ed097f4d1aac7d9e0de4 (diff)
Refs #36485 -- Rewrapped docs to 79 columns line length.
Lines in the docs files were manually adjusted to conform to the 79 columns limit per line (plus newline), improving readability and consistency across the content.
Diffstat (limited to 'docs/releases/2.0.txt')
-rw-r--r--docs/releases/2.0.txt13
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/releases/2.0.txt b/docs/releases/2.0.txt
index cc30a64769..d1c013b622 100644
--- a/docs/releases/2.0.txt
+++ b/docs/releases/2.0.txt
@@ -387,8 +387,9 @@ backends.
* To enable support for :class:`~django.db.models.expressions.Window`
expressions, set ``DatabaseFeatures.supports_over_clause`` to ``True``. You
- may need to customize the ``DatabaseOperations.window_start_rows_start_end()``
- and/or ``window_start_range_start_end()`` methods.
+ may need to customize the
+ ``DatabaseOperations.window_start_rows_start_end()`` and/or
+ ``window_start_range_start_end()`` methods.
* Third-party database backends should add a
``DatabaseOperations.cast_char_field_without_max_length`` attribute with the
@@ -542,11 +543,11 @@ rebuild tables using a script similar to this::
This script hasn't received extensive testing and needs adaption for various
cases such as multiple databases. Feel free to contribute improvements.
-In addition, because of a table alteration limitation of SQLite, it's prohibited
-to perform :class:`~django.db.migrations.operations.RenameModel` and
+In addition, because of a table alteration limitation of SQLite, it's
+prohibited to perform :class:`~django.db.migrations.operations.RenameModel` and
:class:`~django.db.migrations.operations.RenameField` operations on models or
-fields referenced by other models in a transaction. In order to allow migrations
-containing these operations to be applied, you must set the
+fields referenced by other models in a transaction. In order to allow
+migrations containing these operations to be applied, you must set the
``Migration.atomic`` attribute to ``False``.
Miscellaneous