AtkManyToOneRelation: Difference between revisions
Appearance
setLocalKey/setRemoteKey |
No edit summary |
||
| Line 1: | Line 1: | ||
{{relation}} | |||
== atkManyToOneRelation == | == atkManyToOneRelation == | ||
function atkManyToOneRelation($name, $destination, $flags=0) | function atkManyToOneRelation($name, $destination, $flags=0) | ||
Revision as of 21:53, 18 August 2008

atkManyToOneRelation
function atkManyToOneRelation($name, $destination, $flags=0)
- $name The name of the attribute.
- $destination The node we have a relationship with.
If you do not want to use the default primary keys (for example when the * side has a combined PK), you can override them by using the functions:
setLocalKey("a_id");
setRemoteKey("b_id");
Example
Projects all have one coordinator (node B), but one coordinator can have multiple projects (node A). So in the project class, there's a atkManyToOneRelation to a coordinator.
