Informix DataBlade API Programmer's Manual DataBlade API Function Descriptions

The mi_exec() function sends an SQL statement to the database server for parsing, optimization, and execution.

mi_integer mi_exec(conn, stmt_strng, control)

MI_CONNECTION *conn;

const mi_string *stmt_strng;

mi_integer control;

conn	is a pointer to the connection descriptor that a previous call to mi_open(), mi_server_connect(), or mi_server_reconnect() has established.
stmt_strng	is a pointer to the statement string, which contains the text of the SQL statement to execute.
control	is a bit mask of flags that determines the control mode for any results that the executed SQL statement returns. Currently the valid control flags are:
	MI_QUERY_BINARY	The query results are in binary representation rather than text strings.
	MI_QUERY_NORMAL	The query results are in text representation (null-terminated strings).

Valid in Client LIBMI Application?	Valid in User-Defined Routine?
Yes	Yes

The mi_exec() function performs the following tasks:

• Send the statement string to the database server for parsing, optimization, and execution.
• If any rows are to be returned, create and open a cursor that is read-only and sequential.

If the SQL statement is not a SELECT statement, the statement is executed. If it is SELECT, mi_exec() automatically creates and opens a cursor for the retrieved rows.

Tip: The mi_exec() function does not handle execution of prepared statements. To send prepared statements to the database server, use mi_exec_prepared_statement() or mi_open_prepared_statement().

The mi_exec() function only sends the statement; it does not return results to the DataBlade API module. To get results after the execution mi_exec(), the DataBlade API module must examine the results via a loop with mi_get_result().

The current statement must finish before the database server can process the next statement. The mi_query_finish() function can be used to force a statement to finish processing. Informix strongly advises that you use either mi_query_finish() or an mi_get_result() loop after each mi_exec() function.

For general information about sending statements with mi_exec(), see Using Smart Large Objects.

A successful return indicates only that the connection is valid and the statement was successfully executed (for statements other than SELECT) or a cursor was successfully opened (for SELECT). It does not indicate the success of the SQL statement. Use mi_get_result() to determine the success of the SQL statement.

See the descriptions of the following functions: mi_command_is_finished(), mi_exec_prepared_statement(), mi_get_result(), mi_open_prepared_statement(), and mi_query_finish().