From 4b5ed6ad27b3b63ecf1b082653e2e3ee0abb887f Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 1 Jul 2022 14:35:27 -0400 Subject: [PATCH] clarify eager loading terminology Change-Id: Idb27ec5f09ef958d71738e1095b4be7a1377eecb --- doc/build/orm/queryguide.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/build/orm/queryguide.rst b/doc/build/orm/queryguide.rst index e0e85750ac..89f6a3bfa7 100644 --- a/doc/build/orm/queryguide.rst +++ b/doc/build/orm/queryguide.rst @@ -1092,10 +1092,12 @@ When ``yield_per`` is used, the set for the Core execution, so that a streaming / server side cursor will be used if the backend supports it. -The ``yield_per`` execution option **is not compatible with subqueryload eager -loading or joinedload eager loading when using collections**. It is -potentially compatible with selectinload eager loading, provided the database -driver supports multiple, independent cursors. +The ``yield_per`` execution option **is not compatible** with +:ref:`"subquery" eager loading ` loading or +:ref:`"joined" eager loading ` when using collections. It +is potentially compatible with :ref:`"select in" eager loading +` , provided the database driver supports multiple, +independent cursors. Additionally, the ``yield_per`` execution option is not compatible with the :meth:`_engine.Result.unique` method; as this method relies upon -- 2.47.2