From 9d4152911e1e0d95f0753df3d501bbffc8b41040 Mon Sep 17 00:00:00 2001 From: acceptacross <150119116+acceptacross@users.noreply.github.com> Date: Tue, 12 Mar 2024 05:01:42 +0800 Subject: [PATCH] chore: remove repetitive words (#11134) Signed-off-by: acceptacross (cherry picked from commit 64b661d7058818ad6852b208a877804eba294d91) --- doc/build/changelog/changelog_14.rst | 6 +++--- doc/build/changelog/changelog_20.rst | 2 +- doc/build/orm/declarative_mixins.rst | 2 +- doc/build/tutorial/data_select.rst | 2 +- test/dialect/test_sqlite.py | 2 +- test/orm/test_selectin_relations.py | 4 ++-- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/build/changelog/changelog_14.rst b/doc/build/changelog/changelog_14.rst index 55e671e18b..1d6a3f775a 100644 --- a/doc/build/changelog/changelog_14.rst +++ b/doc/build/changelog/changelog_14.rst @@ -976,7 +976,7 @@ This document details individual issue-level changes made throughout Fixed regression where using ORM update() with synchronize_session='fetch' would fail due to the use of evaluators that are now used to determine the - in-Python value for expressions in the the SET clause when refreshing + in-Python value for expressions in the SET clause when refreshing objects; if the evaluators make use of math operators against non-numeric values such as PostgreSQL JSONB, the non-evaluable condition would fail to be detected correctly. The evaluator now limits the use of math mutation @@ -2810,7 +2810,7 @@ This document details individual issue-level changes made throughout :class:`_result.Result` class and implemented it for the filtered result implementations that are used by the ORM, so that it is possible to call the :meth:`_engine.CursorResult.close` method on the underlying - :class:`_engine.CursorResult` when the the ``yield_per`` execution option + :class:`_engine.CursorResult` when the ``yield_per`` execution option is in use to close a server side cursor before remaining ORM results have been fetched. This was again already available for Core result sets but the change makes it available for 2.0 style ORM results as well. @@ -9141,7 +9141,7 @@ This document details individual issue-level changes made throughout cascade operation actually takes place. The new behavior can be established as always by setting the flag to ``False`` on a specific :func:`_orm.relationship`, or more generally can be set up across the board - by setting the the :paramref:`_orm.Session.future` flag to True. + by setting the :paramref:`_orm.Session.future` flag to True. .. seealso:: diff --git a/doc/build/changelog/changelog_20.rst b/doc/build/changelog/changelog_20.rst index 30b1f9579f..8e3ee935b9 100644 --- a/doc/build/changelog/changelog_20.rst +++ b/doc/build/changelog/changelog_20.rst @@ -3612,7 +3612,7 @@ Added an error message when a :func:`_orm.relationship` is mapped against an abstract container type, such as ``Mapped[Sequence[B]]``, without providing the :paramref:`_orm.relationship.container_class` parameter which - is necessary when the type is abstract. Previously the the abstract + is necessary when the type is abstract. Previously the abstract container would attempt to be instantiated at a later step and fail. diff --git a/doc/build/orm/declarative_mixins.rst b/doc/build/orm/declarative_mixins.rst index 0ee8a952bb..9f26207c07 100644 --- a/doc/build/orm/declarative_mixins.rst +++ b/doc/build/orm/declarative_mixins.rst @@ -152,7 +152,7 @@ Augmenting the Base In addition to using a pure mixin, most of the techniques in this section can also be applied to the base class directly, for patterns that should apply to all classes derived from a particular base. The example -below illustrates some of the the previous section's example in terms of the +below illustrates some of the previous section's example in terms of the ``Base`` class:: from sqlalchemy import ForeignKey diff --git a/doc/build/tutorial/data_select.rst b/doc/build/tutorial/data_select.rst index 42b484de8e..aa77539b97 100644 --- a/doc/build/tutorial/data_select.rst +++ b/doc/build/tutorial/data_select.rst @@ -447,7 +447,7 @@ explicitly:: FROM user_account JOIN address ON user_account.id = address.user_id -The other is the the :meth:`_sql.Select.join` method, which indicates only the +The other is the :meth:`_sql.Select.join` method, which indicates only the right side of the JOIN, the left hand-side is inferred:: >>> print(select(user_table.c.name, address_table.c.email_address).join(address_table)) diff --git a/test/dialect/test_sqlite.py b/test/dialect/test_sqlite.py index 245b762cf3..07612480f2 100644 --- a/test/dialect/test_sqlite.py +++ b/test/dialect/test_sqlite.py @@ -3462,7 +3462,7 @@ class OnConflictTest(AssertsCompiledSQL, fixtures.TablesTest): ) # The last inserted primary key should be 2 here - # it is taking the result from the the exotic fixture + # it is taking the result from the exotic fixture eq_(result.inserted_primary_key, (2,)) eq_( diff --git a/test/orm/test_selectin_relations.py b/test/orm/test_selectin_relations.py index 93b3d8710c..d46362abdc 100644 --- a/test/orm/test_selectin_relations.py +++ b/test/orm/test_selectin_relations.py @@ -3340,7 +3340,7 @@ class M2OWDegradeTest( "FROM a WHERE a.id IN (__[POSTCOMPILE_id_1]) ORDER BY a.id", [{"id_1": [1, 3]}], ), - # in the very unlikely case that the the FK col on parent is + # in the very unlikely case that the FK col on parent is # deferred, we degrade to the JOIN version so that we don't need to # emit either for each parent object individually, or as a second # query for them. @@ -3431,7 +3431,7 @@ class M2OWDegradeTest( CompiledSQL( "SELECT a.id AS a_id, a.q AS a_q FROM a ORDER BY a.id", [{}] ), - # in the very unlikely case that the the FK col on parent is + # in the very unlikely case that the FK col on parent is # deferred, we degrade to the JOIN version so that we don't need to # emit either for each parent object individually, or as a second # query for them. -- 2.47.2