From ccaadd5f6fa23e1e78503e0a67bce5cb127de9e6 Mon Sep 17 00:00:00 2001 From: Artem Smirnov Date: Tue, 6 Feb 2024 19:55:41 +0200 Subject: [PATCH] Add bullets (#10973) * Add bullets * Fix as suggested (cherry picked from commit 70ee72b2cb1dbfa37f29628737ab7dccf2de0fa3) --- doc/build/orm/inheritance.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/build/orm/inheritance.rst b/doc/build/orm/inheritance.rst index 3764270d8c..7a19de9ae4 100644 --- a/doc/build/orm/inheritance.rst +++ b/doc/build/orm/inheritance.rst @@ -3,12 +3,13 @@ Mapping Class Inheritance Hierarchies ===================================== -SQLAlchemy supports three forms of inheritance: **single table inheritance**, -where several types of classes are represented by a single table, **concrete -table inheritance**, where each type of class is represented by independent -tables, and **joined table inheritance**, where the class hierarchy is broken -up among dependent tables, each class represented by its own table that only -includes those attributes local to that class. +SQLAlchemy supports three forms of inheritance: + +* **single table inheritance** – several types of classes are represented by a single table; + +* **concrete table inheritance** – each type of class is represented by independent tables; + +* **joined table inheritance** – the class hierarchy is broken up among dependent tables. Each class represented by its own table that only includes those attributes local to that class. The most common forms of inheritance are single and joined table, while concrete inheritance presents more configurational challenges. -- 2.47.2