Doctrine_manual-1-2-en

Chapter 7: Defining Models 74
Listing
7-58
// models/Task.php
class Task extends Doctrine_Record
{
public function setTableDefinition()
{
$this->hasColumn('name', 'string', 100);
$this->hasColumn('parent_id', 'integer');
}
public function setUp()
{
$this->hasOne('Task as Parent', array(
'local' => 'parent_id',
'foreign' => 'id'
)
);
}
}
$this->hasMany('Task as Subtasks', array(
'local' => 'id',
'foreign' => 'parent_id'
)
);
Here is the same example in YAML format. You can read more about YAML in the YAML
Schema Files (page 195) chapter:
Listing
7-59
---
# schema.yml
# ...
Task:
columns:
name: string(100)
parent_id: integer
relations:
Parent:
class: Task
local: parent_id
foreign: id
foreignAlias: Subtasks
The above implementation is purely an example and is not the most efficient way to store
and retrieve hierarchical data. Check the NestedSet behavior included in Doctrine for the
recommended way to deal with hierarchical data.
Join Table Associations
Many to Many
If you are coming from relational database background it may be familiar to you how many-tomany
associations are handled: an additional association table is needed.
----------------- Brought to you by