after the object has been written to the * database. * * Useful methods you can call on $oObject : * * * {@see DBObject::ListPreviousValuesForUpdatedAttributes()} : list of changed attributes and their values before the change * * {@see DBObject::Get()} : for a given attribute the new value that was persisted * * @param \cmdbAbstractObject $oObject The target object * @param CMDBChange|null $oChange A change context. Since 2.0 it is fine to ignore it, as the framework does maintain this information * once for all the changes made within the current page * * @return void * * @deprecated 3.1.0 N°4756 Use EVENT_DB_AFTER_WRITE event instead * @api * @since 2.7.0 N°2293 can access object changes by calling {@see DBObject::ListPreviousValuesForUpdatedAttributes()} on $oObject */ public function OnDBUpdate($oObject, $oChange = null); /** * Invoked when an object is created into the database * * The method is called right after the object has been written to the database. * * @param \cmdbAbstractObject $oObject The target object * @param CMDBChange|null $oChange A change context. Since 2.0 it is fine to ignore it, as the framework does maintain this information * once for all the changes made within the current page * * @return void * @deprecated 3.1.0 N°4756 Use EVENT_DB_AFTER_WRITE event instead * @api */ public function OnDBInsert($oObject, $oChange = null); /** * Invoked when an object is deleted from the database * * The method is called right before the object will be deleted from the database. * * @param \cmdbAbstractObject $oObject The target object * @param CMDBChange|null $oChange A change context. Since 2.0 it is fine to ignore it, as the framework does maintain this information * once for all the changes made within the current page * * @return void * @deprecated 3.1.0 N°4756 Use EVENT_DB_AFTER_DELETE event instead * @api */ public function OnDBDelete($oObject, $oChange = null); }