Closes a previously prepared statement.

Direction

Client to server.

Implemented by

• .

• .

Fields

• 0x19 COM_STMT_CLOSE header.

• statement id.

Example

05 00 00 00 19 04 00 00 00

Response

No response from server.

_{This page is licensed: CC BY-SA / Gnu FDL}

Executes a bulk insert of a previously prepared statement.

A command that returns a result set returns an error (Error packet).

Direction

Client to server.

Fields

• 0xfa : COM_STMT_BULK_EXECUTE header.

• statement id.

• .

Flags

Bulk Flags

Parameter Type Flag

Parameter Indicator

Response

The server can answer with 3 different responses:

• 0xff: if any errors occur.

• 0x00: when query execution works without result set.

• A result set containing affected rows and auto-increment IDs when bulk flag SEND_UNIT_RESULTS is set.

_{This page is licensed: CC BY-SA / Gnu FDL}

Resets a prepared statement on the client and server to state after preparing.

Fields

• int<1> 0x1A COM_STMT_RESET header.

• Statement ID.

Response

or .

Example

_{This page is licensed: CC BY-SA / Gnu FDL}

Fetch rows from a prepared statement.

A COM_STMT_EXECUTE with a non-zero cursor flag must have been successfully executed before any COM_STMT_FETCH commands can be executed.

Fields

• int<1> 0x1C COM_STMT_FETCH header.

• statement id.

• number of rows to fetch.

Response

Returns one or more followed by an .

_{This page is licensed: CC BY-SA / Gnu FDL}

When data for a specific column is large, it can be sent separately to avoid the limitation of max_allowed_packet (see ).

Multiple COM_STMT_SEND_LONG_DATA commands with the same column ID append the data. COM_STMT_SEND_LONG_DATA is sent before .

Fields

Prepares a statement on the server.

Implemented by

Executes a previously prepared statement.

If specific data is large, it can be sent separately prior to this command (see COM_STMT_SEND_LONG_DATA).

If a statement is re-executed without changing the bind types, the types do not need to be sent to the server again.

Direction

Client to server.

Fields

• 0x17 : COM_STMT_EXECUTE header.

• .

• flags.

Statement ID

Statement ID is the identifier of the prepared statement (from ).

Specific "-1" statement id value

Value -1 (0xFFFFFFFF) can be used to indicate to use the last statement prepared on current connection if no COM_STMT_PREPARE has failed since.

This permit pipelining :

• Send COM_STMT_PREPARE + COM_STMT_EXECUTE with statement ID -1.

• Read COM_STMT_PREPARE + COM_STMT_EXECUTE response.

In case COM_STMT_PREPARE returns an error, COM_STMT_EXECUTE returns an error that statement ID -1 is unknown. This permits to avoid much of the network latency.

Flag

Cursors

If the flags of the COM_STMT_EXECUTE request a cursor to be opened, the returned result only contains the column definitions and the EOF that terminates it, and the result set rows are fetched using separate COM_STMT_FETCH commands.

Whether a cursor is actually opened is indicated by the SERVER_STATUS_CURSOR_EXISTS bit in the first EOF packet in the response to the COM_STMT_EXECUTE. If it is not set in, no cursor is opened and a normal result set is returned.

Parameter Flag

Parameter type flag byte:

NULL-Bitmap

The NULL-Bitmap indicates if parameters are null (one bit per parameter). If the parameter is NULL, the bit is set in the bitmap and the parameter value is not sent.

The size in bytes of the NULL-bitmap can be calculated with: (parameter number + 7) / 8

Binary Parameter Encoding

The encoding of the COM_STMT_EXECUTE parameters are the same as the encoding of the .

Response

The server can answer with 3 different responses:

• 0xff: if any errors occur.

• 0x00: when query execution works without result set.

• One (or more) , when query execution return rows (in case of SELECT query, for example).

_{This page is licensed: CC BY-SA / Gnu FDL}

In contrast to the text protocol, the binary protocol transfers data according to the format of the field types returned in PACKET_METADATA.

Fields

_{This page is licensed: CC BY-SA / Gnu FDL}