From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Tue, 30 Mar 2021 23:46:04 +0000 (-0400)
Subject: link to the asyncio ORM section for this issue
X-Git-Tag: rel_1_4_4~2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=214e62aeb7bf7248767ad9e69f094ea69718180b;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

link to the asyncio ORM section for this issue

Change-Id: I1ef2230a1b1b77b55f3d835754836ca1bd023172
references: #6164
---

diff --git a/doc/build/errors.rst b/doc/build/errors.rst
index 7d767a7118..814f62a67c 100644
--- a/doc/build/errors.rst
+++ b/doc/build/errors.rst
@@ -1137,16 +1137,16 @@ with a non compatible :term:`DBAPI`.
 MissingGreenlet
 ---------------
 
-A call to the async :term:`DBAPI` was initiated outside the greenlet spawn context
-usually setup by the SQLAlchemy AsyncIO proxy classes.
-Usually this error happens when an IO was attempted in an unexpected 
-place, without using the provided async api.
-When using the ORM this may be due to a lazy loading attempt, which
-is unsupported when using SQLAlchemy with AsyncIO dialects.
+A call to the async :term:`DBAPI` was initiated outside the greenlet spawn
+context usually setup by the SQLAlchemy AsyncIO proxy classes. Usually this
+error happens when an IO was attempted in an unexpected place, without using
+the provided async api. When using the ORM this may be due to a lazy loading
+attempt, which is unsupported when using SQLAlchemy with AsyncIO dialects.
 
 .. seealso::
 
-    :ref:`_session_run_sync`
+    :ref:`asyncio_orm_avoid_lazyloads` - covers most ORM scenarios where
+    this problem can occur and how to mitigate.
 
 
 Core Exception Classes