本文整理汇总了PHP中JobPeer::removeInstanceFromPool方法的典型用法代码示例。如果您正苦于以下问题：PHP JobPeer::removeInstanceFromPool方法的具体用法？PHP JobPeer::removeInstanceFromPool怎么用？PHP JobPeer::removeInstanceFromPool使用的例子？那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类JobPeer的用法示例。
在下文中一共展示了JobPeer::removeInstanceFromPool方法的1个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的PHP代码示例。
示例1: doDelete
/**
* Performs a DELETE on the database, given a Job or Criteria object OR a primary key value.
*
* @param mixed $values Criteria or Job object or primary key or array of primary keys
* which is used to create the DELETE statement
* @param PropelPDO $con the connection to use
* @return int The number of affected rows (if supported by underlying database driver). This includes CASCADE-related rows
* if supported by native driver or if emulated using Propel.
* @throws PropelException Any exceptions caught during processing will be
* rethrown wrapped into a PropelException.
*/
public static function doDelete($values, PropelPDO $con = null)
{
if ($con === null) {
$con = Propel::getConnection(JobPeer::DATABASE_NAME, Propel::CONNECTION_WRITE);
}
if ($values instanceof Criteria) {
// invalidate the cache for all objects of this type, since we have no
// way of knowing (without running a query) what objects should be invalidated
// from the cache based on this Criteria.
JobPeer::clearInstancePool();
// rename for clarity
$criteria = clone $values;
} elseif ($values instanceof Job) {
// it's a model object
// invalidate the cache for this single object
JobPeer::removeInstanceFromPool($values);
// create criteria based on pk values
$criteria = $values->buildPkeyCriteria();
} else {
// it's a primary key, or an array of pks
$criteria = new Criteria(JobPeer::DATABASE_NAME);
$criteria->add(JobPeer::ID, (array) $values, Criteria::IN);
// invalidate the cache for this object(s)
foreach ((array) $values as $singleval) {
JobPeer::removeInstanceFromPool($singleval);
}
}
// Set the correct dbName
$criteria->setDbName(JobPeer::DATABASE_NAME);
$affectedRows = 0;
// initialize var to track total num of affected rows
try {
// use transaction because $criteria could contain info
// for more than one table or we could emulating ON DELETE CASCADE, etc.
$con->beginTransaction();
$affectedRows += BasePeer::doDelete($criteria, $con);
JobPeer::clearRelatedInstancePool();
$con->commit();
return $affectedRows;
} catch (PropelException $e) {
$con->rollBack();
throw $e;
}
}