From: Lele Gaifax Date: Thu, 29 Dec 2022 09:21:09 +0000 (+0100) Subject: Rectify reference to class LambdaElement, misnamed as LamdaElement (#9037) X-Git-Tag: rel_2_0_0rc2~21 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f6bc1a8dbdc66b279e4b874a12ca6d7abe6482c6;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Rectify reference to class LambdaElement, misnamed as LamdaElement (#9037) Fixes #9034. (cherry picked from commit 532373b18f2e77910bb642a27a2cca3179499389) --- diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst index 643b7e705c..1b842a4e92 100644 --- a/doc/build/core/connections.rst +++ b/doc/build/core/connections.rst @@ -1424,7 +1424,7 @@ Quick Guidelines for Lambdas Above all, the emphasis within the lambda SQL system is ensuring that there is never a mismatch between the cache key generated for a lambda and the -SQL string it will produce. The :class:`_sql.LamdaElement` and related +SQL string it will produce. The :class:`_sql.LambdaElement` and related objects will run and analyze the given lambda in order to calculate how it should be cached on each run, trying to detect any potential problems. Basic guidelines include: