diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-03-28 11:05:46 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-03-28 11:05:46 -0400 |
commit | 9cdbed37f8c420db0b42fb959813d079622c3f3a (patch) | |
tree | 2e57e771db9da7b51932ccdf6638eed8d7d3f2eb /lib/sqlalchemy/ext/automap.py | |
parent | 610e0594e249cd0bb28cb2bd4a7624f63f4510bb (diff) | |
download | sqlalchemy-9cdbed37f8c420db0b42fb959813d079622c3f3a.tar.gz |
clarify doc here
Diffstat (limited to 'lib/sqlalchemy/ext/automap.py')
-rw-r--r-- | lib/sqlalchemy/ext/automap.py | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/sqlalchemy/ext/automap.py b/lib/sqlalchemy/ext/automap.py index 1f9e00a12..dfc838da3 100644 --- a/lib/sqlalchemy/ext/automap.py +++ b/lib/sqlalchemy/ext/automap.py @@ -350,10 +350,10 @@ given as follows:: The foreign key from ``Engineer`` to ``Employee`` is used not for a relationship, but to establish joined inheritance between the two classes. -Note that this means automap will not generate **any relationships** that are -between these two classes, nor for any other classes in the same hierarchy. -If there are actually relationships between classes in the hierarchy, they -must be declared explicitly. Below, as we have two separate foreign keys +Note that this means automap will not generate *any* relationships +for foreign keys that link from a subclass to a superclass. If a mapping +has actual relationships from subclass to superclass as well, those +need to be explicit. Below, as we have two separate foreign keys from ``Engineer`` to ``Employee``, we need to set up both the relationship we want as well as the ``inherit_condition``, as these are not things SQLAlchemy can guess:: |