From adec2c8dd878b8b2cb15341c0920dafcaf10fbf7 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 9 Dec 2011 16:57:29 -0500 Subject: [PATCH] should refer to Mapper class here --- doc/build/orm/tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/build/orm/tutorial.rst b/doc/build/orm/tutorial.rst index 2a56b3013c..6fa77d48f3 100644 --- a/doc/build/orm/tutorial.rst +++ b/doc/build/orm/tutorial.rst @@ -168,7 +168,7 @@ table, known as a **mapped class**. Declarative has provided for us a shorthan called a "Classical Mapping", which specifies these two units separately and is discussed in :ref:`classical_mapping`. The table is actually represented by a datastructure known as :class:`.Table`, and the mapping represented -by a "mapper" object generated by a function called :func:`.mapper`. Declarative performs both of +by a :class:`.Mapper` object generated by a function called :func:`.mapper`. Declarative performs both of these steps for us, making available the :class:`.Table` it has created via the ``__table__`` attribute:: @@ -179,7 +179,7 @@ these steps for us, making available the Column('fullname', String(), table=), Column('password', String(), table=), schema=None) -and while rarely needed, making available the :func:`.mapper` object via the ``__mapper__`` attribute:: +and while rarely needed, making available the :class:`.Mapper` object via the ``__mapper__`` attribute:: >>> User.__mapper__ # doctest: +ELLIPSIS -- 2.39.5