diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-08-18 11:29:25 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-08-18 11:30:23 -0400 |
| commit | 84fbfb0cb33f89e51ba223596f9a4dcebd822a99 (patch) | |
| tree | 42cc914037c2ac02d3ada5c490a47f082982d884 | |
| parent | d36188cb5e44b3fd38d54b6750236d8d9b7df255 (diff) | |
| download | sqlalchemy-84fbfb0cb33f89e51ba223596f9a4dcebd822a99.tar.gz | |
remove nonsensical note
this note is not factually incorrect but it makes no sense
why this would be in the middle of the abstract concrete doc
Change-Id: Icd67d9d9a93ee72714bf85d8d5ca39c0af61f356
(cherry picked from commit acf14885833da238606e6a0df7c5ab256e477f2c)
| -rw-r--r-- | doc/build/orm/inheritance.rst | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/build/orm/inheritance.rst b/doc/build/orm/inheritance.rst index ccda5f20b..0dd1a28c3 100644 --- a/doc/build/orm/inheritance.rst +++ b/doc/build/orm/inheritance.rst @@ -628,14 +628,6 @@ of ``Manager`` and ``Engineer`` instances. This brings us back into the domain of concrete inheritance, and we must build a special mapper against ``Employee`` in order to achieve this. -.. topic:: Mappers can always SELECT - - In SQLAlchemy, a mapper for a class always has to refer to some - "selectable", which is normally a :class:`_schema.Table` but may also refer to any - :func:`_expression.select` object as well. While it may appear that a "single table - inheritance" mapper does not map to a table, these mappers in fact - implicitly refer to the table that is mapped by a superclass. - To modify our concrete inheritance example to illustrate an "abstract" base that is capable of polymorphic loading, we will have only an ``engineer`` and a ``manager`` table and no ``employee`` |