Home | Trees | Indices | Help |
|
---|
|
object --+ | property --+ | datatypes.datatype --+ | _container
|
|||
|
__init__(self,
child_relation,
child_column,
child_key=None,
title=None) @param child_relation: sql.relation object or string, indicating the name of the dependent relation. |
||
|
__init_dbclass__(self,
dbclass,
attribute_name) This methods gets called by dbobject's metaclass. |
||
|
__set_from_result__(self,
ds,
dbobj,
value) A container is not selected from a result. |
||
|
__convert__(self,
value) Containers do not need a convert method or can't use it anyway. |
||
|
sql_literal(self,
dbobj) This container cannot be represented as an SQL literal. |
||
| __select_this_column__(self) | ||
| __select_after_insert__(self, dbobj) | ||
|
child_where(self,
dbobj) A where clause that leads to all the rows in the child table associated with this parent table. |
||
Inherited from Inherited from Inherited from |
|
|||
Inherited from Inherited from |
|
|||
Inherited from |
|
@param child_relation: sql.relation object or string, indicating the name of the dependent relation. @param child_column: It's datatype (datatype object). The datatype's column parameter may be used as well as teh validators. Title and has_default will be ignored. The column name defaults to the container's attribute_name in the parent dbclass. @param child_key: A string indicating the column in the child relation that is used in the foreign key to point to the parent. The the docstrings of the actual implementations for examples, that's going to make it clearer. As a sidenote: This only works for a single-column reference key from the parent class to the child class. It would be possible implementing this for multiple column keys using an anonymous dbclass, but it's just soooo darn complicated! So I thought to myself that orm2 is complecated enough...
|
|
|
|
|
|
|
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0alpha3 on Wed Feb 20 18:17:24 2008 | http://epydoc.sourceforge.net |