Prepares the SQL query pointed to by the null-terminated string query.
The parameter markers must be bound to application variables using mysqli_stmt_bind_param and/or
mysqli_stmt_bind_result before executing the statement or fetching rows.
In the case where you pass a statement to mysqli_stmt_prepare that is longer
than max_allowed_packet of the server, the returned error codes are different
depending on whether you are using MySQL Native Driver (mysqlnd) or MySQL
Client Library (libmysqlclient). The behavior is as follows:
• mysqlnd on Linux returns an error code of 1153. The error message means “got
a packet bigger than max_allowed_packet bytes”.
• mysqlnd on Windows returns an error code 2006. This error message means
“server has gone away” ” .
• libmysqlclient on all platforms returns an error code 2006. This error
message means “server has gone away” ” .
Procedural style only: A statement identifier returned by
The query, as a string. It must consist of a single SQL statement.
You can include one or more parameter markers in the SQL statement
by embedding question mark (?) characters at the appropriate positions.
You should not add a terminating semicolon or
\g to the statement.
The markers are legal only in certain places in
SQL statements. For example, they are allowed
in the VALUES() list of an INSERT statement
(to specify column values for a row), or in a
comparison with a column in a WHERE clause to
specify a comparison value.
However, they are not allowed for identifiers
(such as table or column names), in the select
list that names the columns to be returned by a
SELECT statement), or to specify both operands
of a binary operator such as the = equal sign.
The latter restriction is necessary because it
would be impossible to determine the parameter
type. In general, parameters are legal only in