refer to undefer here

this is the option one might want to use to undefer
a deferred column into a subquery; the message here explains
that is not applicable in 1.4.

Change-Id: Iea6c48f69c540e11ff5c3f6c8c56cc5cf2bf257b

diff --git a/doc/build/changelog/unreleased_14/6661.rst b/doc/build/changelog/unreleased_14/6661.rst
index 6f08971be92e604565b13890e8897a9ad92a891a..9e4907f7918c93739532975c7918fdcc42dc1a6f 100644 (file)
--- a/doc/build/changelog/unreleased_14/6661.rst
+++ b/doc/build/changelog/unreleased_14/6661.rst
@@ -5,7 +5,7 @@
     Refined the behavior of ORM subquery rendering with regards to deferred
     columns and column properties to be more compatible with that of 1.3 while
     also providing for 1.4's newer features. As a subquery in 1.4 does not make
-    use of loader options, including :func:`_orm.deferred`, a subquery that is
+    use of loader options, including :func:`_orm.undefer`, a subquery that is
     against an ORM entity with deferred attributes will now render those
     deferred attributes that refer directly to mapped table columns, as these
     are needed in the outer SELECT if that outer SELECT makes use of these