maxdb_stmt_prepare Prepare a SQL statement for execution Procedure style: boolmaxdb_stmt_prepare resourcestmt stringquery maxdb_stmt_prepare prepares the SQL query pointed to by the null-terminated string query. The statement resource has to be allocated by maxdb_stmt_init. The query must consist of a single SQL statement. You should not add a terminating semicolon or \g to the statement. The parameter query can include one or more parameter markers in the SQL statement by embedding question mark (?) characters at the appropriate positions. 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 Data Manipulation Languange (DML) statements, and not in Data Defination Language (DDL) statements. The parameter markers must be bound to application variables using maxdb_stmt_bind_param and/or maxdb_stmt_bind_result before executing the statement or fetching rows. &reftitle.returnvalues; &return.success; &reftitle.seealso; maxdb_stmt_init, maxdb_stmt_execute, maxdb_stmt_fetch, maxdb_stmt_bind_param, maxdb_stmt_bind_result, maxdb_stmt_close ]]> The above examples would produce the following output: