From: Kevin Kirsche Date: Wed, 8 Sep 2021 19:14:43 +0000 (-0400) Subject: fix: typos in doc/build/core and doc/build/errors (#7006) X-Git-Tag: rel_1_4_24~39 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b288e68c38a014a485892fc1b4910a52a0f88f4a;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git fix: typos in doc/build/core and doc/build/errors (#7006) --- diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst index 5bdcbbb648..ac9ee717fb 100644 --- a/doc/build/core/connections.rst +++ b/doc/build/core/connections.rst @@ -1409,7 +1409,7 @@ Basic guidelines include: # ... sqlalchemy.exc.InvalidRequestError: Closure variable named 'foo' inside of lambda callable at 0x7fed15f35450, file - "", line 2> does not refer to a cachable SQL element, and also + "", line 2> does not refer to a cacheable SQL element, and also does not appear to be serving as a SQL literal bound value based on the default SQL expression returned by the function. This variable needs to remain outside the scope of a SQL-generating lambda so that a proper cache @@ -1419,7 +1419,7 @@ Basic guidelines include: closure variables from being part of the cache key. The above error indicates that :class:`_sql.LambdaElement` will not assume - that the ``Foo`` object passed in will contine to behave the same in all + that the ``Foo`` object passed in will continue to behave the same in all cases. It also won't assume it can use ``Foo`` as part of the cache key by default; if it were to use the ``Foo`` object as part of the cache key, if there were many different ``Foo`` objects this would fill up the cache diff --git a/doc/build/errors.rst b/doc/build/errors.rst index 4058b06eaf..a8e0939a49 100644 --- a/doc/build/errors.rst +++ b/doc/build/errors.rst @@ -48,7 +48,7 @@ select() construct created in "legacy" mode; keyword arguments, etc. The :func:`_expression.select` construct has been updated as of SQLAlchemy 1.4 to support the newer calling style that will be standard in :ref:`SQLAlchemy 2.0 `. For backwards compatibility in the -interm, the construct accepts arguments in both the "legacy" style as well +interim, the construct accepts arguments in both the "legacy" style as well as the "new" style. The "new" style features that column and table expressions are passed @@ -1267,7 +1267,7 @@ attempt, which is unsupported when using SQLAlchemy with AsyncIO dialects. .. _error_xd3s: -No Inspection Avaliable +No Inspection Available ----------------------- Using the :func:`_sa.inspect` function directly on an