Thread: [SQL-CVS] r1359 - SQLObject/docs
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: <sub...@co...> - 2005-12-07 15:52:22
|
Author: ianb Date: 2005-12-07 15:52:14 +0000 (Wed, 07 Dec 2005) New Revision: 1359 Modified: SQLObject/docs/SQLObject.comments.txt Log: Web updates Modified: SQLObject/docs/SQLObject.comments.txt =================================================================== --- SQLObject/docs/SQLObject.comments.txt 2005-12-07 15:46:23 UTC (rev 1358) +++ SQLObject/docs/SQLObject.comments.txt 2005-12-07 15:52:14 UTC (rev 1359) @@ -32,3 +32,12 @@ username: Mike Kent If I have this correctly: For a one-to-many relationship, you use 'ForeignKey' on the 'has one' side, and you use 'MultipleJoin' on the 'has many' side. I found this to be incredibly non-intuitive and confusing. How about 'hasOneOf' and 'hasManyOf'? Or would this cause a problem with a many-to-many relationship, since both sides would use 'hasManyOf'? +==== $(col-class-specifying-columns) c ++ c +++++ c +---------------------------------------- +date: 2005-12-07T08:52:14 +email: mk...@em... +id: 5 +ip: 208.255.226.178 +username: Mike Kent + +So if you declare a column as an alternateID, unique is implied, and we don't need to explicitly declare it? |