Doctrine_manual-1-2-en

Chapter 22: Event Listeners 313
postFetch() fetch() query, data
preFetchAll() fetchAll() query, data
postFetchAll() fetchAll() query, data
preExecute() and postExecute() only get invoked when
Doctrine_Connection::execute() is being called without prepared statement
parameters. Otherwise Doctrine_Connection::execute() invokes prePrepare(),
postPrepare(), preStmtExecute() and postStmtExecute().
Hydration Listeners
The hydration listeners can be used for listening to resultset hydration procedures. Two
methods exist for listening to the hydration procedure: preHydrate() and postHydrate().
If you set the hydration listener on connection level the code within the preHydrate() and
postHydrate() blocks will be invoked by all components within a multi-component
resultset. However if you add a similar listener on table level it only gets invoked when the
data of that table is being hydrated.
Consider we have a class called User with the following fields: first_name, last_name and
age. In the following example we create a listener that always builds a generated field called
full_name based on first_name and last_name fields.
// test.php
Listing
22-9
// ...
class HydrationListener extends Doctrine_Record_Listener
{
public function preHydrate(Doctrine_Event $event)
{
$data = $event->data;
$data['full_name'] = $data['first_name'] . ' ' .
$data['last_name'];
$event->data = $data;
}
}
Now all we need to do is attach this listener to the User record and fetch some users:
// test.php
Listing
22-10
// ...
$userTable = Doctrine_Core::getTable('User');
$userTable->addRecordListener(new HydrationListener());
$q = Doctrine_Query::create()
->from('User');
$users = $q->execute();
foreach ($users as $user) {
echo $user->full_name;
}
----------------- Brought to you by