_update_cache_set

Store data in the private update status cache table.

Note: this function completely ignores the {cache_update}.headers field since that is meaningless for the kinds of data we're caching.

Parameters

$cid: The cache ID to save the data with.

$data: The data to store.

$expire: One of the following values:

• CACHE_PERMANENT: Indicates that the item should never be removed except by explicitly using _update_cache_clear() or update_invalidate_cache().
• A Unix timestamp: Indicates that the item should be kept at least until the given time, after which it will be invalidated.

Related topics

Private update status cache system

We specifically do NOT use the core cache API for saving the fetched data about available updates. It is vitally important that this cache is only cleared when we're populating it after successfully fetching new available update data. Usage of…

3 calls to _update_cache_set()

File

modules/update/update.module, line 546

The "Update status" module checks for available updates of Drupal core and any installed contributed modules and themes. It warns site administrators if newer releases are available via the system status report (admin/reports/status), the…

Code

function _update_cache_set($cid, $data, $expire) {
  $serialized = 0;
  if (is_object($data) || is_array($data)) {
    $data = serialize($data);
    $serialized = 1;
  }
  $created = time();
  db_query("UPDATE {cache_update} SET data = %b, created = %d, expire = %d, serialized = %d WHERE cid = '%s'", $data, $created, $expire, $serialized, $cid);
  if (!db_affected_rows()) {
    @db_query("INSERT INTO {cache_update} (cid, data, created, expire, serialized) VALUES ('%s', %b, %d, %d, %d)", $cid, $data, $created, $expire, $serialized);
  }
}