- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 26.2.3 C API Function Descriptions
- 26.2.3.1 mysql_affected_rows()
- 26.2.3.2 mysql_autocommit()
- 26.2.3.3 mysql_change_user()
- 26.2.3.4 mysql_character_set_name()
- 26.2.3.5 mysql_close()
- 26.2.3.6 mysql_commit()
- 26.2.3.7 mysql_connect()
- 26.2.3.8 mysql_create_db()
- 26.2.3.9 mysql_data_seek()
- 26.2.3.10 mysql_debug()
- 26.2.3.11 mysql_drop_db()
- 26.2.3.12 mysql_dump_debug_info()
- 26.2.3.13 mysql_eof()
- 26.2.3.14 mysql_errno()
- 26.2.3.15 mysql_error()
- 26.2.3.16 mysql_escape_string()
- 26.2.3.17 mysql_fetch_field()
- 26.2.3.18 mysql_fetch_field_direct()
- 26.2.3.19 mysql_fetch_fields()
- 26.2.3.20 mysql_fetch_lengths()
- 26.2.3.21 mysql_fetch_row()
- 26.2.3.22 mysql_field_count()
- 26.2.3.23 mysql_field_seek()
- 26.2.3.24 mysql_field_tell()
- 26.2.3.25 mysql_free_result()
- 26.2.3.26 mysql_get_character_set_info()
- 26.2.3.27 mysql_get_client_info()
- 26.2.3.28 mysql_get_client_version()
- 26.2.3.29 mysql_get_host_info()
- 26.2.3.30 mysql_get_proto_info()
- 26.2.3.31 mysql_get_server_info()
- 26.2.3.32 mysql_get_server_version()
- 26.2.3.33 mysql_get_ssl_cipher()
- 26.2.3.34 mysql_hex_string()
- 26.2.3.35 mysql_info()
- 26.2.3.36 mysql_init()
- 26.2.3.37 mysql_insert_id()
- 26.2.3.38 mysql_kill()
- 26.2.3.39 mysql_library_end()
- 26.2.3.40 mysql_library_init()
- 26.2.3.41 mysql_list_dbs()
- 26.2.3.42 mysql_list_fields()
- 26.2.3.43 mysql_list_processes()
- 26.2.3.44 mysql_list_tables()
- 26.2.3.45 mysql_more_results()
- 26.2.3.46 mysql_next_result()
- 26.2.3.47 mysql_num_fields()
- 26.2.3.48 mysql_num_rows()
- 26.2.3.49 mysql_options()
- 26.2.3.50 mysql_ping()
- 26.2.3.51 mysql_query()
- 26.2.3.52 mysql_real_connect()
- 26.2.3.53 mysql_real_escape_string()
- 26.2.3.54 mysql_real_query()
- 26.2.3.55 mysql_refresh()
- 26.2.3.56 mysql_reload()
- 26.2.3.57 mysql_rollback()
- 26.2.3.58 mysql_row_seek()
- 26.2.3.59 mysql_row_tell()
- 26.2.3.60 mysql_select_db()
- 26.2.3.61 mysql_set_character_set()
- 26.2.3.62 mysql_set_local_infile_default()
- 26.2.3.63 mysql_set_local_infile_handler()
- 26.2.3.64 mysql_set_server_option()
- 26.2.3.65 mysql_shutdown()
- 26.2.3.66 mysql_sqlstate()
- 26.2.3.67 mysql_ssl_set()
- 26.2.3.68 mysql_stat()
- 26.2.3.69 mysql_store_result()
- 26.2.3.70 mysql_thread_id()
- 26.2.3.71 mysql_use_result()
- 26.2.3.72 mysql_warning_count()
26.2.3.54. mysql_real_query()
int mysql_real_query(MYSQL *mysql, const char
*stmt_str, unsigned long length)
Description
Executes the SQL statement pointed to by
stmt_str, which should be a string
length bytes long. Normally, the string must
consist of a single SQL statement and you should not add a
terminating semicolon (“;”) or
\g to the statement. If multiple-statement
execution has been enabled, the string can contain several
statements separated by semicolons. See
Section 26.2.9, “C API Handling of Multiple Statement Execution”.
mysql_query() cannot be used
for statements that contain binary data; you must use
mysql_real_query() instead.
(Binary data may contain the
“\0” character, which
mysql_query() interprets as the
end of the statement string.) In addition,
mysql_real_query() is faster
than mysql_query() because it
does not call strlen() on the statement
string.
If you want to know whether the statement should return a result
set, you can use
mysql_field_count() to check
for this. See Section 26.2.3.22, “mysql_field_count()”.
Return Values
Zero if the statement was successful. Non-zero if an error occurred.
Errors
-
CR_COMMANDS_OUT_OF_SYNCCommands were executed in an improper order.
-
CR_SERVER_GONE_ERRORThe MySQL server has gone away.
-
CR_SERVER_LOSTThe connection to the server was lost during the query.
-
CR_UNKNOWN_ERRORAn unknown error occurred.
User Comments
Connection-lost behavior:
If you lose your connection to the database, subsequent calls to mysql_real_query will attempt to reconnect.
The implicit reconnect will not restore settings like "set names utf8;" and may therefor cause subsequent data corruption by using and expecting the wrong character set.
Add your own comment.