From 4fad095858e218c1c53de3c1ce64fc438688f826 Mon Sep 17 00:00:00 2001 From: Lele Gaifax Date: Wed, 14 Jan 2009 17:02:17 +0000 Subject: [PATCH] Fix a hyperref --- doc/build/ormtutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/ormtutorial.rst b/doc/build/ormtutorial.rst index 6ce2e6b46d..a0db4369c7 100644 --- a/doc/build/ormtutorial.rst +++ b/doc/build/ormtutorial.rst @@ -1115,7 +1115,7 @@ The declarative setup is as follows: ... def __init__(self, keyword): ... self.keyword = keyword -Above, the many-to-many relation above is ``BlogPost.keywords``. The defining feature of a many to many relation is the ``secondary`` keyword argument which references a ``Table`` object representing the association table. This table only contains columns which reference the two sides of the relation; if it has *any* other columns, such as its own primary key, or foreign keys to other tables, SQLAlchemy requires a different usage pattern called the "association object", described at `association_pattern`. +Above, the many-to-many relation above is ``BlogPost.keywords``. The defining feature of a many to many relation is the ``secondary`` keyword argument which references a ``Table`` object representing the association table. This table only contains columns which reference the two sides of the relation; if it has *any* other columns, such as its own primary key, or foreign keys to other tables, SQLAlchemy requires a different usage pattern called the "association object", described at :ref:`association_pattern`. The many-to-many relation is also bi-directional using the ``backref`` keyword. This is the one case where usage of ``backref`` is generally required, since if a separate ``posts`` relation were added to the ``Keyword`` entity, both relations would independently add and remove rows from the ``post_keywords`` table and produce conflicts. -- 2.47.3