Author: phd
Date: 2004-12-01 14:25:00 +0000 (Wed, 01 Dec 2004)
New Revision: 428
Modified:
home/phd/SQLObject/inheritance/docs/Inheritance.txt
Log:
Corrected a number of misspellings and grammar errors.
Modified: home/phd/SQLObject/inheritance/docs/Inheritance.txt
===================================================================
--- home/phd/SQLObject/inheritance/docs/Inheritance.txt 2004-12-01 13:06:25 UTC (rev 427)
+++ home/phd/SQLObject/inheritance/docs/Inheritance.txt 2004-12-01 14:25:00 UTC (rev 428)
@@ -106,20 +106,19 @@
'inherited' classes. These clauses are the link between the id and the
parent id. This will look like the following request::
- SELECT employee.id, employee.id, employee.first_name,
- employee.last_name, from employee FROM person, employee WHERE
- person.first_name = 'Jane' AND employee.position = 'Chief' AND person.id
- = employee.id
+ SELECT employee.id, employee.first_name, employee.last_name
+ FROM person, employee WHERE person.first_name = 'Jane'
+ AND employee.position = 'Chief' AND person.id = employee.id
Some limitation or notice about this version:
-* Only simple inheritance will work. It is not possible to inherits
+* Only simple inheritance will work. It is not possible to inherit
from multiple SQLObject classes.
-* It is possible to inherits from an inherited class and this will
- works well. In the above exemple, you can have a Chief class that
+* It is possible to inherit from an inherited class and this will
+ work well. In the above exemple, you can have a Chief class that
inherits from Employee and all parents attributes will be
available through the Chief class.
-* You may not redefine a parent column in a inherited class (this
+* You may not redefine columns in an inherited class (this
will raise an exception).
* If you don't want 'childName' columns in your last class (one that
will never be inherited), you must set '_inheritable' to 0 in this
|
