# ...
sqlalchemy.exc.InvalidRequestError: Closure variable named 'foo' inside of
lambda callable <code object <lambda> at 0x7fed15f35450, file
- "<stdin>", line 2> does not refer to a cachable SQL element, and also
+ "<stdin>", 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
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
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 <error_b8d9>`. 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
.. _error_xd3s:
-No Inspection Avaliable
+No Inspection Available
-----------------------
Using the :func:`_sa.inspect` function directly on an
projects / thirdparty / sqlalchemy / sqlalchemy.git / commitdiff
