From 9ffdfbb578716d8f04fffd937e0ebc927337fd4d Mon Sep 17 00:00:00 2001 From: Lele Gaifax Date: Wed, 1 Feb 2023 20:24:53 +0100 Subject: [PATCH] Fix minor documentation glitch, replace "row" with "column" (#9215) --- doc/build/orm/inheritance.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/orm/inheritance.rst b/doc/build/orm/inheritance.rst index e99bc1df62..f54506b0ae 100644 --- a/doc/build/orm/inheritance.rst +++ b/doc/build/orm/inheritance.rst @@ -130,7 +130,7 @@ subclasses introduce a second identity are not supported. The ORM uses the value set up by :paramref:`_orm.Mapper.polymorphic_identity` in order to determine which class a row belongs towards when loading rows polymorphically. In the example above, every row which represents an -``Employee`` will have the value ``'employee'`` in its ``type`` row; similarly, +``Employee`` will have the value ``'employee'`` in its ``type`` column; similarly, every ``Engineer`` will get the value ``'engineer'``, and each ``Manager`` will get the value ``'manager'``. Regardless of whether the inheritance mapping uses distinct joined tables for subclasses as in joined table inheritance, or all -- 2.47.3