wppaste
WordPress

wpdb::process_fields( string $table, array $data, string[]|string $format ): array|false

Since
4.2.0
Source
wp-includes/class-wpdb.php:2806
Processes arrays of field/value pairs and field formats.

Description

This is a helper method for wpdb's CRUD methods, which take field/value pairs for inserts, updates, and where clauses. This method first pairs each value with a format. Then it determines the charset of that field, using that to determine if any invalid text would be stripped. If text is stripped, then field processing is rejected and the query fails.

Compatibility

WordPress
since 4.2.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.

Parameters

$tablestring
Table name.
$dataarray
Array of values keyed by their field names.
$formatstring[]|string
Formats or format to be mapped to the values in the data.

Return value

array|false
An array of fields that contain paired value and formats.
False for invalid values.

Performance profile

How much work a call to wpdb::process_fields() 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
Light

Touches nothing outside its own arguments.

Scaling
Scales with input

The body loops, so the work grows with what you pass in.

Instructions
11–52

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
3

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

What one call costs · 6 distinct outcomes

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

WhenInstructionsCalls it makes
$data === false11->process_field_formats()
always18->process_field_formats(), ->process_field_charsets()
always25->process_field_formats(), ->process_field_charsets(), ->process_field_lengths()
always31->process_field_formats(), ->process_field_charsets(), ->process_field_lengths(), ->strip_invalid_text()
$data !== false49–50->process_field_formats(), ->process_field_charsets(), ->process_field_lengths(), ->strip_invalid_text(), wp_load_translations_early(), __(), sprintf()
$data !== false51–52->process_field_formats(), ->process_field_charsets(), ->process_field_lengths(), ->strip_invalid_text(), wp_load_translations_early(), __(), reset(), sprintf()

Across PHP versions

PHPCompiledExecutedBranchesNotes
8.6-dev7411–528
8.57411–528
8.47411–5283 fewer instructions than PHP 8.3
8.37711–538
8.27711–538
8.17711–538
7.47711–538

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 · 6

Used by · 3

Source code

	protected function process_fields( $table, $data, $format ) {		$data = $this->process_field_formats( $data, $format );		if ( false === $data ) {			return false;		} 		$data = $this->process_field_charsets( $data, $table );		if ( false === $data ) {			return false;		} 		$data = $this->process_field_lengths( $data, $table );		if ( false === $data ) {			return false;		} 		$converted_data = $this->strip_invalid_text( $data ); 		if ( $data !== $converted_data ) { 			$problem_fields = array();			foreach ( $data as $field => $value ) {				if ( $value !== $converted_data[ $field ] ) {					$problem_fields[] = $field;				}			} 			wp_load_translations_early(); 			if ( 1 === count( $problem_fields ) ) {				$this->last_error = sprintf(					/* translators: %s: Database field where the error occurred. */					__( 'WordPress database error: Processing the value for the following field failed: %s. The supplied value may be too long or contains invalid data.' ),					reset( $problem_fields )				);			} else {				$this->last_error = sprintf(					/* translators: %s: Database fields where the error occurred. */					__( 'WordPress database error: Processing the values for the following fields failed: %s. The supplied values may be too long or contain invalid data.' ),					implode( ', ', $problem_fields )				);			} 			return false;		} 		return $data;	}

Changelog

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

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-includes/class-wpdb.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.