# 2 - Text Protocol

- [COM\_CHANGE\_USER](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_change_user.md): This command allows a connected client to re-authenticate as a different user without closing and reopening the connection.
- [COM\_CREATE\_DB](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_create_db.md): This command creates a new database on the server, functionally equivalent to the SQL statement CREATE DATABASE.
- [COM\_DEBUG](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_debug.md): This command forces the server to dump debug information to the standard output or log, requiring the SUPER privilege.
- [COM\_DROP\_DB](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_drop_db.md): This command drops an existing database from the server, functionally equivalent to the SQL statement DROP DATABASE.
- [COM\_FIELD\_LIST](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_field_list.md): This command retrieves a list of fields (columns) for a specified table, similar to the SHOW COLUMNS SQL statement.
- [COM\_INIT\_DB](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_init_db.md): This command selects the default database for the current connection, functionally equivalent to the USE statement.
- [COM\_PING](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_ping.md): This command checks if the server is alive and reachable, the server responds with an OK packet if it is running.
- [COM\_PROCESSLIST](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_processlist.md): This command retrieves a list of active threads and their current status, similar to the SHOW PROCESSLIST statement.
- [COM\_PROCESS\_KILL](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_process_kill.md): This command asks the server to terminate a specific connection thread, functionally equivalent to the KILL statement.
- [COM\_QUERY](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_query.md): This command sends an SQL statement to the server for execution immediately, without the prepare/execute steps.
- [COM\_QUIT](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_quit.md): This command instructs the server to close the connection and release associated resources.
- [COM\_RESET\_CONNECTION](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_reset_connection.md): This command resets the session state (variables, tables, etc.) to its initial values without closing the connection.
- [COM\_SET\_OPTION](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_set_option.md): This command configures client-specific options for the current connection, such as enabling or disabling multi-statements.
- [COM\_SHUTDOWN](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_shutdown.md): This command requests the server to shut down, it requires the SHUTDOWN privilege to be executed successfully.
- [COM\_SLEEP](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_sleep.md): This is an internal command used to represent a sleeping connection that is waiting for a new command from the client.
- [COM\_STATISTICS](https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol/com_statistics.md): This command retrieves a human-readable string containing internal server statistics like uptime and thread counts.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/server/reference/clientserver-protocol/2-text-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.