diff options
| author | Lele Gaifax <lele@metapensiero.it> | 2023-02-01 20:24:53 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-01 20:24:53 +0100 |
| commit | 9ffdfbb578716d8f04fffd937e0ebc927337fd4d (patch) | |
| tree | 151ae45cd3260d9b7df0b7eecb6eaf9ec81d59ff | |
| parent | d84e6f8f3c6a346daaa021440a6804ce37f3cb56 (diff) | |
| download | sqlalchemy-9ffdfbb578716d8f04fffd937e0ebc927337fd4d.tar.gz | |
Fix minor documentation glitch, replace "row" with "column" (#9215)
| -rw-r--r-- | doc/build/orm/inheritance.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/orm/inheritance.rst b/doc/build/orm/inheritance.rst index e99bc1df6..f54506b0a 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 |