CascadiaPHP 2024



(PHP 5, PHP 7, PHP 8)

mysqli::stmt_init -- mysqli_stmt_initInitializes a statement and returns an object for use with mysqli_stmt_prepare


Object-oriented style

public mysqli::stmt_init(): mysqli_stmt|false

Procedural style

mysqli_stmt_init(mysqli $mysql): mysqli_stmt|false

Allocates and initializes a statement object suitable for mysqli_stmt_prepare().


Any subsequent calls to any mysqli_stmt function will fail until mysqli_stmt_prepare() was called.



Procedural style only: A mysqli object returned by mysqli_connect() or mysqli_init()

Return Values

Returns an object.

See Also

add a note

User Contributed Notes 2 notes

Jeff C
7 years ago
stmt_init() seems to clear previous (possibly erroneous) results on the DB connection, which means you don't necessarily need to use it but it could make the code more robust.

In a PHPUnit test, I had a sequence of prepared queries on the same connection. One of them fetched a row from a SELECT but didn't keep fetching until it drained the connection, so it left some stale results. When the next query did this:

= $this->getConnection()->getDbConnection();
$preparedQuery = $db->prepare ($query);

the prepare() call generated an error: "Could not prepare query: Commands out of sync; you can't run this command now." Changing to this:

= $this->getConnection()->getDbConnection();
$preparedQuery = $db->stmt_init();
$preparedQuery->prepare ($query);

resolved the problem.
mamdo7 at hotmail dot com
10 years ago
you can use $stmt = $mysqli->prepare(); directly without stmt-init() . i think there is no need for stmt-init .
To Top