From 6daffe5406fcb4c4015229f0737a4c8218c66d76 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Alex=20Gr=C3=B6nholm?= Date: Mon, 25 Jun 2018 15:35:31 +0300 Subject: [PATCH] Fixed typo The name of the strategy is `raise_on_sql` as indicated elsewhere in the documentation. --- doc/build/orm/loading_relationships.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/orm/loading_relationships.rst b/doc/build/orm/loading_relationships.rst index 7173b40b29..f3ee78b129 100644 --- a/doc/build/orm/loading_relationships.rst +++ b/doc/build/orm/loading_relationships.rst @@ -54,7 +54,7 @@ The primary forms of relationship loading are: so that all members of related collections / scalar references are loaded at once by primary key. Select IN loading is detailed at :ref:`selectin_eager_loading`. -* **raise loading** - available via ``lazy='raise'``, ``lazy='raise_sql'``, +* **raise loading** - available via ``lazy='raise'``, ``lazy='raise_on_sql'``, or the :func:`.raiseload` option, this form of loading is triggered at the same time a lazy load would normally occur, except it raises an ORM exception in order to guard against the application making unwanted lazy loads. -- 2.47.2