Doctrine_manual-1-2-en

Chapter 16: Behaviors 242
}
}
);
)
'local' => 'id',
'foreign' => 'user_id'
class Email extends Doctrine_Record
{
public function setTableDefinition()
{
$this->hasColumn('address', 'string');
$this->hasColumn('user_id', 'integer');
}
}
public function setUp()
{
$this->hasOne('User', array(
'local' => 'user_id',
'foreign' => 'id'
)
);
}
Listing
16-8
Here is the same example in YAML format. You can read more about YAML in the YAML
Schema Files (page 195) chapter:
---
User:
columns:
username: string(255)
password: string(255)
Email:
columns:
address: string
user_id: integer
relations:
User:
Now if we extend the User and Email classes and create, for example, classes
ExtendedUser and ExtendedEmail, the ExtendedUser will still have a relation to the
Email class and not the ExtendedEmail class. We could of course override the setUp()
method of the User class and define relation to the ExtendedEmail class, but then we lose
the whole point of inheritance. Doctrine_Template can solve this problem elegantly with
its dependency injection solution.
In the following example we'll define two templates, UserTemplate and EmailTemplate,
with almost identical definitions as the User and Email class had.
Listing
16-9
// models/UserTemplate.php
class UserTemplate extends Doctrine_Template
{
public function setTableDefinition()
{
$this->hasColumn('username', 'string', 255);
----------------- Brought to you by