wppaste
WordPress

upgrade_110()

Since
1.2.0, 6.8.0
Source
wp-admin/includes/upgrade.php:996
Execute changes made in WordPress 1.2.

Compatibility

WordPress
since 6.8.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Performance profile

How much work a call to upgrade_110() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Heavy

Reaches the database via ->get_results().

Scaling
Scales with input

The body loops, so the work grows with how much data it finds.

Instructions
45–101

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 121.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

  • optionoption read or writeadd_option()called directly
  • sqldatabase query->get_results()called directly
  • hookthird-party callbacksapply_filters()one call below upgrade_110()
  • cacheobject cachewp_cache_get()one call below upgrade_110()
  • serializeserialisationmaybe_serialize()one call below upgrade_110()

Further down the call graph this can also reach query and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost upgrade_110() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always45–46->get_results(), get_alloptions_110(), time(), gmdate(), time(), add_option(), ->get_var()
always100–101->get_results(), get_alloptions_110(), time(), gmdate(), time(), add_option(), ->get_var(), ->query(), ->query(), ->query(), ->query(), ->query()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 121 instructions, 45–101 executed per call, 4 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 3

Used by · 1

  • upgrade_all()Functions to be called in installation and upgrade scripts.

Source code

function upgrade_110() {	global $wpdb; 	// Set user_nicename.	$users = $wpdb->get_results( "SELECT ID, user_nickname, user_nicename FROM $wpdb->users" );	foreach ( $users as $user ) {		if ( '' === $user->user_nicename ) {			$newname = sanitize_title( $user->user_nickname );			$wpdb->update( $wpdb->users, array( 'user_nicename' => $newname ), array( 'ID' => $user->ID ) );		}	} 	// Get the GMT offset, we'll use that later on.	$all_options = get_alloptions_110(); 	$time_difference = $all_options->time_difference; 	$server_time    = time() + (int) gmdate( 'Z' );	$weblogger_time = $server_time + $time_difference * HOUR_IN_SECONDS;	$gmt_time       = time(); 	$diff_gmt_server       = ( $gmt_time - $server_time ) / HOUR_IN_SECONDS;	$diff_weblogger_server = ( $weblogger_time - $server_time ) / HOUR_IN_SECONDS;	$diff_gmt_weblogger    = $diff_gmt_server - $diff_weblogger_server;	$gmt_offset            = -$diff_gmt_weblogger; 	// Add a gmt_offset option, with value $gmt_offset.	add_option( 'gmt_offset', $gmt_offset ); 	/*	 * Check if we already set the GMT fields. If we did, then	 * MAX(post_date_gmt) can't be '0000-00-00 00:00:00'.	 * <michel_v> I just slapped myself silly for not thinking about it earlier.	 */	$got_gmt_fields = ( '0000-00-00 00:00:00' !== $wpdb->get_var( "SELECT MAX(post_date_gmt) FROM $wpdb->posts" ) ); 	if ( ! $got_gmt_fields ) { 		// Add or subtract time to all dates, to get GMT dates.		$add_hours   = (int) $diff_gmt_weblogger;		$add_minutes = (int) ( 60 * ( $diff_gmt_weblogger - $add_hours ) );		$wpdb->query( "UPDATE $wpdb->posts SET post_date_gmt = DATE_ADD(post_date, INTERVAL '$add_hours:$add_minutes' HOUR_MINUTE)" );		$wpdb->query( "UPDATE $wpdb->posts SET post_modified = post_date" );		$wpdb->query( "UPDATE $wpdb->posts SET post_modified_gmt = DATE_ADD(post_modified, INTERVAL '$add_hours:$add_minutes' HOUR_MINUTE) WHERE post_modified != '0000-00-00 00:00:00'" );		$wpdb->query( "UPDATE $wpdb->comments SET comment_date_gmt = DATE_ADD(comment_date, INTERVAL '$add_hours:$add_minutes' HOUR_MINUTE)" );		$wpdb->query( "UPDATE $wpdb->users SET user_registered = DATE_ADD(user_registered, INTERVAL '$add_hours:$add_minutes' HOUR_MINUTE)" );	}}

Changelog

Introduced in 1.2.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

6.8.0
User passwords are no longer hashed with md5.from the docblock
1.2.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-admin/includes/upgrade.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.