Here follows a list of the currently known problems with prepared statements:
TIME
,TIMESTAMP
, andDATETIME
do not support parts of seconds (for example, fromDATE_FORMAT()
).When converting an integer to string,
ZEROFILL
is honored with prepared statements in some cases where the MySQL server doesn't print the leading zeros. (For example, withMIN(
).number-with-zerofill
)When converting a floating-point number to a string in the client, the rightmost digits of the converted value may differ slightly from those of the original value.
Prepared statements use the query cache under the conditions described in Section 7.9.3.1, “How the Query Cache Operates”.
Prepared statements do not support multi-statements (that is, multiple statements within a single string separated by “
;
” characters).Before MySQL 5.5.3, prepared
CALL
statements cannot invoke stored procedures that return result sets because prepared statements do not support multiple result sets. Nor can the calling application access a stored procedure'sOUT
orINOUT
parameters when the procedure returns. As of MySQL 5.5.3, these capabilities are supported as described in Section 22.9.16, “C API Support for PreparedCALL
Statements”.