Doctrine_manual-1-2-en

Chapter 22: Event Listeners 318
Listing
22-19
All of the above methods in the listener could optionally be placed in the user class below.
Doctrine will check there for the hooks as well:
class User extends Doctrine_Record
{
// ...
public function preDqlSelect()
{
// ...
}
public function preDqlUpdate()
{
// ...
}
}
public function preDqlDelete()
{
// ...
}
In order for these dql callbacks to be checked, you must explicitly turn them on. Because this
adds a small amount of overhead for each query, we have it off by default. We already
enabled this attribute in an earlier chapter.
Here it is again to refresh your memory:
Listing
22-20
// bootstrap.php
Listing
22-21
// ...
$manager->setAttribute(Doctrine_Core::ATTR_USE_DQL_CALLBACKS, true);
Now when you interact with the User model it will take in to account the deleted flag:
Delete user through record instance:
$user = new User();
$user->username = 'jwage';
$user->password = 'changeme';
$user->save();
$user->delete();
The above call to $user->delete() does not actually delete the record instead it sets the
deleted flag to true.
Listing
22-22
$q = Doctrine_Query::create()
->from('User u');
Listing
22-23
echo $q->getSqlQuery();
SELECT
u.id AS u__id,
u.username AS u__username,
u.password AS u__password,
u.deleted AS u__deleted
----------------- Brought to you by