wpdb::process_field_charsets( array $data, string $table ): array|false

Compatibility

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

Parameters

$dataarray

Array of values and formats keyed by their field names, as it comes from the wpdb::process_field_formats() method. @type array ...$0 { Value and format for this field.

• $valuemixed

  The value to be formatted.

• $formatstring

  The format to be mapped to the value. }

$tablestring

Table name.

Return value

array|false

The same array of data with additional 'charset' keys, or false if the charset for the table cannot be found.

• ...$0array

  Value, format, and charset for this field.

  • $valuemixed

    The value to be formatted.

  • $formatstring

    The format to be mapped to the value.

  • $charsetstring|false

    The charset to be used for the value.

Performance profile

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

5–25

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

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

• hookthird-party callbacksdo_action()one call below wpdb::process_field_charsets()

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 wpdb::process_field_charsets() can have, taken from its control-flow graph on PHP 8.5.

Uses · 2

• is_wp_error()Checks whether the given variable is a WordPress Error.
• wpdb::get_col_charset()Retrieves the character set for the given column.

Used by · 1

• wpdb::process_fields()Processes arrays of field/value pairs and field formats.

Source code

View on Trac ↗View on GitHub ↗

2932	protected function process_field_charsets( $data, $table ) {2933		foreach ( $data as $field => $value ) {2934			if ( '%d' === $value['format'] || '%f' === $value['format'] ) {2935				/*2936				 * We can skip this field if we know it isn't a string.2937				 * This checks %d/%f versus ! %s because its sprintf() could take more.2938				 */2939				$value['charset'] = false;2940			} else {2941				$value['charset'] = $this->get_col_charset( $table, $field );2942				if ( is_wp_error( $value['charset'] ) ) {2943					return false;2944				}2945			}2946 2947			$data[ $field ] = $value;2948		}2949 2950		return $data;2951	}

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 7.0.4 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.