Doctrine_manual-1-2-en

Chapter 10: Component Overview 178
Saving a Blank Record
By default Doctrine doesn't execute when save() is being called on an unmodified record.
There might be situations where you want to force-insert the record even if it has not been
modified. This can be achieved by assigning the state of the record to
Doctrine_Record::STATE_TDIRTY.
Listing
10-68
// test.php
// ...
$user = new User();
$user->state('TDIRTY');
$user->save();
When setting the state you can optionally pass a string for the state and it will be converted
to the appropriate state constant. In the example above, TDIRTY is actually converted to
Doctrine_Record::STATE_TDIRTY.
Mapping Custom Values
There might be situations where you want to map custom values to records. For example
values that depend on some outer sources and you only want these values to be available at
runtime not persisting those values into database. This can be achieved as follows:
Listing
10-69
// test.php
// ...
$user->mapValue('isRegistered', true);
$user->isRegistered; // true
Serializing
Sometimes you may want to serialize your record objects (possibly for caching purposes):
Listing
10-70
// test.php
// ...
$string = serialize($user);
$user = unserialize($string);
Checking Existence
Very commonly you'll need to know if given record exists in the database. You can use the
exists() method for checking if given record has a database row equivalent:
Listing
10-71
// test.php
// ...
$record = new User();
echo $record->exists() ? 'Exists':'Does Not Exist'; // Does Not Exist
$record->username = 'someone';
----------------- Brought to you by