From c81eb1ca289d486c8a45511f439a8b2d8a9808b6 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sun, 8 Jan 2006 19:05:53 +0000 Subject: [PATCH] typos --- doc/build/content/adv_datamapping.myt | 3 ++- doc/build/content/datamapping.myt | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/build/content/adv_datamapping.myt b/doc/build/content/adv_datamapping.myt index 0dc1a0349f..11d492eb1f 100644 --- a/doc/build/content/adv_datamapping.myt +++ b/doc/build/content/adv_datamapping.myt @@ -321,7 +321,8 @@ WHERE rowcount.user_id = users.user_id ORDER BY users.oid, addresses.oid <&|doclib.myt:item, name="inheritance", description="Mapping a Class with Table Inheritance" &> -

Table Inheritance indicates the pattern where two tables, in a parent-child relationship, are mapped to an inheritance chain of classes. If a table "employees" contains additional information about managers in the table "mangaers", a corresponding object inheritance pattern would have an Employee class and a Manager class. Loading a Mangaer object means you are joining managers to employees. For SQLAlchemy, this pattern is just a special case of a mapper that maps against a joined relationship, and is provided via the inherits keyword. + +

Table Inheritance indicates the pattern where two tables, in a parent-child relationship, are mapped to an inheritance chain of classes. If a table "employees" contains additional information about managers in the table "managers", a corresponding object inheritance pattern would have an Employee class and a Manager class. Loading a Manager object means you are joining managers to employees. For SQLAlchemy, this pattern is just a special case of a mapper that maps against a joined relationship, and is provided via the inherits keyword. <&|formatting.myt:code&> class User(object): """a user object.""" diff --git a/doc/build/content/datamapping.myt b/doc/build/content/datamapping.myt index 3bcfe5c767..2d9347da1d 100644 --- a/doc/build/content/datamapping.myt +++ b/doc/build/content/datamapping.myt @@ -331,7 +331,8 @@ DELETE FROM addresses WHERE addresses.address_id = :address_id >>> a1.user is user and a2.user is user True -

The backreference feature also works with many-to-many relationships, which are described later. When creating a backreference, a corresponding property is placed on the child mapper. This proeprty can be overridden with a custom property using the add_property function: + ++

The backreference feature also works with many-to-many relationships, which are described later. When creating a backreference, a corresponding property is placed on the child mapper. This property can be overridden with a custom property using the add_property function: <&|formatting.myt:code&> Address.mapper = mapper(Address, addresses) -- 2.47.2