upgrade_210()

Compatibility

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_210() 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

9–48

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

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

• sqldatabase query->get_results()called directly
• hookthird-party callbacksapply_filters()one call below upgrade_210()

Further down the call graph this can also reach option, cache, serialize, 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 · 8 distinct outcomes

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

Uses · 3

• populate_roles_210()Create and modify WordPress roles for WordPress 2.1.
• wp_schedule_single_event()Schedules an event to run only once.
• mysql2date()Converts given MySQL date string into a different format.

Used by · 1

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

Source code

View on Trac ↗View on GitHub ↗

1261function upgrade_210() {1262	global $wp_current_db_version, $wpdb;1263 1264	if ( $wp_current_db_version < 3506 ) {1265		// Update status and type.1266		$posts = $wpdb->get_results( "SELECT ID, post_status FROM $wpdb->posts" );1267 1268		if ( ! empty( $posts ) ) {1269			foreach ( $posts as $post ) {1270				$status = $post->post_status;1271				$type   = 'post';1272 1273				if ( 'static' === $status ) {1274					$status = 'publish';1275					$type   = 'page';1276				} elseif ( 'attachment' === $status ) {1277					$status = 'inherit';1278					$type   = 'attachment';1279				}1280 1281				$wpdb->query( $wpdb->prepare( "UPDATE $wpdb->posts SET post_status = %s, post_type = %s WHERE ID = %d", $status, $type, $post->ID ) );1282			}1283		}1284	}1285 1286	if ( $wp_current_db_version < 3845 ) {1287		populate_roles_210();1288	}1289 1290	if ( $wp_current_db_version < 3531 ) {1291		// Give future posts a post_status of future.1292		$now = gmdate( 'Y-m-d H:i:59' );1293		$wpdb->query( "UPDATE $wpdb->posts SET post_status = 'future' WHERE post_status = 'publish' AND post_date_gmt > '$now'" );1294 1295		$posts = $wpdb->get_results( "SELECT ID, post_date FROM $wpdb->posts WHERE post_status ='future'" );1296		if ( ! empty( $posts ) ) {1297			foreach ( $posts as $post ) {1298				wp_schedule_single_event( mysql2date( 'U', $post->post_date, false ), 'publish_future_post', array( $post->ID ) );1299			}1300		}1301	}1302}

Changelog

Introduced in 2.1.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.

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.