(PHP 5, PHP 7, PHP 8)
mysqli::stmt_init -- mysqli_stmt_init — Initializes a statement and returns an object for use with mysqli_stmt_prepare
Object-oriented style
Procedural style
Allocates and initializes a statement object suitable for mysqli_stmt_prepare() .
Note:
Any subsequent calls to any mysqli_stmt function will fail until mysqli_stmt_prepare() was called.
mysqlProcedural style only: A mysqli object returned by mysqli_connect() or mysqli_init()
Returns an object.
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:
<?php
$db = $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:
<?php
$db = $this->getConnection()->getDbConnection();
$preparedQuery = $db->stmt_init();
$preparedQuery->prepare ($query);
?>
resolved the problem.you can use $stmt = $mysqli->prepare(); directly without stmt-init() . i think there is no need for stmt-init .