# Reference

- [SQL Structure](/docs/server/reference/sql-structure.md): Explore the SQL structure in MariaDB Server. This section provides a fundamental overview of SQL syntax, components, and concepts that form the basis for interacting with your database.
- [SQL Language Structure](/docs/server/reference/sql-structure/sql-language-structure.md): Explore the SQL language structure in MariaDB Server. This section provides fundamental concepts, syntax rules, and common elements that form the building blocks of SQL queries and commands.
- [Binary Literals](/docs/server/reference/sql-structure/sql-language-structure/binary-literals.md)
- [Date and Time Literals](/docs/server/reference/sql-structure/sql-language-structure/date-and-time-literals.md)
- [Hexadecimal Literals](/docs/server/reference/sql-structure/sql-language-structure/hexadecimal-literals.md)
- [Identifier Case Sensitivity](/docs/server/reference/sql-structure/sql-language-structure/identifier-case-sensitivity.md)
- [Identifier Names](/docs/server/reference/sql-structure/sql-language-structure/identifier-names.md)
- [Identifier Qualifiers](/docs/server/reference/sql-structure/sql-language-structure/identifier-qualifiers.md)
- [Identifier to File Name Mapping](/docs/server/reference/sql-structure/sql-language-structure/identifier-to-file-name-mapping.md)
- [Numeric Literals](/docs/server/reference/sql-structure/sql-language-structure/numeric-iterals.md)
- [Reserved Words](/docs/server/reference/sql-structure/sql-language-structure/reserved-words.md)
- [Boolean Literals](/docs/server/reference/sql-structure/sql-language-structure/sql-language-structure-boolean-literals.md)
- [Schema Qualifiers](/docs/server/reference/sql-structure/sql-language-structure/schema-qualifiers.md): Schema qualifiers manage SQL mode dependent behavior for data types and functions.
- [String Literals](/docs/server/reference/sql-structure/sql-language-structure/string-literals.md)
- [Table Value Constructors](/docs/server/reference/sql-structure/sql-language-structure/table-value-constructors.md)
- [User-Defined Variables](/docs/server/reference/sql-structure/sql-language-structure/user-defined-variables.md)
- [Joins, Subqueries, and Set](/docs/server/reference/sql-structure/joins-subqueries-set.md): Explore joins, subqueries, and set operations in MariaDB SQL. This section details how to combine data from multiple tables, nest queries, and perform set-based operations for complex data retrieval.
- [Geometry](/docs/server/reference/sql-structure/geometry.md): Explore geometric data types and functions in MariaDB Server. This section details how to store, query, and manipulate spatial data, enabling geospatial applications within your database.
- [Geometry Hierarchy](/docs/server/reference/sql-structure/geometry/geometry-hierarchy.md)
- [Geometry Types](/docs/server/reference/sql-structure/geometry/geometry-types.md)
- [GIS Features](/docs/server/reference/sql-structure/geometry/gis-features-in-533.md)
- [GIS Resources](/docs/server/reference/sql-structure/geometry/gis-resources.md)
- [SPATIAL INDEX](/docs/server/reference/sql-structure/geometry/spatial-index.md)
- [NoSQL](/docs/server/reference/sql-structure/nosql.md): Explore MariaDB Server's NoSQL capabilities. This section details how to store and query schemaless data, including JSON, and how to integrate with other NoSQL data sources, enhancing flexibility.
- [Dynamic Columns](/docs/server/reference/sql-structure/nosql/dynamic-columns.md)
- [Dynamic Column API](/docs/server/reference/sql-structure/nosql/dynamic-column-api.md)
- [HANDLER](/docs/server/reference/sql-structure/nosql/handler.md): Explore the HANDLER statement in MariaDB Server for direct table access. This section details how to bypass the SQL optimizer for low-level row operations, useful for specific NoSQL-like interactions.
- [HANDLER](/docs/server/reference/sql-structure/nosql/handler/handler-commands.md)
- [HANDLER for MEMORY Tables](/docs/server/reference/sql-structure/nosql/handler/handler-for-memory-tables.md)
- [HandlerSocket](/docs/server/reference/sql-structure/nosql/handlersocket.md): Explore HandlerSocket for MariaDB Server. This plugin enables high-performance NoSQL-like access directly to InnoDB tables, bypassing SQL parsing for fast key-value operations.
- [HandlerSocket Installation](/docs/server/reference/sql-structure/nosql/handlersocket/handlersocket-installation.md)
- [HandlerSocket Client Libraries](/docs/server/reference/sql-structure/nosql/handlersocket/handlersocket-client-libraries.md)
- [HandlerSocket Configuration Options](/docs/server/reference/sql-structure/nosql/handlersocket/handlersocket-configuration-options.md)
- [HandlerSocket External Resources](/docs/server/reference/sql-structure/nosql/handlersocket/handlersocket-external-resources.md)
- [Operators](/docs/server/reference/sql-structure/operators.md): Learn about operators in MariaDB Server SQL. This section details arithmetic, comparison, logical, and bitwise operators used in expressions and conditions for data manipulation and querying.
- [Operator Precedence](/docs/server/reference/sql-structure/operators/operator-precedence.md): Understand operator precedence in MariaDB Server SQL. This section details the order in which operators are evaluated within expressions, crucial for writing accurate and predictable queries.
- [Arithmetic Operators](/docs/server/reference/sql-structure/operators/arithmetic-operators.md): Learn about arithmetic operators in MariaDB Server SQL. This section details how to perform mathematical calculations like addition, subtraction, multiplication, and division within your queries.
- [Addition Operator (+)](/docs/server/reference/sql-structure/operators/arithmetic-operators/addition-operator.md)
- [Subtraction Operator (-)](/docs/server/reference/sql-structure/operators/arithmetic-operators/subtraction-operator.md)
- [Multiplication Operator (\*)](/docs/server/reference/sql-structure/operators/arithmetic-operators/multiplication-operator.md)
- [Division Operator (/)](/docs/server/reference/sql-structure/operators/arithmetic-operators/division-operator.md)
- [Modulo Operator (%)](/docs/server/reference/sql-structure/operators/arithmetic-operators/modulo-operator.md)
- [Assignment Operators](/docs/server/reference/sql-structure/operators/assignment-operators.md): Learn about assignment operators in MariaDB Server SQL. This section details how to assign values to variables and columns, essential for data manipulation and programmatic logic.
- [Assignment Operator (:=)](/docs/server/reference/sql-structure/operators/assignment-operators/assignment-operator.md)
- [Assignment Operator (=)](/docs/server/reference/sql-structure/operators/assignment-operators/assignment-operators-assignment-operator.md)
- [Comparison Operators](/docs/server/reference/sql-structure/operators/comparison-operators.md): Learn about comparison operators in MariaDB Server SQL. This section details operators like =, >, <, and LIKE used to compare values in conditions, essential for filtering and joining data.
- [BETWEEN AND](/docs/server/reference/sql-structure/operators/comparison-operators/between-and.md)
- [COALESCE](/docs/server/reference/sql-structure/operators/comparison-operators/coalesce.md)
- [=](/docs/server/reference/sql-structure/operators/comparison-operators/equal.md)
- [>=](/docs/server/reference/sql-structure/operators/comparison-operators/greater-than-or-equal.md)
- [>](/docs/server/reference/sql-structure/operators/comparison-operators/greater-than.md)
- [GREATEST](/docs/server/reference/sql-structure/operators/comparison-operators/greatest.md)
- [IN](/docs/server/reference/sql-structure/operators/comparison-operators/in.md)
- [INTERVAL](/docs/server/reference/sql-structure/operators/comparison-operators/interval.md)
- [IS JSON](/docs/server/reference/sql-structure/operators/comparison-operators/is-json.md)
- [IS NOT NULL](/docs/server/reference/sql-structure/operators/comparison-operators/is-not-null.md)
- [IS NOT](/docs/server/reference/sql-structure/operators/comparison-operators/is-not.md)
- [IS NULL](/docs/server/reference/sql-structure/operators/comparison-operators/is-null.md)
- [IS](/docs/server/reference/sql-structure/operators/comparison-operators/is.md)
- [ISNULL](/docs/server/reference/sql-structure/operators/comparison-operators/isnull.md)
- [LEAST](/docs/server/reference/sql-structure/operators/comparison-operators/least.md)
- [<=](/docs/server/reference/sql-structure/operators/comparison-operators/less-than-or-equal.md)
- [<](/docs/server/reference/sql-structure/operators/comparison-operators/less-than.md)
- [NOT BETWEEN](/docs/server/reference/sql-structure/operators/comparison-operators/not-between.md)
- [!=](/docs/server/reference/sql-structure/operators/comparison-operators/not-equal.md)
- [NOT IN](/docs/server/reference/sql-structure/operators/comparison-operators/not-in.md)
- [<=>](/docs/server/reference/sql-structure/operators/comparison-operators/null-safe-equal.md)
- [Logical Operators](/docs/server/reference/sql-structure/operators/logical-operators.md): Learn about logical operators in MariaDB Server SQL. This section details operators like AND, OR, and NOT used to combine or negate conditions, essential for complex filtering and data selection.
- [&&](/docs/server/reference/sql-structure/operators/logical-operators/and.md)
- [!](/docs/server/reference/sql-structure/operators/logical-operators/not.md)
- [||](/docs/server/reference/sql-structure/operators/logical-operators/or.md)
- [XOR](/docs/server/reference/sql-structure/operators/logical-operators/xor.md)
- [Sequences](/docs/server/reference/sql-structure/sequences.md): Learn about sequences in MariaDB Server. This section details how to create and manage sequences for generating unique numbers, often used for primary keys and other auto-incrementing values.
- [Sequence Overview](/docs/server/reference/sql-structure/sequences/sequence-overview.md)
- [ALTER SEQUENCE](/docs/server/reference/sql-structure/sequences/alter-sequence.md)
- [CREATE SEQUENCE](/docs/server/reference/sql-structure/sequences/create-sequence.md): Create a sequence generator. This statement initializes a sequence object that produces a series of unique numeric values on demand.
- [DROP SEQUENCE](/docs/server/reference/sql-structure/sequences/drop-sequence.md)
- [SEQUENCE Functions](/docs/server/reference/sql-structure/sequences/sequence-functions.md): Learn about sequence functions in MariaDB Server. This section details SQL functions for retrieving the next or current value from a sequence, crucial for generating unique identifiers.
- [LASTVAL](/docs/server/reference/sql-structure/sequences/sequence-functions/lastval.md)
- [NEXT VALUE FOR](/docs/server/reference/sql-structure/sequences/sequence-functions/next-value-for-sequence_name.md)
- [NEXTVAL](/docs/server/reference/sql-structure/sequences/sequence-functions/nextval.md)
- [PREVIOUS VALUE FOR](/docs/server/reference/sql-structure/sequences/sequence-functions/previous-value-for-sequence_name.md)
- [SETVAL](/docs/server/reference/sql-structure/sequences/sequence-functions/setval.md)
- [Temporal Tables](/docs/server/reference/sql-structure/temporal-tables.md): Explore temporal tables in MariaDB Server. This section details how to manage data with system-versioning and application-time periods, enabling historical data tracking and time-aware queries.
- [Application-Time Periods](/docs/server/reference/sql-structure/temporal-tables/application-time-periods.md)
- [Bitemporal Tables](/docs/server/reference/sql-structure/temporal-tables/bitemporal-tables.md)
- [System-Versioned Tables](/docs/server/reference/sql-structure/temporal-tables/system-versioned-tables.md): Complete system-versioned tables: WITH SYSTEM VERSIONING syntax, FOR SYSTEM\_TIME AS OF/BETWEEN/ALL queries, and ROW\_START/ROW\_END columns.
- [Vectors](/docs/server/reference/sql-structure/vectors.md): Explore vector data types. This section details how to store and manage numerical arrays, enabling efficient vector similarity search and machine learning applications within your database.
- [Vector Overview](/docs/server/reference/sql-structure/vectors/vector-overview.md): Official MariaDB Vector reference: VECTOR(n) data type, VECTOR INDEX (M, DISTANCE=euclidean|cosine), VEC\_FromText() inserts, VEC\_DISTANCE() queries.
- [CREATE TABLE with Vectors](/docs/server/reference/sql-structure/vectors/create-table-with-vectors.md): Create tables optimized for vector storage. Learn to define columns with the VECTOR data type and configure vector indexes for similarity search.
- [Vector System Variables](/docs/server/reference/sql-structure/vectors/vector-system-variables.md)
- [Vector Framework Integrations](/docs/server/reference/sql-structure/vectors/vector-framework-integrations.md)
- [VECTOR](/docs/server/reference/sql-structure/vectors/vector.md)
- [Optimizing Hybrid Search Query with Reciprocal Rank Fusion (RRF)](/docs/server/reference/sql-structure/vectors/optimizing-hybrid-search-query-with-reciprocal-rank-fusion-rrf.md)
- [SQL Statements](/docs/server/reference/sql-statements.md): Complete reference for SQL Statements in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples.
- [Comment Syntax](/docs/server/reference/sql-statements/comment-syntax.md): Complete SQL comment syntax: single-line # and -- (space required), multi-line /\* \*/ blocks, MySQL /\*!##### \*/ and MariaDB /\*M!##### \*/ executable comments.
- [Account Management](/docs/server/reference/sql-statements/account-management-sql-statements.md): Learn account management SQL statements for MariaDB Server. This section covers commands like CREATE USER, GRANT, and REVOKE to securely manage user access and privileges within your database.
- [ALTER USER](/docs/server/reference/sql-statements/account-management-sql-statements/alter-user.md): Complete ALTER USER guide for MariaDB. Complete syntax for modifying authentication, passwords, and account security settings with comprehensive examples and.
- [CREATE ROLE](/docs/server/reference/sql-statements/account-management-sql-statements/create-role.md): Create new roles to simplify privilege management. Learn how to define a role that can be assigned to multiple users or other roles.
- [CREATE USER](/docs/server/reference/sql-statements/account-management-sql-statements/create-user.md): Complete guide to creating MariaDB user accounts. Complete CREATE USER syntax for authentication methods and password policies with comprehensive examples.
- [DROP ROLE](/docs/server/reference/sql-statements/account-management-sql-statements/drop-role.md): Remove a role from the system. Learn the syntax to delete defined roles and revoke them from any users or roles that currently hold them.
- [DROP USER](/docs/server/reference/sql-statements/account-management-sql-statements/drop-user.md): Complete DROP statement reference for MariaDB. Complete guide for safely removing database objects with CASCADE options with comprehensive examples and best.
- [GRANT](/docs/server/reference/sql-statements/account-management-sql-statements/grant.md): Complete privilege management guide for MariaDB. Complete GRANT syntax for database, table, and column permissions with roles with comprehensive examples and.
- [RENAME USER](/docs/server/reference/sql-statements/account-management-sql-statements/rename-user.md): Rename existing database accounts. This guide explains how to change a user's name while preserving their current privileges and properties.
- [REVOKE](/docs/server/reference/sql-statements/account-management-sql-statements/revoke.md): Remove privileges or roles. Learn how to withdraw previously granted permissions from users or roles to restrict access and secure the database.
- [SET DEFAULT ROLE](/docs/server/reference/sql-statements/account-management-sql-statements/set-default-role.md): Define the default role for a user. Learn how to configure which role is automatically active when a user connects to the server.
- [SET PASSWORD](/docs/server/reference/sql-statements/account-management-sql-statements/set-password.md): Complete reference for SET PASSWORD in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and best.
- [SET SESSION AUTHORIZATION](/docs/server/reference/sql-statements/account-management-sql-statements/set-session-authorization.md): Impersonate another user for the current session. Learn how to assume the identity and privileges of another account for testing or administration.
- [SET ROLE](/docs/server/reference/sql-statements/account-management-sql-statements/set-role.md): Sets the current role for the session. Learn how to enable none, or a specific role to change your current privileges dynamically.
- [Administrative Statements](/docs/server/reference/sql-statements/administrative-sql-statements.md): Explore administrative SQL statements for MariaDB Server. This section covers commands for server management, maintenance, and diagnostics, including BINLOG, KILL, SHUTDOWN, and SHOW.
- [BINLOG](/docs/server/reference/sql-statements/administrative-sql-statements/binlog.md): Executes binary log events directly using base64-encoded data. Primarily used by the mariadb-binlog utility to re-apply events to the server.
- [CACHE INDEX](/docs/server/reference/sql-statements/administrative-sql-statements/cache-index.md): Assigns specific table indices to a named key cache. Optimizes server performance by preloading or dedicating memory to frequently accessed keys.
- [DESCRIBE](/docs/server/reference/sql-statements/administrative-sql-statements/describe.md): Provides information about a table's columns. Acts as a shortcut for SHOW COLUMNS, displaying field names, types, and other attributes.
- [HELP Command](/docs/server/reference/sql-statements/administrative-sql-statements/help-command.md): Displays help information from the server's help tables. Useful for looking up SQL syntax and command descriptions directly from the client.
- [KILL](/docs/server/reference/sql-statements/administrative-sql-statements/kill.md): Terminates a specific connection or query. Allows administrators to stop runaway threads or disconnect users to free up server resources.
- [PURGE BINARY LOGS](/docs/server/reference/sql-statements/administrative-sql-statements/purge-binary-logs.md): Official PURGE BINARY LOGS syntax: delete binlogs using TO 'log\_name' or BEFORE datetime\_expr, replica read constraints, and SHOW BINARY LOGS commands.
- [RESET](/docs/server/reference/sql-statements/administrative-sql-statements/reset.md): Clears internal server buffers, caches, and status variables. Resets state information like the query cache or replication status without a restart.
- [SHUTDOWN](/docs/server/reference/sql-statements/administrative-sql-statements/shutdown.md): Stops the MariaDB server process. Allows a client with the SHUTDOWN privilege to cleanly power down the database instance.
- [USE \[DATABASE\]](/docs/server/reference/sql-statements/administrative-sql-statements/use-database.md): Selects the default database for the current session. Subsequent queries execute against this database unless explicitly qualified by name.
- [ANALYZE and EXPLAIN Statements](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements.md): Learn commands for query analysis. This section covers ANALYZE TABLE and EXPLAIN, used to view execution plans and optimize query performance.
- [ANALYZE FORMAT=JSON](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/analyze-format-json.md): Gain deep insight into query execution with JSON-formatted analysis. This command combines optimizer estimates with actual runtime statistics for precise performance tuning.
- [ANALYZE FORMAT=JSON Examples](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/analyze-formatjson-examples.md): Review practical examples of ANALYZE FORMAT=JSON output. Learn to identify performance bottlenecks by comparing estimated costs against actual execution metrics.
- [ANALYZE: Interpreting rows and filtered members](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/analyze-interpreting-rows-and-filtered-members.md): Understand the r\_rows and r\_filtered fields in analysis output. Learn how these actual runtime counters compare to the optimizer's rows and filtered estimates.
- [ANALYZE Statement](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/analyze-statement.md): Learn to use the ANALYZE statement to execute a query and produce a performance report. This command reveals how close the optimizer's plan was to the actual execution.
- [EXPLAIN ANALYZE](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/explain-analyze.md): Understand the historical context of EXPLAIN ANALYZE in MariaDB. Learn how this syntax maps to the modern ANALYZE statement for profiling query execution.
- [EXPLAIN FORMAT=JSON](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/explain-format-json.md): Get comprehensive query plans in JSON format. This output provides detailed optimizer data, including costs and attached conditions, not found in the tabular view.
- [EXPLAIN](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/explain.md): Complete EXPLAIN statement reference: SELECT/UPDATE/DELETE syntax, EXTENDED and PARTITIONS options, FORMAT=JSON output, EXPLAIN FOR CONNECTION usage.
- [Using Buffer UPDATE Algorithm](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/using-buffer-update-algorithm.md): Understand the 'Using buffer' strategy for UPDATE operations. Learn how MariaDB prevents infinite update loops when modifying indexed columns during a range scan.
- [BACKUP Statements](/docs/server/reference/sql-statements/administrative-sql-statements/backup-commands.md): Learn about backup statements for MariaDB Server. This section details SQL statements and utilities for creating consistent database backups, essential for disaster recovery and data protection.
- [BACKUP LOCK](/docs/server/reference/sql-statements/administrative-sql-statements/backup-commands/backup-lock.md): Protect table files during backups. This command blocks DDL operations like ALTER TABLE while allowing read/write activity, ensuring file consistency for backup tools.
- [BACKUP STAGE](/docs/server/reference/sql-statements/administrative-sql-statements/backup-commands/backup-stage.md): Control backup phases for external tools. Learn how to cycle through stages like START, BLOCK\_DDL, and BLOCK\_COMMIT to perform consistent backups with minimal locking.
- [Storage Snapshots and BACKUP STAGE Statements](/docs/server/reference/sql-statements/administrative-sql-statements/backup-commands/storage-snapshots-and-backup-stage-commands.md): Combine database commands with storage-level snapshots. Learn the correct sequence of BACKUP STAGE commands to freeze writes safely while taking a disk snapshot.
- [FLUSH Statements](/docs/server/reference/sql-statements/administrative-sql-statements/flush-commands.md): Explore commands to clear internal caches. Learn to use FLUSH to reload privileges, clear the query cache, or close open tables.
- [FLUSH](/docs/server/reference/sql-statements/administrative-sql-statements/flush-commands/flush.md): Complete FLUSH statement reference: NO\_WRITE\_TO\_BINLOG/LOCAL syntax, FLUSH TABLES WITH READ LOCK/FOR EXPORT, FLUSH STATUS, and SSL/TLS certificate reload.
- [FLUSH QUERY CACHE](/docs/server/reference/sql-statements/administrative-sql-statements/flush-commands/flush-query-cache.md): Defragment the query cache to optimize memory usage. This command reorganizes the cache to eliminate fragmentation without removing existing cached queries.
- [FLUSH TABLES FOR EXPORT](/docs/server/reference/sql-statements/administrative-sql-statements/flush-commands/flush-tables-for-export.md): Prepare individual tables for binary backup. This command flushes changes to disk and locks tables, allowing safe copying of .ibd files while the server runs.
- [Plugin Statements](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements.md): Manage server plugins. This section covers INSTALL PLUGIN, UNINSTALL PLUGIN, and SHOW PLUGINS for extending server functionality.
- [INSTALL PLUGIN](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/install-plugin.md): Install a specific plugin from a shared library. This statement adds the plugin to the mysql.plugin table and loads its code into the server memory.
- [INSTALL SONAME](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/install-soname.md): Load all plugins contained within a shared library file. This statement automatically discovers and installs every valid plugin found in the specified library.
- [UNINSTALL PLUGIN](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/uninstall-plugin.md): Remove a specific plugin from the server. This statement unloads the plugin code and deletes its entry from the mysql.plugin table to prevent reloading.
- [UNINSTALL SONAME](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/uninstall-soname.md): Uninstall all plugins loaded from a specific library. This statement removes every plugin associated with the library file and unloads the library itself.
- [Replication Statements](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements.md): Control replication topologies. Learn statements like CHANGE MASTER TO and START SLAVE to configure primaries and replicas.
- [CHANGE MASTER TO](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/change-master-to.md): Complete CHANGE MASTER TO reference: MASTER\_HOST/PORT/USER/PASSWORD syntax, MASTER\_LOG\_FILE/POS options, MASTER\_USE\_GTID configuration, and MASTER\_SSL settings.
- [RESET MASTER](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/reset-master.md)
- [RESET REPLICA](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/reset-replica.md)
- [SET GLOBAL SQL\_SLAVE\_SKIP\_COUNTER](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/set-global-sql_slave_skip_counter.md)
- [START REPLICA](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/start-replica.md)
- [STOP REPLICA](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/stop-replica.md)
- [Legacy Replication Statements](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements.md): Category for old replication statements
- [RESET SLAVE](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements/legacy-commands-reset-slave.md)
- [SHOW SLAVE HOSTS](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements/legacy-commands-show-slave-hosts.md)
- [SHOW SLAVE STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements/legacy-commands-show-slave-status.md)
- [START SLAVE](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements/legacy-commands-start-slave.md)
- [STOP SLAVE](/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/legacy-replication-statements/legacy-commands-stop-slave.md)
- [SET Statements](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands.md): Assign values to system variables. Learn to use the SET statement to configure GLOBAL and SESSION variables for tuning server behavior.
- [SET](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set.md): Assign values to different types of variables. Learn the syntax for setting user-defined variables, system variables, and stored program variables.
- [SET CHARACTER SET](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-character-set.md): Map strings to a specific character set. This command updates the character set for the client, results, and connection to ensure correct data encoding.
- [SET NAMES](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-names.md): Configure the character set and collation for the current connection. This ensures the server correctly interprets data sent by the client application.
- [SET PATH](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-path.md)
- [SET SQL\_LOG\_BIN](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-sql_log_bin.md): Enable or disable binary logging for the current session. This statement allows administrators to perform operations without replicating them to replicas.
- [SET STATEMENT](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-statement.md): Set a system variable for the duration of a single query. This statement allows temporary configuration changes that apply only to the immediate statement.
- [SET TRANSACTION](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-transaction.md): Define isolation levels and access modes for transactions. Learn to configure the behavior of the next transaction or the entire session for data consistency.
- [SET Variable](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set-variable.md): Assign values to user-defined variables. This guide explains how to store data in session-specific variables for reuse in subsequent SQL statements.
- [SHOW Statements](/docs/server/reference/sql-statements/administrative-sql-statements/show.md): View server metadata and status. This section lists SHOW statements for inspecting databases, tables, variables, and performance metrics.
- [About SHOW](/docs/server/reference/sql-statements/administrative-sql-statements/show/about-show.md): Overview of the SHOW statement syntax. Learn how to use patterns and WHERE clauses to filter output from various SHOW statements.
- [Extended SHOW](/docs/server/reference/sql-statements/administrative-sql-statements/show/extended-show.md): Understand the extensions to the SHOW statement. Learn how to use WHERE and LIKE clauses to perform complex filtering on metadata results.
- [SHOW ANALYZE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-analyze.md): Retrieve runtime statistics for a currently executing query. This statement provides insights into query plan execution without waiting for completion.
- [SHOW AUTHORS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-authors.md): Display a list of major contributors to the MariaDB and MySQL projects. View names, locations, and specific contributions of developers.
- [SHOW BINARY LOGS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-binary-logs.md): List the binary log files on the server. View the file names and sizes to monitor replication logs and manage disk usage.
- [SHOW BINLOG EVENTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-binlog-events.md): Inspect the contents of a binary log file. This statement displays the events within a specific binlog, useful for debugging replication issues.
- [SHOW MASTER STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-binlog-status.md): View the current status of the primary server's binary log. This statement returns the current log file name and position for replication synchronization.
- [SHOW CHARACTER SET](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-character-set.md): List available character sets. View the default collation, maximum length, and description for each supported character set.
- [SHOW CLIENT\_STATISTICS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-client-statistics.md): View statistics on client connections. This statement displays metrics like bytes sent/received and busy time for connected clients.
- [SHOW COLLATION](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-collation.md): List available collations. View the character set associated with each collation and identifying properties like ID and default status.
- [SHOW COLUMNS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-columns.md): Complete guide to displaying table columns in MariaDB. Complete SHOW COLUMNS syntax with field types, keys, and filtering options for production use.
- [SHOW CONTRIBUTORS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-contributors.md): List financial contributors to the MariaDB Foundation. View the names and contributions of companies and individuals supporting the project.
- [SHOW CREATE DATABASE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-database.md): View the CREATE DATABASE statement. This statement returns the SQL syntax required to recreate a specific database with its current options.
- [SHOW CREATE EVENT](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-event.md): Get the SQL statement to recreate a scheduled event. This statement displays the complete syntax used to define a specific event.
- [SHOW CREATE FUNCTION](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-function.md): Retrieve the CREATE FUNCTION statement. This statement shows the exact SQL used to define a stored function, including its body and characteristics.
- [SHOW CREATE PACKAGE BODY](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-package-body.md): Display the CREATE statement for a package body. This Oracle-compatible statement shows the implementation code of a stored package.
- [SHOW CREATE PACKAGE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-package.md): View the CREATE PACKAGE statement. This statement returns the interface definition of a stored package in MariaDB.
- [SHOW CREATE PROCEDURE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-procedure.md): Get the CREATE PROCEDURE statement. This statement returns the SQL syntax used to define a specific stored procedure.
- [SHOW CREATE SEQUENCE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-sequence.md): View the SQL used to create a sequence. This statement displays the CREATE SEQUENCE statement with current parameter values.
- [SHOW CREATE SERVER](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-server.md): Display the CREATE SERVER statement. This statement shows the configuration details for a defined federated server connection.
- [SHOW CREATE TABLE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-table.md): Get the SQL statement to recreate a table. This statement shows the complete CREATE TABLE syntax, including column definitions and indexes.
- [SHOW CREATE TRIGGER](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-trigger.md): Retrieve the CREATE TRIGGER statement. This statement displays the SQL syntax defining a specific trigger and its timing events.
- [SHOW CREATE USER](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-user.md): View the CREATE USER statement. This statement returns the SQL required to recreate a user account with its authentication details.
- [SHOW CREATE VIEW](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-view.md): Display the CREATE VIEW statement. This statement shows the SQL query that defines a specific view structure.
- [SHOW DATABASES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-databases.md): Complete reference for listing databases in MariaDB. Complete SHOW DATABASES syntax with pattern matching and privilege considerations for production use.
- [SHOW ENGINE INNODB STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-engine-innodb-status.md): View extensive status information for the InnoDB engine. This statement displays details on deadlocks, buffer pool usage, and I/O activity.
- [SHOW ENGINE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-engine.md): Display status information for a storage engine. This statement retrieves operational logs or status details for a specific engine.
- [SHOW ENGINES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-engines.md): List available storage engines. View the support status (default, active, or disabled) and description for each engine.
- [SHOW ERRORS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-errors.md): Display errors from the last executed statement. View error codes, messages, and types for recent failures.
- [SHOW EVENTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-events.md): List scheduled events. View metadata such as the event name, schedule, status, and timing for events in a database.
- [SHOW EXPLAIN](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-explain.md): Get the execution plan for a running query. This statement displays EXPLAIN output for a statement currently executing in another thread.
- [SHOW FUNCTION CODE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-function-code.md): Display the internal instruction representation of a stored function. This debug statement shows the low-level opcodes of the routine.
- [SHOW FUNCTION STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-function-status.md): List stored functions and their characteristics. View metadata like the database, name, type, and creator of stored functions.
- [SHOW GRANTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-grants.md): Complete SHOW GRANTS reference for MariaDB. Complete syntax guide with filtering, pattern matching, and access control options with comprehensive examples.
- [SHOW INDEX\_STATISTICS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-index-statistics.md): View usage statistics for table indexes. This statement displays how often specific indexes are used, helping optimize query performance.
- [SHOW INDEX](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-index.md): Complete SHOW INDEX reference: SHOW {INDEX|INDEXES|KEYS} FROM tbl\_name syntax, output fields (Key\_name, Seq\_in\_index, Cardinality), and WHERE/LIKE filters.
- [SHOW INNODB STATUS (removed)](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-innodb-status-removed.md): Documentation for the deprecated SHOW INNODB STATUS statement. This statement was removed in favor of SHOW ENGINE INNODB STATUS.
- [SHOW LOCALES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-locales.md): List available error message locales. View the language IDs, names, and descriptions for supported localization settings.
- [SHOW OPEN TABLES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-open-tables.md): List currently open tables. View the database, table name, and lock status for tables in the table cache.
- [SHOW PACKAGE BODY STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-package-body-status.md): List stored package bodies. View metadata about the implementation part of Oracle-compatible packages.
- [SHOW PACKAGE STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-package-status.md): List stored packages. View metadata about the interface part of Oracle-compatible packages in the database.
- [SHOW PLUGINS SONAME](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-plugins-soname.md): List plugins and their library files. View information about installed plugins and their associated shared object names.
- [SHOW PLUGINS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-plugins.md): List installed server plugins. View the name, status, type, and library file for each active plugin.
- [SHOW PRIVILEGES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-privileges.md): List available system privileges. View the context and description for each privilege supported by the server.
- [SHOW PROCEDURE CODE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-procedure-code.md): Display the internal instruction representation of a stored procedure. This debug statement shows the low-level opcodes of the routine.
- [SHOW PROCEDURE STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-procedure-status.md): List stored procedures and their characteristics. View metadata like the database, name, type, and creator of stored procedures.
- [SHOW PROCESSLIST](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-processlist.md): Complete SHOW PROCESSLIST reference: FULL keyword for complete queries, PROCESS privilege, columns (Id, User, Host, db, Command, Time, State, Info).
- [SHOW PROFILE](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-profile.md): Display profiling information for a query. View resource usage statistics like CPU and block IO for the most recent statement.
- [SHOW PROFILES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-profiles.md): List queries for which profiling data is available. View the query ID and duration for recent statements when profiling is enabled.
- [SHOW QUERY\_RESPONSE\_TIME](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-query_response_time.md): View the distribution of query execution times. This statement groups queries into time-based buckets to analyze performance.
- [SHOW RELAYLOG EVENTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-relaylog-events.md): Inspect events in the relay log. This statement displays replication events from the relay log on a replica server.
- [SHOW REPLICA HOSTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-replica-hosts.md): List registered replicas. This statement displays information about replica servers connected to the current primary.
- [SHOW REPLICA STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-replica-status.md): Complete SHOW REPLICA STATUS: FOR CHANNEL/connection\_name syntax, SHOW ALL REPLICAS option, thread states (Slave\_IO/SQL\_Running), and lag/log/GTID fields.
- [SHOW STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-status.md): View server status variables. This statement displays counters and metrics for server activity, performance, and health.
- [SHOW TABLE\_STATISTICS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-table-statistics.md): View usage statistics for tables. This statement displays metrics like rows read, changed, and updated for each table.
- [SHOW TABLE STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-table-status.md): Get metadata for tables. View details like engine type, row count, data length, and create time for tables in a database.
- [SHOW TABLES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-tables.md): Complete guide to listing tables in MariaDB. Complete SHOW TABLES syntax reference with LIKE patterns, WHERE conditions, and filtering options.
- [SHOW TRIGGERS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-triggers.md): List triggers defined on tables. View metadata such as the trigger event, timing, and the table it is associated with.
- [SHOW USER\_STATISTICS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-user-statistics.md): View statistics on user activity. This statement displays metrics like CPU time and rows read for each user account.
- [SHOW USER\_VARIABLES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-user_variables.md): List defined user variables. This statement displays the names and values of variables set in the current session.
- [SHOW VARIABLES](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-variables.md): Complete SHOW VARIABLES reference: GLOBAL/SESSION scope syntax, LIKE 'pattern' matching, WHERE expression filters, and INFORMATION\_SCHEMA table queries.
- [SHOW WARNINGS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-warnings.md): Display warnings from the last executed statement. View warning codes, messages, and levels for recent operations.
- [SHOW WSREP\_MEMBERSHIP](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-wsrep_membership.md): View Galera Cluster membership. This statement displays the UUID, name, and address of nodes in the cluster.
- [SHOW WSREP\_STATUS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-wsrep_status.md): View Galera Cluster status variables. This statement displays internal status metrics for the wsrep provider.
- [Data Definition (DDL)](/docs/server/reference/sql-statements/data-definition.md): Learn data definition language (DDL) statements in MariaDB Server. This section covers SQL commands for creating, altering, and dropping databases, tables, indexes, and other schema objects.
- [Atomic DDL](/docs/server/reference/sql-statements/data-definition/atomic-ddl.md): Learn about crash-safe DDL operations in MariaDB. This feature ensures data definition statements are either fully committed or completely rolled back, preventing metadata inconsistency.
- [CONSTRAINT](/docs/server/reference/sql-statements/data-definition/constraint.md): Complete constraints reference: PRIMARY KEY, FOREIGN KEY, UNIQUE, and CHECK syntax in CREATE/ALTER TABLE, ON DELETE/UPDATE actions, TABLE\_CONSTRAINTS table.
- [RENAME TABLE](/docs/server/reference/sql-statements/data-definition/rename-table.md): Change the name of one or more tables atomically. This command moves tables within or between databases while preserving their data and structure.
- [Renaming Databases](/docs/server/reference/sql-statements/data-definition/renaming-databases.md): Learn the supported methods for renaming a database. Since RENAME DATABASE is not available, this guide outlines safe workarounds like dumping and reloading or moving tables.
- [ALTER](/docs/server/reference/sql-statements/data-definition/alter.md): Access the reference for ALTER statements. This section lists commands to modify existing database objects, including tables, databases, users, and servers.
- [ALTER DATABASE](/docs/server/reference/sql-statements/data-definition/alter/alter-database.md): Modify database characteristics. Learn how to change global properties like the default character set and collation for a specific database.
- [ALTER FUNCTION](/docs/server/reference/sql-statements/data-definition/alter/alter-function.md): Change stored function characteristics. This statement allows modifying the security context or comments of a stored function without dropping it.
- [ALTER LOGFILE GROUP](/docs/server/reference/sql-statements/data-definition/alter/alter-logfile-group.md): Understand the support status of this statement. Originally designed for NDB Cluster, it is not currently supported in MariaDB Server.
- [ALTER SERVER](/docs/server/reference/sql-statements/data-definition/alter/alter-server.md): Modify server definitions. Update connection information for external servers defined with CREATE SERVER, primarily used by the Federated engine.
- [ALTER TABLE](/docs/server/reference/sql-statements/data-definition/alter/alter-table.md): Complete ALTER TABLE guide for MariaDB. Complete syntax for modifying columns, indexes, constraints, and table properties with comprehensive examples and.
- [Online Schema Change](/docs/server/reference/sql-statements/data-definition/alter/alter-table/online-schema-change.md): Modify table structures. This guide covers adding columns, changing data types, managing indexes, and other schema changes for existing tables.
- [ALTER TABLESPACE](/docs/server/reference/sql-statements/data-definition/alter/alter-tablespace.md): Understand the status of tablespace management. This statement, originally for NDB, is not supported in MariaDB for InnoDB tablespaces.
- [CREATE](/docs/server/reference/sql-statements/data-definition/create.md): Explore the CREATE statements used to define new database objects. This guide covers syntax for creating databases, tables, indexes, views, and stored routines.
- [CREATE DATABASE](/docs/server/reference/sql-statements/data-definition/create/create-database.md): Complete reference for CREATE DATABASE in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and.
- [CREATE EVENT](/docs/server/reference/sql-statements/data-definition/create/create-event.md): Schedule a new event for automatic execution. This statement defines a scheduled task that runs SQL commands at specific times or intervals.
- [CREATE FUNCTION](/docs/server/reference/sql-statements/data-definition/create/create-function.md): Complete CREATE FUNCTION reference: OR REPLACE/IF NOT EXISTS, DEFINER/SQL SECURITY clauses, RETURNS type, DETERMINISTIC/NO SQL characteristics.
- [CREATE INDEX](/docs/server/reference/sql-statements/data-definition/create/create-index.md): Complete reference for CREATE INDEX in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and best.
- [CREATE LOGFILE GROUP](/docs/server/reference/sql-statements/data-definition/create/create-logfile-group.md): Create a log file group for NDB Cluster. This command allocates undo log space on disk for NDB Disk Data tables.
- [CREATE PACKAGE](/docs/server/reference/sql-statements/data-definition/create/create-package.md): Define the interface for a stored package. This Oracle-compatible statement declares the public variables and subroutines of a package.
- [CREATE PACKAGE BODY](/docs/server/reference/sql-statements/data-definition/create/create-package-body.md): Implement the logic for a stored package. This statement defines the private variables and code for the subroutines declared in the package specification.
- [CREATE SERVER](/docs/server/reference/sql-statements/data-definition/create/create-server.md): Define a connection to a remote server. This command registers server details for use with the FEDERATED or SPIDER storage engines.
- [CREATE TABLESPACE](/docs/server/reference/sql-statements/data-definition/create/create-tablespace.md): Create a tablespace for data storage. This command defines a physical file container for storing table data, primarily for InnoDB or NDB engines.
- [Generated Columns](/docs/server/reference/sql-statements/data-definition/create/generated-columns.md): Complete generated columns reference: VIRTUAL vs PERSISTENT/STORED syntax, CREATE/ALTER TABLE, index/foreign key constraints, sql\_mode consistency.
- [Invisible Columns](/docs/server/reference/sql-statements/data-definition/create/invisible-columns.md): Explains how to define columns that are hidden from wildcard SELECT queries but remain accessible when explicitly referenced, facilitating schema changes without breaking existing applications.
- [Silent Column Changes](/docs/server/reference/sql-statements/data-definition/create/silent-column-changes.md): Explore Silent Column Changes in MariaDB. Learn when the server automatically modifies column definitions or data types during table creation to ensure engine compatibility.
- [DROP](/docs/server/reference/sql-statements/data-definition/drop.md): Find statements to remove database objects. This section details the syntax for deleting databases, tables, users, and other entities when they are no longer needed.
- [DROP DATABASE](/docs/server/reference/sql-statements/data-definition/drop/drop-database.md): Complete guide to removing databases in MariaDB. Complete DROP DATABASE syntax with IF EXISTS, permissions, and recovery options for production use.
- [DROP EVENT](/docs/server/reference/sql-statements/data-definition/drop/drop-event.md): Remove a scheduled event from the server. This command stops the event from executing and deletes its definition from the system tables.
- [DROP INDEX](/docs/server/reference/sql-statements/data-definition/drop/drop-index.md): Remove an existing index from a table. This command deletes the index structure, potentially impacting query performance but freeing storage.
- [DROP LOGFILE GROUP](/docs/server/reference/sql-statements/data-definition/drop/drop-logfile-group.md): Remove a log file group. This statement, primarily for NDB Cluster, deletes the undo log files associated with the specified log file group.
- [DROP PACKAGE BODY](/docs/server/reference/sql-statements/data-definition/drop/drop-package-body.md): Delete the body of a stored package. This command removes the implementation logic while preserving the package specification and interface.
- [DROP PACKAGE](/docs/server/reference/sql-statements/data-definition/drop/drop-package.md): Remove a stored package completely. This command deletes both the package specification (interface) and its body (implementation) from the database.
- [DROP SERVER](/docs/server/reference/sql-statements/data-definition/drop/drop-server.md): Remove a server definition. This command deletes the connection details for a remote server used by the FEDERATED or SPIDER storage engines.
- [DROP TABLESPACE](/docs/server/reference/sql-statements/data-definition/drop/drop-tablespace.md): Delete a tablespace. This command removes the physical file container used for storing table data, applicable to engines like InnoDB or NDB.
- [DROP TRIGGER](/docs/server/reference/sql-statements/data-definition/drop/drop-trigger.md): Remove a trigger from a table. This command deletes the trigger definition, preventing it from firing on future INSERT, UPDATE, or DELETE events.
- [Data Manipulation (DML)](/docs/server/reference/sql-statements/data-manipulation.md): Learn data manipulation language (DML) statements in MariaDB Server. This section covers SQL commands for inserting, updating, deleting, and selecting data within your databases.
- [Changing & Deleting Data](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data.md): Learn to change and delete data in MariaDB Server. This section covers UPDATE and DELETE SQL statements, enabling you to modify existing records and remove unwanted information efficiently.
- [DELETE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/delete.md): Complete guide to deleting data in MariaDB. Complete DELETE syntax with WHERE filtering, JOIN operations, CTEs, and safety considerations for production use.
- [HIGH\_PRIORITY and LOW\_PRIORITY](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/high_priority-and-low_priority.md): Control locking priority for table access. These modifiers determine whether read or write operations take precedence when multiple threads access a table.
- [REPLACE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/replace.md): Insert or replace rows based on unique keys. This statement acts like INSERT, but if a duplicate key exists, it deletes the old row and inserts the new one.
- [REPLACE...RETURNING](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/replacereturning.md): Replace rows and retrieve the results immediately. This extension returns the values of the replaced or inserted rows in the same operation.
- [UPDATE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/update.md): Complete UPDATE statement guide for MariaDB. Complete syntax reference with WHERE conditions, JOIN operations, CTEs, and multi-table updates for production use.
- [Inserting & Loading Data](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data.md): Learn to insert and load data into MariaDB Server. This section covers INSERT and LOAD DATA SQL statements, enabling you to efficiently add new records to your databases.
- [Concurrent Inserts](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/concurrent-inserts.md): Understand concurrent inserts in MyISAM. This feature allows SELECT statements to run simultaneously with INSERT operations, reducing lock contention and improving performance.
- [IGNORE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/ignore.md): Learn about the IGNORE keyword. This modifier suppresses certain errors during statement execution, downgrading them to warnings to allow the operation to proceed.
- [INSERT](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert.md): Complete guide to inserting data in MariaDB. Complete INSERT syntax for single rows, bulk operations, and ON DUPLICATE KEY handling for production use.
- [INSERT - Default & Duplicate Values](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert-default-duplicate-values.md): Handle default and duplicate values during insertion. Learn how MariaDB manages missing columns and how to resolve duplicate key conflicts using various strategies.
- [INSERT DELAYED](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert-delayed.md): Queue inserts for later execution. This MyISAM-specific extension returns control immediately to the client while the server inserts rows when the table is free.
- [INSERT IGNORE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert-ignore.md): Complete INSERT IGNORE reference: ignore insert errors and warnings, duplicate key error handling, invalid value coercion, and SHOW WARNINGS compatibility.
- [INSERT ON DUPLICATE KEY UPDATE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert-on-duplicate-key-update.md): Complete guide to inserting data in MariaDB. Complete INSERT syntax for single rows, bulk operations, and ON DUPLICATE KEY handling for production use.
- [INSERT SELECT](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert-select.md): Copy data between tables. This statement inserts the result set of a SELECT query directly into a target table, enabling efficient bulk data transfer.
- [INSERT...RETURNING](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insertreturning.md): Insert rows and immediately retrieve the results. This extension returns the inserted values, including auto-increments and defaults, in the same round trip.
- [LOAD Data into Tables or Index](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/load-data-into-tables-or-index.md): Bulk load data efficiently. This section covers commands like LOAD DATA INFILE and LOAD XML for high-speed data import from text or XML files.
- [LOAD DATA INFILE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/load-data-into-tables-or-index/load-data-infile.md): Complete reference for LOAD DATA INFILE in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and.
- [LOAD INDEX](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/load-data-into-tables-or-index/load-index.md): Preload table indexes into the key cache. This command, used for MyISAM tables, loads index blocks into memory to warm up the cache and improve subsequent query performance.
- [LOAD XML](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/load-data-into-tables-or-index/load-xml.md): Read data from an XML file into a table. This command parses XML content, mapping elements and attributes to table columns for direct data import.
- [Selecting Data](/docs/server/reference/sql-statements/data-manipulation/selecting-data.md): Learn to select data in MariaDB Server using SQL. This section covers various SELECT statement clauses, including WHERE, GROUP BY, and ORDER BY, to retrieve and filter your data effectively.
- [DUAL](/docs/server/reference/sql-statements/data-manipulation/selecting-data/dual.md): Understand the DUAL table. This dummy table allows selecting values without referencing a real table, often used for calculations or retrieving system variables.
- [FOR UPDATE](/docs/server/reference/sql-statements/data-manipulation/selecting-data/for-update.md): Lock rows for write operations. This clause prevents other transactions from modifying or reading the selected rows until the current transaction ends.
- [GROUP BY](/docs/server/reference/sql-statements/data-manipulation/selecting-data/group-by.md): Group result sets by one or more columns. Learn to aggregate data using functions like SUM, COUNT, and AVG in conjunction with grouping.
- [LIMIT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/limit.md): Complete LIMIT clause reference: LIMIT n, LIMIT offset,row\_count, LIMIT row\_count OFFSET offset syntax, ORDER BY result handling, and UPDATE replication safety.
- [LOCK IN SHARE MODE](/docs/server/reference/sql-statements/data-manipulation/selecting-data/lock-in-share-mode.md): Read rows with a shared lock. This clause ensures rows remain unchanged by other transactions while allowing other sessions to read them.
- [ORDER BY](/docs/server/reference/sql-statements/data-manipulation/selecting-data/order-by.md): Complete ORDER BY clause: sort SELECT/UPDATE/DELETE results with ASC/DESC, multiple expressions, integer column positions, GROUP BY/LIMIT usage.
- [PROCEDURE](/docs/server/reference/sql-statements/data-manipulation/selecting-data/procedure.md): Pass query results to a C procedure. This clause allows processing the result set on the server side before returning it to the client.
- [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md): Complete guide to SELECT queries in MariaDB. Complete syntax reference for joins, subqueries, WHERE clauses, GROUP BY, and aggregate functions.
- [SELECT INTO DUMPFILE](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select-into-dumpfile.md): Export a single row to a file without formatting. This statement writes raw binary data, such as BLOBs, directly to a file on the server.
- [SELECT INTO OUTFILE](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select-into-outfile.md): Complete guide to SELECT queries in MariaDB. Complete syntax reference for joins, subqueries, WHERE clauses, GROUP BY, and aggregate functions.
- [SELECT ... OFFSET ... FETCH](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select-offset-fetch.md): Pagination using standard SQL syntax. This clause limits the number of rows returned and skips a specified number of rows, similar to LIMIT.
- [SELECT WITH ROLLUP](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select-with-rollup.md): Generate super-aggregate summaries. This modifier adds extra rows to the result set representing subtotals and grand totals for grouped columns.
- [Common Table Expressions (CTE)](/docs/server/reference/sql-statements/data-manipulation/selecting-data/common-table-expressions.md): Learn about Common Table Expressions (CTEs) in MariaDB Server. This section explains how to use CTEs for complex, readable, and reusable subqueries, simplifying data selection and manipulation.
- [Recursive Common Table Expressions Overview](/docs/server/reference/sql-statements/data-manipulation/selecting-data/common-table-expressions/recursive-common-table-expressions-overview.md): Process hierarchical data using recursive CTEs. These expressions reference themselves to repeatedly execute a subquery, perfect for traversing tree structures or generating sequences.
- [Non-Recursive Common Table Expressions Overview](/docs/server/reference/sql-statements/data-manipulation/selecting-data/common-table-expressions/non-recursive-common-table-expressions-overview.md): Define simple temporary result sets. Non-recursive CTEs act like query-local views, improving readability by allowing you to define and reuse subqueries within a single statement.
- [WITH](/docs/server/reference/sql-statements/data-manipulation/selecting-data/common-table-expressions/with.md): Complete WITH clause reference: WITH \[RECURSIVE] AS (SELECT...) syntax, recursive CTE support, CYCLE...RESTRICT cycle detection, and max\_recursive\_iterations.
- [Joins](/docs/server/reference/sql-statements/data-manipulation/selecting-data/joins.md): Retrieve data from multiple tables based on related columns. This section covers INNER, LEFT, RIGHT, and CROSS JOIN syntax and usage.
- [JOIN Syntax](/docs/server/reference/sql-statements/data-manipulation/selecting-data/joins/join-syntax.md): Complete reference for JOIN Syntax in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and best.
- [Comma vs JOIN](/docs/server/reference/sql-statements/data-manipulation/selecting-data/joins/comma-vs-join.md): Compare implicit and explicit join syntax. This article explains why using the explicit JOIN syntax with an ON clause is preferred over comma-separated tables for readability and precedence.
- [Set Operations](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations.md): SQL set operations combine the results of multiple query blocks in a single result, using the standard SQL operators EXCEPT, INTERSECT, and UNION, and the Oracle operator MINUS.
- [Precedence Control in Table Operations](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations/precedence-control-in-table-operations.md): Control the execution order of UNION, EXCEPT, and INTERSECT operations. Learn how to use parentheses to define explicit operation priority.
- [EXCEPT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations/except.md): Return rows from the first result set that do not appear in the second. This set operator performs a subtraction of two datasets.
- [INTERSECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations/intersect.md)
- [MINUS](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations/minus.md): Oracle-compatible synonym for the EXCEPT operator. It returns rows from the first query that are not present in the second query.
- [UNION](/docs/server/reference/sql-statements/data-manipulation/selecting-data/set-operations/union.md): Combine results from multiple SELECT statements into a single result set. This operator can optionally remove duplicates or include all rows.
- [Subqueries](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries.md): Nest queries within other SQL statements. Learn to use scalar, column, row, and table subqueries to filter or calculate data dynamically.
- [Subqueries With ALL](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-and-all.md): Compare a value against all results from a subquery. The ALL operator returns TRUE if the comparison holds for every row returned by the subquery.
- [Subqueries With ANY and SOME](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-and-any.md): Compare a value against any result from a subquery. The ANY (or SOME) operator returns TRUE if the comparison holds for at least one row.
- [Subqueries with IN and NOT IN](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-with-in-and-not-in.md)
- [Subqueries With EXISTS](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-and-exists.md): Test for the existence of rows. The EXISTS operator returns TRUE if the subquery returns at least one row, often used for correlated subqueries.
- [Subqueries With JOINs](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-and-joins.md): Understand when to use subqueries versus joins. This guide explains performance implications and how to rewrite subqueries as joins for efficiency.
- [Subqueries in a FROM Clause (Derived Tables)](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-in-a-from-clause-derived-tables.md): Use a subquery as a temporary table. Derived tables allow you to select from the result set of another query within the FROM clause.
- [Row Subqueries](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-row-subqueries.md): Retrieve a single row of multiple values. A row subquery returns a tuple that can be compared against a row constructor in the outer query.
- [Scalar Subqueries](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subqueries-scalar-subqueries.md): Return a single value. A scalar subquery produces a one-row, one-column result that can be used anywhere a constant or expression is valid.
- [Subquery Limitations](/docs/server/reference/sql-statements/data-manipulation/selecting-data/subqueries/subquery-limitations.md): Review restrictions on subquery usage. This page details unsupported operations, such as modifying a table while selecting from it in a subquery.
- [Geometry Statements](/docs/server/reference/sql-statements/geometry-constructors.md): Learn about geometry constructors in MariaDB Server. This section details SQL functions for creating spatial data types like points, lines, and polygons, enabling geospatial data management.
- [Geometry Constructors](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors.md): Learn about geometry constructors in MariaDB Server. This section details SQL functions for creating spatial data types like points, lines, and polygons, enabling geospatial data management.
- [BUFFER](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/buffer.md): Returns a geometry representing all points within a given distance of the geometry value. This function calculates a buffer zone around the spatial object.
- [CONVEXHULL](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/convexhull.md): Returns a geometry representing the convex hull of the given geometry value. It computes the smallest convex polygon that contains the entire geometry.
- [GEOMETRYCOLLECTION](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/geometrycollection.md): Constructs a GeometryCollection value from a list of WKB arguments. This function creates a collection containing multiple geometry objects.
- [LINESTRING](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/linestring.md): Constructs a LineString value from a number of Point values. It creates a linear geometry connecting the specified coordinate points.
- [MULTILINESTRING](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multilinestring.md): Constructs a MultiLineString value from a list of WKB LineString arguments. This function creates a collection of multiple line strings.
- [MULTIPOINT](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipoint.md): Constructs a MultiPoint value from a list of WKB Point arguments. It creates a geometry collection consisting of multiple individual points.
- [MULTIPOLYGON](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/multipolygon.md): Constructs a MultiPolygon value from a list of WKB Polygon arguments. This function creates a geometry collection containing multiple polygons.
- [POINT](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/point.md): Constructs a Point value using its coordinates. This basic constructor creates a point geometry from given X and Y (and optionally Z/M) values.
- [PointOnSurface](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/pointonsurface.md): Returns a Point which is guaranteed to lie on the surface of the given geometry. This is useful for labeling or finding a representative point inside a polygon.
- [POLYGON](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/polygon.md): Constructs a Polygon value from a list of WKB LineString arguments. It defines a filled shape using an outer ring and optional inner rings (holes).
- [ST\_BUFFER](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_buffer.md): Returns a geometry representing all points within a given distance of the geometry. This standard-compliant function creates a buffer zone around the object.
- [ST\_CONVEXHULL](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_convexhull.md): Returns a geometry representing the convex hull of the given geometry. This standard function computes the smallest convex polygon enclosing the geometry.
- [ST\_INTERSECTION](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_intersection.md): Returns a geometry representing the point set intersection of two geometries. It outputs the spatial region shared by both input objects.
- [ST\_POINTONSURFACE](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_pointonsurface.md): Returns a Point guaranteed to lie on the surface of the given geometry. This standard function finds a representative point strictly within the geometry's area.
- [ST\_SYMDIFFERENCE](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_symdifference.md): Returns a geometry representing the point set symmetric difference of two geometries. It outputs the spatial area present in either geometry but not in both.
- [ST\_UNION](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_union.md): Returns a geometry representing the point set union of two geometries. This function merges multiple spatial objects into a single geometry.
- [ST\_AsGeoJSON](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/geojson-st_asgeojson.md): Generates a GeoJSON object from a given geometry. This function converts internal geometry data into the standard JSON-based format for web mapping.
- [ST\_GeomFromGeoJSON](/docs/server/reference/sql-statements/geometry-constructors/geometry-constructors/st_geomfromgeojson.md): Parses a GeoJSON string and returns a geometry. This function converts a standard GeoJSON representation into a MariaDB geometry value.
- [Geometry Properties](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties.md): Learn about geometry properties. This section details SQL functions for retrieving attributes of spatial objects, such as area, length, and bounding box, essential for geospatial analysis.
- [BOUNDARY](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-boundary.md): Synonym for ST\_BOUNDARY. Returns a geometry representing the closure of the combinatorial boundary of the geometry value.
- [DIMENSION](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/dimension.md): Synonym for ST\_DIMENSION. Returns the inherent dimension of a geometry object (0 for Point, 1 for LineString, 2 for Polygon).
- [ENVELOPE](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-envelope.md): Synonym for ST\_ENVELOPE. Returns the Minimum Bounding Rectangle (MBR) for the given geometry as a Polygon.
- [GeometryN](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-geometryn.md): Synonym for ST\_GEOMETRYN. Returns the N-th geometry from a GeometryCollection, numbered starting from 1.
- [GeometryType](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-geometrytype.md): Synonym for ST\_GEOMETRYTYPE. Returns the name of the geometry type (e.g., 'POINT') of the geometry instance.
- [IsClosed](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/isclosed.md): Synonym for ST\_ISCLOSED. Checks if a LineString's start and end points are the same (closed).
- [IsEmpty](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-isempty.md): Synonym for ST\_ISEMPTY. Checks if a geometry is empty (contains no point sets). Returns 1 if empty, 0 otherwise.
- [IsRing](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/isring.md): Synonym for ST\_ISRING. Checks if a LineString is a ring, meaning it is both closed and simple.
- [IsSimple](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-issimple.md): Synonym for ST\_ISSIMPLE. Checks if a geometry is simple, meaning it has no anomalous geometric points like self-intersections.
- [NumGeometries](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-numgeometries.md): Synonym for ST\_NUMGEOMETRIES. Returns the number of geometries contained in a GeometryCollection.
- [SRID](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/geometry-properties-srid.md): Synonym for ST\_SRID. Returns the Spatial Reference Identifier (SRID) integer associated with the geometry.
- [ST\_BOUNDARY](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_boundary.md): Returns the combinatorial boundary of a geometry. For a Polygon, this is the line string defining the boundary.
- [ST\_DIMENSION](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_dimension.md): Returns the inherent dimension of the geometry value. Returns 0 for points, 1 for linear geometries, and 2 for surface geometries.
- [ST\_ENVELOPE](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_envelope.md): Returns the Minimum Bounding Rectangle (MBR) for the geometry value. The result is returned as a Polygon defined by the corner points.
- [ST\_GEOMETRYN](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_geometryn.md): Returns the N-th geometry in a GeometryCollection. Geometries are numbered beginning with 1.
- [ST\_GEOMETRYTYPE](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_geometrytype.md): Returns the name of the geometry type (e.g., 'POINT', 'LINESTRING', 'POLYGON') for the given geometry instance.
- [ST\_ISCLOSED](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_isclosed.md): Returns 1 if the LineString is closed (start and end points are the same), 0 if not, and NULL if the argument is NULL.
- [ST\_ISEMPTY](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_isempty.md): Checks if a geometry is empty. Returns 1 if the geometry contains no points, and 0 otherwise.
- [ST\_IsRing](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_isring.md): Checks if the LineString is a ring. Returns 1 if the LineString is both closed (start equals end) and simple (no self-intersection).
- [ST\_IsSimple](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_issimple.md): Checks if the geometry is simple (no self-intersections or anomalous points). Returns 1 if simple, 0 otherwise.
- [ST\_NUMGEOMETRIES](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_numgeometries.md): Returns the number of geometries in a GeometryCollection. Returns NULL if the argument is not a GeometryCollection.
- [ST\_RELATE](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_relate.md): Tests if two geometries are spatially related according to a given DE-9IM intersection matrix pattern.
- [ST\_SRID](/docs/server/reference/sql-statements/geometry-constructors/geometry-properties/st_srid.md): Returns the Spatial Reference Identifier (SRID) for the geometry. This integer represents the coordinate system used.
- [Geometry Relations](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations.md): Learn about geometry relations in MariaDB Server. This section details SQL functions for determining spatial relationships between geometric objects, such as ST\_Intersects and ST\_Contains.
- [CONTAINS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/contains.md): Synonym for ST\_CONTAINS. Checks if the first geometry completely contains the second geometry, with no points of the second geometry outside the first.
- [CROSSES](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/crosses.md): Synonym for ST\_CROSSES. Checks if two geometries cross, meaning they share some interior points but not all, and the intersection has a lower dimension.
- [DISJOINT](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/disjoint.md): Synonym for ST\_DISJOINT. Checks if two geometries are disjoint, meaning they have no points in common.
- [EQUALS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/equals.md): Synonym for ST\_EQUALS. Checks if two geometries are spatially equal, meaning they contain exactly the same point set.
- [INTERSECTS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/intersects.md): Synonym for ST\_INTERSECTS. Checks if two geometries intersect, meaning they share at least one common point.
- [OVERLAPS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/overlaps.md): Synonym for ST\_OVERLAPS. Checks if two geometries overlap, sharing some but not all points, and having the same dimension.
- [ST\_CONTAINS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-contains.md): Checks if geometry A contains geometry B. Returns 1 if B is completely inside A, 0 otherwise.
- [ST\_CROSSES](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-crosses.md): Checks if two geometries cross. Returns 1 if they intersect but one does not cover the other, and the intersection dimension is less than the maximum dimension.
- [ST\_DIFFERENCE](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st_difference.md): Returns a geometry representing the difference between two geometries. The result contains points from the first geometry that are not in the second.
- [ST\_DISJOINT](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st_disjoint.md): Checks if two geometries are disjoint. Returns 1 if the geometries share no points, 0 otherwise.
- [ST\_DISTANCE](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st_distance.md): Calculates the shortest distance between two geometries. Returns the minimum Euclidean distance between any two points in the geometries.
- [ST\_DISTANCE\_SPHERE](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st_distance_sphere.md): Calculates the spherical distance between two points or geometries. Uses a spherical earth model to determine the minimum distance in meters.
- [ST\_EQUALS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-equals.md): Returns a geometry representing the difference between two geometries. The result contains points from the first geometry that are not in the second.
- [ST\_INTERSECTS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-intersects.md): Checks if two geometries intersect. Returns 1 if the geometries share any portion of space (interior or boundary), 0 otherwise.
- [ST\_LENGTH](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st_length.md): Returns the length of a linear geometry. Calculates the total length of a LineString or MultiLineString in its associated spatial reference units.
- [ST\_OVERLAPS](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-overlaps.md): Checks if two geometries overlap. Returns 1 if they share space but neither completely contains the other, and they have the same dimension.
- [ST\_TOUCHES](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-touches.md): Checks if two geometries touch. Returns 1 if they intersect only at their boundaries and not their interiors.
- [ST\_WITHIN](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/st-within.md): Checks if geometry A is within geometry B. Returns 1 if A is completely inside B, 0 otherwise. This is the inverse of ST\_CONTAINS.
- [TOUCHES](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/touches.md): Synonym for ST\_TOUCHES. Checks if two geometries touch at their boundaries without their interiors intersecting.
- [WITHIN](/docs/server/reference/sql-statements/geometry-constructors/geometry-relations/within.md): Synonym for ST\_WITHIN. Checks if the first geometry is completely enclosed by the second geometry.
- [LineString Properties](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties.md): Learn about LINESTRING properties in MariaDB Server. This section details SQL functions for retrieving attributes of linear spatial objects, such as length, number of points, and start/end points.
- [ENDPOINT](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/linestring-properties-endpoint.md): Synonym for ST\_ENDPOINT. Returns the last point of a LineString geometry.
- [GLENGTH](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/glength.md): Synonym for ST\_LENGTH. Calculates the length of a LineString or MultiLineString in its associated spatial reference units.
- [NumPoints](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/linestring-properties-numpoints.md): Synonym for ST\_NUMPOINTS. Returns the number of points in a LineString geometry.
- [PointN](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/linestring-properties-pointn.md): Synonym for ST\_POINTN. Returns the N-th point in a LineString geometry, where N is a 1-based index.
- [STARTPOINT](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/linestring-properties-startpoint.md): Synonym for ST\_STARTPOINT. Returns the first point of a LineString geometry.
- [ST\_ENDPOINT](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/st_endpoint.md): Returns the end Point of a LineString. This function retrieves the final coordinate in the linear geometry sequence.
- [ST\_NUMPOINTS](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/st_numpoints.md): Returns the count of Points in a LineString. This function calculates the total number of vertices defining the line.
- [ST\_POINTN](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/st_pointn.md): Returns the N-th Point in a LineString. This function retrieves a specific point from the sequence based on its 1-based index.
- [ST\_STARTPOINT](/docs/server/reference/sql-statements/geometry-constructors/linestring-properties/st_startpoint.md): Returns the start Point of a LineString. This function retrieves the initial coordinate in the linear geometry sequence.
- [MBR (Minimum Bounding Rectangle)](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle.md): Learn about Minimum Bounding Rectangles (MBR) in MariaDB Server. This section details how to calculate and use MBRs for spatial indexing and efficient querying of geometric data.
- [MBR Definition](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbr-definition.md): Understand Minimum Bounding Rectangles. An MBR is the smallest rectangle that completely encloses a geometry, defined by its minimum and maximum X and Y coordinates.
- [MBRContains](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrcontains.md): Check if one MBR contains another. Returns 1 if the Minimum Bounding Rectangle of the first geometry completely encloses the MBR of the second geometry.
- [MBRCoveredBy](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrcoveredby.md): Check if one MBR is covered by another. Returns 1 if the MBR of the first geometry is entirely contained within the MBR of the second geometry.
- [MBRDisjoint](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrdisjoint.md): Check if two MBRs are disjoint. Returns 1 if the Minimum Bounding Rectangles of the two geometries do not intersect or touch at all.
- [MBREqual](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrequal.md): Check if two MBRs are identical. Returns 1 if the Minimum Bounding Rectangles of both geometries share the exact same coordinates.
- [MBRIntersects](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrintersects.md): Check if two MBRs intersect. Returns 1 if the Minimum Bounding Rectangles of the geometries share any portion of space, including boundaries.
- [MBROverlaps](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbroverlaps.md): Check if two MBRs overlap. Returns 1 if the MBRs intersect but neither completely contains the other, and they have the same dimension.
- [MBRTouches](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrtouches.md): Check if two MBRs touch. Returns 1 if the MBRs intersect only at their boundaries and do not share any interior points.
- [MBRWithin](/docs/server/reference/sql-statements/geometry-constructors/mbr-minimum-bounding-rectangle/mbrwithin.md): Check if one MBR is within another. Returns 1 if the MBR of the first geometry is completely enclosed by the MBR of the second geometry.
- [Miscellaneous GIS functions](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions.md): Explore miscellaneous GIS functions in MariaDB Server. This section details various SQL functions that support geographic information system operations and spatial data analysis.
- [ST\_Collect](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_collect.md): Aggregate multiple geometries into a collection. This function creates a MultiPoint, MultiLineString, MultiPolygon, or GeometryCollection from a set of geometry arguments.
- [ST\_GeoHash](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_geohash.md): Generate a Geohash string from a point or coordinates. This function encodes spatial locations into short, alphanumeric strings for efficient indexing and proximity searches.
- [ST\_IsValid](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_isvalid.md): Check if a geometry is valid. This function returns 1 if the geometry complies with OGC specifications (e.g., no self-intersections), 0 otherwise.
- [ST\_LatFromGeoHash](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_latfromgeohash.md): Decode a Geohash to retrieve the latitude. This function returns the latitude coordinate (Y-axis) from a given Geohash string.
- [ST\_LongFromGeoHash](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_longfromgeohash.md): Decode a Geohash to retrieve the longitude. This function returns the longitude coordinate (X-axis) from a given Geohash string.
- [ST\_PointFromGeoHash](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_pointfromgeohash.md): Create a Point geometry from a Geohash. This function decodes a Geohash string into a Point object representing the location's center.
- [ST\_Simplify](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_simplify.md): Simplify a geometry using the Douglas-Peucker algorithm. This function reduces the number of vertices in a geometry while preserving its general shape, useful for rendering maps.
- [ST\_Validate](/docs/server/reference/sql-statements/geometry-constructors/miscellaneous-gis-functions/st_validate.md): Validate and optionally return a geometry. This function checks if a geometry is valid according to OGC rules; it returns the geometry if valid, or NULL if not.
- [Point Properties](/docs/server/reference/sql-statements/geometry-constructors/point-properties.md): Learn about POINT properties in MariaDB Server. This section details SQL functions for retrieving attributes of point spatial objects, such as their X and Y coordinates.
- [X](/docs/server/reference/sql-statements/geometry-constructors/point-properties/point-properties-x.md): Synonym for ST\_X. Returns the X-coordinate value of a Point geometry as a double-precision number.
- [Y](/docs/server/reference/sql-statements/geometry-constructors/point-properties/point-properties-y.md): Synonym for ST\_Y. Returns the Y-coordinate value of a Point geometry as a double-precision number.
- [ST\_X](/docs/server/reference/sql-statements/geometry-constructors/point-properties/st_x.md): Returns the X-coordinate of a Point geometry. This function extracts the horizontal coordinate value as a double-precision number.
- [ST\_Y](/docs/server/reference/sql-statements/geometry-constructors/point-properties/st_y.md): Returns the Y-coordinate of a Point geometry. This function extracts the vertical coordinate value as a double-precision number.
- [Polygon Properties](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties.md): Learn about POLYGON properties in MariaDB Server. This section details SQL functions for retrieving attributes of polygonal spatial objects, such as area, perimeter, and the number of rings.
- [CENTROID](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/centroid.md): Synonym for ST\_CENTROID. Returns the mathematical centroid of the Polygon or MultiPolygon as a Point geometry.
- [AREA](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/polygon-properties-area.md): Synonym for ST\_AREA. Returns the double-precision area of the Polygon or MultiPolygon, calculated in its spatial reference system.
- [ExteriorRing](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/polygon-properties-exteriorring.md): Synonym for ST\_ExteriorRing. Returns the exterior ring of a Polygon as a LineString.
- [InteriorRingN](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/polygon-properties-interiorringn.md): Synonym for ST\_InteriorRingN. Returns the N-th interior ring of a Polygon as a LineString.
- [NumInteriorRings](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/polygon-properties-numinteriorrings.md): Synonym for ST\_NumInteriorRings. Returns the number of interior rings in a Polygon geometry.
- [ST\_AREA](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/st_area.md): Returns the area of a Polygon or MultiPolygon. The result is a double-precision number measured in the geometry's spatial reference units.
- [ST\_CENTROID](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/st_centroid.md): Returns the centroid of a Polygon or MultiPolygon. The result is a Point geometry representing the mathematical center of mass.
- [ST\_ExteriorRing](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/st_exteriorring.md): Returns the exterior ring of a Polygon. This function extracts the outer boundary of the polygon as a LineString geometry.
- [ST\_InteriorRingN](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/st_interiorringn.md): Returns the N-th interior ring of a Polygon. This function retrieves a specific inner hole of the polygon as a LineString.
- [ST\_NumInteriorRings](/docs/server/reference/sql-statements/geometry-constructors/polygon-properties/st_numinteriorrings.md): Returns the count of interior rings in a Polygon. This function calculates the total number of inner holes within the polygon.
- [WKB](/docs/server/reference/sql-statements/geometry-constructors/wkb.md): Learn about Well-Known Binary (WKB) in MariaDB Server. This section details how to represent and store geometric data in a binary format, essential for efficient spatial data exchange and storage.
- [AsBinary](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-asbinary.md): Synonym for ST\_AsBinary. Converts a geometry value from its internal format to its Well-Known Binary (WKB) representation.
- [AsWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/aswkb.md): Synonym for ST\_AsBinary. Converts a geometry value from its internal format to its Well-Known Binary (WKB) representation.
- [GeomCollFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-geomcollfromwkb.md): Synonym for ST\_GeomCollFromWKB. Constructs a GeometryCollection value from its WKB representation and an optional SRID.
- [GeometryCollectionFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/geometrycollectionfromwkb.md): Synonym for ST\_GeomCollFromWKB. Constructs a GeometryCollection value from its WKB representation and an optional SRID.
- [GeometryFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/geometryfromwkb.md): Synonym for ST\_GeomFromWKB. Constructs a geometry value of any type from its WKB representation and an optional SRID.
- [GeomFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-geomfromwkb.md): Synonym for ST\_GeomFromWKB. Constructs a geometry value of any type from its WKB representation and an optional SRID.
- [LineFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-linefromwkb.md): Synonym for ST\_LineFromWKB. Constructs a LineString value from its WKB representation and an optional SRID.
- [LineStringFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/linestringfromwkb.md): Synonym for ST\_LineFromWKB. Constructs a LineString value from its WKB representation and an optional SRID.
- [MLineFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/mlinefromwkb.md): Synonym for ST\_MultiLineStringFromWKB. Constructs a MultiLineString value from its WKB representation and an optional SRID.
- [MPointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/mpointfromwkb.md): Synonym for ST\_MultiPointFromWKB. Constructs a MultiPoint value from its WKB representation and an optional SRID.
- [MPolyFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/mpolyfromwkb.md): Synonym for ST\_MultiPolygonFromWKB. Constructs a MultiPolygon value from its WKB representation and an optional SRID.
- [MultiLineStringFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/multilinestringfromwkb.md): Synonym for ST\_MultiLineStringFromWKB. Constructs a MultiLineString value from its WKB representation and an optional SRID.
- [MultiPointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/multipointfromwkb.md): Synonym for ST\_MultiPointFromWKB. Constructs a MultiPoint value from its WKB representation and an optional SRID.
- [MultiPolygonFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/multipolygonfromwkb.md): Synonym for ST\_MultiPolygonFromWKB. Constructs a MultiPolygon value from its WKB representation and an optional SRID.
- [PointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-pointfromwkb.md): Synonym for ST\_PointFromWKB. Constructs a Point value from its WKB representation and an optional SRID.
- [PolyFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/wkb-polyfromwkb.md): Synonym for ST\_PolyFromWKB. Constructs a Polygon value from its WKB representation and an optional SRID.
- [PolygonFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/polygonfromwkb.md): Synonym for ST\_PolyFromWKB. Constructs a Polygon value from its WKB representation and an optional SRID.
- [ST\_AsBinary](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_asbinary.md): Converts a value in internal geometry format to its WKB representation and returns the binary result.
- [ST\_AsWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_aswkb.md): Synonym for ST\_AsBinary. Converts a geometry value from its internal format to its Well-Known Binary (WKB) representation.
- [ST\_GeomCollFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_geomcollfromwkb.md): Constructs a GeometryCollection value from its WKB representation and an optional SRID.
- [ST\_GeometryCollectionFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_geometrycollectionfromwkb.md): Synonym for ST\_GeomCollFromWKB. Constructs a GeometryCollection value from its WKB representation and an optional SRID.
- [ST\_GeometryFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_geometryfromwkb.md): Synonym for ST\_GeomFromWKB. Constructs a geometry value of any type from its WKB representation and an optional SRID.
- [ST\_GeomFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_geomfromwkb.md): Constructs a geometry value of any type using its WKB representation and an optional SRID.
- [ST\_LineFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_linefromwkb.md): Constructs a LineString value using its WKB representation and an optional SRID.
- [ST\_LineStringFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_linestringfromwkb.md): Synonym for ST\_LineFromWKB. Constructs a LineString value from its WKB representation and an optional SRID.
- [ST\_MPointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_mpointfromwkb.md): Synonym for ST\_MultiPointFromWKB. Constructs a MultiPoint value from its WKB representation and an optional SRID.
- [ST\_MPolyFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_mpolyfromwkb.md): Synonym for ST\_MultiPolygonFromWKB. Constructs a MultiPolygon value from its WKB representation and an optional SRID.
- [ST\_MultiPointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_multipointfromwkb.md): Constructs a MultiLineString value using its WKB representation and an optional SRID.
- [ST\_MultiPolygonFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_multipolygonfromwkb.md): Constructs a MultiPolygon value using its WKB representation and an optional SRID.
- [ST\_PointFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_pointfromwkb.md): Constructs a Point value using its WKB representation and an optional SRID.
- [ST\_PolyFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_polyfromwkb.md): Constructs a Polygon value using its WKB representation and an optional SRID.
- [ST\_PolygonFromWKB](/docs/server/reference/sql-statements/geometry-constructors/wkb/st_polygonfromwkb.md): Synonym for ST\_PolyFromWKB. Constructs a Polygon value from its WKB representation and an optional SRID.
- [Well-Known Binary (WKB) Format](/docs/server/reference/sql-statements/geometry-constructors/wkb/well-known-binary-wkb-format.md): Understand the standard binary format for geometry. This overview explains how WKB represents spatial data types for storage and exchange.
- [WKT](/docs/server/reference/sql-statements/geometry-constructors/wkt.md): Learn about Well-Known Text (WKT) in MariaDB Server. This section details how to represent and store geometric data in a text format, essential for human-readable spatial data exchange.
- [WKT Definition](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-definition.md): Understand the Well-Known Text (WKT) format. This section describes the standard ASCII representation for exchanging geometric data.
- [AsText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-astext.md): Synonym for ST\_AsText. Converts a geometry value from its internal format to its Well-Known Text (WKT) representation.
- [AsWKT](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-aswkt.md): Synonym for ST\_AsText. Converts a geometry value from its internal format to its Well-Known Text (WKT) representation.
- [GeomCollFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-geomcollfromtext.md): Synonym for ST\_GeomCollFromText. Constructs a GeometryCollection value from its WKT representation and an optional SRID.
- [GeometryCollectionFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/geometrycollectionfromtext.md): Synonym for ST\_GeomCollFromText. Constructs a GeometryCollection value from its WKT representation and an optional SRID.
- [GeometryFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/geometryfromtext.md): Synonym for ST\_GeomFromText. Constructs a geometry value of any type from its WKT representation and an optional SRID.
- [GeomFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-geomfromtext.md): Synonym for ST\_GeomFromText. Constructs a geometry value of any type from its WKT representation and an optional SRID.
- [LineFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-linefromtext.md): Synonym for ST\_LineFromText. Constructs a LineString value from its WKT representation and an optional SRID.
- [LineStringFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/linestringfromtext.md): Synonym for ST\_LineFromText. Constructs a LineString value from its WKT representation and an optional SRID.
- [MLineFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/mlinefromtext.md): Synonym for ST\_MultiLineStringFromText. Constructs a MultiLineString value from its WKT representation and an optional SRID.
- [MPointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/mpointfromtext.md): Synonym for ST\_MultiPointFromText. Constructs a MultiPoint value from its WKT representation and an optional SRID.
- [MPolyFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/mpolyfromtext.md): Synonym for ST\_MultiPolygonFromText. Constructs a MultiPolygon value from its WKT representation and an optional SRID.
- [MultiLineStringFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/multilinestringfromtext.md): Synonym for ST\_MultiLineStringFromText. Constructs a MultiLineString value from its WKT representation and an optional SRID.
- [MultiPointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/multipointfromtext.md): Synonym for ST\_MultiPointFromText. Constructs a MultiPoint value from its WKT representation and an optional SRID.
- [MultiPolygonFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/multipolygonfromtext.md): Synonym for ST\_MultiPolygonFromText. Constructs a MultiPolygon value from its WKT representation and an optional SRID.
- [PointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-pointfromtext.md): Synonym for ST\_PointFromText. Constructs a Point value from its WKT representation and an optional SRID.
- [PolyFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-polyfromtext.md): Synonym for ST\_PolyFromText. Constructs a Polygon value from its WKT representation and an optional SRID.
- [PolygonFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/polygonfromtext.md): Synonym for ST\_PolyFromText. Constructs a Polygon value from its WKT representation and an optional SRID.
- [ST\_AsText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_astext.md): Converts a value in internal geometry format to its WKT representation and returns the string result.
- [ST\_ASWKT](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_aswkt.md): Synonym for ST\_AsText. Converts a geometry value from its internal format to its Well-Known Text (WKT) representation.
- [ST\_GeomCollFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_geomcollfromtext.md): Constructs a GeometryCollection value from its WKB representation and an optional SRID.
- [ST\_GeometryCollectionFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_geometrycollectionfromtext.md): Synonym for ST\_GeomCollFromText. Constructs a GeometryCollection value from its WKT representation and an optional SRID.
- [ST\_GeometryFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_geometryfromtext.md): Synonym for ST\_GeomFromText. Constructs a geometry value of any type from its WKT representation and an optional SRID.
- [ST\_GeomFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_geomfromtext.md): Constructs a geometry value of any type using its WKT representation and an optional SRID.
- [ST\_LineFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_linefromtext.md): Constructs a LineString value using its WKT representation and an optional SRID.
- [ST\_LineStringFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_linestringfromtext.md): Synonym for ST\_LineFromText. Constructs a LineString value from its WKT representation and an optional SRID.
- [ST\_MPointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_mpointfromtext.md): Synonym for ST\_MultiLineStringFromText. Constructs a MultiLineString value from its WKT representation and an optional SRID.
- [ST\_MPolyFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_mpolyfromtext.md): Synonym for ST\_MultiPointFromText. Constructs a MultiPoint value from its WKT representation and an optional SRID.
- [ST\_MultiLineStringFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_multilinestringfromtext.md): Constructs a MultiLineString value using its WKT representation and an optional SRID.
- [ST\_MultiPointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_multipointfromtext.md): Constructs a MultiPoint value using its WKT representation and an optional SRID.
- [ST\_MultiPolygonFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_multipolygonfromtext.md): Constructs a MultiPolygon value using its WKT representation and an optional SRID.
- [ST\_PointFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_pointfromtext.md): Constructs a Point value using its WKT representation and an optional SRID.
- [ST\_PolyFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_polyfromtext.md): Constructs a Polygon value using its WKT representation and an optional SRID.
- [ST\_PolygonFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/st_polygonfromtext.md): Synonym for ST\_PolyFromText. Constructs a Polygon value from its WKT representation and an optional SRID.
- [ST\_MLineFromText](/docs/server/reference/sql-statements/geometry-constructors/wkt/wkt-st_mlinefromtext.md): Synonym for ST\_MultiLineStringFromText. Constructs a MultiLineString value from its WKT representation and an optional SRID.
- [Prepared Statements](/docs/server/reference/sql-statements/prepared-statements.md): Learn about prepared statements in MariaDB Server. This section details how to use them for efficient and secure execution of repetitive SQL queries, preventing SQL injection vulnerabilities.
- [DEALLOCATE / DROP PREPARE](/docs/server/reference/sql-statements/prepared-statements/deallocate-drop-prepare.md): Release a prepared statement to free resources. This command removes the statement definition and its name from the current session.
- [EXECUTE Statement](/docs/server/reference/sql-statements/prepared-statements/execute-statement.md): Run a previously prepared statement. This command executes the statement using the specified name, optionally supplying input parameters.
- [EXECUTE IMMEDIATE](/docs/server/reference/sql-statements/prepared-statements/execute-immediate.md): Prepare and run a dynamic SQL statement in one step. This command simplifies the process by combining the PREPARE and EXECUTE operations.
- [PREPARE Statement](/docs/server/reference/sql-statements/prepared-statements/prepare-statement.md): Parse and optimize a SQL statement for later use. This command assigns a name to the statement, enabling efficient execution with parameters.
- [Programmatic & Compound Statements](/docs/server/reference/sql-statements/programmatic-compound-statements.md): Explore programmatic compound statements in MariaDB Server. This section covers BEGIN...END blocks, loops, and conditional logic for writing complex stored routines and event definitions.
- [BEGIN END](/docs/server/reference/sql-statements/programmatic-compound-statements/begin-end.md): Group multiple SQL statements into a logical block. This construct defines a compound statement, creating a new scope for variables and exception handling.
- [CASE Statement](/docs/server/reference/sql-statements/programmatic-compound-statements/case-statement.md): Complete reference for CASE Statement in MariaDB. Complete syntax guide with all options, clauses, and practical examples with comprehensive examples and.
- [DECLARE CONDITION](/docs/server/reference/sql-statements/programmatic-compound-statements/declare-condition.md): Define named error conditions. This statement associates a name with a specific SQLSTATE or MariaDB error code for easier handling in stored programs.
- [DECLARE HANDLER](/docs/server/reference/sql-statements/programmatic-compound-statements/declare-handler.md): Specify actions for error conditions. This statement defines handler routines (CONTINUE or EXIT) to manage exceptions or warnings within a block.
- [DECLARE TYPE](/docs/server/reference/sql-statements/programmatic-compound-statements/declare-type.md): Define data types for Oracle compatibility. This statement allows declaring PL/SQL-style record types and associative arrays within stored procedures.
- [DECLARE Variable](/docs/server/reference/sql-statements/programmatic-compound-statements/declare-variable.md): Initialize local variables within a stored program. This statement defines variables with a specific data type and optional default value.
- [FOR](/docs/server/reference/sql-statements/programmatic-compound-statements/for.md): Loop through a range or cursor result set. This control flow statement repeatedly executes a block of code for each item in a specified range or query.
- [GOTO](/docs/server/reference/sql-statements/programmatic-compound-statements/goto.md): Jump to a labeled point in the code. This Oracle-compatible statement transfers execution control to a specific label within the stored program.
- [IF](/docs/server/reference/sql-statements/programmatic-compound-statements/if.md): Execute code based on conditions. This control flow statement runs different blocks of SQL statements depending on whether a specified condition is true.
- [ITERATE](/docs/server/reference/sql-statements/programmatic-compound-statements/iterate.md): Restart the current loop. This statement jumps back to the beginning of a LOOP, REPEAT, or WHILE block, skipping any remaining statements in the current iteration.
- [Labels](/docs/server/reference/sql-statements/programmatic-compound-statements/labels.md): Identify blocks and loops for flow control. Labels provide names for BEGIN...END blocks or loops, allowing them to be targeted by LEAVE, ITERATE, or GOTO statements.
- [LEAVE](/docs/server/reference/sql-statements/programmatic-compound-statements/leave.md): Exit a labeled block or loop immediately. This statement terminates the execution of the current loop or compound statement and continues after the block.
- [LOOP](/docs/server/reference/sql-statements/programmatic-compound-statements/loop.md): Create a simple loop construct. This statement repeatedly executes a block of code until explicitly terminated by a LEAVE statement.
- [REPEAT LOOP](/docs/server/reference/sql-statements/programmatic-compound-statements/repeat-loop.md): Execute a block until a condition is met. This loop construct runs at least once and continues repeating as long as the UNTIL condition remains false.
- [RESIGNAL](/docs/server/reference/sql-statements/programmatic-compound-statements/resignal.md): Propagate error conditions. This statement allows a handler to pass an error condition back to the caller or modify the error information before passing it on.
- [RETURN](/docs/server/reference/sql-statements/programmatic-compound-statements/return.md): Exit a stored function and return a value. This statement terminates function execution and sends the specified result back to the caller.
- [SELECT INTO](/docs/server/reference/sql-statements/programmatic-compound-statements/selectinto.md): Assign query results to variables. This statement retrieves column values from a single row and stores them in local variables or user-defined variables.
- [SIGNAL](/docs/server/reference/sql-statements/programmatic-compound-statements/signal.md): Raise a custom error condition. This statement allows stored programs to generate specific error messages and SQLSTATEs to handle application logic exceptions.
- [WHILE](/docs/server/reference/sql-statements/programmatic-compound-statements/while.md): Execute a block while a condition is true. This loop construct checks a condition before each iteration and repeats the block as long as the condition holds.
- [Using Compound Statements Outside of Stored Programs](/docs/server/reference/sql-statements/programmatic-compound-statements/using-compound-statements-outside-of-stored-programs.md)
- [Cursors](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors.md): Learn about cursors in MariaDB Server's programmatic compound statements. This section details how to iterate over result sets row-by-row within stored procedures and functions.
- [Cursor Overview](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors/cursor-overview.md)
- [CLOSE](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors/close.md)
- [DECLARE CURSOR](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors/declare-cursor.md)
- [FETCH](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors/fetch.md)
- [OPEN](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-cursors/open.md)
- [Diagnostics](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-diagnostics.md): Learn about diagnostics in programmatic compound statements. This section covers error handling and information retrieval within stored procedures and functions for effective debugging.
- [Diagnostics Area](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-diagnostics/diagnostics-area.md)
- [GET DIAGNOSTICS](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-diagnostics/get-diagnostics.md)
- [SQLSTATE](/docs/server/reference/sql-statements/programmatic-compound-statements/programmatic-compound-statements-diagnostics/sqlstate.md)
- [Stored Routine Statements](/docs/server/reference/sql-statements/stored-routine-statements.md): This section covers SQL commands for creating, altering, and dropping stored procedures and functions, essential for programmatic database logic.
- [CALL](/docs/server/reference/sql-statements/stored-routine-statements/call.md): Invoke a stored procedure. This statement executes a previously created stored procedure, optionally passing parameters and returning results.
- [DO](/docs/server/reference/sql-statements/stored-routine-statements/do.md): Execute expressions without returning a result set. This statement runs functions or expressions, often used for side effects like releasing locks.
- [Table Statements](/docs/server/reference/sql-statements/table-statements.md): Learn about table-related SQL statements in MariaDB Server. This section covers commands for creating, altering, dropping, and manipulating tables, essential for managing your database schema.
- [ANALYZE TABLE](/docs/server/reference/sql-statements/table-statements/analyze-table.md): Analyze and store key distribution. This statement updates index statistics used by the optimizer to choose the best execution plan.
- [CHECK TABLE](/docs/server/reference/sql-statements/table-statements/check-table.md): Check tables or views for errors. This statement verifies the integrity of table structure and data for supported storage engines.
- [CHECK VIEW](/docs/server/reference/sql-statements/table-statements/check-view.md): Verify the validity of a view's algorithm. This statement checks if the view definition is correct and references existing tables.
- [CHECKSUM TABLE](/docs/server/reference/sql-statements/table-statements/checksum-table.md): Report a checksum for table contents. This statement calculates a value to compare tables, useful for verifying replication consistency.
- [REPAIR TABLE](/docs/server/reference/sql-statements/table-statements/repair-table.md): Repair corrupted tables. This statement fixes errors in tables for supported storage engines like MyISAM, Aria, and Archive.
- [REPAIR VIEW](/docs/server/reference/sql-statements/table-statements/repair-view.md): Check and correct a view's algorithm. This statement is primarily used by upgrade scripts to ensure view definitions are compatible.
- [TRUNCATE TABLE](/docs/server/reference/sql-statements/table-statements/truncate-table.md): Complete TRUNCATE TABLE reference: TRUNCATE \[TABLE] tbl\_name \[WAIT n|NOWAIT] syntax, InnoDB FOREIGN KEY constraints, implicit commit, and AUTO\_INCREMENT reset.
- [Obsolete Table Statements](/docs/server/reference/sql-statements/table-statements/obsolete-table-commands.md): Browse documentation for removed table commands. This section covers obsolete statements like BACKUP TABLE and RESTORE TABLE.
- [BACKUP TABLE (removed)](/docs/server/reference/sql-statements/table-statements/obsolete-table-commands/backup-table-removed.md)
- [RESTORE TABLE (removed)](/docs/server/reference/sql-statements/table-statements/obsolete-table-commands/restore-table-removed.md)
- [Transactions](/docs/server/reference/sql-statements/transactions.md): Learn about transactions in MariaDB Server. This section covers SQL statements for managing atomic operations (START TRANSACTION, COMMIT, ROLLBACK), ensuring data integrity and consistency.
- [COMMIT](/docs/server/reference/sql-statements/transactions/commit.md): Commit the current transaction. This statement permanently saves all changes made during the current transaction to the database.
- [LOCK TABLES](/docs/server/reference/sql-statements/transactions/lock-tables.md): Complete LOCK TABLES reference: READ/WRITE/WRITE CONCURRENT lock syntax, table aliases, WAIT n|NOWAIT timeouts, UNLOCK TABLES, and innodb\_table\_locks behavior.
- [Metadata Locking](/docs/server/reference/sql-statements/transactions/metadata-locking.md): Understand how MariaDB manages concurrency. Metadata locks protect the structure of database objects from being modified while they are in use.
- [READ COMMITTED](/docs/server/reference/sql-statements/transactions/transactions-read-committed.md): Set the transaction isolation level to READ COMMITTED. In this mode, each query within a transaction sees only data committed before the query began.
- [READ UNCOMMITTED](/docs/server/reference/sql-statements/transactions/transactions-read-uncommitted.md): Set the transaction isolation level to READ UNCOMMITTED. This lowest isolation level allows dirty reads, where a transaction can see uncommitted changes.
- [REPEATABLE READ](/docs/server/reference/sql-statements/transactions/transactions-repeatable-read.md): Set the transaction isolation level to REPEATABLE READ. This default InnoDB level ensures consistent results for repeated reads within the same transaction.
- [ROLLBACK](/docs/server/reference/sql-statements/transactions/rollback.md): Undo changes in the current transaction. This statement reverts the database to its state before the transaction started or to a specific savepoint.
- [SAVEPOINT](/docs/server/reference/sql-statements/transactions/savepoint.md): Create a named marker within a transaction. Savepoints allow you to roll back part of a transaction without canceling the entire operation.
- [SERIALIZABLE](/docs/server/reference/sql-statements/transactions/transactions-serializable.md): Set the transaction isolation level to SERIALIZABLE. This highest level ensures total isolation by converting plain SELECTs to locking reads.
- [SQL statements Causing an Implicit Commit](/docs/server/reference/sql-statements/transactions/sql-statements-that-cause-an-implicit-commit.md): Identify statements that force a commit. Certain commands, like DDL statements, implicitly commit the current transaction before executing.
- [START TRANSACTION](/docs/server/reference/sql-statements/transactions/start-transaction.md): Complete START TRANSACTION reference: BEGIN/COMMIT/ROLLBACK syntax, WITH CONSISTENT SNAPSHOT option, READ ONLY/WRITE modes, AND \[NO] CHAIN/RELEASE modifiers.
- [Transaction Timeouts](/docs/server/reference/sql-statements/transactions/transaction-timeouts.md): Understand how timeouts affect transactions. This section explains system variables that control wait times for locks and transaction duration.
- [UNLOCK TABLES](/docs/server/reference/sql-statements/transactions/transactions-unlock-tables.md): Release explicit table locks. This statement releases all locks acquired by the current session with LOCK TABLES.
- [WAIT and NOWAIT](/docs/server/reference/sql-statements/transactions/wait-and-nowait.md): Control lock wait behavior. These clauses allow statements to wait for a specific timeout or fail immediately if a lock cannot be acquired.
- [XA Transactions](/docs/server/reference/sql-statements/transactions/xa-transactions.md): Manage distributed transactions. This section covers XA statements for coordinating two-phase commits across multiple resources.
- [SQL Functions](/docs/server/reference/sql-functions.md): Discover functions and procedures in MariaDB.
- [Functions & Operators](/docs/server/reference/sql-functions/function-and-operator-reference.md): Comprehensive reference of all SQL functions and operators. This index lists built-in functions for string manipulation, math, date/time, and more.
- [Aggregate Functions](/docs/server/reference/sql-functions/aggregate-functions.md): Perform calculations on multiple rows to return a single value. Includes standard SQL functions like SUM, AVG, COUNT, MIN, and MAX, often used with GROUP BY.
- [AVG](/docs/server/reference/sql-functions/aggregate-functions/avg.md): Calculate the average value. This function computes the arithmetic mean of a numeric expression, ignoring NULL values.
- [BIT\_AND](/docs/server/reference/sql-functions/aggregate-functions/bit_and.md): Perform a bitwise AND operation. This function returns the result of performing a bitwise AND on all values in a given expression.
- [BIT\_OR](/docs/server/reference/sql-functions/aggregate-functions/bit_or.md): Perform a bitwise OR operation. This function returns the result of performing a bitwise OR on all values in a given expression.
- [BIT\_XOR](/docs/server/reference/sql-functions/aggregate-functions/bit_xor.md): Perform a bitwise XOR operation. This function returns the result of performing a bitwise XOR on all values in a given expression.
- [COUNT DISTINCT](/docs/server/reference/sql-functions/aggregate-functions/count-distinct.md): Count unique values. This function returns the number of distinct, non-NULL values found in the specified column or expression.
- [COUNT](/docs/server/reference/sql-functions/aggregate-functions/count.md): Complete COUNT() function reference: COUNT(\*) and COUNT(expr) syntax, COUNT(DISTINCT) usage, GROUP BY aggregation, and OVER(PARTITION BY) window syntax.
- [GROUP\_CONCAT](/docs/server/reference/sql-functions/aggregate-functions/group_concat.md): Complete GROUP\_CONCAT reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples for production use.
- [JSON\_ARRAYAGG](/docs/server/reference/sql-functions/aggregate-functions/json_arrayagg.md): Aggregate values into a JSON array. This function aggregates a result set column into a single JSON array.
- [JSON\_OBJECTAGG](/docs/server/reference/sql-functions/aggregate-functions/json_objectagg.md): Aggregate key-value pairs into a JSON object. This function aggregates two columns or expressions into a single JSON object.
- [MAX](/docs/server/reference/sql-functions/aggregate-functions/max.md): Find the maximum value. This function returns the highest value in a set of values, applicable to numbers, strings, and dates.
- [MIN](/docs/server/reference/sql-functions/aggregate-functions/min.md): Find the minimum value. This function returns the lowest value in a set of values, applicable to numbers, strings, and dates.
- [STD](/docs/server/reference/sql-functions/aggregate-functions/std.md): Calculate population standard deviation. This function returns the square root of the population variance. It is a synonym for STDDEV\_POP().
- [STDDEV](/docs/server/reference/sql-functions/aggregate-functions/stddev.md): Calculate population standard deviation. This function is a synonym for STD() and STDDEV\_POP(), returning the square root of the population variance.
- [STDDEV\_POP](/docs/server/reference/sql-functions/aggregate-functions/stddev_pop.md): Calculate population standard deviation. This function computes the standard deviation assuming the set of values represents the entire population.
- [STDDEV\_SAMP](/docs/server/reference/sql-functions/aggregate-functions/stddev_samp.md): Calculate sample standard deviation. This function computes the standard deviation assuming the set of values represents a sample of the population.
- [SUM](/docs/server/reference/sql-functions/aggregate-functions/sum.md): Calculate the total sum. This function returns the sum of all values in a numeric expression, ignoring NULL values.
- [VAR\_POP](/docs/server/reference/sql-functions/aggregate-functions/var_pop.md): Calculate population variance. This function computes the statistical variance for a set of values assumed to be the entire population.
- [VAR\_SAMP](/docs/server/reference/sql-functions/aggregate-functions/var_samp.md): Calculate sample variance. This function computes the statistical variance for a set of values assumed to be a sample of the population.
- [VARIANCE](/docs/server/reference/sql-functions/aggregate-functions/variance.md): Calculate population variance. This function is a synonym for VAR\_POP() and returns the variance of a set of values.
- [Control Flow Functions](/docs/server/reference/sql-functions/control-flow-functions.md): Learn about control flow functions in MariaDB Server. This section details SQL functions like IF, CASE, and NULLIF, which enable conditional logic within your queries and stored routines.
- [CASE OPERATOR](/docs/server/reference/sql-functions/control-flow-functions/case-operator.md): Implement conditional logic in SQL queries. This operator evaluates conditions and returns a specific value when the first true condition is met.
- [DECODE\_ORACLE](/docs/server/reference/sql-functions/control-flow-functions/decode_oracle.md): Compare a value against a list of conditions. This Oracle-compatible function returns a corresponding result when a match is found, or a default value otherwise.
- [IF Function](/docs/server/reference/sql-functions/control-flow-functions/if-function.md): Complete IF() function reference: IF(expr1,expr2,expr3) conditional syntax, TRUE/NULL evaluation rules, return type context (numeric/string), and examples.
- [IFNULL](/docs/server/reference/sql-functions/control-flow-functions/ifnull.md): Replace NULL values with a fallback. This function returns the first argument if it's not NULL; otherwise, it returns the specified replacement value.
- [NULLIF](/docs/server/reference/sql-functions/control-flow-functions/nullif.md): Compare two expressions and return NULL if they are equal. If the expressions differ, the function returns the first expression.
- [NVL](/docs/server/reference/sql-functions/control-flow-functions/nvl.md): Synonym for IFNULL. This Oracle-compatible function returns the first argument if it is not NULL, or the second argument if the first is NULL.
- [NVL2](/docs/server/reference/sql-functions/control-flow-functions/nvl2.md): Return values based on NULL status. This function returns the second argument if the first is not NULL, and the third argument if the first is NULL.
- [Date & Time Functions](/docs/server/reference/sql-functions/date-time-functions.md): Complete MariaDB date and time functions guide. Complete reference for formatting, calculations, conversions, time zones, and operations for production use.
- [Date and Time Units](/docs/server/reference/sql-functions/date-time-functions/date-and-time-units.md): Reference keywords for date arithmetic. These units, such as DAY, HOUR, and MINUTE, specify the interval type used in functions like DATE\_ADD and EXTRACT.
- [ADD\_MONTHS](/docs/server/reference/sql-functions/date-time-functions/add_months.md): Add a specific number of months to a date. This Oracle-compatible function simplifies date calculations involving monthly intervals.
- [ADDDATE](/docs/server/reference/sql-functions/date-time-functions/adddate.md): Add a time interval to a date. This function performs date arithmetic, adding a specified value like days or hours to a starting date.
- [ADDTIME](/docs/server/reference/sql-functions/date-time-functions/addtime.md): Add a time value to a date or time expression. This function sums two time arguments, returning a new time or datetime result.
- [CONVERT\_TZ](/docs/server/reference/sql-functions/date-time-functions/convert_tz.md): Convert a datetime value between time zones. This function shifts a timestamp from a source time zone to a target time zone.
- [CURDATE](/docs/server/reference/sql-functions/date-time-functions/curdate.md): Return the current date. This function outputs today's date as a value in 'YYYY-MM-DD' or YYYYMMDD format, depending on the context.
- [CURRENT\_DATE](/docs/server/reference/sql-functions/date-time-functions/current_date.md): Synonym for CURDATE(). Returns the current date as a value in 'YYYY-MM-DD' or YYYYMMDD format.
- [CURRENT\_TIME](/docs/server/reference/sql-functions/date-time-functions/current_time.md): Synonym for CURTIME(). Returns the current time as a value in 'HH:MM:SS' or HHMMSS format.
- [CURRENT\_TIMESTAMP](/docs/server/reference/sql-functions/date-time-functions/current_timestamp.md): Synonym for NOW(). Returns the current date and time as a value in 'YYYY-MM-DD HH:MM:SS' or YYYYMMDDHHMMSS format.
- [CURTIME](/docs/server/reference/sql-functions/date-time-functions/curtime.md): Return the current time. This function outputs the current time of day as a value in 'HH:MM:SS' or HHMMSS format.
- [DATE FUNCTION](/docs/server/reference/sql-functions/date-time-functions/date-function.md): Extract the date part from a datetime expression. This function returns the year, month, and day portions, discarding the time component.
- [DATE\_ADD](/docs/server/reference/sql-functions/date-time-functions/date_add.md): Complete DATE\_ADD() reference: DATE\_ADD(date, INTERVAL expr unit) syntax, negative interval support, unit keywords (DAY/MONTH/YEAR), and return types.
- [DATE\_FORMAT](/docs/server/reference/sql-functions/date-time-functions/date_format.md): Complete DATE\_FORMAT reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples with comprehensive examples.
- [DATE\_SUB](/docs/server/reference/sql-functions/date-time-functions/date_sub.md): Subtract a time interval from a date. This function calculates a past date by subtracting a specified unit, such as days, from a starting value.
- [DATEDIFF](/docs/server/reference/sql-functions/date-time-functions/datediff.md): Complete DATEDIFF() reference: DATEDIFF(expr1,expr2) syntax, date vs datetime expression handling, time component ignore, and positive/negative results.
- [DAY](/docs/server/reference/sql-functions/date-time-functions/day.md): Synonym for DAYOFMONTH(). Returns the day of the month (1-31) for a given date.
- [DAYNAME](/docs/server/reference/sql-functions/date-time-functions/dayname.md): Return the name of the weekday. This function returns the full name of the day, such as 'Monday' or 'Sunday', for a given date.
- [DAYOFMONTH](/docs/server/reference/sql-functions/date-time-functions/dayofmonth.md): Return the day of the month. This function extracts the day portion of a date, returning a number from 1 to 31.
- [DAYOFWEEK](/docs/server/reference/sql-functions/date-time-functions/dayofweek.md): Return the weekday index. This function returns a number from 1 (Sunday) to 7 (Saturday) representing the day of the week.
- [DAYOFYEAR](/docs/server/reference/sql-functions/date-time-functions/dayofyear.md): Return the day of the year. This function returns a number from 1 to 366 indicating the day's position within the year.
- [EXTRACT](/docs/server/reference/sql-functions/date-time-functions/extract.md): Extract a specific part of a date. This function retrieves components like YEAR, MONTH, DAY, or HOUR from a date or datetime expression.
- [FORMAT\_PICO\_TIME](/docs/server/reference/sql-functions/date-time-functions/format_pico_time.md): Format a time in picoseconds. This function converts a numeric picosecond value into a human-readable string with units like ps, ns, us, ms, s, m, h, or d.
- [FROM\_DAYS](/docs/server/reference/sql-functions/date-time-functions/from_days.md): Convert a day number to a date. This function returns a DATE value corresponding to the number of days since year 0.
- [FROM\_UNIXTIME](/docs/server/reference/sql-functions/date-time-functions/from_unixtime.md): Convert a Unix timestamp to a datetime. This function formats a Unix timestamp as a date string or number in the current time zone.
- [GET\_FORMAT](/docs/server/reference/sql-functions/date-time-functions/get_format.md): Return a format string. This function provides standard format strings for DATE\_FORMAT and STR\_TO\_DATE based on regions like 'USA' or 'EUR'.
- [HOUR](/docs/server/reference/sql-functions/date-time-functions/hour.md): Extract the hour. This function returns the hour portion of a time or datetime value as a number from 0 to 23.
- [LAST\_DAY](/docs/server/reference/sql-functions/date-time-functions/last_day.md): Return the last day of the month. This function calculates the date of the final day for the month containing the given date.
- [LOCALTIME](/docs/server/reference/sql-functions/date-time-functions/localtime.md): Synonym for NOW(). Returns the current date and time in the session time zone.
- [LOCALTIMESTAMP](/docs/server/reference/sql-functions/date-time-functions/localtimestamp.md): Synonym for NOW(). Returns the current date and time in the session time zone as a datetime value.
- [MAKEDATE](/docs/server/reference/sql-functions/date-time-functions/makedate.md): Create a date from a year and day of year. This function constructs a DATE value given a year and the day number within that year.
- [MAKETIME](/docs/server/reference/sql-functions/date-time-functions/maketime.md): Create a time from hour, minute, and second. This function constructs a TIME value from three numeric arguments.
- [MICROSECOND](/docs/server/reference/sql-functions/date-time-functions/microsecond.md): Extract microseconds. This function returns the microsecond part of a time or datetime expression as a number from 0 to 999999.
- [Microseconds in MariaDB](/docs/server/reference/sql-functions/date-time-functions/microseconds-in-mariadb.md): Understand microsecond precision. This concept page explains how MariaDB stores and handles fractional seconds in time data types.
- [MINUTE](/docs/server/reference/sql-functions/date-time-functions/minute.md): Extract the minute. This function returns the minute portion of a time or datetime value as a number from 0 to 59.
- [MONTH](/docs/server/reference/sql-functions/date-time-functions/month.md): Extract the month. This function returns the month portion of a date as a number from 1 (January) to 12 (December).
- [MONTHNAME](/docs/server/reference/sql-functions/date-time-functions/monthname.md): Return the name of the month. This function returns the full name of the month, such as 'January' or 'December', for a given date.
- [MONTHS\_BETWEEN](/docs/server/reference/sql-functions/date-time-functions/months_between.md): Calculate the difference between two months.
- [NOW](/docs/server/reference/sql-functions/date-time-functions/now.md): Complete NOW() function reference: NOW(\[precision]) and CURRENT\_TIMESTAMP synonyms, TIMESTAMP vs DATETIME types, timezone/DST handling, and fractional seconds.
- [PERIOD\_ADD](/docs/server/reference/sql-functions/date-time-functions/period_add.md): Add months to a period. This function adds a specified number of months to a period formatted as YYMM or YYYYMM.
- [PERIOD\_DIFF](/docs/server/reference/sql-functions/date-time-functions/period_diff.md): Calculate the difference between periods. This function returns the number of months between two periods formatted as YYMM or YYYYMM.
- [QUARTER](/docs/server/reference/sql-functions/date-time-functions/quarter.md): Return the quarter of the year. This function returns a number from 1 to 4 indicating the quarter for a given date.
- [SEC\_TO\_TIME](/docs/server/reference/sql-functions/date-time-functions/sec_to_time.md): Convert seconds to time. This function returns a TIME value corresponding to the number of seconds elapsed from the start of the day.
- [SECOND](/docs/server/reference/sql-functions/date-time-functions/second.md): Extract the second. This function returns the second portion of a time or datetime value as a number from 0 to 59.
- [STR\_TO\_DATE](/docs/server/reference/sql-functions/date-time-functions/str_to_date.md): Complete STR\_TO\_DATE() reference: parse strings to DATE/TIME/DATETIME, format specifiers (%Y %m %d %H %i %s), invalid input handling, and SQL\_MODE errors.
- [SUBDATE](/docs/server/reference/sql-functions/date-time-functions/subdate.md): Subtract a time interval from a date. This synonym for DATE\_SUB calculates a past date by subtracting a specified unit from a starting value.
- [SUBTIME](/docs/server/reference/sql-functions/date-time-functions/subtime.md): Subtract a time value. This function subtracts one time or datetime expression from another and returns the result.
- [SYSDATE](/docs/server/reference/sql-functions/date-time-functions/sysdate.md): Return the time of execution. Unlike NOW(), which returns the start time of the statement, SYSDATE() returns the time it executes.
- [TIME](/docs/server/reference/sql-functions/date-time-functions/time-function.md): Extract the time portion. This function returns the time part of a time or datetime expression.
- [TIME\_FORMAT](/docs/server/reference/sql-functions/date-time-functions/time_format.md): Format a time. This function formats a time value according to a format string, similar to DATE\_FORMAT but for time values.
- [TIME\_TO\_SEC](/docs/server/reference/sql-functions/date-time-functions/time_to_sec.md)
- [TIMEDIFF](/docs/server/reference/sql-functions/date-time-functions/timediff.md): Subtract two time values. This function calculates the difference between two time or datetime expressions.
- [TIMESTAMP](/docs/server/reference/sql-functions/date-time-functions/timestamp-function.md): Convert to datetime or add time. With one argument, it returns a datetime; with two, it adds a time expression to a date or datetime.
- [TIMESTAMPADD](/docs/server/reference/sql-functions/date-time-functions/timestampadd.md): Add an interval to a timestamp. This function adds a specified integer number of units (like MONTH or SECOND) to a datetime expression.
- [TIMESTAMPDIFF](/docs/server/reference/sql-functions/date-time-functions/timestampdiff.md): Calculate the difference between timestamps. This function returns the difference between two datetime expressions in the specified unit.
- [TO\_DATE](/docs/server/reference/sql-functions/date-time-functions/to_date.md)
- [TO\_DAYS](/docs/server/reference/sql-functions/date-time-functions/to_days.md): Convert a date to a day number. This function returns the number of days between year 0 and the given date.
- [TO\_SECONDS](/docs/server/reference/sql-functions/date-time-functions/to_seconds.md): Convert a date to seconds. This function returns the number of seconds from year 0 to the given date or datetime.
- [TRUNC](/docs/server/reference/sql-functions/date-time-functions/trunc.md): Truncate a date. In Oracle mode, this function truncates a date value to a specified unit of measure.
- [UNIX\_TIMESTAMP](/docs/server/reference/sql-functions/date-time-functions/unix_timestamp.md): Return a Unix timestamp. This function returns the number of seconds since the Unix Epoch ('1970-01-01 00:00:00' UTC).
- [UTC\_DATE](/docs/server/reference/sql-functions/date-time-functions/utc_date.md): Return the current UTC date. This function returns the current Coordinated Universal Time date in 'YYYY-MM-DD' or YYYYMMDD format.
- [UTC\_TIME](/docs/server/reference/sql-functions/date-time-functions/utc_time.md): Return the current UTC time. This function returns the current Coordinated Universal Time in 'HH:MM:SS' or HHMMSS format.
- [UTC\_TIMESTAMP](/docs/server/reference/sql-functions/date-time-functions/utc_timestamp.md): Return the current UTC timestamp. This function returns the current Coordinated Universal Time date and time.
- [WEEK](/docs/server/reference/sql-functions/date-time-functions/week.md): Return the week number. This function returns the week number for a date, with an optional mode to define the start of the week.
- [WEEKDAY](/docs/server/reference/sql-functions/date-time-functions/weekday.md): Return the weekday index. This function returns the index of the day of the week (0=Monday, 6=Sunday).
- [WEEKOFYEAR](/docs/server/reference/sql-functions/date-time-functions/weekofyear.md): Return the calendar week. This function returns the week number of the date (1-53), equivalent to WEEK(date, 3).
- [YEAR](/docs/server/reference/sql-functions/date-time-functions/year.md): Extract the year. This function returns the year portion of a date as a number from 1000 to 9999.
- [YEARWEEK](/docs/server/reference/sql-functions/date-time-functions/yearweek.md): Return the year and week. This function returns the year and week number for a date, useful for grouping results by week.
- [Numeric Functions](/docs/server/reference/sql-functions/numeric-functions.md): Learn about numeric functions in MariaDB Server. This section details SQL functions for performing mathematical calculations, rounding, and manipulating numeric values in your queries.
- [ABS](/docs/server/reference/sql-functions/numeric-functions/abs.md): Calculate absolute value. This function returns the non-negative value of a number, removing any negative sign.
- [ACOS](/docs/server/reference/sql-functions/numeric-functions/acos.md): Calculate arc cosine. This function returns the angle in radians whose cosine is the given number.
- [ASIN](/docs/server/reference/sql-functions/numeric-functions/asin.md): Calculate arc cosine. This function returns the angle in radians whose cosine is the given number.
- [ATAN](/docs/server/reference/sql-functions/numeric-functions/atan.md): Calculate arc tangent. This function returns the angle in radians whose tangent is the given number.
- [ATAN2](/docs/server/reference/sql-functions/numeric-functions/atan2.md): Calculate arc tangent of two variables. This function returns the angle in radians between the positive x-axis and the point (X, Y).
- [CEIL](/docs/server/reference/sql-functions/numeric-functions/ceil.md): Synonym for CEILING(). Rounds a number up to the nearest integer.
- [CEILING](/docs/server/reference/sql-functions/numeric-functions/ceiling.md): Round up to the nearest integer. This function returns the smallest integer value that is greater than or equal to the argument.
- [CONV](/docs/server/reference/sql-functions/numeric-functions/conv.md): Convert numbers between bases. This function transforms a number from one numeric base system to another.
- [COS](/docs/server/reference/sql-functions/numeric-functions/cos.md): Calculate cosine. This function returns the cosine of an angle given in radians.
- [COT](/docs/server/reference/sql-functions/numeric-functions/cot.md): Calculate cotangent. This function returns the cotangent of an angle given in radians.
- [CRC32](/docs/server/reference/sql-functions/numeric-functions/crc32.md): Compute cyclic redundancy check. This function returns a 32-bit unsigned integer representing the CRC32 checksum of a string.
- [CRC32C](/docs/server/reference/sql-functions/numeric-functions/crc32c.md): Compute CRC32C checksum. This function calculates a cyclic redundancy check value using the Castagnoli polynomial.
- [DEGREES](/docs/server/reference/sql-functions/numeric-functions/degrees.md): Convert radians to degrees. This function transforms an angle measured in radians to its equivalent in degrees.
- [DIV](/docs/server/reference/sql-functions/numeric-functions/div.md): Perform integer division. This operator divides one number by another and returns the integer result, discarding any remainder.
- [EXP](/docs/server/reference/sql-functions/numeric-functions/exp.md): Calculate exponential value. This function returns the value of e (the base of natural logarithms) raised to the power of the argument.
- [FLOOR](/docs/server/reference/sql-functions/numeric-functions/floor.md): Round down to the nearest integer. This function returns the largest integer value that is less than or equal to the argument.
- [LN](/docs/server/reference/sql-functions/numeric-functions/ln.md): Calculate natural logarithm. This function returns the logarithm of a number to the base e.
- [LOG](/docs/server/reference/sql-functions/numeric-functions/log.md): Calculate logarithm. This function returns the natural logarithm of a number, or the logarithm to a specified base if two arguments are provided.
- [LOG10](/docs/server/reference/sql-functions/numeric-functions/log10.md): Calculate base-10 logarithm. This function returns the logarithm of a number to the base 10.
- [LOG2](/docs/server/reference/sql-functions/numeric-functions/log2.md): Calculate base-2 logarithm. This function returns the logarithm of a number to the base 2.
- [MOD](/docs/server/reference/sql-functions/numeric-functions/mod.md): Calculate modulo. This function returns the remainder of a number divided by another number.
- [OCT](/docs/server/reference/sql-functions/numeric-functions/oct.md): Convert to octal. This function returns the octal string representation of a numeric argument.
- [PI](/docs/server/reference/sql-functions/numeric-functions/pi.md): Return the value of pi. This function returns the mathematical constant π (approximately 3.141593).
- [POW](/docs/server/reference/sql-functions/numeric-functions/pow.md): Synonym for POWER(). Returns the value of a number raised to the power of another number.
- [POWER](/docs/server/reference/sql-functions/numeric-functions/power.md): Calculate power. This function returns the value of a number raised to the specified exponent.
- [RADIANS](/docs/server/reference/sql-functions/numeric-functions/radians.md): Convert degrees to radians. This function transforms an angle measured in degrees to its equivalent in radians.
- [RAND](/docs/server/reference/sql-functions/numeric-functions/rand.md): Generate a random number. This function returns a random floating-point value between 0 and 1.
- [ROUND](/docs/server/reference/sql-functions/numeric-functions/round.md): Round a number. This function rounds a number to a specified number of decimal places.
- [SIGN](/docs/server/reference/sql-functions/numeric-functions/sign.md): Return the sign of a number. This function returns -1, 0, or 1 depending on whether the argument is negative, zero, or positive.
- [SIN](/docs/server/reference/sql-functions/numeric-functions/sin.md): Calculate sine. This function returns the sine of an angle given in radians.
- [SQRT](/docs/server/reference/sql-functions/numeric-functions/sqrt.md): Calculate square root. This function returns the non-negative square root of a number.
- [TAN](/docs/server/reference/sql-functions/numeric-functions/tan.md): Calculate tangent. This function returns the tangent of an angle given in radians.
- [TO\_NUMBER](/docs/server/reference/sql-functions/numeric-functions/to_number.md): Convert a string to a number. This Oracle-compatible function parses a string using a specified format and returns a numeric value.
- [TRUNCATE](/docs/server/reference/sql-functions/numeric-functions/truncate.md): Truncate a number. This function truncates a number to a specified number of decimal places.
- [Pseudo Columns](/docs/server/reference/sql-functions/pseudo-columns.md): MariaDB has pseudo columns that can be used for different purposes.
- [\_rowid](/docs/server/reference/sql-functions/pseudo-columns/_rowid.md): Access the unique row identifier. This pseudo column often aliases the primary key, allowing direct row access even if the primary key column name is unknown.
- [Secondary Functions](/docs/server/reference/sql-functions/secondary-functions.md): Explore secondary functions in MariaDB Server. This section details various SQL functions that support specialized operations, enhancing data manipulation and analysis beyond core functionalities.
- [Bit Functions and Operators](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators.md): Perform bitwise logic and manipulation. This section covers operators like AND, OR, XOR, and functions for shifting bits or counting set bits in binary data.
- [BIT\_COUNT](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/bit_count.md): Count the set bits. This function returns the number of bits that are set to 1 in the binary representation of a number.
- [~](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/bitwise-not.md): Invert all bits. This unary operator flips every bit in the operand, changing 1s to 0s and 0s to 1s.
- [|](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/bitwise-or.md): Perform bitwise OR. This operator compares bits and returns 1 if at least one of the corresponding bits is 1.
- [^](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/bitwise-xor.md): Perform bitwise exclusive OR. This operator returns 1 only if the corresponding bits of the operands are different.
- [&](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/bitwise_and.md): Perform bitwise AND. This operator compares bits of two operands and returns 1 only if both corresponding bits are 1.
- [Parentheses](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/parentheses.md): Control operator precedence. Parentheses are used to group expressions and enforce the order of evaluation in complex operations.
- [<<](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/shift-left.md): Shift bits to the left. This operator shifts the binary representation of a number to the left by a specified number of positions, filling with zeros.
- [>>](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/shift-right.md): Shift bits to the right. This operator shifts the binary representation of a number to the right by a specified number of positions.
- [TRUE FALSE](/docs/server/reference/sql-functions/secondary-functions/bit-functions-and-operators/true-false.md): Boolean literal for 1 = TRUE or 0 = FALSE, respectively.
- [Encryption, Hashing and Compression Functions](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions.md): Learn about encryption, hashing, and compression functions. This section details SQL functions for securing data, generating hashes, and compressing/decompressing information within your database.
- [AES\_DECRYPT](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/aes_decrypt.md): Decrypt data using AES. This function decrypts a string that was encrypted using the Advanced Encryption Standard (AES) algorithm.
- [AES\_ENCRYPT](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/aes_encrypt.md): Encrypt data using AES. This function encrypts a string using the Advanced Encryption Standard (AES) algorithm and returns a binary string.
- [COMPRESS](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/compress.md): Compress a string. This function compresses a string argument and returns the result as a binary string, useful for saving storage space.
- [DECODE](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/decode.md): Decrypt a string. This function decrypts an encrypted string using a password. It is the reverse of the ENCODE function.
- [DES\_DECRYPT](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/des_decrypt.md): Decrypt data using DES. This function decrypts a string that was encrypted using the Data Encryption Standard (DES) algorithm.
- [DES\_ENCRYPT](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/des_encrypt.md): Encrypt data using DES. This function encrypts a string using the Data Encryption Standard (DES) algorithm.
- [ENCODE](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/encode.md): Encrypt a string. This function encrypts a string using a password, returning a binary string. It is the reverse of the DECODE function.
- [ENCRYPT](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/encrypt.md): Encrypt a string using Unix crypt(). This function encrypts a string using the Unix crypt() system call, typically used for password hashing.
- [KDF](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/kdf.md): Derive a key. This function derives a key from a password using a Key Derivation Function (KDF), enhancing security for password storage.
- [MD5](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/md5.md): Calculate MD5 checksum. This function returns the MD5 hash of a string as a 32-character hexadecimal number.
- [OLD\_PASSWORD](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/old_password.md): Generate pre-4.1 password hash. This function creates a password hash compatible with the hashing method used in MySQL versions prior to 4.1.
- [PASSWORD](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/password.md): Calculate password hash. This function calculates a password hash string for a plaintext password.
- [RANDOM\_BYTES](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/random_bytes.md): Generate random bytes. This function returns a binary string of random bytes of a specified length, suitable for cryptographic use.
- [SHA1](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/sha1.md): Calculate SHA-1 checksum. This function computes the SHA-1 160-bit checksum for a string, returning a 40-character hexadecimal string.
- [SHA2](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/sha2.md): Calculate SHA-2 checksum. This function computes the SHA-2 family of hash functions (SHA-224, SHA-256, SHA-384, and SHA-512).
- [UNCOMPRESS](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/uncompress.md): Uncompress a compressed string. This function uncompresses a binary string compressed by the COMPRESS function.
- [UNCOMPRESSED\_LENGTH](/docs/server/reference/sql-functions/secondary-functions/encryption-hashing-and-compression-functions/uncompressed_length.md): Return length of uncompressed string. This function returns the length of a compressed string before it was compressed.
- [Information Functions](/docs/server/reference/sql-functions/secondary-functions/information-functions.md): Retrieve system and session metadata. This section details functions to access database names, user details, version info, and query statistics like row counts.
- [BENCHMARK](/docs/server/reference/sql-functions/secondary-functions/information-functions/benchmark.md): Execute an expression repeatedly. This function runs a scalar expression a specified number of times, primarily for measuring query execution speed.
- [BINLOG\_GTID\_POS](/docs/server/reference/sql-functions/secondary-functions/information-functions/binlog_gtid_pos.md): Retrieve GTID position from a binary log file. This function returns the Global Transaction ID corresponding to a specific file and position in the binlog.
- [CHARSET](/docs/server/reference/sql-functions/secondary-functions/information-functions/charset.md): Return the character set of a string. This function identifies the character set encoding used by the argument.
- [COERCIBILITY](/docs/server/reference/sql-functions/secondary-functions/information-functions/coercibility.md): Determine collation coercibility. This function returns a numeric value indicating the priority of the argument's collation in comparison operations.
- [COLLATION](/docs/server/reference/sql-functions/secondary-functions/information-functions/collation.md): Return the collation of a string. This function outputs the name of the collation rule used for sorting and comparing the string argument.
- [CONNECTION\_ID](/docs/server/reference/sql-functions/secondary-functions/information-functions/connection_id.md): Return the connection ID. This function retrieves the unique thread identifier for the current client connection.
- [CURRENT\_ROLE](/docs/server/reference/sql-functions/secondary-functions/information-functions/current_role.md): Returns the current role. The current role can be set with SET ROLE or SET DEFAULT ROLE.
- [CURRENT\_USER](/docs/server/reference/sql-functions/secondary-functions/information-functions/current_user.md): Return the authenticated user name. This function displays the user name and host name combination used by the server to authenticate the current client.
- [DATABASE](/docs/server/reference/sql-functions/secondary-functions/information-functions/database.md): Return the default database name. This function outputs the name of the currently selected database for the session.
- [DECODE\_HISTOGRAM](/docs/server/reference/sql-functions/secondary-functions/information-functions/decode_histogram.md): Inspect histogram data. This function allows viewing the distribution statistics stored in a histogram for query optimization analysis.
- [DEFAULT](/docs/server/reference/sql-functions/secondary-functions/information-functions/default.md): Return the default value for a column. This function retrieves the value assigned to a column if no explicit value is provided during insertion.
- [FOUND\_ROWS](/docs/server/reference/sql-functions/secondary-functions/information-functions/found_rows.md): Count rows found by the last SELECT statement. This function returns the total number of rows matching the query, disregarding any LIMIT clause.
- [LAST\_INSERT\_ID](/docs/server/reference/sql-functions/secondary-functions/information-functions/last_insert_id.md): Return the last automatically generated value. This function retrieves the most recent AUTO\_INCREMENT value generated by an INSERT statement.
- [LAST\_VALUE](/docs/server/reference/sql-functions/secondary-functions/information-functions/last_value.md): Return the last value from a sequence. This function retrieves the most recently generated value from a sequence object.
- [PROCEDURE ANALYSE](/docs/server/reference/sql-functions/secondary-functions/information-functions/procedure-analyse.md): Analyze query results. This procedure examines the result set and suggests optimal data types for columns based on the data.
- [ROW\_COUNT](/docs/server/reference/sql-functions/secondary-functions/information-functions/row_count.md): Count rows affected by the last statement. This function returns the number of rows inserted, updated, or deleted by the previous DML operation.
- [ROWNUM](/docs/server/reference/sql-functions/secondary-functions/information-functions/rownum.md)
- [SCHEMA](/docs/server/reference/sql-functions/secondary-functions/information-functions/schema.md): Synonym for DATABASE(). Returns the name of the default database currently in use.
- [SESSION\_USER](/docs/server/reference/sql-functions/secondary-functions/information-functions/session_user.md): Return the current user name. This function returns the user name and host name as provided by the client when connecting.
- [SYSTEM\_USER](/docs/server/reference/sql-functions/secondary-functions/information-functions/system_user.md): Synonym for USER(). Returns the MariaDB user name and host name associated with the current session.
- [USER](/docs/server/reference/sql-functions/secondary-functions/information-functions/user.md): Return the current MariaDB user. This function returns the user name and host name provided by the client upon connection.
- [VERSION](/docs/server/reference/sql-functions/secondary-functions/information-functions/version.md): Complete VERSION reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples with comprehensive examples and.
- [Miscellaneous Functions](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions.md): Explore specialized utilities. This category includes functions for benchmarking, managing UUIDs, converting IP addresses, and handling binary data formats.
- [FORMAT\_BYTES](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/miscellaneous-functions-format_bytes.md): Convert bytes to a human-readable string. This function formats a numeric byte count into units like KiB, MiB, GiB, up to EiB.
- [GET\_LOCK](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/get_lock.md): Acquire a named user-level lock. This function attempts to obtain a lock with a specified name and timeout, returning 1 on success or 0 on timeout.
- [INET6\_ATON](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/inet6_aton.md): Convert an IPv6 address to binary. This function takes an IPv6 (or IPv4) address string and returns it as a VARBINARY(16) string.
- [INET6\_NTOA](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/inet6_ntoa.md): Convert a binary IPv6 address to string. This function takes a binary IPv6 address (like from INET6\_ATON) and returns its human-readable string representation.
- [INET\_ATON](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/inet_aton.md): Convert an IPv4 address to an integer. This function takes a dotted-quad IP string (e.g., '1.2.3.4') and returns its numeric representation.
- [INET\_NTOA](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/inet_ntoa.md): Convert an integer to an IPv4 address. This function takes a numeric IP value and returns its dotted-quad string representation.
- [IS\_FREE\_LOCK](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_free_lock.md): Check if a named lock is free. This function returns 1 if the specified lock is available (not currently held), and 0 if it is in use.
- [IS\_IPV4](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_ipv4.md): Check validity of an IPv4 address. This function returns 1 if the argument is a valid IPv4 address string, and 0 otherwise.
- [IS\_IPV4\_COMPAT](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_ipv4_compat.md): Check if an IPv6 address is IPv4-compatible. This function returns 1 if the binary IPv6 address represents an IPv4-compatible address.
- [IS\_IPV4\_MAPPED](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_ipv4_mapped.md): Check if an IPv6 address is IPv4-mapped. This function returns 1 if the binary IPv6 address represents an IPv4-mapped address.
- [IS\_IPV6](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_ipv6.md): Check validity of an IPv6 address. This function returns 1 if the argument is a valid IPv6 address string, and 0 otherwise.
- [IS\_USED\_LOCK](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/is_used_lock.md): Check who holds a named lock. This function returns the connection identifier of the client holding the lock, or NULL if the lock is free.
- [MASTER\_GTID\_WAIT](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/master_gtid_wait.md): Wait for a replica to apply a GTID. This function blocks until the replica has executed transactions up to the specified Global Transaction ID.
- [MASTER\_POS\_WAIT](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/master_pos_wait.md): Wait for a replica to reach a log position. This function blocks until the replica has read and applied updates up to a specified position in the master's binary log.
- [NAME\_CONST](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/name_const.md): Force a column name for an expression. This function is primarily used internally for replication to ensure consistent column naming.
- [OLD\_VALUE](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/old-value.md): Access values in ON DUPLICATE KEY UPDATE. This function retrieves the value that would have been inserted into a column if no key conflict occurred.
- [RELEASE\_ALL\_LOCKS](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/release_all_locks.md): Release all named locks held by the session. This function frees all user-level locks acquired with GET\_LOCK() in the current connection.
- [RELEASE\_LOCK](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/release_lock.md): Release a specific named lock. This function frees a user-level lock previously obtained with GET\_LOCK(), allowing others to acquire it.
- [SLEEP](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/sleep.md): Pause query execution. This function pauses the script for a specified number of seconds, returning 0 if successful or 1 if interrupted.
- [SYS\_GUID](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/sys_guid.md): Generate a UUID without hyphens. This Oracle-compatible function returns a globally unique identifier as a 32-character hexadecimal string.
- [UUID](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/uuid.md): Official UUID() function reference: generate UUIDv1 values, 128-bit 36-character format (aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee), and replication safety.
- [UUID\_SHORT](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/uuid_short.md): Generate a short 64-bit UUID. This function returns a unique, monotonically increasing integer suitable for use as a compact identifier.
- [UUID\_v4](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/uuid_v4.md): Generate a random UUID (v4). This function returns a version 4 UUID, which is generated using random numbers.
- [UUID\_v7](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/uuid_v7.md): Generate a time-ordered UUID (v7). This function returns a version 7 UUID, which is sortable by creation time.
- [VALUES / VALUE](/docs/server/reference/sql-functions/secondary-functions/miscellaneous-functions/values-value.md): Access values in ON DUPLICATE KEY UPDATE. This function retrieves the value that would have been inserted into a column if no key conflict occurred.
- [Special Functions](/docs/server/reference/sql-functions/special-functions.md): Explore special functions in MariaDB Server. This section details unique SQL functions that provide specialized capabilities, often related to server internals, diagnostics, or specific data handling.
- [Dynamic Columns Functions](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions.md): Manage schema-less data within relational tables. These functions, such as COLUMN\_CREATE and COLUMN\_GET, allow you to store and retrieve variable sets of columns in a single BLOB field.
- [COLUMN\_ADD](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_add.md): Update dynamic columns. This function adds or updates values within a dynamic column blob, returning the new blob content.
- [COLUMN\_CHECK](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_check.md): Verify dynamic column integrity. This function checks if a blob containing dynamic columns is valid and returns 1 if it is, 0 otherwise.
- [COLUMN\_CREATE](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_create.md): Create a dynamic column blob. This function generates a binary string containing specified column names and values for storage in a BLOB.
- [COLUMN\_DELETE](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_delete.md): Remove dynamic columns. This function deletes specified columns from a dynamic column blob and returns the updated blob.
- [COLUMN\_EXISTS](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_exists.md): Check for a dynamic column. This function returns 1 if a specified column exists within a dynamic column blob, and 0 otherwise.
- [COLUMN\_GET](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_get.md): Retrieve a dynamic column value. This function extracts a specific column's value from a dynamic column blob, casting it to a specified type.
- [COLUMN\_JSON](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_json.md): Convert dynamic columns to JSON. This function returns a JSON string representation of the data stored in a dynamic column blob.
- [COLUMN\_LIST](/docs/server/reference/sql-functions/special-functions/dynamic-columns-functions/column_list.md): List dynamic column names. This function returns a comma-separated list of all column names contained within a dynamic column blob.
- [Galera Functions](/docs/server/reference/sql-functions/special-functions/galera-functions.md): Interact with the Galera Cluster plugin. These functions provide internal status information and control mechanisms specific to synchronous multi-master replication nodes.
- [WSREP\_LAST\_SEEN\_GTID](/docs/server/reference/sql-functions/special-functions/galera-functions/wsrep_last_seen_gtid.md): Return the GTID of the most recent write transaction. This function helps determine the transaction ID to use for synchronization waiting.
- [WSREP\_LAST\_WRITTEN\_GTID](/docs/server/reference/sql-functions/special-functions/galera-functions/wsrep_last_written_gtid.md): Return the GTID of the client's last write. This function identifies the specific transaction ID generated by the current client's most recent write operation.
- [WSREP\_SYNC\_WAIT\_UPTO\_GTID](/docs/server/reference/sql-functions/special-functions/galera-functions/wsrep_sync_wait_upto_gtid.md): Wait for a specific GTID to be applied. This function blocks the client until the node has committed the transaction with the specified Global Transaction ID.
- [Geographic Functions](/docs/server/reference/sql-functions/special-functions/geographic-functions.md): Process geospatial data. This collection of functions allows you to create, analyze, and manipulate geometric shapes like points, lines, and polygons within your database.
- [JSON Functions](/docs/server/reference/sql-functions/special-functions/json-functions.md): Complete JSON Functions reference: JSON\_EXTRACT(), JSON\_SET(), JSON\_REPLACE(), JSON\_SEARCH() syntax for path queries, document updates, and value retrieval.
- [JSONPath Expressions](/docs/server/reference/sql-functions/special-functions/json-functions/jsonpath-expressions.md): Understand JSONPath syntax. This guide explains how to use JSONPath to select and extract specific elements, objects, or arrays from JSON documents.
- [Differences between JSON\_QUERY and JSON\_VALUE](/docs/server/reference/sql-functions/special-functions/json-functions/differences-between-json_query-and-json_value.md): Learn the difference between JSON\_QUERY and JSON\_VALUE in MariaDB. JSON\_QUERY returns objects or arrays, while JSON\_VALUE extracts scalar values.
- [JSON\_ARRAY](/docs/server/reference/sql-functions/special-functions/json-functions/json_array.md): Create a JSON array. This function evaluates a list of values and returns a JSON array containing those values.
- [JSON\_ARRAY\_APPEND](/docs/server/reference/sql-functions/special-functions/json-functions/json_array_append.md): Explore JSON\_ARRAY\_APPEND in MariaDB. This function appends values to the end of specified arrays within a JSON document, returning the modified result.
- [JSON\_ARRAY\_INSERT](/docs/server/reference/sql-functions/special-functions/json-functions/json_array_insert.md): This function inserts values into a JSON document at a specified path, returning the modified document, and supports evaluating multiple path-value pairs sequentially.
- [JSON\_ARRAY\_INTERSECT](/docs/server/reference/sql-functions/special-functions/json-functions/json_array_intersect.md): Available from version 11.2, this function compares two JSON arrays and returns a new array containing only the items present in both.
- [JSON\_COMPACT](/docs/server/reference/sql-functions/special-functions/json-functions/json_compact.md): Learn about the JSON\_COMPACT function in MariaDB. This function removes all unnecessary whitespace from a JSON document, minimizing its size for efficient storage and transmission.
- [JSON\_CONTAINS](/docs/server/reference/sql-functions/special-functions/json-functions/json_contains.md): Check for JSON containment. This function returns 1 if a candidate JSON document is contained within a target JSON document, or 0 otherwise.
- [JSON\_CONTAINS\_PATH](/docs/server/reference/sql-functions/special-functions/json-functions/json_contains_path.md): Check for a JSON path. This function returns 1 if a specified path exists within a JSON document, or 0 if it does not.
- [JSON\_DEPTH](/docs/server/reference/sql-functions/special-functions/json-functions/json_depth.md): Discover JSON\_DEPTH in MariaDB. This function returns the maximum depth of a JSON document, assigning a depth of 1 to scalars and empty structures, and higher values for nested data.
- [JSON\_DETAILED](/docs/server/reference/sql-functions/special-functions/json-functions/json_detailed.md): Explore JSON\_DETAILED in MariaDB. Also known as JSON\_PRETTY, this function formats JSON documents with indentation and newlines to emphasize nested structures for readability.
- [JSON\_EQUALS](/docs/server/reference/sql-functions/special-functions/json-functions/json_equals.md): Discover JSON\_EQUALS in MariaDB. This function checks for equality between two JSON objects, returning 1 if they are equal, 0 if not, handling key order and data types intelligently.
- [JSON\_EXISTS](/docs/server/reference/sql-functions/special-functions/json-functions/json_exists.md): Explore JSON\_EXISTS in MariaDB. This function checks whether a specified JSON document contains an element at a given path, returning 1 for existence and 0 otherwise.
- [JSON\_EXTRACT](/docs/server/reference/sql-functions/special-functions/json-functions/json_extract.md): Complete JSON\_EXTRACT() reference: JSON\_EXTRACT(json\_doc, path\[, path]...) syntax, JSONPath arguments, NULL/error behavior, and multi-match array autowrap.
- [JSON\_INSERT](/docs/server/reference/sql-functions/special-functions/json-functions/json_insert.md): Learn about the JSON\_INSERT function in MariaDB. This function inserts new data into a JSON document without replacing existing values, returning the updated document or NULL.
- [JSON\_KEY\_VALUE](/docs/server/reference/sql-functions/special-functions/json-functions/json_key_value.md): Explore JSON\_KEY\_VALUE in MariaDB. Available from version 11.2, this function extracts key/value pairs from a JSON object, enabling easier data transformation and usage with JSON\_TABLE.
- [JSON\_KEYS](/docs/server/reference/sql-functions/special-functions/json-functions/json_keys.md): Return keys from a JSON object. This function returns the keys from the top-level value of a JSON object as a JSON array.
- [JSON\_LENGTH](/docs/server/reference/sql-functions/special-functions/json-functions/json_length.md): Return the length of a JSON document. This function returns the length of a JSON document or, if a path is given, the length of the value within the path.
- [JSON\_LOOSE](/docs/server/reference/sql-functions/special-functions/json-functions/json_loose.md): Discover JSON\_LOOSE in MariaDB. This function adds spaces to a JSON document to improve its readability, providing a format that is easier for humans to scan than compact JSON.
- [JSON\_MERGE](/docs/server/reference/sql-functions/special-functions/json-functions/json_merge.md): Merge JSON documents. This function merges two or more JSON documents into a single JSON document, preserving all keys and values.
- [JSON\_MERGE\_PATCH](/docs/server/reference/sql-functions/special-functions/json-functions/json_merge_patch.md): Learn about JSON\_MERGE\_PATCH in MariaDB. This RFC 7396-compliant function merges JSON documents by overwriting duplicate keys, serving as a modern replacement for the deprecated JSON\_MERGE.
- [JSON\_MERGE\_PRESERVE](/docs/server/reference/sql-functions/special-functions/json-functions/json_merge_preserve.md): Explore JSON\_MERGE\_PRESERVE in MariaDB. This function merges JSON documents while keeping all members, including those with duplicate keys, effectively acting as a synonym for the legacy JSON\_MERGE.
- [JSON\_NORMALIZE](/docs/server/reference/sql-functions/special-functions/json-functions/json_normalize.md): Discover JSON\_NORMALIZE in MariaDB. This function recursively sorts keys and removes spaces from a JSON document, enabling reliable equality comparisons and unique constraints on JSON data.
- [JSON\_OBJECT](/docs/server/reference/sql-functions/special-functions/json-functions/json_object.md): Create a JSON object. This function evaluates a list of key-value pairs and returns a JSON object containing those pairs.
- [JSON\_OBJECT\_FILTER\_KEYS](/docs/server/reference/sql-functions/special-functions/json-functions/json_object_filter_keys.md): Discover JSON\_OBJECT\_FILTER\_KEYS in MariaDB. Available from version 11.2, this function returns a new JSON object containing only the key-value pairs where the keys match those provided in a specified
- [JSON\_OBJECT\_TO\_ARRAY](/docs/server/reference/sql-functions/special-functions/json-functions/json_object_to_array.md): Explore JSON\_OBJECT\_TO\_ARRAY in MariaDB. Available from version 11.2, this function converts JSON objects into arrays of key-value pairs, facilitating operations like finding common values when used w
- [JSON\_OVERLAPS](/docs/server/reference/sql-functions/special-functions/json-functions/json_overlaps.md): Discover JSON\_OVERLAPS in MariaDB. Available from version 10.9, this function compares two JSON documents, returning true if they share at least one common key-value pair, array element, or scalar val
- [JSON\_PRETTY](/docs/server/reference/sql-functions/special-functions/json-functions/json_pretty.md): Learn about JSON\_PRETTY in MariaDB. This function is an alias for JSON\_DETAILED, serving to format JSON documents in a human-readable way by adding indentation and newlines.
- [JSON\_QUERY](/docs/server/reference/sql-functions/special-functions/json-functions/json_query.md): Extract a JSON object or array. This function extracts data from a JSON document at a given path, returning a JSON object or array.
- [JSON\_QUOTE](/docs/server/reference/sql-functions/special-functions/json-functions/json_quote.md): Quote a string as a JSON value. This function wraps a string with double quotes and escapes special characters to create a valid JSON string literal.
- [JSON\_REMOVE](/docs/server/reference/sql-functions/special-functions/json-functions/json_remove.md): Remove data from a JSON document. This function removes data from a JSON document at a specified path and returns the result.
- [JSON\_REPLACE](/docs/server/reference/sql-functions/special-functions/json-functions/json_replace.md): Replace values in a JSON document. This function replaces existing values in a JSON document and returns the result.
- [JSON\_SCHEMA\_VALID](/docs/server/reference/sql-functions/special-functions/json-functions/json_schema_valid.md): Discover JSON\_SCHEMA\_VALID in MariaDB. Available from version 11.1, this function validates a JSON document against a specified JSON Schema (Draft 2020), returning true if valid.
- [JSON\_SEARCH](/docs/server/reference/sql-functions/special-functions/json-functions/json_search.md): Search for a value in a JSON document. This function returns the path to the given string within a JSON document.
- [JSON\_SET](/docs/server/reference/sql-functions/special-functions/json-functions/json_set.md): Insert or update data in a JSON document. This function inserts or updates data in a JSON document at a specified path and returns the result.
- [JSON\_TABLE](/docs/server/reference/sql-functions/special-functions/json-functions/json_table.md): Convert JSON data to a relational table. This table function extracts data from a JSON document and returns it as a relational table with columns.
- [JSON\_TYPE](/docs/server/reference/sql-functions/special-functions/json-functions/json_type.md): Return the type of a JSON value. This function returns a string indicating the type of a JSON value (e.g., OBJECT, ARRAY, INTEGER).
- [JSON\_UNQUOTE](/docs/server/reference/sql-functions/special-functions/json-functions/json_unquote.md): Unquote a JSON value. This function removes the quotes from a JSON string and unescapes special characters.
- [JSON\_VALID](/docs/server/reference/sql-functions/special-functions/json-functions/json_valid.md): Check if a value is valid JSON. This function returns 1 if the argument is a valid JSON document, and 0 otherwise.
- [JSON\_VALUE](/docs/server/reference/sql-functions/special-functions/json-functions/json_value.md): Extract a scalar value from a JSON document. This function extracts a value from a JSON document at a given path and returns it as a scalar.
- [JSON Validation Function](/docs/server/reference/sql-functions/special-functions/json-functions/json-validation-function.md)
- [Window Functions](/docs/server/reference/sql-functions/special-functions/window-functions.md): Explore window functions in MariaDB Server. This section details SQL functions that perform calculations across a set of table rows related to the current row, enabling advanced analytical queries.
- [Window Functions Overview](/docs/server/reference/sql-functions/special-functions/window-functions/window-functions-overview.md): Understand window function concepts. These functions operate on a set of rows (window) defined by an OVER clause, returning a value for each row without collapsing results.
- [Window Frames](/docs/server/reference/sql-functions/special-functions/window-functions/window-frames.md): Define subsets of rows for calculation. Window frames specify which rows relative to the current row are included in the window function's calculation.
- [ColumnStore Window Functions](/docs/server/reference/sql-functions/special-functions/window-functions/window-functions-columnstore-window-functions.md): Review window function support in ColumnStore. This page details the specific window functions and limitations applicable when using the ColumnStore storage engine.
- [CUME\_DIST](/docs/server/reference/sql-functions/special-functions/window-functions/cume_dist.md): Calculate cumulative distribution. This function returns the relative rank of the current row within its partition, calculated as the percentage of rows preceding or peer to it.
- [DENSE\_RANK](/docs/server/reference/sql-functions/special-functions/window-functions/dense_rank.md): Calculate rank without gaps. This function assigns a rank to each row within a partition, with tied values receiving the same rank and no numbers skipped.
- [FIRST\_VALUE](/docs/server/reference/sql-functions/special-functions/window-functions/first_value.md): Return the value from the first row in the window frame. This function retrieves the value of an expression from the first row of the defined window.
- [LAG](/docs/server/reference/sql-functions/special-functions/window-functions/lag.md): Access data from a preceding row. This function returns the value of an expression from a row at a specified physical offset prior to the current row.
- [LEAD](/docs/server/reference/sql-functions/special-functions/window-functions/lead.md): Access data from a following row. This function returns the value of an expression from a row at a specified physical offset after the current row.
- [MEDIAN](/docs/server/reference/sql-functions/special-functions/window-functions/median.md): Calculate the median value. This window function returns the middle value (50th percentile) of an ordered set of values within the window.
- [NTH\_VALUE](/docs/server/reference/sql-functions/special-functions/window-functions/nth_value.md): Return the value from the N-th row. This function retrieves the value of an expression from the N-th row within the window frame.
- [NTILE](/docs/server/reference/sql-functions/special-functions/window-functions/ntile.md): Distribute rows into buckets. This function divides the rows in an ordered partition into a specified number of approximately equal groups.
- [PERCENT\_RANK](/docs/server/reference/sql-functions/special-functions/window-functions/percent_rank.md): Calculate relative rank. This function returns the percentage rank of the current row within its partition, ranging from 0 to 1.
- [PERCENTILE\_CONT](/docs/server/reference/sql-functions/special-functions/window-functions/percentile_cont.md): Calculate a continuous percentile. This inverse distribution function returns an interpolated value that corresponds to the specified percentile.
- [PERCENTILE\_DISC](/docs/server/reference/sql-functions/special-functions/window-functions/percentile_disc.md): Calculate a discrete percentile. This inverse distribution function returns an actual value from the dataset that corresponds to the specified percentile.
- [RANK](/docs/server/reference/sql-functions/special-functions/window-functions/rank.md): Calculate rank with gaps. This function assigns a rank to each row, with tied values receiving the same rank and subsequent ranks skipped.
- [ROW\_NUMBER](/docs/server/reference/sql-functions/special-functions/window-functions/row_number.md): Complete ROW\_NUMBER() reference: ROW\_NUMBER() OVER() window syntax, PARTITION BY clauses, ORDER BY ordering, and RANK()/DENSE\_RANK() comparisons.
- [String Functions](/docs/server/reference/sql-functions/string-functions.md): Learn about string functions in MariaDB Server. This section details SQL functions for manipulating, searching, and formatting text strings, essential for data cleansing and presentation.
- [ASCII](/docs/server/reference/sql-functions/string-functions/ascii.md): Return the ASCII value of the first character. This function returns the numeric ASCII code for the leftmost character of the input string.
- [BIN](/docs/server/reference/sql-functions/string-functions/bin.md): Return the binary representation of a number. This function converts a number to its binary string equivalent.
- [BINARY Operator](/docs/server/reference/sql-functions/string-functions/binary-operator.md): Cast a string to a binary string. This operator converts a character string to a binary string, often used for case-sensitive comparisons.
- [BIT\_LENGTH](/docs/server/reference/sql-functions/string-functions/bit_length.md): Return the length of a string in bits. This function calculates the size of the string in bits (length in bytes multiplied by 8).
- [CAST](/docs/server/reference/sql-functions/string-functions/cast.md): Complete CAST reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples with comprehensive examples and best.
- [CHAR Function](/docs/server/reference/sql-functions/string-functions/char-function.md): Return the character for each integer passed. This function interprets arguments as integer ASCII values and returns a string of those characters.
- [CHAR\_LENGTH](/docs/server/reference/sql-functions/string-functions/char_length.md): Return the length of a string in characters. This function counts the number of characters in the string, treating multi-byte characters as single units.
- [CHARACTER\_LENGTH](/docs/server/reference/sql-functions/string-functions/character_length.md): Synonym for CHAR\_LENGTH(). Returns the number of characters in the string.
- [CHR](/docs/server/reference/sql-functions/string-functions/chr.md): Return the character for a specific ASCII value. This function is similar to CHAR() but accepts a single integer argument.
- [CONCAT](/docs/server/reference/sql-functions/string-functions/concat.md): Complete CONCAT reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples with comprehensive examples and.
- [CONCAT\_WS](/docs/server/reference/sql-functions/string-functions/concat_ws.md): Concatenate with separator. This function joins strings with a specified separator. It skips NULL values during concatenation.
- [CONVERT](/docs/server/reference/sql-functions/string-functions/convert.md): Complete CONVERT() reference: CONVERT(expr,type) and CONVERT(expr USING charset) syntax, SIGNED/UNSIGNED/BINARY/CHAR types, and CAST() differences.
- [ELT](/docs/server/reference/sql-functions/string-functions/elt.md): Return the string at a specific index. This function returns the N-th string from a list of arguments.
- [EXPORT\_SET](/docs/server/reference/sql-functions/string-functions/export_set.md): Return a string representation of bits. This function generates a string based on the bits set in a number, using specified 'on' and 'off' strings.
- [EXTRACTVALUE](/docs/server/reference/sql-functions/string-functions/extractvalue.md): Extract a value from XML. This function returns the text content of an XML fragment matching a given XPath expression.
- [FIELD](/docs/server/reference/sql-functions/string-functions/field.md): Return the index of a string in a list. This function returns the position of the first argument within the subsequent list of arguments.
- [FIND\_IN\_SET](/docs/server/reference/sql-functions/string-functions/find_in_set.md): Return the index of a string in a comma-separated list. This function finds the position of a string within a list of strings separated by commas.
- [FORMAT](/docs/server/reference/sql-functions/string-functions/format.md): Format a number. This function formats a number to a format like '#,###,###.##', rounded to a specified number of decimal places.
- [FROM\_BASE64](/docs/server/reference/sql-functions/string-functions/from_base64.md): Decode a base-64 encoded string. This function takes a base-64 string and returns the decoded binary result.
- [HEX](/docs/server/reference/sql-functions/string-functions/hex.md): Return the hexadecimal representation. This function converts a number or string to its hexadecimal string equivalent.
- [INSERT Function](/docs/server/reference/sql-functions/string-functions/insert-function.md): Insert a substring into a string. This function inserts a string within another string at a specified position and length, replacing existing characters.
- [INSTR](/docs/server/reference/sql-functions/string-functions/instr.md): Return the position of the first occurrence of a substring. This function locates a substring within a string and returns its index.
- [LCASE](/docs/server/reference/sql-functions/string-functions/lcase.md): Synonym for LOWER(). Converts a string to lowercase characters.
- [LEFT](/docs/server/reference/sql-functions/string-functions/left.md): Return the leftmost characters. This function returns the specified number of characters from the beginning (left) of a string.
- [LENGTH](/docs/server/reference/sql-functions/string-functions/length.md): Return the length of a string in bytes. This function counts the number of bytes in the string, which may differ from character count for multi-byte strings.
- [LENGTHB](/docs/server/reference/sql-functions/string-functions/lengthb.md): Return the length of a string in bytes. This function is a synonym for LENGTH() in default mode, returning the byte count.
- [LIKE](/docs/server/reference/sql-functions/string-functions/like.md): Complete LIKE operator reference: LIKE/NOT LIKE pattern matching syntax, % and \_ wildcards, ESCAPE clause, NULL behavior, and collation case-sensitivity.
- [LOAD\_FILE](/docs/server/reference/sql-functions/string-functions/load_file.md): Read a file from the server. This function reads the content of a file located on the server host and returns it as a string.
- [LOCATE](/docs/server/reference/sql-functions/string-functions/locate.md): Return the position of the first occurrence of a substring. This function finds the starting position of a substring within a string.
- [LOWER](/docs/server/reference/sql-functions/string-functions/lower.md): Convert a string to lowercase. This function returns the string with all characters converted to lowercase.
- [LPAD](/docs/server/reference/sql-functions/string-functions/lpad.md): Left-pad a string. This function pads a string on the left side with a specified string until it reaches a certain length.
- [LTRIM](/docs/server/reference/sql-functions/string-functions/ltrim.md): Remove leading spaces. This function returns the string with any leading whitespace characters removed.
- [MAKE\_SET](/docs/server/reference/sql-functions/string-functions/make_set.md): Return a set of comma-separated strings. This function returns a string consisting of substrings corresponding to the set bits in a given number.
- [MATCH AGAINST](/docs/server/reference/sql-functions/string-functions/match-against.md): Perform a full-text search. This construct searches for a text query against a set of columns indexed with a FULLTEXT index.
- [MID](/docs/server/reference/sql-functions/string-functions/mid.md): Synonym for SUBSTRING(). Returns a substring starting at a specified position for a given length.
- [NATURAL\_SORT\_KEY](/docs/server/reference/sql-functions/string-functions/natural_sort_key.md): Generate a sort key for natural ordering. This function produces a key that allows strings containing numbers to be sorted in a human-readable order.
- [NOT LIKE](/docs/server/reference/sql-functions/string-functions/not-like.md): Negated pattern matching. This operator tests whether a string does NOT match a specified SQL pattern.
- [NOT REGEXP](/docs/server/reference/sql-functions/string-functions/not-regexp.md): Negated regular expression matching. This operator tests whether a string does NOT match a specified regular expression pattern.
- [OCTET\_LENGTH](/docs/server/reference/sql-functions/string-functions/octet_length.md): Return the length of a string in bytes. This function is a synonym for LENGTH() and returns the number of bytes in the string.
- [ORD](/docs/server/reference/sql-functions/string-functions/ord.md): Return the numeric value of the first character. This function returns the code for the leftmost character, supporting multi-byte characters.
- [POSITION](/docs/server/reference/sql-functions/string-functions/position.md): Synonym for LOCATE(). Returns the position of the first occurrence of a substring within a string.
- [QUOTE](/docs/server/reference/sql-functions/string-functions/quote.md): Quote a string for SQL usage. This function produces a string ready for use as a data value in an SQL statement, escaping special characters.
- [REPEAT Function](/docs/server/reference/sql-functions/string-functions/repeat-function.md): Repeat a string. This function returns a string consisting of the input string repeated a specified number of times.
- [REPLACE Function](/docs/server/reference/sql-functions/string-functions/replace-function.md): Complete REPLACE Function reference for MariaDB. Complete function guide with syntax, parameters, return values, and usage examples for production use.
- [REVERSE](/docs/server/reference/sql-functions/string-functions/reverse.md): Reverse a string. This function returns the string with the order of its characters reversed.
- [RIGHT](/docs/server/reference/sql-functions/string-functions/right.md): Return the rightmost characters. This function returns the specified number of characters from the end (right) of a string.
- [RPAD](/docs/server/reference/sql-functions/string-functions/rpad.md): Right-pad a string. This function pads a string on the right side with a specified string until it reaches a certain length.
- [RTRIM](/docs/server/reference/sql-functions/string-functions/rtrim.md): Remove trailing spaces. This function returns the string with any trailing whitespace characters removed.
- [SFORMAT](/docs/server/reference/sql-functions/string-functions/sformat.md): Format strings with arbitrary patterns. This function allows complex string formatting using a pattern string and arguments.
- [SOUNDEX](/docs/server/reference/sql-functions/string-functions/soundex.md): Return the Soundex string. This function calculates the Soundex key for a string, allowing comparison of words that sound similar.
- [SOUNDS LIKE](/docs/server/reference/sql-functions/string-functions/sounds-like.md): Compare strings by sound. This operator tests if two strings have the same Soundex value, useful for fuzzy matching.
- [SPACE](/docs/server/reference/sql-functions/string-functions/space.md): Return a string of spaces. This function returns a string consisting of a specified number of space characters.
- [STRCMP](/docs/server/reference/sql-functions/string-functions/strcmp.md): Compare two strings. This function returns 0 if strings are equal, -1 if the first is smaller, and 1 if the first is larger.
- [SUBSTR](/docs/server/reference/sql-functions/string-functions/substr.md)
- [SUBSTRING](/docs/server/reference/sql-functions/string-functions/substring.md): Complete SUBSTRING() reference: syntax forms (pos,len, FROM/FOR), negative position from end, NULL handling, and Oracle sql\_mode position 0 behavior.
- [SUBSTRING\_INDEX](/docs/server/reference/sql-functions/string-functions/substring_index.md): Complete SUBSTRING\_INDEX() reference: SUBSTRING\_INDEX(str,delim,count) syntax, positive/negative count, case-sensitive delimiter, NULL rules.
- [TO\_BASE64](/docs/server/reference/sql-functions/string-functions/to_base64.md): Encode a string to base-64. This function converts a string argument to its base-64 encoded form.
- [TO\_CHAR](/docs/server/reference/sql-functions/string-functions/to_char.md): Convert to string. This function converts a value (often date/time) to a string, potentially using a format mask.
- [TRIM](/docs/server/reference/sql-functions/string-functions/trim.md): Remove spaces from both ends. This function removes leading and trailing whitespace (or other specified characters) from a string.
- [TRIM\_ORACLE](/docs/server/reference/sql-functions/string-functions/trim_oracle.md): Oracle-compatible TRIM function. This version of TRIM provides compatibility with Oracle's syntax for removing characters from a string.
- [Type Conversion](/docs/server/reference/sql-functions/string-functions/type-conversion.md): Understand Type Conversion in MariaDB. Learn the rules for implicit conversion during comparisons and arithmetic, and how to use CAST for predictable results.
- [UCASE](/docs/server/reference/sql-functions/string-functions/ucase.md): Synonym for UPPER(). Converts a string to uppercase characters.
- [UNHEX](/docs/server/reference/sql-functions/string-functions/unhex.md): Convert hexadecimal to string. This function interprets pairs of hexadecimal digits as numbers and converts them to the characters they represent.
- [UPDATEXML](/docs/server/reference/sql-functions/string-functions/updatexml.md): Replace a portion of XML. This function replaces a section of XML markup matching an XPath expression with a new XML fragment.
- [UPPER](/docs/server/reference/sql-functions/string-functions/upper.md): Convert a string to uppercase. This function returns the string with all characters converted to uppercase.
- [WEIGHT\_STRING](/docs/server/reference/sql-functions/string-functions/weight_string.md): Return the weight string. This function returns the binary string that represents the sorting and comparison value of the input string.
- [Regular Expressions Functions](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions.md): Learn about regular expression functions in MariaDB Server. This section details SQL functions for powerful pattern matching and manipulation of string data using regular expressions.
- [Regular Expressions Overview](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/regular-expressions-overview.md): Get an overview of regex usage. This page introduces the pattern matching capabilities and common metacharacters used in MariaDB regular expressions.
- [PCRE - Perl Compatible Regular Expressions](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/pcre.md): Understand MariaDB's regex support. This concept page explains the PCRE library integration, detailing supported syntax, character classes, and special characters.
- [REGEXP](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/regexp.md): Complete REGEXP operator reference: expr REGEXP/RLIKE pat syntax, 1/0/NULL return values, NOT REGEXP aliases, BINARY case-sensitivity, default\_regex\_flags.
- [REGEXP\_INSTR](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/regexp_instr.md): Return the index of a regex match. This function finds the starting position of the first substring that matches the given pattern.
- [REGEXP\_REPLACE](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/regexp_replace.md): Replace regex matches in a string. This function substitutes occurrences of a pattern with a specified replacement string.
- [REGEXP\_SUBSTR](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/regexp_substr.md): Return the substring matching a regex. This function extracts the actual part of the string that matches the given pattern.
- [RLIKE](/docs/server/reference/sql-functions/string-functions/regular-expressions-functions/rlike.md): Synonym for REGEXP. This operator performs a regular expression match against a string argument.
- [Vector Functions](/docs/server/reference/sql-functions/vector-functions.md): Explore vector functions. This section details SQL functions for manipulating and querying vector data types, enabling efficient similarity search and AI/ML applications within your  database.
- [VEC\_DISTANCE](/docs/server/reference/sql-functions/vector-functions/vector-functions-vec_distance.md): Calculate distance between vectors. This function computes the distance between two vectors using either Euclidean or Cosine metric, depending on the index.
- [VEC\_DISTANCE\_COSINE](/docs/server/reference/sql-functions/vector-functions/vec_distance_cosine.md): Calculate Cosine distance. This function computes the Cosine distance between two vectors, measuring the cosine of the angle between them.
- [VEC\_DISTANCE\_EUCLIDEAN](/docs/server/reference/sql-functions/vector-functions/vec_distance_euclidean.md): Calculate Euclidean distance. This function computes the Euclidean (L2) distance between two vectors, representing the straight-line distance.
- [VEC\_FromText](/docs/server/reference/sql-functions/vector-functions/vec_fromtext.md): Convert text to vector. This function parses a JSON array string representation of a vector and converts it into the binary VECTOR data type.
- [VEC\_ToText](/docs/server/reference/sql-functions/vector-functions/vec_totext.md): Convert vector to text. This function takes a binary VECTOR data type and returns its JSON array string representation.
- [Data Types](/docs/server/reference/data-types.md): Comprehensive MariaDB data types reference. Complete guide for numeric, string, date/time, spatial, and JSON types with storage specifications.
- [Data Type Storage Requirements](/docs/server/reference/data-types/data-type-storage-requirements.md): Reference for storage space usage. This page lists the disk space consumed by each data type, helping with capacity planning and schema optimization.
- [AUTO\_INCREMENT](/docs/server/reference/data-types/auto_increment.md): Complete AUTO\_INCREMENT data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range limits for production use.
- [AUTO\_INCREMENT FAQ](/docs/server/reference/data-types/auto_increment-faq.md): Answers to common questions about AUTO\_INCREMENT. Learn about gaps in sequences, resetting values, and behavior in different storage engines.
- [NULL Values](/docs/server/reference/data-types/null-values.md): Understand the concept of NULL. This page explains how NULL represents missing or unknown data and how it interacts with comparison operators and functions.
- [ROW TYPE OF](/docs/server/reference/data-types/row-type-of.md): Declare row-based variables. This PL/SQL compatibility feature allows declaring variables that match the structure of a table row or cursor.
- [SERIAL](/docs/server/reference/data-types/serial.md): Alias for BIGINT UNSIGNED NOT NULL AUTO\_INCREMENT UNIQUE. This shorthand data type is often used to define primary keys.
- [TYPE OF](/docs/server/reference/data-types/type-of.md): Declare variables based on existing types. This feature allows defining variables or parameters that inherit the data type of a table column or another variable.
- [Numeric Data Types](/docs/server/reference/data-types/numeric-data-types.md): Complete numeric types reference: INT/BIGINT ranges, DECIMAL(M,D) precision/scale, FLOAT/DOUBLE storage sizes, and numeric type selection guidelines.
- [Numeric Data Type Overview](/docs/server/reference/data-types/numeric-data-types/numeric-data-type-overview.md): General introduction to numeric data types. This page summarizes the available integer, fixed-point, and floating-point types and their storage characteristics.
- [BIGINT](/docs/server/reference/data-types/numeric-data-types/bigint.md): Large integer type. A BIGINT uses 8 bytes and can store values from -9223372036854775808 to 9223372036854775807 (signed) or 0 to 18446744073709551615 (unsigned).
- [BIT](/docs/server/reference/data-types/numeric-data-types/bit.md): Bit-field data type. A BIT(M) column stores M bits per value, allowing storage of binary values from 1 to 64 bits in length.
- [BOOL](/docs/server/reference/data-types/numeric-data-types/bool.md): Synonym for TINYINT(1). This type is commonly used to represent boolean values, where 0 is considered false and non-zero values are true.
- [BOOLEAN](/docs/server/reference/data-types/numeric-data-types/boolean.md): Complete BOOLEAN type reference: TINYINT(1) synonym, TRUE/FALSE aliases, CREATE TABLE/SHOW CREATE TABLE output, and IF()/IS operator evaluation.
- [DEC, NUMERIC, FIXED](/docs/server/reference/data-types/numeric-data-types/dec-numeric-fixed.md): Synonyms for DECIMAL. These keywords declare fixed-point numbers, which store exact numeric data with a defined precision and scale.
- [DEC](/docs/server/reference/data-types/numeric-data-types/numeric-data-types-dec.md): Synonym for DECIMAL. This keyword creates a fixed-point column with exact precision, suitable for financial calculations.
- [DECIMAL](/docs/server/reference/data-types/numeric-data-types/decimal.md): Complete DECIMAL type reference: DECIMAL(M,D) syntax, precision limits (M≤65, D≤38), SIGNED/UNSIGNED/ZEROFILL options, and rounding behavior.
- [DOUBLE PRECISION](/docs/server/reference/data-types/numeric-data-types/double-precision.md): Synonym for DOUBLE. This keyword declares a normal-size (8-byte) floating-point number with double precision.
- [DOUBLE](/docs/server/reference/data-types/numeric-data-types/double.md): Double precision floating-point number. A DOUBLE column uses 8 bytes to store large or precise approximate values.
- [FIXED](/docs/server/reference/data-types/numeric-data-types/fixed.md): Synonym for DECIMAL. This keyword is used to define columns that require exact numeric precision, such as currency.
- [FLOAT](/docs/server/reference/data-types/numeric-data-types/float.md): Single precision floating-point number. A FLOAT column uses 4 bytes and stores approximate values with less precision than DOUBLE.
- [FLOAT4](/docs/server/reference/data-types/numeric-data-types/float4.md): Synonym for FLOAT. This keyword declares a single-precision floating-point column.
- [FLOAT8](/docs/server/reference/data-types/numeric-data-types/float8.md): Synonym for DOUBLE. This keyword declares a double-precision floating-point column.
- [Floating-point Accuracy](/docs/server/reference/data-types/numeric-data-types/floating-point-accuracy.md): Explanation of floating-point precision issues. This page details why FLOAT and DOUBLE types are approximate and how rounding errors occur.
- [INT](/docs/server/reference/data-types/numeric-data-types/int.md): Complete INT type reference: INT(M) syntax, signed (-2147483648 to 2147483647) vs unsigned (0 to 4294967295) ranges, and ZEROFILL padding guidelines.
- [INT1](/docs/server/reference/data-types/numeric-data-types/int1.md): Synonym for TINYINT. This type uses 1 byte of storage.
- [INT2](/docs/server/reference/data-types/numeric-data-types/int2.md): Synonym for SMALLINT. This type uses 2 bytes of storage.
- [INT3](/docs/server/reference/data-types/numeric-data-types/int3.md): Synonym for MEDIUMINT. This type uses 3 bytes of storage.
- [INT4](/docs/server/reference/data-types/numeric-data-types/int4.md): Synonym for INT. This type uses 4 bytes of storage.
- [INT8](/docs/server/reference/data-types/numeric-data-types/int8.md): Synonym for BIGINT. This type uses 8 bytes of storage.
- [INTEGER](/docs/server/reference/data-types/numeric-data-types/integer.md): Synonym for INT. This keyword declares a standard 4-byte integer column.
- [MEDIUMINT](/docs/server/reference/data-types/numeric-data-types/mediumint.md): Medium-sized integer. A MEDIUMINT column uses 3 bytes and stores values from -8388608 to 8388607 (signed) or 0 to 16777215 (unsigned).
- [MIDDLEINT](/docs/server/reference/data-types/numeric-data-types/middleint.md): Synonym for MEDIUMINT. This keyword refers to the 3-byte integer type.
- [NUMBER](/docs/server/reference/data-types/numeric-data-types/number.md): Oracle-compatible synonym for DECIMAL. This type is used for fixed-point arithmetic.
- [NUMERIC](/docs/server/reference/data-types/numeric-data-types/numeric.md): Synonym for DECIMAL. This type stores exact numeric data values.
- [REAL](/docs/server/reference/data-types/numeric-data-types/real.md): Synonym for DOUBLE. In standard SQL mode, REAL is a double-precision floating-point number.
- [SMALLINT](/docs/server/reference/data-types/numeric-data-types/smallint.md): Small integer type. A SMALLINT column uses 2 bytes and stores values from -32768 to 32767 (signed) or 0 to 65535 (unsigned).
- [TINYINT](/docs/server/reference/data-types/numeric-data-types/tinyint.md): Very small integer type. A TINYINT column uses 1 byte and stores values from -128 to 127 (signed) or 0 to 255 (unsigned).
- [Date and Time Data Types](/docs/server/reference/data-types/date-and-time-data-types.md): Store temporal values. This section covers data types for dates, times, and timestamps, including DATE, DATETIME, TIMESTAMP, TIME, and YEAR.
- [DATE](/docs/server/reference/data-types/date-and-time-data-types/date.md): Complete DATE type reference: YYYY-MM-DD format, YYMMDD input literals, date range 1000-01-01 to 9999-12-31, and zero-date SQL\_MODE handling.
- [DATETIME](/docs/server/reference/data-types/date-and-time-data-types/datetime.md): Complete DATETIME data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range limits for production use.
- [SQL\_TSI\_YEAR](/docs/server/reference/data-types/date-and-time-data-types/sql_tsi_year.md): Synonym for YEAR. This keyword is an alias used for declaring a column to store year values.
- [TIME](/docs/server/reference/data-types/date-and-time-data-types/time.md): Store time values. This type handles time durations or time of day, ranging from '-838:59:59' to '838:59:59' with optional microsecond precision.
- [TIMESTAMP](/docs/server/reference/data-types/date-and-time-data-types/timestamp.md): Complete TIMESTAMP data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range limits for production use.
- [YEAR Data Type](/docs/server/reference/data-types/date-and-time-data-types/year-data-type.md): Store year values. This type stores a year in 2-digit or 4-digit format, supporting values from 1901 to 2155, and 0000.
- [String Data Types](/docs/server/reference/data-types/string-data-types.md): Store text and binary data. This section covers character types like CHAR, VARCHAR, and TEXT, as well as binary types like BLOB and BINARY.
- [BLOB and TEXT Data Types](/docs/server/reference/data-types/string-data-types/blob-and-text-data-types.md): Overview of large object types. This page compares BLOB (binary) and TEXT (character) types, explaining their storage and usage differences.
- [BINARY](/docs/server/reference/data-types/string-data-types/binary.md): Fixed-length binary string type. This type stores a fixed number of bytes, padding with zero bytes if the data is shorter.
- [BLOB](/docs/server/reference/data-types/string-data-types/blob.md): Variable-length binary large object. BLOB columns can store binary data up to 65,535 bytes, suitable for images or other non-text files.
- [CHAR](/docs/server/reference/data-types/string-data-types/char.md): Fixed-length character string type. CHAR columns store strings of a specified length (0 to 255), padding with spaces if necessary.
- [CHARACTER](/docs/server/reference/data-types/string-data-types/character.md): Fixed-length character string type. CHARACTER columns store strings of a specified length (0 to 255), padding with spaces if necessary.
- [CHAR BYTE](/docs/server/reference/data-types/string-data-types/char-byte.md): Fixed-length binary string type. This type stores a fixed number of bytes, padding with zero bytes if the data is shorter.
- [CHAR VARYING](/docs/server/reference/data-types/string-data-types/char-varying.md)
- [CLOB](/docs/server/reference/data-types/string-data-types/clob.md): In Oracle mode, CLOB is an alias for the LONGTEXT data type used to store large text objects.
- [ENUM](/docs/server/reference/data-types/string-data-types/enum.md): Complete ENUM type reference: ENUM('v1','v2') syntax, CHARACTER SET/COLLATE options, NULL/empty string defaults, and numeric index sorting guidelines.
- [INET4](/docs/server/reference/data-types/string-data-types/inet4.md): IPv4 address data type. Stores IPv4 addresses as 4-byte binary strings for efficient storage and retrieval.
- [INET6](/docs/server/reference/data-types/string-data-types/inet6.md): IPv6 address data type. Stores IPv6 addresses as 16-byte binary strings, also supporting IPv4 addresses via mapping.
- [JSON Data Type](/docs/server/reference/data-types/string-data-types/json.md): Complete JSON Data Type data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range limits for production use.
- [LONG and LONG VARCHAR](/docs/server/reference/data-types/string-data-types/long-and-long-varchar.md): LONG and LONG VARCHAR are compatibility synonyms for the MEDIUMTEXT string data type.
- [LONG CHAR VARYING](/docs/server/reference/data-types/string-data-types/long-char-varying.md): LONG CHAR VARYING is a compatibility synonym for the MEDIUMTEXT string data type.
- [LONG CHARACTER VARYING](/docs/server/reference/data-types/string-data-types/long-character-varying.md): LONG CHARACTER VARYING is a compatibility synonym for the MEDIUMTEXT string data type.
- [LONG VARBINARY](/docs/server/reference/data-types/string-data-types/long-varbinary.md): LONG VARBINARY is a compatibility synonym for the MEDIUMBLOB binary data type.
- [LONG VARCHAR](/docs/server/reference/data-types/string-data-types/long-varchar.md): LONG VARCHAR is a compatibility synonym for the MEDIUMTEXT string data type.
- [LONG VARCHARACTER](/docs/server/reference/data-types/string-data-types/long-varcharacter.md): LONG VARCHARACTER is a compatibility synonym for the MEDIUMTEXT string data type.
- [LONGBLOB](/docs/server/reference/data-types/string-data-types/longblob.md): Very large binary object. A LONGBLOB column can store up to 4GB of binary data.
- [LONGTEXT](/docs/server/reference/data-types/string-data-types/longtext.md): Complete LONGTEXT type reference: 4GB (2^32-1) storage limit, CHARACTER SET/COLLATE syntax, max\_allowed\_packet constraints, and JSON/CLOB aliases.
- [MEDIUMBLOB](/docs/server/reference/data-types/string-data-types/mediumblob.md): Medium-sized binary object. A MEDIUMBLOB column can store up to 16MB of binary data.
- [MEDIUMTEXT](/docs/server/reference/data-types/string-data-types/mediumtext.md): Medium-sized character string. A MEDIUMTEXT column can store up to 16MB of text data.
- [NATIONAL CHAR](/docs/server/reference/data-types/string-data-types/national-char.md): NATIONAL CHAR is a synonym for the CHAR data type that uses the predefined utf8 character set.
- [NATIONAL CHAR VARYING](/docs/server/reference/data-types/string-data-types/national-char-varying.md): NATIONAL CHAR VARYING is a synonym for VARCHAR that uses the predefined utf8 character set.
- [NATIONAL CHARACTER VARYING](/docs/server/reference/data-types/string-data-types/national-character-varying.md): NATIONAL CHARACTER VARYING is a synonym for VARCHAR using the predefined utf8 character set.
- [NATIONAL CHARACTER](/docs/server/reference/data-types/string-data-types/national-character.md): NATIONAL CHARACTER is a synonym for the CHAR data type using the predefined utf8 character set.
- [NATIONAL VARCHAR](/docs/server/reference/data-types/string-data-types/national-varchar.md): NATIONAL VARCHAR is a synonym for the VARCHAR data type using the predefined utf8 character set.
- [NATIONAL VARCHARACTER](/docs/server/reference/data-types/string-data-types/national-varcharacter.md): NATIONAL VARCHARACTER is a synonym for VARCHAR using the predefined utf8 character set.
- [NCHAR](/docs/server/reference/data-types/string-data-types/nchar.md): NCHAR is a synonym for the fixed-length CHAR string data type using the utf8 character set.
- [NCHAR VARCHAR](/docs/server/reference/data-types/string-data-types/nchar-varchar.md): NCHAR VARCHAR is a synonym for the VARCHAR string data type using the utf8 character set.
- [NCHAR VARCHARACTER](/docs/server/reference/data-types/string-data-types/nchar-varcharacter.md): NCHAR VARCHARACTER is a synonym for VARCHAR using the utf8 character set.
- [NCHAR VARYING](/docs/server/reference/data-types/string-data-types/nchar-varying.md): NCHAR VARYING is a synonym for the VARCHAR string data type using the utf8 character set.
- [RAW](/docs/server/reference/data-types/string-data-types/raw.md): In Oracle mode, RAW is a variable-length binary data type synonymous with VARBINARY.
- [ROW](/docs/server/reference/data-types/string-data-types/row.md): ROW is a data type used in stored programs to store a complete row of data from a cursor or table.
- [SET Data Type](/docs/server/reference/data-types/string-data-types/set-data-type.md): String object with zero or more values from a predefined list. A SET column can store multiple values selected from a list of permitted strings.
- [TEXT](/docs/server/reference/data-types/string-data-types/text.md): Complete TEXT type reference: TEXT(M) syntax, 65,535 byte maximum, 2-byte length prefix, DEFAULT value support, and indexing constraints rules.
- [TINYBLOB](/docs/server/reference/data-types/string-data-types/tinyblob.md): Very small binary object. A TINYBLOB column can store up to 255 bytes of binary data.
- [TINYTEXT](/docs/server/reference/data-types/string-data-types/tinytext.md): Very small character string. A TINYTEXT column can store up to 255 characters.
- [UUID Data Type](/docs/server/reference/data-types/string-data-types/uuid-data-type.md): Official UUID data type reference: 128-bit storage optimization, CAST from CHAR/VARCHAR/BINARY types, RFC4122 string format, and UUIDv6/v7 support.
- [VARBINARY](/docs/server/reference/data-types/string-data-types/varbinary.md): Variable-length binary string type. VARBINARY columns store binary strings of variable length up to a specified maximum.
- [VARCHAR](/docs/server/reference/data-types/string-data-types/varchar.md): Complete VARCHAR reference: VARCHAR(M) syntax, length limits (0-65532 per row), CHARACTER SET/COLLATE options, indexing rules, and trailing spaces.
- [VARCHAR2](/docs/server/reference/data-types/string-data-types/varchar2.md): Variable-length character string type. VARCHAR2 columns store strings of variable length up to a specified maximum (up to 65,535).
- [VARCHARACTER](/docs/server/reference/data-types/string-data-types/varcharacter.md): Variable-length character string type. VARCHARACTER columns store strings of variable length up to a specified maximum (up to 65,535).
- [XMLTYPE](/docs/server/reference/data-types/string-data-types/xmltype.md)
- [Character Sets and Collations](/docs/server/reference/data-types/string-data-types/character-sets.md): Learn about character sets in MariaDB Server. This section details how different character sets and collations impact string storage, comparison, and sorting within your database.
- [Character Set and Collation Overview](/docs/server/reference/data-types/string-data-types/character-sets/character-set-and-collation-overview.md): Learn the core concepts of character sets and collations in MariaDB, including how they define string storage and sorting rules.
- [Setting Character Sets and Collations](/docs/server/reference/data-types/string-data-types/character-sets/setting-character-sets-and-collations.md): Complete Setting Character Sets and Collations data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range.
- [Supported Character Sets and Collations](/docs/server/reference/data-types/string-data-types/character-sets/supported-character-sets-and-collations.md): Complete character sets reference: SHOW CHARACTER SET command, information\_schema.CHARACTER\_SETS/COLLATIONS tables, NO PAD queries, and ci/cs flags.
- [Unicode](/docs/server/reference/data-types/string-data-types/character-sets/unicode.md): Explore MariaDB's support for Unicode, covering the differences between the utf8mb3 and utf8mb4 character sets for multi-byte storage.
- [Internationalization and Localization](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization.md): Discover how MariaDB supports internationalization and localization, enabling databases to store and process data in multiple languages.
- [Coordinated Universal Time](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization/coordinated-universal-time.md): Coordinated Universal Time (UTC) is the primary time standard by which the world regulates clocks and time, and is the internal storage format for MariaDB timestamp values.
- [Locales Plugin](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization/locales-plugin.md): The LOCALES plugin enables the INFORMATION\_SCHEMA.LOCALES table and SHOW LOCALES statement, allowing users to view all locales compiled into the server.
- [Server Locale](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization/server-locale.md): Server locale settings control the language for date and time functions via lc\_time\_names and the language for error messages via lc\_messages.
- [Setting the Language for Error Messages](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization/setting-the-language-for-error-messages.md): Learn how to configure the lc\_messages and lc\_messages\_dir system variables to display server error messages in a supported local language.
- [Time Zones](/docs/server/reference/data-types/string-data-types/character-sets/internationalization-and-localization/time-zones.md): Complete Time Zones data type guide for MariaDB. Complete reference for syntax, valid values, storage requirements, and range limits for production use.
- [Plugins](/docs/server/reference/plugins.md): Explore plugins in MariaDB Server. This section details how to extend database functionality, security, and performance by leveraging various loadable plugins, from authentication to storage engines.
- [Plugin Overview](/docs/server/reference/plugins/plugin-overview.md): MariaDB supports loading plugins at startup or runtime to extend functionality, including storage engines, security features, and logging capabilities, without rebuilding the server.
- [Plugin Maturity](/docs/server/reference/plugins/list-of-plugins.md): This page lists the maturity level (Alpha, Beta, Gamma, Stable) of various MariaDB plugins, helping users determine which are suitable for production environments.
- [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-enterprise-audit.md): The MariaDB Enterprise Audit plugin logs detailed data access and configuration changes, offering advanced filtering to meet security and compliance requirements.
- [MariaDB Community Audit Plugin](/docs/server/reference/plugins/mariadb-audit-plugin.md): Complete MariaDB Audit Plugin reference: server\_audit activity logging, connection/query event tracking, file/syslog output, and compliance configuration.
- [Audit Plugin Overview](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-overview.md): The MariaDB Audit Plugin records server activity, including connections, queries, and table access, to help meet organizational auditing and compliance regulations.
- [Audit Plugin Installation](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-installation.md): Follow this guide to install the Audit Plugin on your MariaDB server. Learn how to verify the plugin file's location, load it dynamically, or configure it to load automatically at startup.
- [Audit Plugin Configuration](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-configuration.md): Configure the Audit Plugin to suit your monitoring requirements. Learn how to enable logging, select specific event types to record, and exclude specific users from the audit trail.
- [Audit Plugin Log Settings](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-log-settings.md): Control where and how the audit data is stored. This section explains how to direct output to a file or the system syslog, and how to configure logging parameters for different environments.
- [Audit Plugin Location and Rotation of Logs](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-location-and-rotation-of-logs.md): Manage your audit log files effectively. Learn how to define the log file path, set size limits, and configure rotation strategies to prevent log files from consuming all available disk space.
- [Audit Plugin Log Format](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-log-format.md): Understand the structure of audit log entries. This guide breaks down the fields in the log records, including timestamps, server IDs, user details, and the specific operations performed.
- [Audit Plugin Options and System Variables](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-options-and-system-variables.md): Browse the complete reference of system variables for the Audit Plugin. Use these settings to fine-tune logging behavior, control performance impact, and manage log file handling.
- [Audit Plugin Status Variables](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-status-variables.md): Monitor the performance and status of the Audit Plugin. View variables that track the number of logged events and current settings to ensure the auditing system is functioning correctly.
- [Audit Plugin Versions](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-versions.md): Review the version history of the MariaDB Audit Plugin. Check compatibility with different MariaDB Server releases and identify which features or bug fixes are included in each version.
- [Authentication Plugins](/docs/server/reference/plugins/authentication-plugins.md): Explore the authentication plugins available in MariaDB, such as ed25519, GSSAPI, and PAM, which provide flexible and secure methods for user verification.
- [Pluggable Authentication Overview](/docs/server/reference/plugins/authentication-plugins/pluggable-authentication-overview.md): Pluggable authentication allows MariaDB to use various authentication methods, enabling external validation, different hashing algorithms, and role-based access control.
- [Authentication Plugin - caching\_sha2\_password](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-caching_sha2_password.md)
- [Authentication Plugin - ed25519](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-ed25519.md): The ed25519 authentication plugin provides high-security password authentication using the Elliptic Curve Digital Signature Algorithm, a modern alternative to SHA-1.
- [Authentication Plugin - GSSAPI](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-gssapi.md): Complete GSSAPI authentication setup: Kerberos/SSPI single sign-on, INSTALL SONAME 'auth\_gssapi', gssapi\_keytab\_path/principal\_name, CREATE USER syntax.
- [Authentication Plugin - mysql\_native\_password](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-mysql_native_password.md): Complete Authentication Plugin - mysql\_native\_password guide for MariaDB. Complete reference documentation for implementation, configuration, and usage.
- [Authentication Plugin - mysql\_old\_password](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-mysql_old_password.md): This plugin provides backward compatibility for pre-4.1 clients using an older, insecure password hashing algorithm and should not be used for new installations.
- [Authentication Plugin - Named Pipe](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-named-pipe.md): The named\_pipe authentication plugin allows Windows users connecting via named pipes to authenticate using their operating system credentials without a password.
- [Authentication Plugin - PARSEC](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-parsec.md): PARSEC is a modern, secure authentication plugin that uses salted passwords and elliptic curve cryptography to prevent replay attacks and secure user credentials.
- [Authentication Plugin - SHA-256](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-sha-256.md): The SHA-256 authentication plugin uses the SHA-256 hashing algorithm for password storage, offering stronger security than the default SHA-1 method.
- [Authentication Plugin - Unix Socket](/docs/server/reference/plugins/authentication-plugins/authentication-plugin-unix-socket.md): Official Unix socket authentication: OS user login via SO\_PEERCRED/uid matching, CREATE USER IDENTIFIED VIA unix\_socket, and unix\_socket force modes.
- [Authentication with Pluggable Authentication Modules (PAM)](/docs/server/reference/plugins/authentication-plugins/authentication-with-pluggable-authentication-modules-pam.md): Learn about authentication with Pluggable Authentication Modules (PAM) in MariaDB Server. This section details how to integrate MariaDB with PAM for centralized and flexible user authentication.
- [Authentication Plugin - PAM](/docs/server/reference/plugins/authentication-plugins/authentication-with-pluggable-authentication-modules-pam/authentication-plugin-pam.md): The PAM authentication plugin delegates password validation to the operating system's PAM framework, enabling integration with LDAP, Kerberos, and other services.
- [Configuring PAM Authentication and User Mapping with LDAP Authentication](/docs/server/reference/plugins/authentication-plugins/authentication-with-pluggable-authentication-modules-pam/configuring-pam-authentication-and-user-mapping-with-ldap-authentication.md): Learn to configure the PAM plugin to authenticate users via LDAP and map LDAP groups to MariaDB accounts using the pam\_user\_map module.
- [Configuring PAM Authentication and User Mapping with Unix Authentication](/docs/server/reference/plugins/authentication-plugins/authentication-with-pluggable-authentication-modules-pam/configuring-pam-authentication-and-user-mapping-with-unix-authentication.md): This guide shows how to authenticate database users using local Unix accounts and map Unix groups to MariaDB users with the PAM plugin.
- [User and Group Mapping with PAM](/docs/server/reference/plugins/authentication-plugins/authentication-with-pluggable-authentication-modules-pam/user-and-group-mapping-with-pam.md): The pam\_user\_map PAM module allows administrators to map external PAM users and groups to specific MariaDB accounts for flexible authorization management.
- [MariaDB Replication & Cluster Plugins](/docs/server/reference/plugins/mariadb-replication-cluster-plugins.md): This section covers plugins specifically designed for high availability and clustering, including the wsrep\_provider plugin used for Galera Cluster integration.
- [WSREP\_INFO Plugin](/docs/server/reference/plugins/mariadb-replication-cluster-plugins/wsrep_info-plugin.md): The WSREP\_INFO plugin adds the WSREP\_MEMBERSHIP and WSREP\_STATUS tables to the Information Schema, providing detailed insights into Galera Cluster membership and status.
- [wsrep\_provider](/docs/server/reference/plugins/mariadb-replication-cluster-plugins/wsrep_provider.md): The wsrep\_provider plugin exposes Galera Cluster provider options as individual system variables, allowing for easier configuration and validation of cluster settings.
- [Other Plugins](/docs/server/reference/plugins/other-plugins.md): Discover additional plugins that extend MariaDB Server functionality, such as the Disks, Feedback, and Query Response Time plugins, for specialized use cases.
- [Disks Plugin](/docs/server/reference/plugins/other-plugins/disks-plugin.md): The Disks plugin adds the DISKS table to the Information Schema, providing metadata about the system's disk storage and usage.
- [Feedback Plugin](/docs/server/reference/plugins/other-plugins/feedback-plugin.md): The Feedback plugin collects and sends anonymous server usage and configuration data to MariaDB to help improve the software.
- [inet4](/docs/server/reference/plugins/other-plugins/inet4.md): The inet4 plugin provides the INET4 data type, allowing for efficient native storage and manipulation of IPv4 addresses as 4-byte binary strings.
- [METADATA\_LOCK\_INFO Plugin](/docs/server/reference/plugins/other-plugins/metadata-lock-info-plugin.md): This plugin creates the METADATA\_LOCK\_INFO table in the Information Schema, allowing users to view active metadata locks and their owners.
- [MYSQL\_JSON](/docs/server/reference/plugins/other-plugins/mysql_json.md): The MYSQL\_JSON plugin provides a JSON data type alias for compatibility, ensuring that tables created with the MySQL JSON type can be read by MariaDB.
- [mhnsw](/docs/server/reference/plugins/other-plugins/mhnsw.md): The mhnsw plugin implements the Hierarchical Navigable Small World algorithm, enabling high-performance approximate nearest neighbor search for vector data.
- [online\_alter\_log](/docs/server/reference/plugins/other-plugins/online_alter_log.md): The online\_alter\_log plugin provides logging capabilities for online ALTER TABLE operations, helping administrators monitor and debug schema changes.
- [Query Cache Information Plugin](/docs/server/reference/plugins/other-plugins/query-cache-information-plugin.md): This plugin exposes the contents of the query cache via the QUERY\_CACHE\_INFO table in the Information Schema, aiding in performance analysis.
- [Query Response Time Plugin](/docs/server/reference/plugins/other-plugins/query-response-time-plugin.md): The Query Response Time plugin collects and displays the distribution of query execution times, helping to identify performance bottlenecks.
- [User Variables Plugin](/docs/server/reference/plugins/other-plugins/user-variables-plugin.md): The User Variables plugin adds the USER\_VARIABLES table to the Information Schema, allowing users to inspect defined user variables and their values.
- [Password Validation Plugins](/docs/server/reference/plugins/password-validation-plugins.md): Password validation plugins, like simple\_password\_check and cracklib, enforce strong password policies by checking new passwords against defined complexity rules.
- [Password Validation Plugin Overview](/docs/server/reference/plugins/password-validation-plugins/password-validation.md): General introduction into plugins that enforce specific security policies and complexity rules for user passwords.
- [Cracklib Password Check Plugin](/docs/server/reference/plugins/password-validation-plugins/cracklib-password-check-plugin.md): The Cracklib Password Check Plugin enforces password strength by validating new passwords against the CrackLib library and its dictionary.
- [Password Reuse Check Plugin](/docs/server/reference/plugins/password-validation-plugins/password-reuse-check-plugin.md): The Password Reuse Check Plugin prevents users from reusing previous passwords, with a retention policy controlled by the password\_reuse\_check\_interval variable.
- [password\_reuse\_check\_interval Variable](/docs/server/reference/plugins/password-validation-plugins/password_reuse_check_interval.md): This system variable defines the retention period in days for the password history used by the Password Reuse Check Plugin to prevent reuse.
- [Simple Password Check Plugin](/docs/server/reference/plugins/password-validation-plugins/simple-password-check-plugin.md): The Simple Password Check Plugin enforces basic password complexity rules, such as minimum length and required numbers of digits, letters, and special characters.
- [System Tables](/docs/server/reference/system-tables.md): Explore system tables in MariaDB Server. These internal tables store metadata and configuration information about the database, essential for administration, monitoring, and advanced querying.
- [Information Schema](/docs/server/reference/system-tables/information-schema.md): Query information\_schema.tables in MariaDB Server. This system table provides metadata about all tables in the databases, including their names, types, storage engines, and other crucial properties.
- [TIME\_MS column in INFORMATION\_SCHEMA.PROCESSLIST](/docs/server/reference/system-tables/information-schema/time_ms-column-in-information_schemaprocesslist.md): The TIME\_MS column in the INFORMATION\_SCHEMA.PROCESSLIST table displays the time a thread has been in its current state in milliseconds, offering higher precision than the standard TIME column.
- [Information Schema Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables.md): Query information\_schema.tables in MariaDB Server. These system tables provides metadata about all tables in the databases, including their names, types, storage engines, and other crucial properties.
- [Information Schema ALL\_PLUGINS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/all-plugins-table-information-schema.md): The Information Schema ALL\_PLUGINS table contains information about server plugins, whether installed or not, providing a superset of SHOW PLUGINS SONAME.
- [Information Schema APPLICABLE\_ROLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-applicable_roles-table.md): The Information Schema APPLICABLE\_ROLES table shows the role authorizations that the current user may use, detailing grantable and default status.
- [Information Schema CATALOG Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-catalog-table.md): The Information Schema CATALOG table stores information about catalogs on the server, including default character sets and collations.
- [Information Schema CHARACTER\_SETS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-character_sets-table.md): The Information Schema CHARACTER\_SETS table contains a list of supported character sets, their default collations, and maximum lengths.
- [Information Schema CHECK\_CONSTRAINTS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-check_constraints-table.md): The Information Schema CHECK\_CONSTRAINTS table stores metadata about the constraints defined for tables in all databases, including the check clause.
- [Information Schema CLIENT\_STATISTICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-client_statistics-table.md): The Information Schema CLIENT\_STATISTICS table holds statistics about client connections, such as total connections, bytes sent/received, and command counts.
- [Information Schema COLLATION\_CHARACTER\_SET\_APPLICABILITY Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-collation_character_set_applicability-table.md): The Information Schema COLLATION\_CHARACTER\_SET\_APPLICABILITY table maps which character sets are associated with which collations.
- [Information Schema COLLATIONS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-collations-table.md): The Information Schema COLLATIONS table contains a list of supported collations, indicating their associated character sets and compilation status.
- [Information Schema COLUMN\_PRIVILEGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-column_privileges-table.md): The Information Schema COLUMN\_PRIVILEGES table contains column privilege information derived from the mysql.columns\_priv grant table.
- [Information Schema COLUMNS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-columns-table.md): The Information Schema COLUMNS table provides information about columns in each table on the server, including data types, defaults, and nullability.
- [Information Schema DISKS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-disks-table.md): The Information Schema DISKS table, created by the DISKS plugin, displays metadata such as total and available space for disks on the system.
- [Information Schema ENABLED\_ROLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-enabled_roles-table.md): The Information Schema ENABLED\_ROLES table lists all roles that are currently enabled for the current session, including nested roles.
- [Information Schema ENGINES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-engines-table.md): The Information Schema ENGINES table displays status information about the server's storage engines, including support level and transaction capabilities.
- [Information Schema EVENTS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-events-table.md): The Information Schema EVENTS table stores information about scheduled events on the server, including their timing, definition, and status.
- [Information Schema FEEDBACK Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-feedback-table.md): The Information Schema FEEDBACK table is created when the Feedback Plugin is enabled and contains the usage data collected for submission.
- [Information Schema FILE\_KEY\_MANAGEMENT\_KEYS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-file_key_management_keys.md): The Information Schema FILES table provides information about files stored in tablespaces, such as those used by the InnoDB storage engine.
- [Information Schema HASHICORP\_KEY\_MANAGEMENT\_CACHE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-hashicorp_key_management_cache.md): The Information Schema HASHICORP\_KEY\_MANAGEMENT\_CACHE table provides information about keys managed by the HashiCorp Key Management plugin.
- [Information Schema GEOMETRY\_COLUMNS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-geometry_columns-table.md): The Information Schema GEOMETRY\_COLUMNS table describes the geometry columns in tables, providing details on spatial reference systems and geometry types.
- [Information Schema GLOBAL\_STATUS and SESSION\_STATUS Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-global_status-and-session_status-tables.md): The GLOBAL\_STATUS and SESSION\_STATUS tables store the global and session values of server status variables, respectively.
- [Information Schema GLOBAL\_VARIABLES and SESSION\_VARIABLES Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-global_variables-and-session_variables-tables.md): The GLOBAL\_VARIABLES and SESSION\_VARIABLES tables store the global and session values of all system variables, respectively.
- [Information Schema INDEX\_STATISTICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-index_statistics-table.md): The Information Schema INDEX\_STATISTICS table provides statistics on index usage, helping to identify unused indexes and optimize performance.
- [Information Schema KEY\_CACHES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-key_caches-table.md): The Information Schema KEY\_CACHES table displays statistics about the segmented key cache, including block usage and read/write requests.
- [Information Schema KEY\_COLUMN\_USAGE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-key_column_usage-table.md): The Information Schema KEY\_COLUMN\_USAGE table details which columns in a table are constrained by keys, such as primary or foreign keys.
- [Information Schema KEY\_PERIOD\_USAGE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-key_period_usage-table.md): The Information Schema KEY\_PERIOD\_USAGE table describes how keys reference application-time periods, detailing constraints involving those periods.
- [Information Schema KEYWORDS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-keywords-table.md): The Information Schema KEYWORDS table contains a complete list of reserved and non-reserved keywords recognized by the MariaDB server.
- [Information Schema LOCALES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-locales-table.md): The Information Schema LOCALES table lists all compiled-in locales available to the server, providing their IDs, names, and descriptions.
- [Information Schema METADATA\_LOCK\_INFO Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-metadata_lock_info-table.md): The Information Schema METADATA\_LOCK\_INFO table shows active metadata locks and user locks, helping to diagnose locking conflicts.
- [Information Schema MROONGA\_STATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-mroonga_stats-table.md): The Information Schema MROONGA\_STATS table provides statistical information specific to the Mroonga full-text search storage engine.
- [Information Schema OPTIMIZER\_TRACE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-optimizer_trace-table.md): The Information Schema OPTIMIZER\_TRACE table contains details about the optimizer's decision-making process for the last executed query.
- [Information Schema PARAMETERS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-parameters-table.md): The Information Schema PARAMETERS table stores information about parameters for stored procedures and functions, including data types and modes.
- [Information Schema PARTITIONS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-partitions-table.md): The Information Schema PARTITIONS table provides detailed metadata about table partitions, including partition methods and data distribution.
- [Information Schema PERIODS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-periods-table.md): The Information Schema PERIODS table provides information about Application-Time Periods, detailing the start and end columns for system versioning.
- [Information Schema PLUGINS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/plugins-table-information-schema.md): The Information Schema PLUGINS table contains information about server plugins, including their status, type, and library paths.
- [Information Schema PROCESSLIST Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-processlist-table.md): The Information Schema PROCESSLIST table contains detailed information about running threads, including their current state and execution time.
- [Information Schema PROFILING Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-profiling-table.md): The Information Schema PROFILING table provides statement resource usage details, such as CPU time and block operations, when profiling is enabled.
- [Information Schema QUERY\_CACHE\_INFO Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-query_cache_info-table.md): The Information Schema QUERY\_CACHE\_INFO table shows all queries currently stored in the query cache, aiding in cache performance analysis.
- [Information Schema QUERY\_RESPONSE\_TIME Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-query_response_time-table.md): The Information Schema QUERY\_RESPONSE\_TIME table displays the distribution of query execution times, helping to identify performance bottlenecks.
- [Information Schema REFERENTIAL\_CONSTRAINTS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-referential_constraints-table.md): The Information Schema REFERENTIAL\_CONSTRAINTS table contains metadata about foreign keys, including update and delete rules.
- [Information Schema ROUTINES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-routines-table.md): The Information Schema ROUTINES table stores information about stored procedures and stored functions, including their definitions and properties.
- [Information Schema SCHEMA\_PRIVILEGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-schema_privileges-table.md): The Information Schema SCHEMA\_PRIVILEGES table contains information about database-level privileges granted to accounts.
- [Information Schema SCHEMATA Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-schemata-table.md): The Information Schema SCHEMATA table stores information about databases on the server, including default character sets and collations.
- [Information Schema SEQUENCES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-sequences-table.md): The Information Schema SEQUENCES table provides metadata about sequence objects, including their minimum, maximum, and current values.
- [Information Schema SLAVE\_STATUS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-slave_status-table.md): The Information Schema SLAVE\_STATUS table displays status information for the replication slave threads, similar to SHOW SLAVE STATUS.
- [Information Schema SPATIAL\_REF\_SYS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-spatial_ref_sys-table.md): The Information Schema SPATIAL\_REF\_SYS table stores information about available Spatial Reference Systems (SRS) for geometry data.
- [Information Schema SPIDER\_ALLOC\_MEM Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-spider_alloc_mem-table.md): The Information Schema SPIDER\_ALLOC\_MEM table tracks memory allocation for the Spider storage engine, aiding in resource monitoring.
- [Information Schema SQL\_FUNCTIONS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-sql_functions-table.md): The Information Schema SQL\_FUNCTIONS table lists all available SQL functions, including built-in functions and user-defined functions.
- [Information Schema STATISTICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-statistics-table.md): The Information Schema STATISTICS table provides information about table indexes, serving as a standard-compliant alternative to SHOW INDEX.
- [Information Schema SYSTEM\_VARIABLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-system_variables-table.md): The Information Schema SYSTEM\_VARIABLES table contains all system variables and their current global or session values.
- [Information Schema TABLE\_CONSTRAINTS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-table_constraints-table.md): The Information Schema TABLE\_CONSTRAINTS table describes constraints on tables, such as PRIMARY KEY, UNIQUE, and FOREIGN KEY constraints.
- [Information Schema TABLE\_PRIVILEGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-table_privileges-table.md): The Information Schema TABLE\_PRIVILEGES table lists privileges granted specifically at the table level.
- [Information Schema TABLE\_STATISTICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-table_statistics-table.md): The Information Schema TABLE\_STATISTICS table provides usage statistics for tables, such as the number of rows read or changed.
- [Information Schema TABLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-tables-table.md): Complete Information Schema TABLES reference: TABLE\_ROWS, DATA\_LENGTH/INDEX\_LENGTH, CREATE\_TIME/UPDATE\_TIME columns, TEMPORARY='Y', and WHERE clause queries.
- [Information Schema TABLESPACES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-tablespaces-table.md): The Information Schema TABLESPACES table provides information about active tablespaces, specifically for the InnoDB storage engine.
- [Information Schema THREAD\_POOL\_GROUPS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-thread_pool_groups-table.md): The Information Schema THREAD\_POOL\_GROUPS table provides details about the thread groups in the thread pool, including active thread counts.
- [Information Schema THREAD\_POOL\_QUEUES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-thread_pool_queues-table.md): The Information Schema THREAD\_POOL\_QUEUES table shows the status of the queues within the thread pool, detailing pending connections.
- [Information Schema THREAD\_POOL\_STATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-thread_pool_stats-table.md): The Information Schema THREAD\_POOL\_STATS table provides performance statistics for the thread pool, such as thread creation and efficiency.
- [Information Schema THREAD\_POOL\_WAITS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-thread_pool_waits-table.md): The Information Schema THREAD\_POOL\_WAITS table lists the number of times threads in the thread pool have waited for various events.
- [Information Schema TRIGGERED\_UPDATE\_COLUMNS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-triggered_update_columns.md): The Information Schema TRIGGERED\_UPDATE\_COLUMNS table identifies which columns are modified by the SET clause of a specific trigger.
- [Information Schema TRIGGERS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-triggers-table.md): The Information Schema TRIGGERS table contains detailed information about triggers, including the event, timing, and action statement.
- [Information Schema USER\_PRIVILEGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-user_privileges-table.md): The Information Schema USER\_PRIVILEGES table lists global privileges granted to user accounts, derived from the mysql.user table.
- [Information Schema USER\_STATISTICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-user_statistics-table.md): The Information Schema USER\_STATISTICS table provides activity statistics for users, such as bytes sent and rows read, aiding in auditing.
- [Information Schema USER\_VARIABLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-user_variables-table.md): The Information Schema USERS\_VARIABLES table lists user accounts, including whether they are global or local, and details about their password expiration.
- [Information Schema USERS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-users-table.md): The Information Schema USERS table lists user accounts, including whether they are global or local, and details about their password expiration.
- [Information Schema WSREP\_BF\_ABORTS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_bf_aborts.md): The Information Schema WSREP\_BF\_ABORTS table provides statistics on Galera Cluster brute force aborts, detailing the victim and transaction IDs.
- [Information Schema WSREP\_CERT\_KEYS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_cert_keys.md): The Information Schema WSREP\_CERT\_KEYS table displays the certification keys for transactions currently being processed by the Galera Cluster.
- [Information Schema WSREP\_CERT\_KEYS\_HISTORY](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_cert_keys_history.md): The Information Schema WSREP\_CERT\_KEYS\_HISTORY table logs a history of certification keys for recently processed Galera transactions.
- [Information Schema WSREP\_CONNECTIONS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_connections.md): The Information Schema WSREP\_CONNECTIONS table shows active connections to the Galera Cluster, primarily used for debugging cluster membership.
- [Information Schema WSREP\_MEMBERSHIP Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_membership-table.md): The Information Schema WSREP\_MEMBERSHIP table lists the current members of the Galera Cluster, including their node UUIDs, names, and IP addresses.
- [Information Schema WSREP\_STATUS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_status-table.md): The Information Schema WSREP\_STATUS table provides a comprehensive view of the Galera Cluster status variables, similar to SHOW STATUS LIKE 'wsrep%'
- [Information Schema WSREP\_THD\_STATE](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_thd_state.md): The Information Schema WSREP\_THD\_STATE table displays the internal state of Galera threads, helping to monitor replication progress and locking.
- [Information Schema WSREP\_THD\_STATE\_HISTORY](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-wsrep_thd_state_history.md): The Information Schema WSREP\_THD\_STATE\_HISTORY table maintains a history of thread states for Galera replication, aiding in post-incident analysis.
- [Information Schema InnoDB Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables.md): These system tables provide detailed metadata about InnoDB tables, including their structure, storage, and other crucial properties for analysis.
- [Information Schema INNODB\_CMP\_PER\_INDEX and INNODB\_CMP\_PER\_INDEX\_RESET Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb-tables-information-schema-innodb_cmp_per_index-an.md): These tables provide status information on compression operations for XtraDB/InnoDB tables, grouped by individual indexes.
- [Information Schema INNODB\_BUFFER\_PAGE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_page-table.md): The Information Schema INNODB\_BUFFER\_PAGE table contains detailed information about each page currently in the InnoDB buffer pool.
- [Information Schema INNODB\_BUFFER\_PAGE\_LRU Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_page_lru-table.md): The Information Schema INNODB\_BUFFER\_PAGE\_LRU table details pages in the buffer pool and their position in the LRU eviction list.
- [Information Schema INNODB\_BUFFER\_POOL\_PAGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_pool_pages-table.md): The Information Schema INNODB\_BUFFER\_POOL\_PAGES table provides a record for each page in the buffer pool, specific to the XtraDB engine.
- [Information Schema INNODB\_BUFFER\_POOL\_PAGES\_BLOB Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_pool_pages_blob-table.md): The INNODB\_BUFFER\_POOL\_PAGES\_BLOB table contains information about blob pages in the buffer pool, only available for XtraDB.
- [Information Schema INNODB\_BUFFER\_POOL\_PAGES\_INDEX Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_pool_pages_index-table.md): The INNODB\_BUFFER\_POOL\_PAGES\_INDEX table provides information about index pages in the buffer pool, specific to the XtraDB engine.
- [Information Schema INNODB\_BUFFER\_POOL\_STATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_buffer_pool_stats-table.md): The Information Schema INNODB\_BUFFER\_POOL\_STATS table displays high-level statistics about the InnoDB buffer pool's activity.
- [Information Schema INNODB\_CHANGED\_PAGES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_changed_pages-table.md): The Information Schema INNODB\_CHANGED\_PAGES table lists pages that have been modified since a specific checkpoint.
- [Information Schema INNODB\_CMP and INNODB\_CMP\_RESET Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_cmp-and-innodb_cmp_reset-tables.md): These tables contain status information on compression operations for compressed XtraDB/InnoDB tables, detailing compress and uncompress ops.
- [Information Schema INNODB\_CMPMEM and INNODB\_CMPMEM\_RESET Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_cmpmem-and-innodb_cmpmem_reset-tables.md): These tables provide status statistics on compressed pages within the buffer pool, useful for analyzing compression efficiency.
- [Information Schema INNODB\_FT\_BEING\_DELETED Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_being_deleted-table.md): This table is used only during an OPTIMIZE TABLE operation to store the document IDs of rows currently being deleted from an InnoDB FULLTEXT index.
- [Information Schema INNODB\_FT\_CONFIG Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_config-table.md): The Information Schema INNODB\_FT\_CONFIG table displays metadata about the configuration of an InnoDB FULLTEXT index, such as the internal cache size.
- [Information Schema INNODB\_FT\_DEFAULT\_STOPWORD Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_default_stopword-table.md): The INNODB\_FT\_DEFAULT\_STOPWORD table lists the default stop words used by InnoDB FULLTEXT indexes when no custom stopword list is defined.
- [Information Schema INNODB\_FT\_DELETED Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_deleted-table.md): The INNODB\_FT\_DELETED table lists document IDs of rows that have been deleted from an InnoDB FULLTEXT index but not yet removed from the index files.
- [Information Schema INNODB\_FT\_INDEX\_CACHE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_index_cache-table.md): The INNODB\_FT\_INDEX\_CACHE table displays token information from newly inserted rows in a FULLTEXT index before the data is flushed to disk.
- [Information Schema INNODB\_FT\_INDEX\_TABLE Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_ft_index_table-table.md): The INNODB\_FT\_INDEX\_TABLE table provides information about the inverted index (tokens and positions) for an InnoDB FULLTEXT index currently in use.
- [Information Schema INNODB\_LOCK\_WAITS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_lock_waits-table.md): The Information Schema INNODB\_LOCK\_WAITS table maps blocked transactions to the transactions that are blocking them, aiding in deadlock analysis.
- [Information Schema INNODB\_LOCKS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_locks-table.md): The INNODB\_LOCKS table provides information about locks that a transaction has requested but not yet obtained, or locks that are blocking another transaction.
- [Information Schema INNODB\_METRICS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_metrics-table.md): The Information Schema INNODB\_METRICS table contains a wide range of low-level performance metrics and counters for the InnoDB storage engine.
- [Information Schema INNODB\_MUTEXES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_mutexes-table.md): The Information Schema INNODB\_MUTEXES table displays statistics about InnoDB mutex and read-write lock waits, helping to identify internal contention.
- [Information Schema INNODB\_SYS\_COLUMNS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_columns-table.md): The INNODB\_SYS\_COLUMNS table contains metadata about InnoDB table columns, derived directly from the internal InnoDB data dictionary.
- [Information Schema INNODB\_SYS\_DATAFILES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_datafiles-table.md): The INNODB\_SYS\_DATAFILES table, now deprecated and removed, was intended to provide metadata for InnoDB tablespace paths.
- [Information Schema INNODB\_SYS\_FIELDS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_fields-table.md): The INNODB\_SYS\_FIELDS table lists the fields that comprise InnoDB indexes, detailing their position within the index structure.
- [Information Schema INNODB\_SYS\_FOREIGN Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_foreign-table.md): The INNODB\_SYS\_FOREIGN table provides metadata about foreign key constraints defined on InnoDB tables, including reference details.
- [Information Schema INNODB\_SYS\_FOREIGN\_COLS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_foreign_cols-table.md): The INNODB\_SYS\_FOREIGN\_COLS table maps columns to their respective foreign key constraints within the InnoDB storage engine.
- [Information Schema INNODB\_SYS\_INDEXES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_indexes-table.md): The INNODB\_SYS\_INDEXES table provides metadata about InnoDB indexes, including the table they belong to, unique IDs, and type.
- [Information Schema INNODB\_SYS\_SEMAPHORE\_WAITS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_semaphore_waits-table.md): The INNODB\_SYS\_SEMAPHORE\_WAITS table displays threads currently waiting for semaphores, which is useful for debugging high-concurrency contention.
- [Information Schema INNODB\_SYS\_TABLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_tables-table.md): The INNODB\_SYS\_TABLES table exposes the internal InnoDB data dictionary metadata for tables, including row formats and space IDs.
- [Information Schema INNODB\_SYS\_TABLESPACES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_tablespaces-table.md): The INNODB\_SYS\_TABLESPACES table provides metadata about the tablespaces used by InnoDB, including space ID, page size, and filename.
- [Information Schema INNODB\_SYS\_TABLESTATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_tablestats-table.md): The INNODB\_SYS\_TABLESTATS table offers low-level performance statistics for InnoDB tables, such as row counts and modification counters.
- [Information Schema INNODB\_SYS\_VIRTUAL Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_sys_virtual-table.md): The INNODB\_SYS\_VIRTUAL table contains metadata about the base columns of virtual generated columns in InnoDB tables.
- [Information Schema INNODB\_TABLESPACES\_ENCRYPTION Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_tablespaces_encryption-table.md): The INNODB\_TABLESPACES\_ENCRYPTION table provides metadata about encrypted InnoDB tablespaces, including key versions and rotation status.
- [Information Schema INNODB\_TABLESPACES\_SCRUBBING Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_tablespaces_scrubbing-table.md): The INNODB\_TABLESPACES\_SCRUBBING table contains statistics about background data scrubbing processes for InnoDB tablespaces.
- [Information Schema INNODB\_TRX Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_trx-table.md): The INNODB\_TRX table stores information about currently executing InnoDB transactions, including transaction state, start time, and locks.
- [Information Schema TEMP\_TABLES\_INFO Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-temp_tables_info-table.md): The TEMP\_TABLES\_INFO table lists active InnoDB temporary tables, including their column counts and tablespace identifiers.
- [Information Schema INNODB\_UNDO\_LOGS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-innodb-tables/information-schema-innodb_undo_logs-table.md): The INNODB\_UNDO\_LOGS table, an XtraDB enhancement, contains information about undo log segments, including transaction IDs and states.
- [Information Schema MyRocks Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables.md): Query INFORMATION\_SCHEMA.MYROCKS\_TABLES. These system tables provide metadata about MyRocks tables, including their storage, compression, and other properties for performance analysis.
- [Information Schema ROCKSDB\_CF\_OPTIONS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_cf_options-table.md): The Information Schema ROCKSDB\_CF\_OPTIONS table contains information about MyRocks column families, such as the column family name and option type.
- [Information Schema ROCKSDB\_CFSTATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_cfstats-table.md): The Information Schema ROCKSDB\_CFSTATS table provides statistics for each column family in the MyRocks storage engine.
- [Information Schema ROCKSDB\_COMPACTION\_STATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_compaction_stats-table.md): The Information Schema ROCKSDB\_COMPACTION\_STATS table contains statistics about compaction operations performed by the RocksDB engine.
- [Information Schema ROCKSDB\_DBSTATS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_dbstats-table.md): The Information Schema ROCKSDB\_DBSTATS table displays database-level statistics for the MyRocks storage engine.
- [Information Schema ROCKSDB\_DDL Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_ddl-table.md): The Information Schema ROCKSDB\_DDL table contains information about Data Definition Language (DDL) operations in MyRocks, including table and index names.
- [Information Schema ROCKSDB\_DEADLOCK Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_deadlock-table.md): The Information Schema ROCKSDB\_DEADLOCK table provides information about deadlocks that have occurred within the MyRocks storage engine.
- [Information Schema ROCKSDB\_GLOBAL\_INFO Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_global_info-table.md): The Information Schema ROCKSDB\_GLOBAL\_INFO table contains global configuration information for the MyRocks storage engine.
- [Information Schema ROCKSDB\_INDEX\_FILE\_MAP Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_index_file_map-table.md): The Information Schema ROCKSDB\_INDEX\_FILE\_MAP table maps MyRocks indexes to their corresponding SST files, useful for understanding data storage.
- [Information Schema ROCKSDB\_LOCKS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_locks-table.md): The Information Schema ROCKSDB\_LOCKS table displays information about locks currently held or requested by MyRocks transactions.
- [Information Schema ROCKSDB\_PERF\_CONTEXT Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_perf_context-table.md): The Information Schema ROCKSDB\_PERF\_CONTEXT table contains performance counters for the current session, providing granular metrics on RocksDB operations.
- [Information Schema ROCKSDB\_PERF\_CONTEXT\_GLOBAL Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_perf_context_global-table.md): The Information Schema ROCKSDB\_PERF\_CONTEXT\_GLOBAL table aggregates performance counters from all sessions, offering a global view of MyRocks performance.
- [Information Schema ROCKSDB\_SST\_PROPS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_sst_props-table.md): The Information Schema ROCKSDB\_SST\_PROPS table displays properties of SST files, such as data size and compression ratios, for MyRocks tables.
- [Information Schema ROCKSDB\_TRX Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-myrocks-tables/information-schema-rocksdb_trx-table.md): The Information Schema ROCKSDB\_TRX table provides information about active transactions in MyRocks, including transaction IDs and states.
- [Information Schema XtraDB Tables](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-xtradb-tables.md): These system tables provide metadata about XtraDB tables, including their storage, statistics, and other properties for advanced analysis and management.
- [Information Schema CHANGED\_PAGE\_BITMAPS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-xtradb-tables/information-schema-changed_page_bitmaps-table.md): The XTRADB\_INTERNAL\_HASH\_TABLES table provides memory usage statistics for internal hash tables used by the XtraDB/InnoDB storage engine.
- [Information Schema XTRADB\_INTERNAL\_HASH\_TABLES Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-xtradb-tables/information-schema-xtradb_internal_hash_tables-table.md): The XTRADB\_INTERNAL\_HASH\_TABLES table provides memory usage statistics for internal hash tables used by the XtraDB/InnoDB storage engine.
- [Information Schema XTRADB\_READ\_VIEW Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-xtradb-tables/information-schema-xtradb_read_view-table.md): The XTRADB\_READ\_VIEW table displays the current MVCC read views, showing which transactions are visible to active queries.
- [Information Schema XTRADB\_RSEG Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-xtradb-tables/information-schema-xtradb_rseg-table.md): The XTRADB\_RSEG table contains detailed information about the rollback segments used by XtraDB for undo logging and MVCC.
- [Performance Schema](/docs/server/reference/system-tables/performance-schema.md): Explore performance\_schema in MariaDB Server. This system database provides detailed, low-level insights into server execution, helping you diagnose performance bottlenecks and optimize your database.
- [Performance Schema Digests](/docs/server/reference/system-tables/performance-schema/performance-schema-digests.md): Statement digests aggregate statistics for similar queries by removing specific data values, allowing you to identify performance patterns across statement types.
- [Performance Schema Overview](/docs/server/reference/system-tables/performance-schema/performance-schema-overview.md): The Performance Schema is a feature for monitoring server performance that inspects internal execution details at a low level with minimal overhead.
- [Performance Schema Status Variables](/docs/server/reference/system-tables/performance-schema/performance-schema-status-variables.md): This page lists status variables that track the internal health of the Performance Schema, such as counters for lost events due to memory constraints.
- [Performance Schema System Variables](/docs/server/reference/system-tables/performance-schema/performance-schema-system-variables.md): Configure the Performance Schema using these system variables to control buffer sizes, set instrumentation limits, and enable specific consumers at startup.
- [Performance Schema Tables](/docs/server/reference/system-tables/performance-schema/performance-schema-tables.md): Explore the tables in the performance\_schema database, which expose granular metrics on server events, locks, threads, and I/O for detailed performance analysis.
- [List of Performance Schema Tables](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/list-of-performance-schema-tables.md): Browse the List of Performance Schema Tables in MariaDB. Access a comprehensive index of tables and descriptions to assist in monitoring server performance.
- [Performance Schema accounts Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-accounts-table.md): The Performance Schema accounts table stores statistics on current and total connections for each client account connecting to the server.
- [Performance Schema cond\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-cond_instances-table.md): The cond\_instances table lists all active condition objects (internal code mechanisms for thread signaling) currently on the server.
- [Performance Schema events\_stages\_current Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_current-table.md): The events\_stages\_current table shows the current stage event for each thread, including timer information and nesting details.
- [Performance Schema events\_stages\_history Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_history-table.md): This table records the ten most recent completed stage events per thread, useful for analyzing recent thread activity.
- [Performance Schema events\_stages\_history\_long Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_history_long-table.md): The events\_stages\_history\_long table stores the most recent 10,000 completed stage events globally, providing a deeper history than per-thread tables.
- [Performance Schema events\_stages\_summary\_by\_account\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_summary_by_account_by_event_name-table.md): This table summarizes stage events aggregated by the client account and the specific event name, showing counts and wait times.
- [Performance Schema events\_stages\_summary\_by\_host\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_summary_by_host_by_event_name-table.md): This table summarizes stage events aggregated by the client host and the event name, allowing performance analysis per host.
- [Performance Schema events\_stages\_summary\_by\_thread\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_summary_by_thread_by_event_name-table.md): This table summarizes stage events aggregated by thread and event name, providing granular statistics on thread execution stages.
- [Performance Schema events\_stages\_summary\_by\_user\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_summary_by_user_by_event_name-table.md): This table summarizes stage events aggregated by user name and event name, helping to identify users with resource-intensive stages.
- [Performance Schema events\_stages\_summary\_global\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_stages_summary_global_by_event_name-table.md): This table summarizes stage events aggregated by the client host and the event name, allowing performance analysis per host.
- [Performance Schema events\_statements\_current Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_current-table.md): The events\_statements\_current table displays the current statement event for each thread, including SQL text, timer stats, and error codes.
- [Performance Schema events\_statements\_history Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_history-table.md): This table records the ten most recent completed statement events per thread, offering a short-term history of executed SQL statements.
- [Performance Schema events\_statements\_history\_long Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_history_long-table.md): The events\_statements\_history\_long table stores the most recent 10,000 completed statement events globally, providing extensive query history.
- [Performance Schema events\_statements\_summary\_by\_account\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_account_by_event_name-table.md): This table summarizes statement events aggregated by client account and event name, detailing execution counts and timer statistics.
- [Performance Schema events\_statements\_summary\_by\_digest Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_digest-table.md): This table aggregates statement events by schema and digest, providing execution counts, latency, and locking statistics for normalized queries.
- [Performance Schema events\_statements\_summary\_by\_host\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_host_by_event_name-table.md): This table summarizes statement events aggregated by client host and event name, showing execution frequency and wait times per host.
- [Performance Schema events\_statements\_summary\_by\_program Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_program-table.md): This table provides summary statistics for statements executed within stored programs, such as procedures, functions, triggers, and events.
- [Performance Schema events\_statements\_summary\_by\_thread\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_thread_by_event_name-table.md): This table summarizes statement events aggregated by thread and event name, allowing analysis of statement execution per individual thread.
- [Performance Schema events\_statements\_summary\_by\_user\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_by_user_by_event_name-table.md): This table summarizes statement events aggregated by user name and event name, helping to identify users executing specific statement types.
- [Performance Schema events\_statements\_summary\_global\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_statements_summary_global_by_event_name-table.md): This table provides a global summary of statement events aggregated by event name, showing total execution counts and wait times for the server.
- [Performance Schema events\_transactions\_current Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_current-table.md): The events\_transactions\_current table displays the current transaction event for each thread, including state, isolation level, and GTID.
- [Performance Schema events\_transactions\_history Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_history-table.md): This table records the ten most recent completed stage events per thread, useful for analyzing recent thread activity.
- [Performance Schema events\_transactions\_history\_long Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_history_long-table.md): The events\_stages\_history\_long table stores the most recent 10,000 completed stage events globally, providing a deeper history than per-thread tables.
- [Performance Schema events\_transactions\_summary\_by\_account\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_summary_by_account_by_event_name-tab.md): This table summarizes stage events aggregated by the client account and the specific event name, showing counts and wait times.
- [Performance Schema events\_transactions\_summary\_by\_host\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_summary_by_host_by_event_name-table.md): This table summarizes stage events aggregated by the client host and the event name, allowing performance analysis per host.
- [Performance Schema events\_transactions\_summary\_by\_thread\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_summary_by_thread_by_event_name-tabl.md): This table summarizes stage events aggregated by thread and event name, providing granular statistics on thread execution stages.
- [Performance Schema events\_transactions\_summary\_by\_user\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_summary_by_user_by_event_name-table.md): This table summarizes stage events aggregated by user name and event name, helping to identify users with resource-intensive stages.
- [Performance Schema events\_transactions\_summary\_global\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_summary_global_by_event_name-table.md): This table provides a global summary of statement events aggregated by event name, showing total execution counts and wait times for the server.
- [Performance Schema events\_waits\_current Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_current-table.md): The events\_waits\_current table displays the most recent wait event for each thread, including timer and object information.
- [Performance Schema events\_waits\_history Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_history-table.md): This table records the ten most recent completed wait events per thread, useful for diagnosing recent latency issues.
- [Performance Schema events\_waits\_history\_long Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_history_long-table.md): The events\_waits\_history\_long table stores the most recent 10,000 completed wait events globally, autosized at startup.
- [Performance Schema events\_waits\_summary\_by\_account\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_by_account_by_event_name-table.md): This table summarizes wait events aggregated by client account and event name, providing statistics on wait times and execution counts.
- [Performance Schema events\_waits\_summary\_by\_host\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_by_host_by_event_name-table.md): This table summarizes wait events aggregated by client host and event name, helping to analyze wait latencies on a per-host basis.
- [Performance Schema events\_waits\_summary\_by\_instance Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_by_instance-table.md): This table summarizes wait events per instrument instance, allowing detailed analysis of specific locks, mutexes, or conditions.
- [Performance Schema events\_waits\_summary\_by\_thread\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_by_thread_by_event_name-table.md): This table summarizes wait events aggregated by thread and event name, useful for pinpointing threads experiencing high wait times.
- [Performance Schema events\_waits\_summary\_by\_user\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_by_user_by_event_name-table.md): This table summarizes wait events aggregated by user name and event name, helping to identify users triggering significant wait events.
- [Performance Schema events\_waits\_summary\_global\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_waits_summary_global_by_event_name-table.md): This table provides a global summary of wait events aggregated by event name, showing total server-wide wait statistics.
- [Performance Schema file\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-file_instances-table.md): The file\_instances table lists all file objects currently open by the server, including filenames and the number of open handles.
- [Performance Schema file\_summary\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-file_summary_by_event_name-table.md): This table summarizes file I/O events aggregated by event name, detailing read/write counts and bytes transferred for each file type.
- [Performance Schema file\_summary\_by\_instance Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-file_summary_by_instance-table.md): This table summarizes file I/O events aggregated by file instance, providing granular I/O statistics for individual files.
- [Performance Schema global\_status Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-global_status-table.md): The global\_status table provides a persistent view of global server status variables, aggregating statistics across all threads.
- [Performance Schema host\_cache Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-host_cache-table.md): The host\_cache table exposes the internal host cache contents, including IP-to-hostname resolution details and connection error counters.
- [Performance Schema hosts Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-hosts-table.md): The hosts table contains aggregated connection statistics for each client host, including counts for current and total historical connections.
- [Performance Schema memory\_summary\_by\_account\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-memory_summary_by_account_by_event_name-table.md): This table summarizes memory usage events aggregated by client account and event name, tracking current usage and high-water marks.
- [Performance Schema memory\_summary\_by\_host\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-memory_summary_by_host_by_event_name-table.md): This table summarizes memory usage events aggregated by client host and event name, helping to analyze memory consumption patterns per host.
- [Performance Schema memory\_summary\_by\_thread\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-memory_summary_by_thread_by_event_name-table.md): This table summarizes memory usage events aggregated by thread and event name, allowing for detailed memory profiling of individual threads.
- [Performance Schema memory\_summary\_by\_user\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-memory_summary_by_user_by_event_name-table.md): This table summarizes memory usage events aggregated by user name and event name, useful for identifying users with high memory footprints.
- [Performance Schema memory\_summary\_global\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-memory_summary_global_by_event_name-table.md): This table provides a global summary of memory usage events aggregated by event name, showing total memory allocation across the server.
- [Performance Schema metadata\_locks Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-metadata_locks-table.md): The metadata\_locks table lists currently held and requested metadata locks, which protect database object definitions from concurrent modification.
- [Performance Schema mutex\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-mutex_instances-table.md): The mutex\_instances table lists all active mutexes (mutual exclusions) instrumented by the Performance Schema, showing their locked state.
- [Performance Schema objects\_summary\_global\_by\_type Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-objects_summary_global_by_type-table.md): This table aggregates usage statistics for objects (tables, events, etc.) by type, schema, and name, showing global access counts and timers.
- [Performance Schema performance\_timers Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-performance_timers-table.md): The performance\_timers table lists available event timers (cycle, nanosecond, microsecond, millisecond) and their overhead characteristics.
- [Performance Schema prepared\_statements\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-prepared_statements_instances-table.md): The rwlock\_instances table lists all active read-write lock instances, showing the write-lock owner and the number of waiting readers or writers.
- [Performance Schema replication\_applier\_configuration Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-replication_applier_configuration-table.md): This table displays the configuration parameters used by the replica to connect to the primary server, such as host, port, and user credentials.
- [Performance Schema replication\_applier\_status Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-replication_applier_status-table.md): The replication\_applier\_status\_by\_worker table provides status information for each worker thread involved in parallel replication.
- [Performance Schema replication\_applier\_status\_by\_coordinator Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-replication_applier_status_by_coordinator-table.md): This table shows the status of the coordinator thread when parallel replication is enabled, detailing the distribution of transactions to workers.
- [Performance Schema replication\_applier\_status\_by\_worker Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-replication_applier_status_by_worker-table.md): The replication\_applier\_status\_by\_worker table provides status information for each worker thread involved in parallel replication.
- [Performance Schema replication\_connection\_configuration Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-replication_connection_configuration-table.md): This table displays the configuration parameters used by the replica to connect to the primary server, such as host, port, and user credentials.
- [Performance Schema rwlock\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-rwlock_instances-table.md): The rwlock\_instances table lists all active read-write lock instances, showing the write-lock owner and the number of waiting readers or writers.
- [Performance Schema session\_account\_connect\_attrs Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-session_account_connect_attrs-table.md): This table exposes connection attributes for the current session's account, providing metadata passed by the client application for identification.
- [Performance Schema session\_connect\_attrs Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-session_connect_attrs-table.md): The session\_connect\_attrs table lists connection attributes for the current session, offering details about the client library and environment.
- [Performance Schema session\_status Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-session_status-table.md): The session\_status table displays status variable values for the current session, providing data equivalent to the SHOW SESSION STATUS statement.
- [Performance Schema setup\_actors Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-setup_actors-table.md): The setup\_actors table configures which foreground threads (users/hosts) are monitored, allowing for targeted instrumentation of specific accounts.
- [Performance Schema setup\_consumers Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-setup_consumers-table.md): The setup\_consumers table controls which consumers (destinations) are enabled to store event data, managing the flow of metrics to history tables.
- [Performance Schema setup\_instruments Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-setup_instruments-table.md): The setup\_instruments table lists all supported instruments, allowing administrators to enable collection and configure timing for specific events.
- [Performance Schema setup\_objects Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-setup_objects-table.md): The setup\_objects table configures which database objects (tables, stored programs) are instrumented, enabling filtering by schema or name.
- [Performance Schema setup\_timers Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-setup_timers-table.md): The setup\_timers table defines the timer type (e.g., NANOSECOND, MICROSECOND) used for each instrument class within the Performance Schema.
- [Performance Schema socket\_instances Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-socket_instances-table.md): The socket\_instances table lists active network socket connections, providing details such as the IP address, port, and state of each socket.
- [Performance Schema socket\_summary\_by\_event\_name Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-socket_summary_by_event_name-table.md): This table summarizes socket I/O events aggregated by event name, showing execution counts and wait times for operations like send and receive.
- [Performance Schema socket\_summary\_by\_instance Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-socket_summary_by_instance-table.md): This table summarizes socket I/O events per socket instance, allowing for traffic analysis and latency monitoring of individual connections.
- [Performance Schema status\_by\_account Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-status_by_account-table.md): The status\_by\_account table aggregates session status variables by client account, showing cumulative counters for specific user-host combinations.
- [Performance Schema status\_by\_host Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-status_by_host-table.md): The status\_by\_host table aggregates session status variables by client host, useful for tracking activity levels from specific application servers.
- [Performance Schema status\_by\_thread Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-status_by_thread-table.md): The status\_by\_thread table lists session status variables for each active thread, effectively providing a "SHOW SESSION STATUS" for every connection.
- [Performance Schema status\_by\_user Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-status_by_user-table.md): The status\_by\_user table aggregates session status variables by user name, summarizing activity across all connections for a specific user identity.
- [Performance Schema table\_handles Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-table_handles-table.md): The table\_handles table lists all open table handles, showing which threads are currently accessing which table instances and the locks they hold.
- [Performance Schema table\_io\_waits\_summary\_by\_index\_usage Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-table_io_waits_summary_by_index_usage-table.md): This table aggregates I/O wait statistics by index, helping to identify which indexes handle the most traffic or are causing latency.
- [Performance Schema table\_io\_waits\_summary\_by\_table Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-table_io_waits_summary_by_table-table.md): This table summarizes I/O wait events by table, detailing the frequency and latency of fetch, insert, update, and delete operations.
- [Performance Schema table\_lock\_waits\_summary\_by\_table Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-table_lock_waits_summary_by_table-table.md): This table aggregates table lock wait events, allowing administrators to identify tables experiencing high contention due to locking.
- [Performance Schema threads Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-threads-table.md): The threads table lists all instrumented threads, mapping internal thread IDs to process IDs and providing execution status for every thread.
- [Performance Schema users Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-users-table.md): The users table tracks connection statistics aggregated by user name, including current active connections and total historical connections.
- [Performance Schema user\_variables\_by\_thread Table](/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-user_variables_by_thread-table.md): This table exposes user-defined variables set within active threads, allowing inspection of custom variables across all sessions.
- [Sys Schema](/docs/server/reference/system-tables/sys-schema.md): This schema provides a simplified and user-friendly view of Performance Schema and Information Schema data, aiding in database diagnostics and performance tuning.
- [Sys Schema sys\_config Table](/docs/server/reference/system-tables/sys-schema/sys-schema-sys_config-table.md): The sys\_config table holds persistent configuration options for the Sys Schema, stored using the Aria storage engine to maintain settings across restarts.
- [Sys Schema Stored Functions](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions.md): Explore sys\_schema stored functions in MariaDB Server. These functions simplify querying performance and configuration data, offering a user-friendly interface for database diagnostics.
- [extract\_schema\_from\_file\_name](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/extract_schema_from_file_name.md): This function takes a file path and returns the schema name it belongs to, assuming the file is located within the schema's directory.
- [extract\_table\_from\_file\_name](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/extract_table_from_file_name.md): This function extracts and returns the table name from a given file path, determined solely by parsing the path string.
- [format\_bytes](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/sys_schema_format_bytes.md): Convert bytes to a human-readable string. This function formats a numeric byte count into units like KiB, MiB, GiB, up to EiB.
- [format\_path](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/format_path.md): The format\_path function replaces specific system paths in a given string with their corresponding system variable names for better readability.
- [format\_statement](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/format_statement.md): This function formats and truncates an SQL statement string to a specified length, making it suitable for display in summary views.
- [format\_time](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/format_time.md): The format\_time function converts a time value in picoseconds into a human-readable string with appropriate units (e.g., ms, s, min).
- [list\_add](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/list_add.md): This function appends a value to a comma-separated list of values, which is useful for modifying system variables that take list values.
- [list\_drop](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/list_drop.md): The list\_drop function removes a specified value from a comma-separated list, returning the modified list.
- [ps\_is\_account\_enabled](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_is_account_enabled.md): This function checks whether a specific user account is enabled for instrumentation in the Performance Schema setup\_actors table.
- [ps\_is\_consumer\_enabled](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_is_consumer_enabled.md): This function returns YES or NO indicating whether a specific consumer is currently enabled in the Performance Schema.
- [ps\_is\_instrument\_default\_enabled](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_is_instrument_default_enabled.md): This function checks if a given Performance Schema instrument is enabled by default, returning YES or NO.
- [ps\_is\_instrument\_default\_timed](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_is_instrument_default_timed.md): This function checks if a specific Performance Schema instrument is timed by default, returning YES or NO based on the server's default configuration.
- [ps\_is\_thread\_instrumented](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_is_thread_instrumented.md): The ps\_is\_thread\_instrumented function checks whether a specific thread ID is currently instrumented by the Performance Schema.
- [ps\_thread\_account](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_thread_account.md): This function returns the user account (username@hostname) associated with a specific Performance Schema thread ID.
- [ps\_thread\_id](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_thread_id.md): The ps\_thread\_id function returns the internal Performance Schema thread ID associated with a given connection ID.
- [ps\_thread\_stack](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_thread_stack.md): This function returns a JSON-formatted stack trace of all statements, stages, and events for a given thread, useful for deep diagnostics.
- [ps\_thread\_trx\_info](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/ps_thread_trx_info.md): The ps\_thread\_trx\_info function returns a JSON object detailing the current transaction and executed statements for a specific thread.
- [quote\_identifier](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/quote_identifier.md): This function quotes a given string with backticks to ensure it can be safely used as an identifier in SQL statements.
- [sys\_get\_config](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/sys_get_config.md): The sys\_get\_config function retrieves the value of a specified configuration option from the sys\_config table, or a user variable if set.
- [version\_major](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/version_major.md): This function returns the major version number of the MariaDB Server instance (e.g., 10 from 10.6.4).
- [version\_minor](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/version_minor.md): This function returns the minor version number of the MariaDB Server instance, such as the 6 in 10.6.4.
- [version\_patch](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-functions/version_patch.md): This function returns the patch release version number of the MariaDB Server instance, such as the 4 in 10.6.4.
- [Sys Schema Stored Procedures](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures.md): Explore sys\_schema stored procedures in MariaDB Server. These procedures simplify complex administrative and diagnostic tasks, offering streamlined access to performance and configuration insights.
- [create\_synonym\_db](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/create_synonym_db.md): The create\_synonym\_db stored procedure creates a new database that contains views mirroring all tables from a source database, useful for creating aliases.
- [optimizer\_switch Helper Functions](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/optimizer_switch-helper-functions.md): These helper functions allow you to easily enable or disable specific optimizer\_switch flags for the current session.
- [ps\_trace\_statement\_digest](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/ps_trace_statement_digest.md): This procedure traces a specific statement digest in the Performance Schema, capturing details about its execution for performance analysis.
- [ps\_trace\_thread](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/ps_trace_thread.md): The ps\_trace\_thread procedure captures a trace of Performance Schema instrumentation for a specific thread and dumps it to a .dot formatted graph file.
- [ps\_truncate\_all\_tables](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/ps_truncate_all_tables.md): This procedure truncates all Performance Schema summary tables, effectively resetting all aggregated performance statistics.
- [statement\_performance\_analyzer](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/statement_performance_analyzer.md): This diagnostic procedure creates a report of the statements currently running or recently run on the server, aiding in performance troubleshooting.
- [table\_exists](/docs/server/reference/system-tables/sys-schema/sys-schema-stored-procedures/table_exists.md): The table\_exists procedure checks for the existence of a specific table, view, or temporary table within a given database.
- [Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views.md): Explore sys\_schema views in MariaDB Server. These views offer simplified, aggregated insights into server performance, I/O, and memory usage, making diagnostics and monitoring easier.
- [host\_summary and x$host\_summary Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/host_summary-and-xhost_summary-sys-schema-views.md): The host\_summary views provide a high-level overview of activity per client host, including statement counts, file I/O, and connection statistics.
- [host\_summary\_by\_file\_io and x$host\_summary\_by\_file\_io Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/host_summary_by_file_io-and-xhost_summary_by_file_io-sys-schema-views.md): These views summarize file I/O events grouped by client host, detailing total I/O counts and latency to identify hosts generating heavy disk traffic.
- [host\_summary\_by\_file\_io\_type and x$host\_summary\_by\_file\_io\_type Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/host_summary_by_file_io_type-and-xhost_summary_by_file_io_type-sys-schema-v.md): These views provide a breakdown of file I/O events by event type (e.g., read, write) for each host, helping to characterize the I/O workload.
- [host\_summary\_by\_stages and x$host\_summary\_by\_stages Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/host_summary_by_stages-and-xhost_summary_by_stages-sys-schema-views.md): These views summarize statement execution stages grouped by host, showing where threads spend the most time during query processing.
- [host\_summary\_by\_statement\_type and x$host\_summary\_by\_statement\_type Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/host_summary_by_statement_type-and-xhost_summary_by_statement_type-sys-sche.md): These views aggregate executed statements by type (e.g., SELECT, INSERT) and host, providing statistics on frequency and latency.
- [host\_summary\_by\_statement\_latency and x$host\_summary\_by\_statement\_latency Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/sys-schema-views-host_summary_by_statement_latency-and-xhost_summary_by_sta.md): These views summarize statement statistics grouped by host, sorted by total latency, helping to identify hosts running the most time-consuming queries.
- [innodb\_buffer\_stats\_by\_schema and x$innodb\_buffer\_stats\_by\_schema Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/innodb_buffer_stats_by_schema-and-xinnodb_buffer_stats_by_schema-sys-schema.md): These views summarize InnoDB buffer pool usage, showing the amount of memory and number of pages allocated to each database schema.
- [innodb\_buffer\_stats\_by\_table and x$innodb\_buffer\_stats\_by\_table Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/innodb_buffer_stats_by_table-and-xinnodb_buffer_stats_by_table-sys-schema-v.md): These views provide a granular breakdown of InnoDB buffer pool usage by individual tables, sorted by buffer allocation size.
- [innodb\_lock\_waits and x$innodb\_lock\_waits Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/innodb_lock_waits-and-xinnodb_lock_waits-sys-schema-views.md): These views summarize lock wait information, linking waiting transactions to blocking transactions to help diagnose deadlocks and contention.
- [io\_by\_thread\_by\_latency and x$io\_by\_thread\_by\_latency Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/io_by_thread_by_latency-and-xio_by_thread_by_latency-sys-schema-views.md): These views rank threads by I/O latency, making it easier to identify specific threads that are consuming the most disk resources.
- [io\_global\_by\_file\_by\_bytes and x$io\_global\_by\_file\_by\_bytes Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/io_global_by_file_by_bytes-and-xio_global_by_file_by_bytes-sys-schema-views.md): These views summarize global file I/O statistics grouped by file path, sorted by total bytes read and written.
- [io\_global\_by\_file\_by\_latency and x$io\_global\_by\_file\_by\_latency Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/io_global_by_file_by_latency-and-xio_global_by_file_by_latency-sys-schema-v.md): These views summarize global file I/O statistics grouped by file path, sorted by total latency to highlight slow I/O targets.
- [io\_global\_by\_wait\_by\_bytes and x$io\_global\_by\_wait\_by\_bytes Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/io_global_by_wait_by_bytes-and-xio_global_by_wait_by_bytes-sys-schema-views.md): These views summarize global I/O consumers by event name, displaying total bytes read and written to identify high-throughput events.
- [io\_global\_by\_wait\_by\_latency and x$io\_global\_by\_wait\_by\_latency Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/io_global_by_wait_by_latency-and-xio_global_by_wait_by_latency-sys-schema-v.md): These views summarize global I/O consumers by event name, sorted by total latency, helping to pinpoint slow I/O event types.
- [latest\_file\_io and x$latest\_file\_io Sys Schema Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/latest_file_io-and-xlatest_file_io-sys-schema-views.md): These views display the most recent file I/O events, providing a real-time look at which files are being accessed by the server.
- [memory\_by\_host\_by\_current\_bytes and x$memory\_by\_host\_by\_current\_bytes Views](/docs/server/reference/system-tables/sys-schema/sys-schema-views/memory_by_host_by_current_bytes-and-xmemory_by_host_by_current_bytes-views.md): These views summarize current memory usage grouped by client host, enabling administrators to track memory consumption per connected host.
- [metrics Sys Schema View](/docs/server/reference/system-tables/sys-schema/sys-schema-views/metrics-sys-schema-view.md): The metrics view consolidates key performance metrics from Global Status, InnoDB Metrics, and memory summaries into a single unified table.
- [privileges\_by\_table\_by\_level Sys Schema View](/docs/server/reference/system-tables/sys-schema/sys-schema-views/privileges_by_table_by_level-sys-schema-view.md): The privileges\_by\_table\_by\_level view lists granted privileges broken down by table and the level (Global, Schema, or Table) at which they were granted.
- [schema\_auto\_increment\_columns Sys Schema View](/docs/server/reference/system-tables/sys-schema/sys-schema-views/schema_auto_increment_columns-sys-schema-view.md): The schema\_auto\_increment\_columns view lists tables with AUTO\_INCREMENT columns, showing the current value and the maximum allowed value for the column type.
- [schema\_object\_overview Sys Schema View](/docs/server/reference/system-tables/sys-schema/sys-schema-views/schema_object_overview-sys-schema-view.md): The schema\_object\_overview view provides a count of different database objects (such as tables, views, and routines) within each schema on the server.
- [The mysql Database Tables](/docs/server/reference/system-tables/the-mysql-database-tables.md): Explore tables in the mysql database in MariaDB Server. These system tables store essential information for server operation, including user privileges, security settings, and global configuration.
- [mysql.column\_stats Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-column_stats-table.md): The mysql.column\_stats table stores engine-independent column statistics, such as histograms, used by the optimizer to improve query execution plans.
- [mysql.columns\_priv Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-columns_priv-table.md): The mysql.columns\_priv table records column-level privileges granted to users, detailing specific access rights for individual columns.
- [mysql.db Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-db-table.md): The mysql.db table stores database-level privileges, determining which users have access to specific databases and what actions they can perform.
- [mysql.event Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-event-table.md): The mysql.event table contains the definitions and scheduling information for events created with the CREATE EVENT statement.
- [mysql.func Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-func-table.md): The mysql.func table registers user-defined functions (UDFs), storing their names and the shared library files containing their code.
- [mysql.general\_log Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysqlgeneral_log-table.md): The mysql.general\_log table captures a record of all SQL statements received by the server when general query logging is enabled and written to tables.
- [mysql.global\_priv Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-global_priv-table.md): The mysql.global\_priv table stores global privileges and account properties for all users, replacing the older mysql.user table structure.
- [mysql.gtid\_slave\_pos Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysqlgtid_slave_pos-table.md): The mysql.gtid\_slave\_pos table tracks the Global Transaction ID (GTID) of the last applied transaction on a replica to ensure replication consistency.
- [mysql.help\_category Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-help_category-table.md): The mysql.help\_category table stores category information for the server-side help system, organizing help topics into a hierarchy.
- [mysql.help\_keyword Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-help_keyword-table.md): The mysql.help\_keyword table maps keywords to help topics, facilitating keyword-based searches within the MariaDB help system.
- [mysql.help\_relation Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-help_relation-table.md): The mysql.help\_relation table links help keywords to help topics, defining the structure of the server-side help system.
- [mysql.help\_topic Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-help_topic-table.md): The mysql.help\_topic table stores the detailed content of help topics, including descriptions and examples displayed by the HELP command.
- [mysql.index\_stats Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-index_stats-table.md): The mysql.index\_stats table stores engine-independent index statistics, such as cardinality, used by the optimizer to plan query execution.
- [mysql.innodb\_index\_stats](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-innodb_index_stats.md): The mysql.innodb\_index\_stats table stores persistent index statistics for InnoDB, allowing optimizer plans to remain stable across restarts.
- [mysql.innodb\_table\_stats](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-innodb_table_stats.md): The mysql.innodb\_table\_stats table holds persistent table-level statistics for InnoDB, such as row counts, used for query optimization.
- [mysql.password\_reuse\_check\_history Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysqlpassword_reuse_check_history-table.md): This table stores a history of password hashes to enforce security policies regarding password reuse when the relevant plugin is enabled.
- [mysql.plugin Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-plugin-table.md): The mysql.plugin table records information about installed server plugins, ensuring they are reloaded automatically upon server startup.
- [mysql.proc Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-proc-table.md): The mysql.proc table stores the definitions, body, and metadata for stored procedures and functions created on the server.
- [mysql.procs\_priv Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-procs_priv-table.md): The mysql.procs\_priv table records privileges granted to users specifically for executing or altering stored procedures and functions.
- [mysql.proxies\_priv Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-proxies_priv-table.md): The mysql.proxies\_priv table manages proxy user privileges, defining which accounts are authorized to proxy as other users.
- [mysql.roles\_mapping Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-roles_mapping-table.md): The mysql.roles\_mapping table manages role assignments, linking user accounts to the roles they have been granted.
- [mysql.servers Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-servers-table.md): The mysql.servers table stores connection information for remote servers, used by the FEDERATED and Spider storage engines.
- [mysql.slow\_log Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-slow_log-table.md): The mysql.slow\_log table records details of queries that exceed the long\_query\_time threshold when slow query logging to tables is enabled.
- [mysql.table\_stats Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-table_stats-table.md): The mysql.table\_stats table stores engine-independent statistics about tables, such as row counts, to assist the optimizer.
- [mysql.tables\_priv Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-tables_priv-table.md): The mysql.tables\_priv table records table-level privileges granted to users, specifying which actions they can perform on specific tables.
- [mysql.time\_zone Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-time_zone-table.md): The mysql.time\_zone table assigns a unique ID to each time zone supported by the server, linking to other time zone system tables.
- [mysql.time\_zone\_leap\_second Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-time_zone_leap_second-table.md): The mysql.time\_zone\_leap\_second table lists leap second corrections to be applied to specific time zones.
- [mysql.time\_zone\_name Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-time_zone_name-table.md): The mysql.time\_zone\_name table maps human-readable time zone names (e.g., "Europe/Berlin") to their internal time zone IDs.
- [mysql.time\_zone\_transition Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-time_zone_transition-table.md): The mysql.time\_zone\_transition table defines the exact times at which daylight saving time or other time zone transitions occur.
- [mysql.time\_zone\_transition\_type Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-time_zone_transition_type-table.md): The mysql.time\_zone\_transition\_type table describes the properties of time zone transitions, such as the offset and abbreviation.
- [mysql.transaction\_registry Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-transaction_registry-table.md): The mysql.transaction\_registry table is used by system-versioned tables to track transaction IDs and their commit timestamps.
- [mysql.user Table](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-user-table.md): Complete mysql.user table reference: mysql.global\_priv view, Host/User identifiers, plugin/authentication\_string fields, and GRANT/CREATE USER integration.
- [Spider mysql Database Tables](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables.md): Explore Spider-related tables within the mysql database. These system tables store crucial configuration and metadata for the Spider storage engine, essential for distributed deployments.
- [mysql.spider\_link\_failed\_log Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_link_failed_log-table.md): This table logs failures when attempting to establish connections to remote Spider links, helping to diagnose network or configuration issues.
- [mysql.spider\_link\_mon\_servers Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_link_mon_servers-table.md): This table defines the remote servers used for link monitoring in the Spider storage engine, ensuring high availability and failover handling.
- [mysql.spider\_table\_crd Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_table_crd-table.md): The mysql.spider\_table\_crd table stores cardinality statistics for Spider tables, which the optimizer uses to create efficient query plans.
- [mysql.spider\_table\_position\_for\_recovery Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_table_position_for_recovery-table.md): This table records XA transaction positions for Spider tables, essential for recovering distributed transactions after a crash.
- [mysql.spider\_table\_sts Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_table_sts-table.md): The mysql.spider\_table\_sts table holds statistics such as row counts and data length for Spider tables, supporting the optimizer.
- [mysql.spider\_tables Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_tables-table.md): This table stores specific parameters and metadata for Spider tables, defining how they map to remote backend tables.
- [mysql.spider\_xa Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_xa-table.md): The mysql.spider\_xa table tracks the status of XA transactions involving Spider tables, ensuring atomicity across distributed nodes.
- [mysql.spider\_xa\_failed\_log Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_xa_failed_log-table.md): This table logs details of failed XA transactions in the Spider storage engine, providing a record for troubleshooting distributed transaction errors.
- [mysql.spider\_xa\_member Table](/docs/server/reference/system-tables/the-mysql-database-tables/spider-mysql-database-tables/mysql-spider_xa_member-table.md): The mysql.spider\_xa\_member table lists the member nodes participating in a distributed XA transaction managed by the Spider engine.
- [Obsolete mysql Database Tables](/docs/server/reference/system-tables/the-mysql-database-tables/obsolete-mysql-database-tables.md): Explore obsolete tables in the mysql database for MariaDB Server. This section provides information on deprecated system tables, useful for understanding historical contexts or migration planning.
- [mysql.host Table](/docs/server/reference/system-tables/the-mysql-database-tables/obsolete-mysql-database-tables/mysql-host-table.md)
- [mysql.ndb\_binlog\_index Table](/docs/server/reference/system-tables/the-mysql-database-tables/obsolete-mysql-database-tables/mysqlndb_binlog_index-table.md)
- [Error Codes](/docs/server/reference/error-codes.md)
- [MariaDB Error Code Reference](/docs/server/reference/error-codes/mariadb-error-code-reference.md)
- [Operating System Error Codes](/docs/server/reference/error-codes/operating-system-error-codes.md)
- [MariaDB Error Codes 1000 to 1099](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099.md)
- [Error 1000: hashchk](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1000.md)
- [Error 1001: isamchk](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1001.md)
- [Error 1002: NO](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1002.md)
- [Error 1003: YES](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1003.md)
- [Error 1004: Can't create file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1004.md)
- [Error 1005: Can't create table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1005.md)
- [Error 1006: Can't create database](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1006.md): Reference for MariaDB error 1006 (HY000), including common causes like insufficient disk space and file permission issues.
- [Error 1007: Can't create database, database exists](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1007.md)
- [Error 1008: Can't drop database; database doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1008.md)
- [Error 1009: Error dropping database (can't delete)](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1009.md)
- [Error 1010: Error dropping database (can't rmdir)](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1010.md)
- [Error 1011: Error on delete of](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1011.md)
- [Error 1012: Can't read record in system table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1012.md)
- [Error 1013: Can't get status of](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1013.md)
- [Error 1014: Can't get working directory](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1014.md)
- [Error 1015: Can't lock file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1015.md)
- [Error 1016: Can't open file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1016.md)
- [Error 1017: Can't find file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1017.md)
- [Error 1018: Can't read dir of](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1018.md)
- [Error 1019: Can't change dir to](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1019.md)
- [Error 1020: Record has changed since last read in table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1020.md)
- [Error 1021: Disk full (%s); waiting for someone to free some space](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1021.md)
- [Error 1022: Can't write; duplicate key in table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1022.md)
- [Error 1023: Error on close of](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1023.md)
- [Error 1024: Error reading file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1024.md)
- [Error 1025: Error on rename of](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1025.md)
- [Error 1026: Error writing file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1026.md)
- [Error 1027: is locked against change](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1027.md)
- [Error 1028: Sort aborted](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1028.md)
- [Error 1029: View doesn't exist for](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1029.md)
- [Error 1030: Got error from storage engine](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1030.md)
- [Error 1031: Table storage engine doesn't have this option](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1031.md)
- [Error 1032: Can't find record in](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1032.md)
- [Error 1033: Incorrect information in file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1033.md)
- [Error 1034: Incorrect key file for table; try to repair it](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1034.md)
- [Error 1035: Old key file for table; repair it!](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1035.md)
- [Error 1036: Table is read only](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1036.md)
- [Error 1037: Out of memory; restart server and try again](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1037.md)
- [Error 1038: Out of sort memory, consider increasing server sort buffer size](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1038.md)
- [Error 1039: Unexpected EOF found when reading file](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1039.md)
- [Error 1040: Too many connections](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1040.md)
- [Error 1041: Out of memory](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1041.md)
- [Error 1042: Can't get hostname for your address](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1042.md)
- [Error 1043: Bad handshake](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1043.md)
- [Error 1044: Access denied for user](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1044.md)
- [Error 1045: Access denied for user (using password)](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1045.md)
- [Error 1046: No database selected](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1046.md)
- [Error 1047: Unknown command](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1047.md)
- [Error 1048: Column cannot be null](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1048.md)
- [Error 1049: Unknown database](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1049.md)
- [Error 1050: Table already exists](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1050.md)
- [Error 1051: Unknown table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1051.md)
- [Error 1052: Column is ambiguous](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1052.md)
- [Error 1053: Server shutdown in progress](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1053.md)
- [Error 1054: Unknown column](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1054.md)
- [Error 1055: isn't in GROUP BY](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1055.md)
- [Error 1056: Can't group on](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1056.md)
- [Error 1057: Statement has sum functions and columns in same statement](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1057.md)
- [Error 1058: Column count doesn't match value count](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1058.md)
- [Error 1059: Identifier name is too long](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1059.md)
- [Error 1060: Duplicate column name](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1060.md)
- [Error 1061: Duplicate key name](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1061.md)
- [Error 1062: Duplicate entry for key](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1062.md)
- [Error 1063: Incorrect column specifier for column](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1063.md)
- [Error 1064: near at line](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1064.md)
- [Error 1065: Query was empty](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1065.md)
- [Error 1066: Not unique table/alias](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1066.md)
- [Error 1067: Invalid default value for](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1067.md)
- [Error 1068: Multiple primary key defined](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1068.md)
- [Error 1069: Too many keys specified; max keys allowed](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1069.md)
- [Error 1070: Too many key parts specified; max parts allowed](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1070.md)
- [Error 1071: Specified key was too long; max key length is](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1071.md)
- [Error 1072: Key column doesn't exist in table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1072.md)
- [Error 1073: BLOB column can't be used in key specification with the used table type](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1073.md)
- [Error 1074: Column length too big for column; use BLOB or TEXT instead](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1074.md)
- [Error 1075: Incorrect table definition; there can be only one auto column and it must be defined as](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1075.md)
- [Error 1076: ready for connections](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1076.md)
- [Error 1077: Normal shutdown](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1077.md)
- [Error 1078: Got signal. Aborting!](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1078.md)
- [Error 1079: Shutdown complete](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1079.md)
- [Error 1080: Forcing close of thread](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1080.md)
- [Error 1081: Can't create IP socket](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1081.md)
- [Error 1082: Table has no index like the one used in CREATE INDEX; recreate the table](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1082.md)
- [Error 1083: Field separator argument is not what is expected; check the manual](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1083.md)
- [Error 1084: You can't use fixed rowlength with BLOBs; please use 'fields terminated by'](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1084.md)
- [Error 1085: The file must be in the database directory or be readable by all](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1085.md)
- [Error 1086: File already exists](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1086.md)
- [Error 1087: Records Deleted Skipped Warnings](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1087.md)
- [Error 1088: Records Duplicates](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1088.md)
- [Error 1089: Incorrect prefix key; the used key part isn't a string, the used length is longer than t](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1089.md)
- [Error 1090: You can't delete all columns with ALTER TABLE; use DROP TABLE instead](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1090.md)
- [Error 1091: Can't DROP; check that column/key exists](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1091.md)
- [Error 1092: Records Duplicates Warnings](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1092.md)
- [Error 1093: You can't specify target table for update in FROM clause](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1093.md)
- [Error 1094: Unknown thread id](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1094.md)
- [Error 1095: You are not owner of thread](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1095.md)
- [Error 1096: No tables used](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1096.md)
- [Error 1097: Too many strings for column and SET](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1097.md)
- [Error 1098: Can't generate a unique log-filename](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1098.md)
- [Error 1099: Table was locked with a READ lock and can't be updated](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1099.md)
- [MariaDB Error Codes 1100 to 1199](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199.md)
- [Error 1100: Table was not locked with LOCK TABLES](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1100.md)
- [Error 1101: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1101.md)
- [Error 1102: Incorrect database name](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1102.md)
- [Error 1103: Incorrect table name](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1103.md)
- [Error 1104: The SELECT would examine more than MAX\_JOIN\_SIZE rows](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1104.md)
- [Error 1105: Unknown error](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1105.md)
- [Error 1106: Unknown procedure](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1106.md)
- [Error 1107: Incorrect parameter count to procedure](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1107.md)
- [Error 1108: Incorrect parameters to procedure](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1108.md)
- [Error 1109: Unknown table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1109.md)
- [Error 1110: Column specified twice](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1110.md)
- [Error 1111: Invalid use of group function](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1111.md)
- [Error 1112: Table uses an extension that doesn't exist in this MariaDB version](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1112.md)
- [Error 1113: A table must have at least 1 column](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1113.md)
- [Error 1114: The table is full](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1114.md)
- [Error 1115: Unknown character set](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1115.md)
- [Error 1116: Too many tables; MariaDB can only use tables in a join](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1116.md)
- [Error 1117: Too many columns](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1117.md)
- [Error 1118: Row size too large](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1118.md)
- [Error 1119: Thread stack overrun](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1119.md)
- [Error 1120: Cross dependency found in OUTER JOIN; examine your ON conditions](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1120.md)
- [Error 1121: Table handler doesn't support NULL in given index](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1121.md)
- [Error 1122: Can't load function](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1122.md)
- [Error 1123: Can't initialize function](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1123.md)
- [Error 1124: No paths allowed for shared library](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1124.md)
- [Error 1125: Function already exists](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1125.md)
- [Error 1126: Can't open shared library](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1126.md)
- [Error 1127: Can't find symbol in library](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1127.md)
- [Error 1128: Function is not defined](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1128.md)
- [Error 1129: Host is blocked because of many connection errors](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1129.md)
- [Error 1130: Host is not allowed to connect to this MariaDB server](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1130.md)
- [Error 1131: You are using MariaDB as an anonymous user](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1131.md)
- [Error 1132: You must have privileges to update tables in the mysql database](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1132.md)
- [Error 1133: Can't find any matching row in the user table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1133.md)
- [Error 1134: Rows matched Changed Warnings](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1134.md)
- [Error 1135: Can't create a new thread](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1135.md)
- [Error 1136: Column count doesn't match value count at row](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1136.md)
- [Error 1137: Can't reopen table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1137.md)
- [Error 1138: Invalid use of NULL value](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1138.md)
- [Error 1139: Got error from regexp](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1139.md)
- [Error 1140: Mixing of GROUP columns with no GROUP columns](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1140.md)
- [Error 1141: There is no such grant defined for user on host](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1141.md)
- [Error 1142: command denied to user for table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1142.md)
- [Error 1143: command denied to user for column in table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1143.md)
- [Error 1144: Illegal GRANT/REVOKE command](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1144.md)
- [Error 1145: The host or user argument to GRANT is too long](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1145.md)
- [Error 1146: Table doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1146.md)
- [Error 1147: There is no such grant defined for user on host on table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1147.md)
- [Error 1148: The used command is not allowed with this MariaDB version](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1148.md)
- [Error 1149: You have an error in your SQL syntax](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1149.md)
- [Error 1150: Delayed insert thread couldn't get requested lock for table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1150.md)
- [Error 1151: Too many delayed threads in use](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1151.md)
- [Error 1152: Aborted connection to db user](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1152.md)
- [Error 1153: Got a packet bigger than 'max\_allowed\_packet' bytes](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1153.md)
- [Error 1154: Got a read error from the connection pipe](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1154.md)
- [Error 1155: Got an error from fcntl()](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1155.md)
- [Error 1156: Got packets out of order](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1156.md)
- [Error 1157: Couldn't uncompress communication packet](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1157.md)
- [Error 1158: Got an error reading communication packets](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1158.md): Error 1158 diagnostic reference: communication packet read errors, client abort causes, log\_warnings≥4 diagnostics, error log parsing, and perror output.
- [Error 1159: Got timeout reading communication packets](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1159.md)
- [Error 1160: Got an error writing communication packets](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1160.md)
- [Error 1161: Got timeout writing communication packets](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1161.md)
- [Error 1162: Result string is longer than 'max\_allowed\_packet' bytes](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1162.md)
- [Error 1163: The used table type doesn't support BLOB/TEXT columns](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1163.md)
- [Error 1164: The used table type doesn't support AUTO\_INCREMENT columns](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1164.md)
- [Error 1165: INSERT DELAYED can't be used with table because it is locked](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1165.md)
- [Error 1166: Incorrect column name](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1166.md)
- [Error 1167: The used storage engine can't index column](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1167.md)
- [Error 1168: Unable to open underlying table which is differently defined or of non-MyISAM type or do](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1168.md)
- [Error 1169: Can't write, because of unique constraint, to table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1169.md)
- [Error 1170: BLOB/TEXT column used in key specification without a key length](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1170.md)
- [Error 1171: All parts of a PRIMARY KEY must be NOT NULL](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1171.md)
- [Error 1172: Result consisted of more than one row](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1172.md)
- [Error 1173: This table type requires a primary key](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1173.md)
- [Error 1174: This version of MariaDB is not compiled with RAID support](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1174.md)
- [Error 1175: You are using safe update mode and you tried to update a table without a WHERE that uses](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1175.md)
- [Error 1176: Key doesn't exist in table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1176.md)
- [Error 1177: Can't open table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1177.md)
- [Error 1178: The storage engine for the table doesn't support](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1178.md)
- [Error 1179: You are not allowed to execute this command in a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1179.md)
- [Error 1180: Got error during COMMIT](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1180.md)
- [Error 1181: Got error during ROLLBACK](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1181.md)
- [Error 1182: Got error during FLUSH\_LOGS](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1182.md)
- [Error 1183: Got error during CHECKPOINT](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1183.md)
- [Error 1184: Aborted connection to db user host](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1184.md)
- [Error 1185: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1185.md)
- [Error 1186: Binlog closed, cannot RESET MASTER](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1186.md)
- [Error 1187: Failed rebuilding the index of dumped table](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1187.md)
- [Error 1188: Error from master](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1188.md)
- [Error 1189: Net error reading from master](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1189.md)
- [Error 1190: Net error writing to master](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1190.md)
- [Error 1191: Can't find FULLTEXT index matching the column list](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1191.md)
- [Error 1192: Can't execute the given command because you have active locked tables or an active trans](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1192.md)
- [Error 1193: Unknown system variable](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1193.md)
- [Error 1194: Table is marked as crashed and should be repaired](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1194.md)
- [Error 1195: Table is marked as crashed and last (automatic?) repair failed](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1195.md)
- [Error 1196: Some non-transactional changed tables couldn't be rolled back](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1196.md)
- [Error 1197: Multi-statement transaction required more than 'max\_binlog\_cache\_size' bytes of storage](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1197.md)
- [Error 1198: This operation cannot be performed with a running slave; run STOP SLAVE first](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1198.md)
- [Error 1199: This operation requires a running slave; configure slave and do START SLAVE](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1199.md)
- [MariaDB Error Codes 1200 to 1299](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299.md)
- [Error 1200: The server is not configured as slave](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1200.md)
- [Error 1201: Could not initialize master info structure](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1201.md)
- [Error 1202: Could not create slave thread; check system resources](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1202.md)
- [Error 1203: User already has more than 'max\_user\_connections' active connections](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1203.md)
- [Error 1204: You may only use constant expressions with SET](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1204.md)
- [Error 1205: Lock wait timeout exceeded; try restarting transaction](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1205.md)
- [Error 1206: The total number of locks exceeds the lock table size](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1206.md)
- [Error 1207: Update locks cannot be acquired during a READ UNCOMMITTED transaction](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1207.md)
- [Error 1208: DROP DATABASE not allowed while thread is holding global read lock](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1208.md)
- [Error 1209: CREATE DATABASE not allowed while thread is holding global read lock](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1209.md)
- [Error 1210: Incorrect arguments to](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1210.md)
- [Error 1211: is not allowed to create new users](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1211.md)
- [Error 1212: Incorrect table definition; all MERGE tables must be in the same database](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1212.md)
- [Error 1213: Deadlock found when trying to get lock; try restarting transaction](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1213.md)
- [Error 1214: The used table type doesn't support FULLTEXT indexes](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1214.md)
- [Error 1215: Cannot add foreign key constraint](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1215.md)
- [Error 1216: Cannot add or update a child row: a foreign key constraint fails](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1216.md)
- [Error 1217: Cannot delete or update a parent row: a foreign key constraint fails](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1217.md)
- [Error 1218: Error connecting to master](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1218.md)
- [Error 1219: Error running query on master](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1219.md)
- [Error 1220: Error when executing command](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1220.md)
- [Error 1221: Incorrect usage of](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1221.md)
- [Error 1222: The used SELECT statements have a different number of columns](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1222.md)
- [Error 1223: Can't execute the query because you have a conflicting read lock](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1223.md)
- [Error 1224: Mixing of transactional and non-transactional tables is disabled](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1224.md)
- [Error 1225: Option used twice in statement](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1225.md)
- [Error 1226: User has exceeded the resource](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1226.md)
- [Error 1227: Access denied; you need (at least one of) the privilege(s) for this operation](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1227.md)
- [Error 1228: Variable is a SESSION variable and can't be used with SET GLOBAL](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1228.md)
- [Error 1229: Variable is a GLOBAL variable and should be set with SET GLOBAL](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1229.md)
- [Error 1230: Variable doesn't have a default value](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1230.md)
- [Error 1231: Variable can't be set to the value of](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1231.md)
- [Error 1232: Incorrect argument type to variable](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1232.md)
- [Error 1233: Variable can only be set, not read](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1233.md)
- [Error 1234: Incorrect usage/placement](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1234.md)
- [Error 1235: This version of MariaDB doesn't yet support](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1235.md)
- [Error 1236: Got fatal error from master when reading data from binary log](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1236.md)
- [Error 1237: Slave SQL thread ignored the query because of replicate-\*-table rules](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1237.md)
- [Error 1238: Variable is a](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1238.md)
- [Error 1239: Incorrect foreign key definition](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1239.md)
- [Error 1240: Key reference and table reference don't match](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1240.md)
- [Error 1241: Operand should contain column(s)](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1241.md)
- [Error 1242: Subquery returns more than 1 row](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1242.md)
- [Error 1243: Unknown prepared statement handler given](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1243.md)
- [Error 1244: Help database is corrupt or does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1244.md)
- [Error 1245: Cyclic reference on subqueries](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1245.md)
- [Error 1246: Converting column from to](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1246.md)
- [Error 1247: Reference not supported](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1247.md)
- [Error 1248: Every derived table must have its own alias](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1248.md)
- [Error 1249: Select was reduced during optimization](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1249.md)
- [Error 1250: Table from one of the SELECTs cannot be used](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1250.md)
- [Error 1251: Client does not support authentication protocol requested by server](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1251.md)
- [Error 1252: All parts of a SPATIAL index must be NOT NULL](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1252.md)
- [Error 1253: COLLATION is not valid for CHARACTER SET](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1253.md)
- [Error 1254: Slave is already running](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1254.md)
- [Error 1255: Slave already has been stopped](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1255.md)
- [Error 1256: Uncompressed data size too large](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1256.md)
- [Error 1257: ZLIB: Not enough memory](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1257.md)
- [Error 1258: ZLIB: Not enough room in the output buffer](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1258.md)
- [Error 1259: ZLIB: Input data corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1259.md)
- [Error 1260: Row was cut by GROUP\_CONCAT()](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1260.md)
- [Error 1261: Row doesn't contain data for all columns](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1261.md)
- [Error 1262: Row was truncated; it contained more data than there were input columns](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1262.md)
- [Error 1263: Column set to default value; NULL supplied to NOT NULL columnError 1263: Column set to d](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1263.md)
- [Error 1264: Out of range value for column](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1264.md)
- [Error 1265: Data truncated for column](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1265.md)
- [Error 1266: Using storage engine for table](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1266.md)
- [Error 1267: Illegal mix of collations for operation](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1267.md)
- [Error 1268: Cannot drop one or more of the requested users](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1268.md)
- [Error 1269: Can't revoke all privileges for one or more of the requested users](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1269.md)
- [Error 1270: Illegal mix of collations for operation](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1270.md)
- [Error 1271: Illegal mix of collations for operation](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1271.md)
- [Error 1272: Variable is not a variable component (can't be used as XXXX.variable\_name)](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1272.md)
- [Error 1273: Unknown collation](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1273.md)
- [Error 1274: SSL parameters in CHANGE MASTER are ignored because this MariaDB slave was compiled with](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1274.md)
- [Error 1275: Server is running in --secure-auth mode, but has a password in the old format](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1275.md)
- [Error 1276: Field or reference of SELECT was resolved in SELECT](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1276.md)
- [Error 1277: Incorrect parameter or combination of parameters for START SLAVE UNTIL](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1277.md)
- [Error 1278: It is recommended to use --skip-slave-start when doing step-by-step replication with STA](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1278.md)
- [Error 1279: SQL thread is not to be started so UNTIL options are ignored](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1279.md)
- [Error 1280: Incorrect index name](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1280.md)
- [Error 1281: Incorrect catalog name](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1281.md)
- [Error 1282: Query cache failed to set size; new query cache size is](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1282.md)
- [Error 1283: Column cannot be part of FULLTEXT index](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1283.md)
- [Error 1284: Unknown key cache](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1284.md)
- [Error 1285: MariaDB is started in --skip-name-resolve mode](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1285.md)
- [Error 1286: Unknown storage engine](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1286.md)
- [Error 1287: is deprecated and will be removed in a future release. Please use instead](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1287.md)
- [Error 1288: The target table of the is not updatable](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1288.md)
- [Error 1289: The feature is disabled; you need MariaDB built with to have it working](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1289.md)
- [Error 1290: The MariaDB server is running with the option so it cannot execute this statement](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1290.md)
- [Error 1291: Column has duplicated value](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1291.md)
- [Error 1292: Truncated incorrect value](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1292.md)
- [Error 1293: Incorrect table definition; there can be only one TIMESTAMP column with CURRENT\_TIMESTAM](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1293.md)
- [Error 1294: Invalid ON UPDATE clause](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1294.md)
- [Error 1295: This command is not supported in the prepared statement protocol yet](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1295.md)
- [Error 1296: Got error from](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1296.md)
- [Error 1297: Got temporary error from](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1297.md)
- [Error 1298: Unknown or incorrect time zone](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1298.md)
- [Error 1299: Invalid TIMESTAMP value in column at row](/docs/server/reference/error-codes/mariadb-error-codes-1200-to-1299/e1299.md)
- [MariaDB Error Codes 1300 to 1399](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399.md)
- [Error 1300: Invalid character string](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1300.md)
- [Error 1301: Result was larger than max\_allowed\_packet - truncated](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1301.md)
- [Error 1302: Conflicting declarations](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1302.md)
- [Error 1303: Can't create from within another stored routine](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1303.md)
- [Error 1304: already exists](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1304.md)
- [Error 1305: does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1305.md)
- [Error 1306: Failed to DROP](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1306.md)
- [Error 1307: Failed to CREATE](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1307.md)
- [Error 1308: with no matching label](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1308.md)
- [Error 1309: Redefining label](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1309.md)
- [Error 1310: End-label without match](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1310.md)
- [Error 1311: Referring to uninitialized variable](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1311.md)
- [Error 1312: PROCEDURE can't return a result set in the given context](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1312.md)
- [Error 1313: RETURN is only allowed in a FUNCTION](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1313.md)
- [Error 1314: is not allowed in stored procedures](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1314.md)
- [Error 1315: The update log is deprecated and replaced by the binary log](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1315.md)
- [Error 1316: The update log is deprecated and replaced by the binary log; SET SQL\_LOG\_UPDATE has been](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1316.md)
- [Error 1317: Query execution was interrupted](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1317.md)
- [Error 1318: Incorrect number of arguments; expected, got](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1318.md)
- [Error 1319: Undefined CONDITION](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1319.md)
- [Error 1320: No RETURN found in FUNCTION](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1320.md)
- [Error 1321: FUNCTION ended without RETURN](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1321.md)
- [Error 1322: Cursor statement must be a SELECT](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1322.md)
- [Error 1323: Cursor SELECT must not have INTO](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1323.md)
- [Error 1324: Undefined CURSOR](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1324.md)
- [Error 1325: Cursor is already open](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1325.md)
- [Error 1326: Cursor is not open](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1326.md)
- [Error 1327: Undeclared variable](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1327.md)
- [Error 1328: Incorrect number of FETCH variables](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1328.md)
- [Error 1329: No data - zero rows fetched, selected, or processed](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1329.md)
- [Error 1330: Duplicate parameter](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1330.md)
- [Error 1331: Duplicate variable](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1331.md)
- [Error 1332: Duplicate condition](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1332.md)
- [Error 1333: Duplicate cursor](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1333.md)
- [Error 1334: Failed to ALTER](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1334.md)
- [Error 1335: Subquery value not supported](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1335.md)
- [Error 1336: is not allowed in stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1336.md)
- [Error 1337: Variable or condition declaration after cursor or handler declaration](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1337.md)
- [Error 1338: Cursor declaration after handler declaration](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1338.md)
- [Error 1339: Case not found for CASE statement](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1339.md)
- [Error 1340: Configuration file is too big](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1340.md)
- [Error 1341: Malformed file type header in file](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1341.md)
- [Error 1342: Unexpected end of file while parsing comment](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1342.md)
- [Error 1343: Error while parsing parameter](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1343.md)
- [Error 1344: Unexpected end of file while skipping unknown parameter](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1344.md)
- [Error 1345: EXPLAIN/SHOW can not be issued; lacking privileges for underlying table](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1345.md)
- [Error 1346: File has unknown type in its header](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1346.md)
- [Error 1347: '%s.%s' is not %s](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1347.md)
- [Error 1348: Column is not updatable](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1348.md)
- [Error 1349: View's SELECT contains a subquery in the FROM clause](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1349.md)
- [Error 1350: View's SELECT contains clause](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1350.md)
- [Error 1351: View's SELECT contains a variable or parameter](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1351.md)
- [Error 1352: View's SELECT refers to a temporary table'](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1352.md)
- [Error 1353: View's SELECT and view's field list have different column counts](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1353.md)
- [Error 1354: View merge algorithm can't be used here for now](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1354.md)
- [Error 1355: View being updated does not have complete key of underlying table in it](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1355.md)
- [Error 1356: View references invalid table(s) or column(s) or function(s) or definer/invoker of view](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1356.md)
- [Error 1357: Can't drop or alter from within another stored routine](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1357.md)
- [Error 1358: GOTO is not allowed in a stored procedure handler](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1358.md)
- [Error 1359: Trigger already exists](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1359.md)
- [Error 1360: Trigger does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1360.md)
- [Error 1361: Trigger's is view or temporary table](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1361.md)
- [Error 1362: Updating of row is not allowed in trigger](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1362.md)
- [Error 1363: There is no row in trigger](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1363.md)
- [Error 1364: Field doesn't have a default value](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1364.md)
- [Error 1365: Division by 0](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1365.md)
- [Error 1366: Incorrect value for column at row](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1366.md)
- [Error 1367: Illegal value found during parsing](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1367.md)
- [Error 1368: CHECK OPTION on non-updatable view](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1368.md)
- [Error 1369: CHECK OPTION failed](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1369.md)
- [Error 1370: command denied to user for routine](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1370.md)
- [Error 1371: Failed purging old relay logs](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1371.md)
- [Error 1372: Password hash should be a %d-digit hexadecimal number](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1372.md)
- [Error 1373: Target log not found in binlog index](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1373.md)
- [Error 1374: I/O error reading log index file](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1374.md)
- [Error 1375: Server configuration does not permit binlog purge](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1375.md)
- [Error 1376: Failed on fseek()](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1376.md)
- [Error 1377: Fatal error during log purge](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1377.md)
- [Error 1378: A purgeable log is in use, will not purge](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1378.md)
- [Error 1379: Unknown error during log purge](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1379.md)
- [Error 1380: Failed initializing relay log position](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1380.md)
- [Error 1381: You are not using binary logging](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1381.md)
- [Error 1382: The syntax is reserved for purposes internal to the MariaDB server](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1382.md)
- [Error 1383: WSAStartup Failed](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1383.md)
- [Error 1384: Can't handle procedures with different groups yet](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1384.md)
- [Error 1385: Select must have a group with this procedure](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1385.md)
- [Error 1386: Can't use ORDER clause with this procedure](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1386.md)
- [Error 1387: Binary logging and replication forbid changing the global server](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1387.md)
- [Error 1388: Can't map file](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1388.md)
- [Error 1389: Wrong magic in](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1389.md)
- [Error 1390: Prepared statement contains too many placeholders](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1390.md)
- [Error 1391: Key part length cannot be 0](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1391.md)
- [Error 1392: View text checksum failed](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1392.md)
- [Error 1393: Can not modify more than one base table through a join view](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1393.md)
- [Error 1394: Can not insert into join view without fields list](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1394.md)
- [Error 1395: Can not delete from join view](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1395.md)
- [Error 1396: Operation failed for](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1396.md)
- [Error 1397: XAER\_NOTA: Unknown XID](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1397.md)
- [Error 1398: XAER\_INVAL: Invalid arguments (or unsupported command)](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1398.md)
- [Error 1399: XAER\_RMFAIL: The command cannot be executed when global transaction is in the state](/docs/server/reference/error-codes/mariadb-error-codes-1300-to-1399/e1399.md)
- [MariaDB Error Codes 1400 to 1499](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499.md)
- [Error 1400: XAER\_OUTSIDE: Some work is done outside global transaction](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1400.md)
- [Error 1401: XAER\_RMERR: Fatal error occurred in the transaction branch - check your data for consist](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1401.md)
- [Error 1402: XA\_RBROLLBACK: Transaction branch was rolled back](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1402.md)
- [Error 1403: There is no such grant defined for user on host on routine](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1403.md)
- [Error 1404: Failed to grant EXECUTE and ALTER ROUTINE privileges](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1404.md)
- [Error 1405: Failed to revoke all privileges to dropped routine](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1405.md)
- [Error 1406: Data too long for column at row](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1406.md)
- [Error 1407: Bad SQLSTATE](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1407.md)
- [Error 1408: ready for connections. Version: socket: port:](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1408.md)
- [Error 1409: Can't load value from file with fixed size rows to variable](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1409.md)
- [Error 1410: You are not allowed to create a user with GRANT](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1410.md)
- [Error 1411: Incorrect value for function](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1411.md)
- [Error 1412: Table definition has changed, please retry transaction](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1412.md)
- [Error 1413: Duplicate handler declared in the same block](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1413.md)
- [Error 1414: OUT or INOUT argument for routine is not a variable or NEW pseudo-variable in BEFORE tri](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1414.md)
- [Error 1415: Not allowed to return a result set from](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1415.md)
- [Error 1416: Cannot get geometry object from data you send to the GEOMETRY field](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1416.md)
- [Error 1417: A routine failed and has neither NO SQL nor READS SQL DATA in its declaration](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1417.md)
- [Error 1418: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration an](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1418.md)
- [Error 1419: You do not have the SUPER privilege and binary logging is enabled](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1419.md)
- [Error 1420: You can't execute a prepared statement which has an open cursor associated with it](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1420.md)
- [Error 1421: The statement has no open cursor](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1421.md)
- [Error 1422: Explicit or implicit commit is not allowed in stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1422.md)
- [Error 1423: Field of view underlying table doesn't have a default value](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1423.md)
- [Error 1424: Recursive stored functions and triggers are not allowed.](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1424.md)
- [Error 1425: Too big scale specified for column](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1425.md)
- [Error 1426: Too big precision specified for column](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1426.md)
- [Error 1427: For float(M,D, double(M,D or decimal(M,D, M must be >= D](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1427.md)
- [Error 1428: You can't combine write-locking of system tables with other tables or lock types](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1428.md)
- [Error 1429: Unable to connect to foreign data source](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1429.md)
- [Error 1430: There was a problem processing the query on the foreign data source](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1430.md)
- [Error 1431: The foreign data source you are trying to reference does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1431.md)
- [Error 1432: Can't create federated table. The data source connection string is not in the correct fo](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1432.md)
- [Error 1433: The data source connection string is not in the correct format](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1433.md)
- [Error 1434: Can't create federated table. Foreign data src error](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1434.md)
- [Error 1435: Trigger in wrong schema](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1435.md)
- [Error 1436: Thread stack overrun](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1436.md)
- [Error 1437: Routine body is too long](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1437.md)
- [Error 1438: Cannot drop default keycache](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1438.md)
- [Error 1439: Display width out of range for column](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1439.md)
- [Error 1440: XAER\_DUPID: The XID already exists](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1440.md)
- [Error 1441: Datetime function: field overflow](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1441.md)
- [Error 1442: Can't update table in stored function/trigger because it is already used by statement wh](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1442.md)
- [Error 1443: The definition of table prevents operation on table](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1443.md)
- [Error 1444: The prepared statement contains a stored routine call that refers to that same statement](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1444.md)
- [Error 1445: Not allowed to set autocommit from a stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1445.md)
- [Error 1446: Definer is not fully qualified](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1446.md)
- [Error 1447: View has no definer information (old table format)](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1447.md)
- [Error 1448: You need the SUPER privilege for creation view with definer](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1448.md)
- [Error 1449: The user specified as a definer does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1449.md)
- [Error 1450: Changing schema from is not allowed.](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1450.md)
- [Error 1451: Cannot delete or update a parent row: a foreign key constraint fails](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1451.md)
- [Error 1452: Cannot add or update a child row: a foreign key constraint fails](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1452.md)
- [Error 1453: Variable must be quoted with ..., or renamed](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1453.md)
- [Error 1454: No definer attribute for trigger](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1454.md)
- [Error 1455: has an old format, you should re-create the object(s)](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1455.md)
- [Error 1456: Recursive limit (as set by the max\_sp\_recursion\_depth variable) was exceeded for routine](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1456.md)
- [Error 1457: Failed to load routine](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1457.md)
- [Error 1458: Incorrect routine name](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1458.md)
- [Error 1459: Table upgrade required. Please do "REPAIR TABLE" or dump/reload to fix it!](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1459.md)
- [Error 1460: AGGREGATE is not supported for stored functions](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1460.md)
- [Error 1461: Can't create more than max\_prepared\_stmt\_count statements](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1461.md)
- [Error 1462: contains view recursion](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1462.md)
- [Error 1463: Non-grouping field is used in clause](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1463.md)
- [Error 1464: The used table type doesn't support SPATIAL indexes](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1464.md)
- [Error 1465: Triggers can not be created on system tables](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1465.md)
- [Error 1466: Leading spaces are removed from name](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1466.md)
- [Error 1467: Failed to read auto-increment value from storage engine](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1467.md)
- [Error 1468: user name](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1468.md)
- [Error 1469: host name](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1469.md)
- [Error 1470: String is too long for (should be no longer than )](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1470.md)
- [Error 1471: The target table of the is not insertable-into](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1471.md)
- [Error 1472: Table is differently defined or of non-MyISAM type or doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1472.md)
- [Error 1473: Too high level of nesting for select](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1473.md)
- [Error 1474: Name has become ''](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1474.md)
- [Error 1475: First character of the FIELDS TERMINATED string is ambiguous](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1475.md)
- [Error 1476: The foreign server you are trying to create already exists](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1476.md)
- [Error 1477: The foreign server name you are trying to reference does not exist. Data source error](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1477.md)
- [Error 1478: Table storage engine does not support the create option](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1478.md)
- [Error 1479: Syntax error: PARTITIONING requires definition of VALUES for each partition](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1479.md)
- [Error 1480: Only PARTITIONING can use VALUES in partition definition](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1480.md)
- [Error 1481: MAXVALUE can only be used in last partition definition](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1481.md)
- [Error 1482: Subpartitions can only be hash partitions and by key](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1482.md)
- [Error 1483: Must define subpartitions on all partitions if on one partition](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1483.md)
- [Error 1484: Wrong number of partitions defined, mismatch with previous setting](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1484.md)
- [Error 1485: Wrong number of subpartitions defined, mismatch with previous setting](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1485.md)
- [Error 1486: Constant/Random expression in (sub)partitioning function is not allowed](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1486.md)
- [Error 1487: Expression in RANGE/LIST VALUES must be constant](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1487.md)
- [Error 1488: Field in list of fields for partition function not found in table](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1488.md)
- [Error 1489: List of fields is only allowed in KEY partitions](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1489.md)
- [Error 1490: The partition info in the frm file is not consistent with what can be written into the f](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1490.md)
- [Error 1491: The function returns the wrong type](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1491.md)
- [Error 1492: For partitions each partition must be defined](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1492.md)
- [Error 1493: VALUES LESS THAN value must be strictly increasing for each partition](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1493.md)
- [Error 1494: VALUES value must be of same type as partition function](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1494.md)
- [Error 1495: Multiple definition of same constant in list partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1495.md)
- [Error 1496: Partitioning can not be used stand-alone in query](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1496.md)
- [Error 1497: The mix of handlers in the partitions is not allowed in this version of MariaDB](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1497.md)
- [Error 1498: For the partitioned engine it is necessary to define all](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1498.md)
- [Error 1499: Too many partitions (including subpartitions) were defined](/docs/server/reference/error-codes/mariadb-error-codes-1400-to-1499/e1499.md)
- [MariaDB Error Codes 1500 to 1599](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599.md)
- [Error 1500: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpar](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1500.md)
- [Error 1501: Failed to create specific handler file](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1501.md)
- [Error 1502: A BLOB field is not allowed in partition function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1502.md)
- [Error 1503: must include all columns in the table's partitioning function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1503.md)
- [Error 1504: Number of = 0 is not an allowed value](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1504.md)
- [Error 1505: Partition management on a not partitioned table is not possible](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1505.md)
- [Error 1506: Foreign key clause is not yet supported in conjunction with partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1506.md)
- [Error 1507: Error in list of partitions to](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1507.md)
- [Error 1508: Cannot remove all partitions, use DROP TABLE instead](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1508.md)
- [Error 1509: COALESCE PARTITION can only be used on HASH/KEY partitions](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1509.md)
- [Error 1510: REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbe](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1510.md)
- [Error 1511: REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables usin](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1511.md)
- [Error 1512: PARTITION can only be used on RANGE/LIST partitions](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1512.md)
- [Error 1513: Trying to Add partition(s) with wrong number of subpartitions](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1513.md)
- [Error 1514: At least one partition must be added](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1514.md)
- [Error 1515: At least one partition must be coalesced](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1515.md)
- [Error 1516: More partitions to reorganize than there are partitions](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1516.md)
- [Error 1517: Duplicate partition name](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1517.md)
- [Error 1518: It is not allowed to shut off binlog on this command](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1518.md)
- [Error 1519: When reorganizing a set of partitions they must be in consecutive order](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1519.md)
- [Error 1520: Reorganize of range partitions cannot change total ranges except for last partition wher](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1520.md)
- [Error 1521: Partition function not supported in this version for this handler](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1521.md)
- [Error 1522: Partition state cannot be defined from CREATE/ALTER TABLE](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1522.md)
- [Error 1523: The handler only supports 32 bit integers in VALUES](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1523.md)
- [Error 1524: Plugin is not loaded](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1524.md)
- [Error 1525: Incorrect value](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1525.md)
- [Error 1526: Table has no partition for value](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1526.md)
- [Error 1527: It is not allowed to specify more than once](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1527.md)
- [Error 1528: Failed to create](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1528.md)
- [Error 1529: Failed to drop](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1529.md)
- [Error 1530: The handler doesn't support autoextend of tablespaces](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1530.md)
- [Error 1531: A size parameter was incorrectly specified, either number or on the form 10M](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1531.md)
- [Error 1532: The size number was correct but we don't allow the digit part to be more than 2 billion](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1532.md)
- [Error 1533: Failed to alter](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1533.md)
- [Error 1534: Writing one row to the row-based binary log failed](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1534.md)
- [Error 1535: Table definition on master and slave does not match](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1535.md)
- [Error 1536: Slave running with --log-slave-updates must use row-based binary logging to be able to r](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1536.md)
- [Error 1537: Event already exists](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1537.md)
- [Error 1538: Failed to store event. Error code from storage engine.](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1538.md)
- [Error 1539: Unknown event](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1539.md)
- [Error 1540: Failed to alter event](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1540.md)
- [Error 1541: Failed to drop](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1541.md)
- [Error 1542: INTERVAL is either not positive or too big](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1542.md)
- [Error 1543: ENDS is either invalid or before STARTS](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1543.md)
- [Error 1544: Event execution time is in the past. Event has been disabled](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1544.md)
- [Error 1545: Failed to open mysql.event](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1545.md)
- [Error 1546: No datetime expression provided](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1546.md)
- [Error 1547: Column count is wrong. Expected found. The table is probably corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1547.md)
- [Error 1548: Cannot load from mysql. The table is probably corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1548.md)
- [Error 1549: Failed to delete the event from mysql.event](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1549.md)
- [Error 1550: Error during compilation of event's body](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1550.md)
- [Error 1551: Same old and new event name](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1551.md)
- [Error 1552: Data for column too long](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1552.md)
- [Error 1553: Cannot drop index needed in a foreign key constraint](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1553.md)
- [Error 1554: The syntax is deprecated and will be removed in MariaDB](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1554.md)
- [Error 1555: You can't write-lock a log table. Only read access is possible](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1555.md)
- [Error 1556: You can't use locks with log tables](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1556.md)
- [Error 1557: Upholding foreign key constraints for table, entry, key would lead to a duplicate entry](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1557.md)
- [Error 1558: Column count is wrong. Expected found. Created with MariaDB now running. Please use mysq](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1558.md)
- [Error 1559: Cannot switch out of the row-based binary log format when the session has open temporary](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1559.md)
- [Error 1560: Cannot change the binary logging format inside a stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1560.md)
- [Error 1561: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1561.md)
- [Error 1562: Cannot create temporary table with partitions](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1562.md)
- [Error 1563: Partition constant is out of partition function domain](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1563.md)
- [Error 1564: This partition function is not allowed](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1564.md)
- [Error 1565: Error in DDL log](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1565.md)
- [Error 1566: Not allowed to use NULL value in VALUES LESS THAN](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1566.md)
- [Error 1567: Incorrect partition name](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1567.md)
- [Error 1568: Transaction isolation level can't be changed while a transaction is in progress](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1568.md)
- [Error 1569: ALTER TABLE causes auto\_increment resequencing, resulting in duplicate entry for key](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1569.md)
- [Error 1570: Internal scheduler error](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1570.md)
- [Error 1571: Error during starting/stopping of the scheduler](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1571.md)
- [Error 1572: Engine cannot be used in partitioned tables](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1572.md)
- [Error 1573: Cannot activate log](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1573.md)
- [Error 1574: The server was not built with row-based replication](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1574.md)
- [Error 1575: Decoding of base64 string failed](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1575.md)
- [Error 1576: Recursion of EVENT DDL statements is forbidden when body is present](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1576.md)
- [Error 1577: Cannot proceed because system tables used by Event Scheduler were found damaged at serve](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1577.md)
- [Error 1578: Only integers allowed as number here](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1578.md)
- [Error 1579: This storage engine cannot be used for log tables](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1579.md)
- [Error 1580: You cannot '%s' a log table if logging is enabled](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1580.md)
- [Error 1581: Cannot rename. When logging enabled, rename to/from log table must rename two tables](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1581.md)
- [Error 1582: Incorrect parameter count in the call to native function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1582.md)
- [Error 1583: Incorrect parameters in the call to native function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1583.md)
- [Error 1584: Incorrect parameters in the call to stored function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1584.md)
- [Error 1585: This function has the same name as a native function](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1585.md)
- [Error 1586: Duplicate entry for key](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1586.md)
- [Error 1587: Too many files opened, please execute the command again](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1587.md)
- [Error 1588: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1588.md)
- [Error 1589: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1589.md)
- [Error 1590: The incident occured on the master](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1590.md)
- [Error 1591: Table has no partition for some existing values](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1591.md)
- [Error 1592: Unsafe statement written to the binary log using statement format since BINLOG\_FORMAT =](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1592.md)
- [Error 1593: Fatal error](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1593.md)
- [Error 1594: Relay log read failure](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1594.md)
- [Error 1595: Relay log write failure](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1595.md)
- [Error 1596: Failed to create](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1596.md)
- [Error 1597: Master command failed](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1597.md)
- [Error 1598: Binary logging not possible](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1598.md)
- [Error 1599: View has no creation context](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1599.md)
- [MariaDB Error Codes 1600 to 1699](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699.md)
- [Error 1600: Creation context of view is invalid](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1600.md)
- [Error 1601: Creation context of stored routine is invalid](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1601.md)
- [Error 1602: Corrupted TRG file for table](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1602.md)
- [Error 1603: Triggers for table have no creation context](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1603.md)
- [Error 1604: Trigger creation context of table is invalid](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1604.md)
- [Error 1605: Creation context of event is invalid](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1605.md)
- [Error 1606: Cannot open table for trigger](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1606.md)
- [Error 1607: Cannot create stored routine. Check warnings](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1607.md)
- [Error 1608: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1608.md)
- [Error 1609: The BINLOG statement of type was not preceded by a format description BINLOG statement.](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1609.md)
- [Error 1610: Corrupted replication event was detected](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1610.md)
- [Error 1611: Invalid column reference in LOAD DATA](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1611.md)
- [Error 1612: Being purged log was not found](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1612.md)
- [Error 1613: XA\_RBTIMEOUT: Transaction branch was rolled back: took too long](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1613.md)
- [Error 1614: XA\_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1614.md)
- [Error 1615: Prepared statement needs to be re-prepared](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1615.md)
- [Error 1616: DELAYED option not supported for table](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1616.md)
- [Error 1617: The master info structure does not exist](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1617.md)
- [Error 1618: option ignored](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1618.md)
- [Error 1619: Built-in plugins cannot be deleted](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1619.md)
- [Error 1620: Plugin is busy and will be uninstalled on shutdown](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1620.md)
- [Error 1621: variable is read-only. Use SET to assign the value](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1621.md)
- [Error 1622: Storage engine does not support rollback for this statement](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1622.md)
- [Error 1623: Unexpected master's heartbeat data](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1623.md)
- [Error 1624: The requested value for the heartbeat period is either negative or exceeds the maximum a](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1624.md)
- [Error 1625: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1625.md)
- [Error 1626: Error in parsing conflict function](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1626.md)
- [Error 1627: Write to exceptions table failed](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1627.md)
- [Error 1628: Comment for table is too long](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1628.md)
- [Error 1629: Comment for field is too long](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1629.md)
- [Error 1630: FUNCTION does not exist. Check the 'Function Name Parsing and Resolution' section in the](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1630.md)
- [Error 1631: Database](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1631.md)
- [Error 1632: Table](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1632.md)
- [Error 1633: Partition](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1633.md)
- [Error 1634: Subpartition](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1634.md)
- [Error 1635: Temporary](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1635.md)
- [Error 1636: Renamed](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1636.md)
- [Error 1637: Too many active concurrent transactions](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1637.md)
- [Error 1638: Non-ASCII separator arguments are not fully supported](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1638.md)
- [Error 1639: debug sync point wait timed out](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1639.md)
- [Error 1640: debug sync point hit limit reached](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1640.md)
- [Error 1641: Duplicate condition information item](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1641.md)
- [Error 1642: Unhandled user-defined warning condition](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1642.md)
- [Error 1643: Unhandled user-defined not found condition](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1643.md)
- [Error 1644: Unhandled user-defined exception condition](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1644.md)
- [Error 1645: RESIGNAL when handler not active](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1645.md)
- [Error 1646: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1646.md)
- [Error 1647: Data truncated for condition item](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1647.md)
- [Error 1648: Data too long for condition item](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1648.md)
- [Error 1649: Unknown locale](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1649.md)
- [Error 1650: The requested server id clashes with the slave startup option --replicate-same-server-id](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1650.md)
- [Error 1651: Query cache is disabled; restart the server with query\_cache\_type=1 to enable it](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1651.md)
- [Error 1652: Duplicate partition field name](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1652.md)
- [Error 1653: Inconsistency in usage of column lists for partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1653.md)
- [Error 1654: Partition column values of incorrect type](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1654.md)
- [Error 1655: Too many fields](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1655.md)
- [Error 1656: Cannot use MAXVALUE as value in VALUES IN](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1656.md)
- [Error 1657: Cannot have more than one value for this type of partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1657.md)
- [Error 1658: Row expressions in VALUES IN only allowed for multi-field column partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1658.md)
- [Error 1659: Field is of a not allowed type for this type of partitioning](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1659.md)
- [Error 1660: The total length of the partitioning fields is too large](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1660.md)
- [Error 1661: Cannot execute statement: impossible to write to binary log since both row-incapable eng](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1661.md)
- [Error 1662: Cannot execute statement: impossible to write to binary log since BINLOG\_FORMAT = ROW an](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1662.md)
- [Error 1663: Cannot execute statement: impossible to write to binary log since statement is unsafe, s](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1663.md)
- [Error 1664: Cannot execute statement: impossible to write to binary log since statement is in row fo](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1664.md)
- [Error 1665: Cannot execute statement: impossible to write to binary log since BINLOG\_FORMAT = STATEM](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1665.md)
- [Error 1666: Cannot execute statement: impossible to write to binary log since statement is in row fo](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1666.md)
- [Error 1667: Cannot execute statement: impossible to write to binary log since more than one engine i](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1667.md)
- [Error 1668: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set o](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1668.md)
- [Error 1669: The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1669.md)
- [Error 1670: The statement is unsafe because it uses the general log, slow query log, or performance\_](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1670.md)
- [Error 1671: Statement is unsafe because it invokes a trigger or a stored function that inserts into](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1671.md)
- [Error 1672: Statement is unsafe because it uses a UDF which may not return the same value on the sla](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1672.md)
- [Error 1673: Statement is unsafe because it uses a system variable that may have a different value on](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1673.md)
- [Error 1674: Statement is unsafe because it uses a system function that may return a different value](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1674.md)
- [Error 1675: Statement is unsafe because it accesses a non-transactional table after accessing a tran](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1675.md)
- [Error 1676: Statement](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1676.md)
- [Error 1677: Column of table cannot be converted from type to type](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1677.md)
- [Error 1678: Can't create conversion table for table](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1678.md)
- [Error 1679: Cannot modify @@session.binlog\_format inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1679.md)
- [Error 1680: The path specified is too long](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1680.md)
- [Error 1681: is deprecated and will be removed in a future release.](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1681.md)
- [Error 1682: Native table has the wrong structure](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1682.md)
- [Error 1683: Invalid performance\_schema usage](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1683.md)
- [Error 1684: Table was skipped since its definition is being modified by concurrent DDL statement](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1684.md)
- [Error 1685: Cannot modify @@session.binlog\_direct\_non\_transactional\_updates inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1685.md)
- [Error 1686: Cannot change the binlog direct flag inside a stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1686.md)
- [Error 1687: A SPATIAL index may only contain a geometrical type column](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1687.md)
- [Error 1688: Comment for index is too long](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1688.md)
- [Error 1689: Wait on a lock was aborted due to a pending exclusive lock](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1689.md)
- [Error 1690: value is out of range in](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1690.md)
- [Error 1691: A variable of a non-integer based type in LIMIT clause](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1691.md)
- [Error 1692: Mixing self-logging and non-self-logging engines in a statement is unsafe.](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1692.md)
- [Error 1693: Statement accesses nontransactional table as well as transactional or temporary table, a](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1693.md)
- [Error 1694: Cannot modify @@session.sql\_log\_bin inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1694.md)
- [Error 1695: Cannot change the sql\_log\_bin inside a stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1695.md)
- [Error 1696: Failed to read from the .par file](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1696.md)
- [Error 1697: VALUES value for partition must have type INT](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1697.md)
- [Error 1698: Access denied for user](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1698.md)
- [Error 1699: SET PASSWORD has no significance for users authenticating via plugins](/docs/server/reference/error-codes/mariadb-error-codes-1600-to-1699/e1699.md)
- [MariaDB Error Codes 1700 to 1799](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799.md)
- [Error 1700: GRANT with IDENTIFIED WITH is illegal because the user already exists](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1700.md)
- [Error 1701: Cannot truncate a table referenced in a foreign key constraint](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1701.md)
- [Error 1702: Plugin is force\_plus\_permanent and can not be unloaded](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1702.md)
- [Error 1703: The requested value for the heartbeat period is less than 1 millisecond](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1703.md)
- [Error 1704: The requested value for the heartbeat period exceeds the value of slave\_net\_timeout seco](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1704.md)
- [Error 1705: Multi-row statements required more than 'max\_binlog\_stmt\_cache\_size' bytes of storage; i](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1705.md)
- [Error 1706: Primary key/partition key update is not allowed since the table is updated both as and](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1706.md)
- [Error 1707: Table rebuild required. Please do "ALTER TABLE FORCE" or dump/reload to fix it!](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1707.md)
- [Error 1708: The value of should be no less than the value of](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1708.md)
- [Error 1709: Index column size too large. The maximum column size is bytes.](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1709.md)
- [Error 1710: Trigger has an error in its body](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1710.md)
- [Error 1711: Unknown trigger has an error in its body](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1711.md)
- [Error 1712: Index is corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1712.md)
- [Error 1713: Undo log record is too big](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1713.md)
- [Error 1714: INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the S](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1714.md)
- [Error 1715: INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows ar](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1715.md)
- [Error 1716: REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1716.md)
- [Error 1717: CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the S](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1717.md)
- [Error 1718: CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1718.md)
- [Error 1719: UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1719.md)
- [Error 1720: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1720.md)
- [Error 1721: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1721.md)
- [Error 1722: Statements writing to a table with an auto-increment column after selecting from another](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1722.md)
- [Error 1723: CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1723.md)
- [Error 1724: INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1724.md)
- [Error 1725: Table is being used in foreign key check.](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1725.md)
- [Error 1726: Storage engine does not support system tables](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1726.md)
- [Error 1727: INSERT into autoincrement field which is not the first part in the composed primary key](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1727.md)
- [Error 1728: Cannot load from. The table is probably corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1728.md)
- [Error 1729: The requested value for the master delay exceeds the maximum](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1729.md)
- [Error 1730: Only Format\_description\_log\_event and row events are allowed in BINLOG statements](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1730.md)
- [Error 1731: Non matching attribute between partition and table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1731.md)
- [Error 1732: Table to exchange with partition is partitioned](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1732.md)
- [Error 1733: Table to exchange with partition is temporary](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1733.md)
- [Error 1734: Subpartitioned table, use subpartition instead of partition](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1734.md)
- [Error 1735: Unknown partition in table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1735.md)
- [Error 1736: Tables have different definitions](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1736.md)
- [Error 1737: Found a row that does not match the partition](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1737.md)
- [Error 1738: Option binlog\_cache\_size is greater than max\_binlog\_cache\_size; setting binlog\_cache\_siz](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1738.md)
- [Error 1739: Cannot use access on index due to type or collation conversion on field](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1739.md)
- [Error 1740: Table to exchange with partition has foreign key references](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1740.md)
- [Error 1741: Key value was not found in table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1741.md)
- [Error 1742: Data for column too long](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1742.md)
- [Error 1743: Replication event checksum verification failed while reading from network.](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1743.md)
- [Error 1744: Replication event checksum verification failed while reading from a log file](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1744.md)
- [Error 1745: Option binlog\_stmt\_cache\_size is greater than max\_binlog\_stmt\_cache\_size](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1745.md)
- [Error 1746: Can't update table while is being created](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1746.md)
- [Error 1747: PARTITION () clause on non partitioned table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1747.md)
- [Error 1748: Found a row not matching the given partition set](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1748.md)
- [Error 1749: partition doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1749.md)
- [Error 1750: Failure while changing the type of replication repository](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1750.md)
- [Error 1751: The creation of some temporary tables could not be rolled back.](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1751.md)
- [Error 1752: Some temporary tables were dropped, but these operations could not be rolled back.](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1752.md)
- [Error 1753: is not supported in multi-threaded slave mode](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1753.md)
- [Error 1754: The number of modified databases exceeds the maximum](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1754.md)
- [Error 1755: Cannot execute the current event group in the parallel mode](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1755.md)
- [Error 1756: %s](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1756.md)
- [Error 1757: FULLTEXT index is not supported for partitioned tables](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1757.md)
- [Error 1758: Invalid condition number](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1758.md)
- [Error 1759: Sending passwords in plain text without SSL/TLS is extremely insecure](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1759.md)
- [Error 1760: Storing MariaDB user name or password information in the master.info repository is not s](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1760.md)
- [Error 1761: Foreign key constraint for table, record would lead to a duplicate entry in table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1761.md)
- [Error 1762: Foreign key constraint for table, record would lead to a duplicate entry in a child tabl](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1762.md)
- [Error 1763: Setting authentication options is not possible when only the Slave SQL Thread is being s](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1763.md)
- [Error 1764: The table does not have FULLTEXT index to support this query](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1764.md)
- [Error 1765: The system variable cannot be set in stored functions or triggers](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1765.md)
- [Error 1766: The system variable cannot be set when there is an ongoing transaction](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1766.md)
- [Error 1767: The system variable @@SESSION.GTID\_NEXT has the value which is not listed in @@SESSION.G](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1767.md)
- [Error 1768: The system variable @@SESSION.GTID\_NEXT cannot change inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1768.md)
- [Error 1769: The statement 'SET' cannot invoke a stored function](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1769.md)
- [Error 1770: The system variable @@SESSION.GTID\_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID\_NEXT\_L](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1770.md)
- [Error 1771: Skipping transaction because it has already been executed and logged](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1771.md)
- [Error 1772: Malformed GTID set specification](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1772.md)
- [Error 1773: Malformed GTID set encoding](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1773.md)
- [Error 1774: Malformed GTID specification](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1774.md)
- [Error 1775: Impossible to generate Global Transaction Identifier: the integer component reached the](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1775.md)
- [Error 1776: Parameters MASTER\_LOG\_FILE, MASTER\_LOG\_POS, RELAY\_LOG\_FILE and RELAY\_LOG\_POS cannot be s](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1776.md)
- [Error 1777: CHANGE MASTER TO MASTER\_AUTO\_POSITION = 1 can only be executed when @@GLOBAL.GTID\_MODE =](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1777.md)
- [Error 1778: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID\_](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1778.md)
- [Error 1779: GTID\_MODE = ON or GTID\_MODE = UPGRADE\_STEP\_2 requires DISABLE\_GTID\_UNSAFE\_STATEMENTS = 1](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1779.md)
- [Error 1780: @@GLOBAL.GTID\_MODE = ON or UPGRADE\_STEP\_1 or UPGRADE\_STEP\_2 requires --log-bin and --log](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1780.md)
- [Error 1781: @@SESSION.GTID\_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID\_MODE = OFF](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1781.md)
- [Error 1782: @@SESSION.GTID\_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID\_MODE = ON](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1782.md)
- [Error 1783: @@SESSION.GTID\_NEXT\_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID\_MODE = OFF](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1783.md)
- [Error 1784: Found a Gtid\_log\_event or Previous\_gtids\_log\_event when @@GLOBAL.GTID\_MODE = OFF](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1784.md)
- [Error 1785: When @@GLOBAL.ENFORCE\_GTID\_CONSISTENCY = 1, updates to non-transactional tables can only](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1785.md)
- [Error 1786: CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE\_GTID\_CONSISTENCY = 1](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1786.md)
- [Error 1787: When @@GLOBAL.ENFORCE\_GTID\_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DR](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1787.md)
- [Error 1788: The value of @@GLOBAL.GTID\_MODE can only change one step at a time](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1788.md)
- [Error 1789: The slave is connecting using CHANGE MASTER TO MASTER\_AUTO\_POSITION = 1, but the master](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1789.md)
- [Error 1790: @@SESSION.GTID\_NEXT cannot be changed by a client that owns a GTID](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1790.md)
- [Error 1791: Unknown EXPLAIN format name](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1791.md)
- [Error 1792: Cannot execute statement in a READ ONLY transaction](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1792.md)
- [Error 1793: Comment for table partition is too long](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1793.md)
- [Error 1794: Slave is not configured or failed to initialize properly. You must at least set --server](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1794.md)
- [Error 1795: InnoDB presently supports one FULLTEXT index creation at a time](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1795.md)
- [Error 1796: Cannot create FULLTEXT index on temporary InnoDB table](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1796.md)
- [Error 1797: Column is of wrong type for an InnoDB FULLTEXT index](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1797.md)
- [Error 1798: Index '%s' is of wrong type for an InnoDB FULLTEXT index](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1798.md)
- [Error 1799: Creating index required more than 'innodb\_online\_alter\_log\_max\_size' bytes of modificati](/docs/server/reference/error-codes/mariadb-error-codes-1700-to-1799/e1799.md)
- [MariaDB Error Codes 1800 to 1899](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899.md)
- [Error 1800: Unknown ALGORITHM](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1800.md)
- [Error 1801: Unknown LOCK type](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1801.md)
- [Error 1802: CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in M](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1802.md)
- [Error 1803: Cannot recover after SLAVE errored out in parallel execution mode](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1803.md)
- [Error 1804: Cannot clean up worker info tables](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1804.md)
- [Error 1805: Column count of is wrong. Expected, found. The table is probably corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1805.md)
- [Error 1806: Slave must silently retry current transaction](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1806.md)
- [Error 1807: There is a foreign key check running on table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1807.md)
- [Error 1808: Schema mismatch](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1808.md)
- [Error 1809: Table in system tablespace](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1809.md)
- [Error 1810: IO Read error](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1810.md)
- [Error 1811: IO Write error](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1811.md)
- [Error 1812: Tablespace is missing for table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1812.md)
- [Error 1813: Tablespace for table exists. Please DISCARD the tablespace before IMPORT](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1813.md)
- [Error 1814: Tablespace has been discarded for table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1814.md)
- [Error 1815: Internal error](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1815.md)
- [Error 1816: ALTER TABLE IMPORT TABLESPACE failed with error](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1816.md)
- [Error 1817: Index corrupt](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1817.md)
- [Error 1818: YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1818.md)
- [Error 1819: Your password does not satisfy the current policy requirements](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1819.md)
- [Error 1820: You must SET PASSWORD before executing this statement](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1820.md)
- [Error 1821: Failed to add the foreign key constaint. Missing index for constraint in the foreign tab](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1821.md)
- [Error 1822: Failed to add the foreign key constaint. Missing index for constraint in the referenced](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1822.md)
- [Error 1823: Failed to add the foreign key constraint to system tables](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1823.md)
- [Error 1824: Failed to open the referenced table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1824.md)
- [Error 1825: Failed to add the foreign key constraint on table. Incorrect options in FOREIGN KEY cons](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1825.md)
- [Error 1826: Duplicate foreign key constraint name](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1826.md)
- [Error 1827: The password hash doesn't have the expected format](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1827.md)
- [Error 1828: Cannot drop column: needed in a foreign key constraint](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1828.md)
- [Error 1829: Cannot drop column: needed in a foreign key constraint of table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1829.md)
- [Error 1830: Column cannot be NOT NULL: needed in a foreign key constraint SET NULL](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1830.md)
- [Error 1831: Duplicate index defined on the table. This is deprecated and will be disallowed in a fut](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1831.md)
- [Error 1832: Cannot change column: used in a foreign key constraint](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1832.md)
- [Error 1833: Cannot change column: used in a foreign key constraint of table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1833.md)
- [Error 1834: Cannot delete rows from table which is parent in a foreign key constraint of table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1834.md)
- [Error 1835: Malformed communication packet.](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1835.md)
- [Error 1836: Running in read-only mode](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1836.md)
- [Error 1837: When GTID\_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLL](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1837.md)
- [Error 1838: The system variable cannot be set in stored procedures](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1838.md)
- [Error 1839: @@GLOBAL.GTID\_PURGED can only be set when @@GLOBAL.GTID\_MODE = ON](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1839.md)
- [Error 1840: @@GLOBAL.GTID\_PURGED can only be set when @@GLOBAL.GTID\_EXECUTED is empty](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1840.md)
- [Error 1841: @@GLOBAL.GTID\_PURGED can only be set when there are no ongoing transactions (not even in](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1841.md)
- [Error 1842: @@GLOBAL.GTID\_PURGED was changed from to](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1842.md)
- [Error 1843: @@GLOBAL.GTID\_EXECUTED was changed from to](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1843.md)
- [Error 1844: Cannot execute statement: impossible to write to binary log since BINLOG\_FORMAT = STATEM](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1844.md)
- [Error 1845: is not supported for this operation. Try](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1845.md)
- [Error 1846: is not supported. Reason: Try](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1846.md)
- [Error 1847: COPY algorithm requires a lock](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1847.md)
- [Error 1848: Partition specific operations do not yet support LOCK/ALGORITHM](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1848.md)
- [Error 1849: Columns participating in a foreign key are renamed](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1849.md)
- [Error 1850: Cannot change column type INPLACE](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1850.md)
- [Error 1851: Adding foreign keys needs foreign\_key\_checks=OFF](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1851.md)
- [Error 1852: Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1852.md)
- [Error 1853: Dropping a primary key is not allowed without also adding a new primary key](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1853.md)
- [Error 1854: Adding an auto-increment column requires a lock](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1854.md)
- [Error 1855: Cannot replace hidden FTS\_DOC\_ID with a user-visible one](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1855.md)
- [Error 1856: Cannot drop or rename FTS\_DOC\_ID](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1856.md)
- [Error 1857: Fulltext index creation requires a lock](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1857.md)
- [Error 1858: sql\_slave\_skip\_counter can not be set when the server is running with @@GLOBAL.GTID\_MODE](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1858.md)
- [Error 1859: Duplicate entry for key](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1859.md)
- [Error 1860: Long database name and identifier for object resulted in path length exceeding character](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1860.md)
- [Error 1861: cannot silently convert NULL values, as required in this SQL\_MODE](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1861.md)
- [Error 1862: Your password has expired. To log in you must change it using a client that supports exp](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1862.md)
- [Error 1863: Found a row in wrong partition](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1863.md)
- [Error 1864: Cannot schedule event, relay-log name, position to Worker thread because its size exceed](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1864.md)
- [Error 1865: Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1865.md)
- [Error 1866: The binary log file is logically corrupted](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1866.md)
- [Error 1867: file was not purged because it was being read by thread(s), purged only out of](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1867.md)
- [Error 1868: file was not purged because it is the active log file](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1868.md)
- [Error 1869: Auto-increment value in UPDATE conflicts with internally generated values](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1869.md)
- [Error 1870: Row events are not logged for statements that modify BLACKHOLE tables in row format](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1870.md)
- [Error 1871: Slave failed to initialize master info structure from the repository](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1871.md)
- [Error 1872: Slave failed to initialize relay log info structure from the repository](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1872.md)
- [Error 1873: Access denied trying to change to user (using password). Disconnecting.](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1873.md)
- [Error 1874: InnoDB is in read only mode](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1874.md)
- [Error 1875: STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1875.md)
- [Error 1876: STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1876.md)
- [Error 1877: Operation cannot be performed. The table is missing, corrupt or contains bad data](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1877.md)
- [Error 1878: Temporary file write failure](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1878.md)
- [Error 1879: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuil](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1879.md)
- [Error 1880: "](/docs/server/reference/error-codes/mariadb-error-codes-1800-to-1899/e1880.md)
- [MariaDB Error Codes 1900 to 1999](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999.md)
- [Error 1900: "](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1900.md)
- [Error 1901: Function or expression cannot be used in the clause of](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1901.md)
- [Error 1902: "](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1902.md)
- [Error 1903: Primary key cannot be defined upon a generated column](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1903.md)
- [Error 1904: Key/Index cannot be defined on a virtual generated column](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1904.md)
- [Error 1905: Cannot define foreign key with clause on a generated column](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1905.md)
- [Error 1906: The value specified for generated column in table has been ignored](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1906.md)
- [Error 1907: This is not yet supported for generated columns](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1907.md)
- [Error 1908: "](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1908.md)
- [Error 1909: "](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1909.md)
- [Error 1910: storage engine does not support generated columns](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1910.md)
- [Error 1911: Unknown option](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1911.md)
- [Error 1912: Incorrect value for option](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1912.md)
- [Error 1913: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1913.md)
- [Error 1914: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1914.md)
- [Error 1915: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1915.md)
- [Error 1916: Got overflow when converting to. Value truncated](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1916.md)
- [Error 1917: Truncated value when converting to](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1917.md)
- [Error 1918: Encountered illegal value when converting to](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1918.md)
- [Error 1919: Encountered illegal format of dynamic column string](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1919.md)
- [Error 1920: Dynamic column implementation limit reached](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1920.md)
- [Error 1921: Illegal value used as argument of dynamic column function](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1921.md)
- [Error 1922: Dynamic column contains unknown character set](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1922.md)
- [Error 1923: At least one of the 'in\_to\_exists' or 'materialization' optimizer\_switch flags must be '](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1923.md)
- [Error 1924: Query cache is disabled (resize or similar command in progress); repeat this command lat](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1924.md)
- [Error 1925: Query cache is globally disabled and you can't enable it only for this session](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1925.md)
- [Error 1926: View ORDER BY clause ignored because there is other ORDER BY clause already](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1926.md)
- [Error 1927: Connection was killed](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1927.md)
- [Error 1928: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1928.md)
- [Error 1929: Cannot modify @@session.skip\_replication inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1929.md)
- [Error 1930: Cannot modify @@session.skip\_replication inside a stored function or trigger](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1930.md)
- [Error 1931: Query execution was interrupted. The query exceeded. The query result may be incomplete](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1931.md)
- [Error 1932: Table doesn't exist in engine](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1932.md)
- [Error 1933: Target is not running an EXPLAINable command](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1933.md)
- [Error 1934: Connection conflicts with existing connection](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1934.md)
- [Error 1935: Master](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1935.md)
- [Error 1936: Can't %s SLAVE](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1936.md)
- [Error 1937: SLAVE started](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1937.md)
- [Error 1938: SLAVE stopped](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1938.md)
- [Error 1939: Engine failed to discover table with](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1939.md)
- [Error 1940: Failed initializing replication GTID state](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1940.md)
- [Error 1941: Could not parse GTID list](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1941.md)
- [Error 1942: Could not update replication slave gtid state](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1942.md)
- [Error 1943: GTID conflict (duplicate domain id)](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1943.md)
- [Error 1944: Failed to open](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1944.md)
- [Error 1945: Connecting slave requested to start from GTID, which is not in the master's binlog](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1945.md)
- [Error 1946: Failed to load replication slave GTID position from table](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1946.md)
- [Error 1947: Specified GTID conflicts with the binary log which contains a more recent GTID](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1947.md)
- [Error 1948: Specified value for @@gtid\_slave\_pos contains no value for replication domain](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1948.md)
- [Error 1949: START SLAVE UNTIL master\_gtid\_pos requires that slave is using GTID](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1949.md)
- [Error 1950: An attempt was made to binlog GTID which would create an out-of-order sequence number wi](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1950.md)
- [Error 1951: The binlog on the master is missing the GTID requested by the slave](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1951.md)
- [Error 1952: Unexpected GTID received from master after reconnect](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1952.md)
- [Error 1953: Cannot modify @@session.gtid\_domain\_id or @@session.gtid\_seq\_no inside a transaction](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1953.md)
- [Error 1954: Cannot modify @@session.gtid\_domain\_id or @@session.gtid\_seq\_no inside a stored function](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1954.md)
- [Error 1955: Connecting slave requested to start from GTID which is not in the master's binlog](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1955.md)
- [Error 1956: This operation is not allowed if any GTID has been logged to the binary log](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1956.md)
- [Error 1957: Unknown query id](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1957.md)
- [Error 1958: Bad base64 data as position](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1958.md)
- [Error 1959: Invalid role specification](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1959.md)
- [Error 1960: The current user is invalid](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1960.md)
- [Error 1961: Cannot grant role to](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1961.md)
- [Error 1962: Cannot revoke role from](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1962.md)
- [Error 1963: Cannot change @@slave\_parallel\_threads while another change is in progress](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1963.md)
- [Error 1964: Commit failed due to failure of an earlier commit on which this one depends](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1964.md)
- [Error 1965: is a view](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1965.md)
- [Error 1966: When using GTID, @@sql\_slave\_skip\_counter can not be used](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1966.md)
- [Error 1967: The definition for table is too big](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1967.md)
- [Error 1968: Plugin already installed](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1968.md)
- [Error 1969: Query execution was interrupted (max\_statement\_time exceeded)](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1969.md)
- [Error 1970: does not support subqueries or stored functions](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1970.md)
- [Error 1971: The system variable cannot be set in SET STATEMENT](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1971.md)
- [Error 1972: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1972.md)
- [Error 1973: Can't create user; it already exists](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1973.md)
- [Error 1974: Can't drop user; it doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1974.md)
- [Error 1975: Can't create role; it already exists](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1975.md)
- [Error 1976: Can't drop role; it doesn't exist](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1976.md)
- [Error 1977: Cannot convert character to](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1977.md)
- [Error 1978: Incorrect default value for column](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1978.md)
- [Error 1979: You are not owner of query](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1979.md)
- [Error 1980: Engine-independent statistics are not collected for column](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1980.md)
- [Error 1981: Aggregate function of SELECT belongs to SELECT](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1981.md)
- [Error 1982: option ignored for InnoDB partition](/docs/server/reference/error-codes/mariadb-error-codes-1900-to-1999/e1982.md)
- [MariaDB Error Codes 3000 to 3099](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099.md)
- [Error 3000: File is corrupted](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3000.md)
- [Error 3001: Query partially completed on the master (error on master) and was aborted](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3001.md)
- [Error 3002: Query caused different errors on master and slave](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3002.md)
- [Error 3003: Storage engine for table is not loaded](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3003.md)
- [Error 3004: GET STACKED DIAGNOSTICS when handler not active](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3004.md)
- [Error 3005: is no longer supported. The statement was converted to](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3005.md)
- [Error 3006: Statement is unsafe because it uses a fulltext parser plugin which may not return the sa](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3006.md)
- [Error 3007: Cannot DISCARD/IMPORT tablespace associated with temporary table](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3007.md)
- [Error 3008: Foreign key cascade delete/update exceeds max depth of](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3008.md)
- [Error 3009: Column count of is wrong](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3009.md)
- [Error 3010: Trigger does not have CREATED attribute](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3010.md)
- [Error 3011: Referenced trigger for the given action time and event type does not exist](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3011.md)
- [Error 3012: EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3012.md)
- [Error 3013: Invalid size for column](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3013.md)
- [Error 3014: Table storage engine found required create option missing](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3014.md)
- [Error 3015: Out of memory in storage engine](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3015.md)
- [Error 3016: The password for anonymous user cannot be expired](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3016.md)
- [Error 3017: This operation cannot be performed with a running slave sql thread](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3017.md)
- [Error 3018: Cannot create FULLTEXT index on materialized subquery](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3018.md)
- [Error 3019: Undo Log error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3019.md)
- [Error 3020: Invalid argument for logarithm](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3020.md)
- [Error 3021: This operation cannot be performed with a running slave io thread](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3021.md)
- [Error 3022: This operation may not be safe when the slave has temporary tables](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3022.md)
- [Error 3023: CHANGE MASTER TO with a MASTER\_LOG\_FILE clause but no MASTER\_LOG\_POS clause may not be s](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3023.md)
- [Error 3024: Query execution was interrupted, maximum statement execution time exceeded](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3024.md)
- [Error 3025: Select is not a read only statement, disabling timer](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3025.md)
- [Error 3026: Duplicate entry](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3026.md)
- [Error 3027: mode no longer has any effect. Use STRICT\_ALL\_TABLES or STRICT\_TRANS\_TABLES instead.](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3027.md)
- [Error 3028: Expression of ORDER BY contains aggregate function and applies to a UNION](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3028.md)
- [Error 3029: Expression of ORDER BY contains aggregate function and applies to the result of a non-ag](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3029.md)
- [Error 3030: Slave worker has stopped after at least one previous worker encountered an error when sl](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3030.md)
- [Error 3031: slave\_preserve\_commit\_order is not supported](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3031.md)
- [Error 3032: The server is currently in offline mode](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3032.md)
- [Error 3033: Binary geometry function given two geometries of different srids](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3033.md)
- [Error 3034: Calling geometry function with unsupported types of arguments](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3034.md)
- [Error 3035: Unknown GIS error occurred in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3035.md)
- [Error 3036: Unknown exception caught in GIS function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3036.md)
- [Error 3037: Invalid GIS data provided to function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3037.md)
- [Error 3038: The geometry has no data in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3038.md)
- [Error 3039: Unable to calculate centroid because geometry is empty in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3039.md)
- [Error 3040: Geometry overlay calculation error: geometry data is invalid in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3040.md)
- [Error 3041: Geometry turn info calculation error: geometry data is invalid in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3041.md)
- [Error 3042: Analysis procedures of intersection points interrupted unexpectedly in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3042.md)
- [Error 3043: Unknown exception thrown in function](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3043.md)
- [Error 3044: Memory allocation error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3044.md)
- [Error 3045: Domain error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3045.md)
- [Error 3046: Length error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3046.md)
- [Error 3047: Invalid argument error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3047.md)
- [Error 3048: Out of range error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3048.md)
- [Error 3049: Overflow error error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3049.md)
- [Error 3050: Range error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3050.md)
- [Error 3051: Underflow error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3051.md)
- [Error 3052: Logic error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3052.md)
- [Error 3053: Runtime error](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3053.md)
- [Error 3054: Unknown exception](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3054.md)
- [Error 3055: Geometry byte string must be little endian](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3055.md)
- [Error 3056: The password provided for the replication user exceeds the maximum length of 32 characte](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3056.md)
- [Error 3057: Incorrect user-level lock name](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3057.md)
- [Error 3058: Deadlock found when trying to get user-level lock](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3058.md)
- [Error 3059: REPLACE cannot be executed as it requires deleting rows that are not in the view](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3059.md)
- [Error 3060: Do not support online operation on table with GIS index](/docs/server/reference/error-codes/mariadb-error-codes-3000-to-3099/e3060.md)
- [MariaDB Error Codes 4000 to 4099](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099.md)
- [Error 4000: COM\_MULTI can't return a result set in the given context](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4000.md)
- [Error 4001: Command is not allowed for COM\_MULTI](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4001.md)
- [Error 4002: WITH column list and SELECT field list have different column counts](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4002.md)
- [Error 4003: Too many WITH elements in WITH clause](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4003.md)
- [Error 4004: Duplicate query name in WITH clause](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4004.md)
- [Error 4005: No anchors for recursive WITH element](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4005.md)
- [Error 4006: Unacceptable mutual recursion with anchored table](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4006.md)
- [Error 4007: Reference to recursive WITH table in materialized derived](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4007.md)
- [Error 4008: Restrictions imposed on recursive definitions are violated for table](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4008.md)
- [Error 4009: Window specification with name is not defined](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4009.md)
- [Error 4010: Multiple window specifications with the same name](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4010.md)
- [Error 4011: Window specification referencing another one cannot contain partition list](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4011.md)
- [Error 4012: Referenced window specification already contains order list](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4012.md)
- [Error 4013: Referenced window specification cannot contain window frame](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4013.md)
- [Error 4014: Unacceptable combination of window frame bound specifications](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4014.md)
- [Error 4015: Window function is allowed only in SELECT list and ORDER BY clause](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4015.md)
- [Error 4016: Window function is not allowed in window specification](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4016.md)
- [Error 4017: Window frame is not allowed with](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4017.md)
- [Error 4018: No order list in window specification for](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4018.md)
- [Error 4019: RANGE-type frame requires ORDER BY clause with single sort key](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4019.md)
- [Error 4020: Integer is required for ROWS-type frame](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4020.md)
- [Error 4021: Numeric datatype is required for RANGE-type frame](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4021.md)
- [Error 4022: Frame exclusion is not supported yet](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4022.md)
- [Error 4023: This window function may not have a window frame](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4023.md)
- [Error 4024: Argument of NTILE must be greater than 0](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4024.md)
- [Error 4025: CONSTRAINT failed for](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4025.md)
- [Error 4026: Expression in the clause is too big](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4026.md)
- [Error 4027: Got an error evaluating stored expression](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4027.md)
- [Error 4028: Got an error when calculating default value for](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4028.md)
- [Error 4029: Expression for field is referring to uninitialized field](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4029.md)
- [Error 4030: Only one DEFAULT partition allowed](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4030.md)
- [Error 4031: Referenced trigger for the given action time and event type does not exist](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4031.md)
- [Error 4032: Default/ignore value is not supported for such parameter usage](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4032.md)
- [Error 4033: Only row based replication supported for bulk operations](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4033.md)
- [Error 4034: Uncompress the compressed binlog failed](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4034.md)
- [Error 4035: Broken JSON string in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4035.md)
- [Error 4036: Character disallowed in JSON in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4036.md)
- [Error 4037: Unexpected end of JSON text in argument to function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4037.md)
- [Error 4038: Syntax error in JSON text in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4038.md)
- [Error 4039: Incorrect escaping in JSON text in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4039.md)
- [Error 4040: Limit on JSON nested strucures depth is reached in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4040.md)
- [Error 4041: Unexpected end of JSON path in argument to function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4041.md)
- [Error 4042: Syntax error in JSON path in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4042.md)
- [Error 4043: Limit on JSON path depth is reached in argument to function at position](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4043.md)
- [Error 4044: Wildcards in JSON path not allowed in argument to function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4044.md)
- [Error 4045: JSON path should end with an array identifier in argument to function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4045.md)
- [Error 4046: Argument 2 to function must be "one" or "all".](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4046.md)
- [Error 4047: CREATE TEMPORARY TABLE is not allowed with ROW\_FORMAT=COMPRESSED or KEY\_BLOCK\_SIZE.](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4047.md)
- [Error 4048: Incorrect GeoJSON format specified for st\_geomfromgeojson function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4048.md)
- [Error 4049: Incorrect GeoJSON format - too few points for linestring specified](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4049.md)
- [Error 4050: Incorrect GeoJSON format - polygon not closed](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4050.md)
- [Error 4051: Path expression '$' is not allowed in argument to function](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4051.md)
- [Error 4052: A slave with the same server\_uuid/server\_id as this slave has connected to the master](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4052.md)
- [Error 4053: Flashback does not support](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4053.md)
- [Error 4054: Keys are out order during bulk load](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4054.md)
- [Error 4055: Bulk load rows overlap existing rows](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4055.md)
- [Error 4056: Can't execute updates on master with binlog\_format != ROW](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4056.md)
- [Error 4057: MyRocks supports only READ COMMITTED and REPEATABLE READ isolation levels](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4057.md)
- [Error 4058: When unique checking is disabled in MyRocks, INSERT,UPDATE,LOAD statements with clauses](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4058.md)
- [Error 4059: Can't execute updates when you started a transaction with START TRANSACTION WITH CONSIST](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4059.md)
- [Error 4060: This transaction was rolled back and cannot be committed. Only supported operation is to](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4060.md)
- [Error 4061: MyRocks currently does not support ROLLBACK TO SAVEPOINT if modifying rows](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4061.md)
- [Error 4062: Only REPEATABLE READ isolation level is supported for START TRANSACTION WITH CONSISTENT](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4062.md)
- [Error 4063: Unsupported collation on string indexed column](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4063.md)
- [Error 4064: Table '%s' does not exist, but metadata information exists inside MyRocks. This is a sig](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4064.md)
- [Error 4065: Column family flag is different from an existing flag](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4065.md)
- [Error 4066: TTL duration in MyRocks must be an unsigned non-null 64-bit integer](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4066.md)
- [Error 4067: Status error received from RocksDB](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4067.md)
- [Error 4068: Status error received from RocksDB](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4068.md)
- [Error 4069: TTL support is currently disabled when table has a hidden PK](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4069.md)
- [Error 4070: TTL column in MyRocks must be an unsigned non-null 64-bit integer, exist inside the tabl](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4070.md)
- [Error 4071: The per-index column family option has been deprecated](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4071.md)
- [Error 4072: MyRocks failed creating new key definitions during alter](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4072.md)
- [Error 4073: MyRocks failed populating secondary key during alter](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4073.md)
- [Error 4074: Window functions can not be used as arguments to group functions](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4074.md)
- [Error 4075: OK packet too large](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4075.md)
- [Error 4076: Incorrect GeoJSON format - empty 'coordinates' array](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4076.md)
- [Error 4077: MyRocks doesn't currently support collations with "No pad" attribute](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4077.md)
- [Error 4078: Illegal parameter data types for operation](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4078.md)
- [Error 4079: Illegal parameter data type for operation](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4079.md)
- [Error 4080: Incorrect parameter count to cursor](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4080.md)
- [Error 4081: Unknown structured system variable or ROW routine variable](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4081.md)
- [Error 4082: Row variable does not have a field](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4082.md)
- [Error 4083: END identifier does not match](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4083.md)
- [Error 4084: Sequence has run out](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4084.md)
- [Error 4085: Sequence values are conflicting](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4085.md)
- [Error 4086: Sequence table structure is invalid](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4086.md)
- [Error 4087: Sequence access error](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4087.md)
- [Error 4088: Sequences requires binlog\_format mixed or row](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4088.md)
- [Error 4089: is not a SEQUENCE](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4089.md)
- [Error 4090: is not a SEQUENCE](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4090.md)
- [Error 4091: Unknown SEQUENCE](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4091.md)
- [Error 4092: Unknown VIEW](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4092.md)
- [Error 4093: Wrong INSERT into a SEQUENCE. One can only do single table INSERT into a sequence object](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4093.md)
- [Error 4094: At line in](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4094.md)
- [Error 4095: Subroutine is declared in the package specification but is not defined in the package bo](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4095.md)
- [Error 4096: Subroutine has a forward declaration but is not defined](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4096.md)
- [Error 4097: Compressed column can't be used in key specification](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4097.md)
- [Error 4098: Unknown compression method](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4098.md)
- [Error 4099: The used table value constructor has a different number of values](/docs/server/reference/error-codes/mariadb-error-codes-4000-to-4099/e4099.md)
- [MariaDB Error Codes 4100 to 4199](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199.md)
- [Error 4100: Field reference can't be used in table value constructor](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4100.md)
- [Error 4101: Numeric datatype is required for function](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4101.md)
- [Error 4102: Argument to the function is not a constant for a partition](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4102.md)
- [Error 4103: Argument to the function does not belong to the range \[0,1\]](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4103.md)
- [Error 4104: function only accepts arguments that can be converted to numerical types](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4104.md)
- [Error 4105: Aggregate specific instruction (FETCH GROUP NEXT ROW) used in a wrong context](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4105.md)
- [Error 4106: Aggregate specific instruction(FETCH GROUP NEXT ROW) missing from the aggregate function](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4106.md)
- [Error 4107: Limit only accepts integer values](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4107.md)
- [Error 4108: Invisible column must have a default value](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4108.md)
- [Error 4109: Rows matched: Changed: Inserted: Warnings:](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4109.md)
- [Error 4110: must be of type for system-versioned table](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4110.md)
- [Error 4111: Transaction-precise system versioning for is not supported](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4111.md)
- [Error 4112: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4112.md)
- [Error 4113: Wrong partitioning type, expected type](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4113.md)
- [Error 4114: Versioned table last HISTORY partition is out of, need more HISTORY partitions](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4114.md)
- [Error 4115: Maybe missing parameters](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4115.md)
- [Error 4116: Can only drop oldest partitions when rotating by INTERVAL](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4116.md)
- [Error 4117: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4117.md)
- [Error 4118: Partition contains non-historical data](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4118.md)
- [Error 4119: Not allowed for system-versioned. Change @@system\_versioning\_alter\_history to proceed wi](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4119.md)
- [Error 4120: Not allowed for system-versioned. Change to/from native system versioning engine is not](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4120.md)
- [Error 4121: SYSTEM\_TIME range selector is not allowed](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4121.md)
- [Error 4122: Conflicting FOR SYSTEM\_TIME clauses in WITH RECURSIVE](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4122.md)
- [Error 4123: Table must have at least one versioned column](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4123.md)
- [Error 4124: Table is not system-versioned](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4124.md)
- [Error 4125: Wrong parameters for: missing](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4125.md)
- [Error 4126: PERIOD FOR SYSTEM\_TIME must use columns](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4126.md)
- [Error 4127: Wrong parameters for partitioned: wrong value for](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4127.md)
- [Error 4128: Wrong partitions for: must have at least one HISTORY and exactly one last CURRENT](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4128.md)
- [Error 4129: TRX\_ID not found in mysql.transaction\_registry](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4129.md)
- [Error 4130: Can not change system versioning field](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4130.md)
- [Error 4131: Can not DROP SYSTEM VERSIONING for table partitioned BY SYSTEM\_TIME](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4131.md)
- [Error 4132: System-versioned tables in the database are not supported](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4132.md)
- [Error 4133: Transaction registry is disabled](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4133.md)
- [Error 4134: Duplicate ROW column](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4134.md)
- [Error 4135: Table is already system-versioned](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4135.md)
- [Error 4136: You should never see it](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4136.md)
- [Error 4137: System-versioned tables do not support](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4137.md)
- [Error 4138: Transaction-precise system-versioned tables do not support partitioning by ROW START or](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4138.md)
- [Error 4139: The index file for table is full](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4139.md)
- [Error 4140: The column cannot be changed more than once in a single UPDATE statement](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4140.md)
- [Error 4141: Row with no elements is not allowed in table value constructor in this context](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4141.md)
- [Error 4142: SYSTEM\_TIME partitions in table does not support historical query](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4142.md)
- [Error 4143: index does not support this operation](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4143.md)
- [Error 4144: Changing table options requires the table to be rebuilt](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4144.md)
- [Error 4145: Can't execute the command as you have a BACKUP STAGE active](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4145.md)
- [Error 4146: You must start backup with "BACKUP STAGE START"](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4146.md)
- [Error 4147: Backup stage is same or before current backup stage](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4147.md)
- [Error 4148: Backup stage failed](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4148.md)
- [Error 4149: Unknown backup stage: Stage should be one of START, FLUSH, BLOCK\_DDL, BLOCK\_COMMIT or EN](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4149.md)
- [Error 4150: User is blocked because of too many credential errors; unblock with 'FLUSH PRIVILEGES'](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4150.md)
- [Error 4151: Access denied, this account is locked](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4151.md)
- [Error 4152: Application-time period table cannot be temporary](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4152.md)
- [Error 4153: Fields of PERIOD FOR have different types](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4153.md)
- [Error 4154: Cannot specify more than one application-time period](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4154.md)
- [Error 4155: Period field cannot be](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4155.md)
- [Error 4156: Period is not found in table](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4156.md)
- [Error 4157: Column used in period specified in update SET list](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4157.md)
- [Error 4158: Can't DROP CONSTRAINT. Use DROP PERIOD for this](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4158.md)
- [Error 4159: Specified key part was too long; max key part length is](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4159.md)
- [Error 4160: Comment for database is too long](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4160.md)
- [Error 4161: Unknown data type](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4161.md)
- [Error 4162: Operator does not exists](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4162.md)
- [Error 4163: Table history row start is later than row end](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4163.md)
- [Error 4164: STARTS is later than query time, first history partition may exceed INTERVAL value](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4164.md)
- [Error 4165: DDL-statement is forbidden as table storage engine does not support Galera replication](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4165.md)
- [Error 4166: The used command is not allowed because the MariaDB server or client has disabled the lo](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4166.md)
- [Error 4167: No secure transports are configured, unable to set --require\_secure\_transport=ON](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4167.md)
- [Error 4168: Slave SQL thread ignored the '%s' because table is shared](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4168.md)
- [Error 4169: AUTO\_INCREMENT column cannot be used in the UNIQUE index](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4169.md)
- [Error 4170: Key cannot explicitly include column](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4170.md)
- [Error 4171: Key cannot have WITHOUT OVERLAPS](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4171.md)
- [Error 4172: is not allowed in this context](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4172.md)
- [Error 4173: Engine does not support rollback. Changes where commited during rollback call](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4173.md)
- [Error 4174: A primary key cannot be marked as IGNORE](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4174.md)
- [Error 4175: SKIP LOCKED makes this statement unsafe](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4175.md)
- [Error 4176: Field can't be set for JSON\_TABLE](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4176.md)
- [Error 4177: Every table function must have an alias](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4177.md)
- [Error 4178: Can't store an array or an object in the scalar column of JSON\_TABLE](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4178.md)
- [Error 4179: Can't store multiple matches of the path in the column of JSON\_TABLE](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4179.md)
- [Error 4180: FETCH ... WITH TIES requires ORDER BY clause to be present](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4180.md)
- [Error 4181: Dropped orphan trigger, originally created for table](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4181.md)
- [Error 4182: Storage engine is disabled](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4182.md)
- [Error 4183: SFORMAT error](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4183.md)
- [Error 4184: Convert partition is not supported for subpartitioned table](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4184.md)
- [Error 4185: MariaDB tried to use the %s, but its provider plugin is not loaded](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4185.md)
- [Error 4186: Failed to parse histogram for table at offset](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4186.md)
- [Error 4187: OUT or INOUT argument for function is not allowed here](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4187.md)
- [Error 4188: Replicated query table can not be temporary](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4188.md)
- [Error 4189: Versioned table: adding HISTORY partition(s) failed](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4189.md)
- [Error 4190: is implicitly changing the value of from to](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4190.md)
- [Error 4191: CHANGE MASTER TO option is missing requirement](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4191.md)
- [Error 4192: Slave log event execution was interrupted (slave\_max\_statement\_time exceeded)](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4192.md)
- [Error 4193: Invalid value for keyword](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4193.md)
- [Error 4194: keyword is not supported](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4194.md)
- [Error 4195: Variable schema is not supported](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4195.md)
- [Error 4196: Pseudo thread id should not be modified by the client as it will be overwritten](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4196.md)
- [Error 4197: Wrong number of columns](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4197.md)
- [Error 4198: Sequence tables cannot have any keys](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4198.md)
- [Error 4199: Sequence tables cannot have any constraints](/docs/server/reference/error-codes/mariadb-error-codes-4100-to-4199/e4199.md)
- [MariaDB Error Codes 4200 to 4299](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299.md)
- [Error 4200: ORDER BY](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4200.md)
- [Error 4201: The variable is ignored](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4201.md)
- [Error 4202: Incorrect column name count for derived table](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4202.md)
- [Error 4203: Values were longer than max\_sort\_length. Sorting used only the first bytes](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4203.md)
- [Error 4204: Invalid binary vector format](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4204.md)
- [Error 4205: Invalid vector format at offset](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4205.md)
- [Error 4206: Cannot determine distance type for VEC\_DISTANCE, index is not found](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4206.md)
- [Error 4221: Unresolved table name for hint](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4221.md)
- [Error 4222: Unresolved index name for hint](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4222.md)
- [Error 4223: Optimizer hints are not supported inside view definitions](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4223.md)
- [Error 4224: Hint is ignored as malformed](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4224.md)
- [Error 4225: Optimizer hints at the INSERT part of a INSERT..SELECT statement are not supported](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4225.md)
- [Error 4226: Slave SQL thread aborted](/docs/server/reference/error-codes/mariadb-error-codes-4200-to-4299/e4226.md)
- [Client/Server Protocol](/docs/server/reference/clientserver-protocol.md): Understand the MariaDB client/server protocol. This section details how clients communicate with the server, including connection, authentication, query execution, and result set handling.
- [Protocol Data Types](/docs/server/reference/clientserver-protocol/protocol-data-types.md): This page defines the fundamental data types used in the MariaDB client/server protocol, including integers, strings, and binary representations.
- [MariaDB Protocol Differences with MySQL](/docs/server/reference/clientserver-protocol/mariadb-protocol-differences-with-mysql.md): Learn about the specific extensions and differences in the MariaDB protocol compared to MySQL, such as extended capability flags and metadata.
- [0 - Packet](/docs/server/reference/clientserver-protocol/0-packet.md): Understand the standard packet structure in the MariaDB protocol, including the packet header, length, sequence number, and payload handling.
- [1 - Connecting](/docs/server/reference/clientserver-protocol/1-connecting.md): Learn about the connection phase in the client/server protocol. This section details how clients establish initial communication with the server, including handshaking and authentication processes.
- [Connecting](/docs/server/reference/clientserver-protocol/1-connecting/connection.md): The connection phase involves an initial handshake where the client and server exchange capabilities, default settings, and authentication data to establish a session.
- [Connecting via sha256\_password](/docs/server/reference/clientserver-protocol/1-connecting/sha256_password-plugin.md): The sha256\_password plugin manages authentication using SHA-256 encryption, supporting both clear text passwords over SSL and RSA encrypted password exchange.
- [Connecting via caching\_sha2\_password](/docs/server/reference/clientserver-protocol/1-connecting/caching_sha2_password-authentication-plugin.md): This plugin implements the caching\_sha2\_password authentication method, using an in-memory cache for fast authentication or RSA encryption for full verification.
- [2 - Text Protocol](/docs/server/reference/clientserver-protocol/2-text-protocol.md): Understand the text protocol in the Server's client/server communication. This section details how SQL commands and results are exchanged as plain text, including command types and packet structures.
- [COM\_CHANGE\_USER](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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.
- [3 - Binary Protocol (Prepared Statements)](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements.md): Understand the binary protocol for prepared statements. This section details how prepared statements are exchanged efficiently between client and server, optimizing performance and security.
- [COM\_STMT\_BULK\_EXECUTE](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_bulk_execute.md): This command executes a bulk insert for a previously prepared statement, using a compact binary format for efficiency.
- [COM\_STMT\_CLOSE](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/3-binary-protocol-prepared-statements-com_stmt_close.md): This command deallocates a prepared statement on the server, freeing up associated resources.
- [COM\_STMT\_EXECUTE](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_execute.md): This command executes a prepared statement using parameter values provided in the binary protocol format.
- [COM\_STMT\_FETCH](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_fetch.md): This command fetches rows from an existing result set of a prepared statement that was executed with a cursor.
- [COM\_STMT\_PREPARE](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_prepare.md): This command prepares an SQL statement on the server, returning a statement ID and metadata about parameters and columns.
- [COM\_STMT\_RESET](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_reset.md): This command resets the data of a prepared statement on the server, clearing any buffers or previous parameter values.
- [COM\_STMT\_SEND\_LONG\_DATA](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/com_stmt_send_long_data.md): This command sends long data, such as BLOB or TEXT values, in chunks for a specific parameter of a prepared statement.
- [Server Response Packets (Binary Protocol)](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/server-response-packets-binary-protocol.md): This section details the structure of response packets sent by the server when using the binary protocol, particularly for result sets.
- [PACKET\_BINDATA](/docs/server/reference/clientserver-protocol/3-binary-protocol-prepared-statements/server-response-packets-binary-protocol/packet_bindata.md): This packet type in the binary protocol transfers result set row data in a compact binary format, determined by the column types returned in metadata.
- [4 - Server Response Packets](/docs/server/reference/clientserver-protocol/4-server-response-packets.md): Understand server response packets in MariaDB's client/server protocol. This section details the various types of packets sent by the server, including OK, Error, and Result Set packets.
- [EOF\_Packet](/docs/server/reference/clientserver-protocol/4-server-response-packets/eof_packet.md): The EOF\_Packet marks the end of a result set or a sequence of packets, containing warning counts and server status flags.
- [ERR\_Packet](/docs/server/reference/clientserver-protocol/4-server-response-packets/err_packet.md): The ERR\_Packet is sent by the server to report an error, containing a numeric error code, SQL state marker, and a human-readable error message.
- [LOCAL\_INFILE\_Packet](/docs/server/reference/clientserver-protocol/4-server-response-packets/packet_local_infile.md): The LOCAL\_INFILE\_Packet is sent by the server to request a file from the client during the execution of a LOAD DATA LOCAL INFILE statement.
- [OK\_Packet](/docs/server/reference/clientserver-protocol/4-server-response-packets/ok_packet.md): The OK\_Packet is sent by the server to indicate the successful completion of a command, conveying affected row counts and server status flags.
- [Result Set Packets](/docs/server/reference/clientserver-protocol/4-server-response-packets/result-set-packets.md): A result set consists of a sequence of packets including column counts, column definitions, and row data, terminated by an EOF or OK packet.
- [Result Set Row](/docs/server/reference/clientserver-protocol/4-server-response-packets/resultset-row.md): A result set row packet contains the data for a single row in a query result, formatted as text or binary depending on the execution context.
- [Replication Protocol](/docs/server/reference/clientserver-protocol/replication-protocol.md): Understand the replication protocol. This section details how primary and replica servers communicate, exchanging binary log events to ensure data consistency and enable high availability.
- [1-Binlog Events](/docs/server/reference/clientserver-protocol/replication-protocol/1-binlog-events.md): This section provides an overview of the various events recorded in the binary log, which are the core units of replication data transmission.
- [2-Binlog Event Header](/docs/server/reference/clientserver-protocol/replication-protocol/2-binlog-event-header.md): Every binary log event starts with a standardized header containing metadata such as the timestamp, event type, server ID, and event size.
- [3-Binlog Network Stream](/docs/server/reference/clientserver-protocol/replication-protocol/3-binlog-network-stream.md): Describes the continuous packet stream format used to transmit binary log events from the primary server to the replica over the network.
- [4-Semi-Sync Replication](/docs/server/reference/clientserver-protocol/replication-protocol/4-semi-sync-replication.md): Explains the handshake and acknowledgement process for semi-synchronous replication, ensuring data is committed on at least one replica.
- [5-Replica Registration](/docs/server/reference/clientserver-protocol/replication-protocol/5-replica-registration.md): Details the initialization phase where a replica connects to the primary, authenticates, sends capabilities, and registers for updates.
- [ANNOTATE\_ROWS\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/annotate_rows_event.md): This event accompanies row-based events to provide the original SQL query text, which is useful for auditing and debugging replication.
- [BEGIN\_LOAD\_QUERY\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/begin_load_query_event.md): Used during LOAD DATA INFILE operations, this event marks the beginning of the data load and contains the initial query information.
- [BINLOG\_CHECKPOINT\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/binlog_checkpoint_event.md): A marker event indicating a checkpoint in the binary log, used to ensure consistency and safe rotation of log files.
- [COM\_BINLOG\_DUMP](/docs/server/reference/clientserver-protocol/replication-protocol/com_binlog_dump.md): This command is sent by a replica to the primary server to request the start of the binary log event stream from a specific file and position.
- [COM\_REGISTER\_SLAVE](/docs/server/reference/clientserver-protocol/replication-protocol/com_register_slave.md): This command is used by a replica to register its details, such as server ID, hostname, and port, with the primary server.
- [EXECUTE\_LOAD\_QUERY\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/execute_load_query_event.md): This event is used for LOAD DATA INFILE operations, managing the execution phase similar to a QUERY\_EVENT but with extra static fields for file handling.
- [Fake GTID\_LIST Event](/docs/server/reference/clientserver-protocol/replication-protocol/fake-gtid_list-event.md): A synthetic event sent by the master after the initial handshake to inform the replica of its current GTID state, it is not written to the binary log.
- [Fake ROTATE\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/fake-rotate_event.md): An artificial event sent to the replica to indicate the name of the binary log file on the master, ensuring the replica knows which file is being read.
- [FORMAT\_DESCRIPTION\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/format_description_event.md): This descriptor event appears at the start of every binary log file, defining the server version, binlog version, and header lengths for all event types.
- [GTID\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/gtid_event.md): The GTID\_EVENT marks the start of a new transaction event group, associating it with a Global Transaction ID (GTID) and providing commit flags.
- [GTID\_LIST\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/gtid_list_event.md): Logged during binlog rotation or checkpoints, this event lists the GTIDs present in the binary log to help replicas determine their replication state.
- [HEARTBEAT\_LOG\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/heartbeat_log_event.md): A heartbeat event sent over the network by the master when there are no binlog events, ensuring the replica knows the connection is still active.
- [INTVAR\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/intvar_event.md): This event records integer values for auto-increment columns or the LAST\_INSERT\_ID function, ensuring that these values are replicated deterministically.
- [QUERY\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/query_event.md): The QUERY\_EVENT records text-based SQL statements for statement-based replication, capturing the query string and execution context like the default database.
- [RAND\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/rand_event.md): The RAND\_EVENT records the two seed values used for the random number generator, ensuring that calls to the RAND() function produce identical results on replicas.
- [ROTATE\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/rotate_event.md): The ROTATE\_EVENT indicates a log rotation, specifying the name of the next binary log file and the position where writing will continue.
- [ROWS\_EVENT\_V1/V2, ROWS\_COMPRESSED\_EVENT\_V1](/docs/server/reference/clientserver-protocol/replication-protocol/rows_event_v1v2-rows_compressed_event_v1.md): These events record row-level changes (WRITE, UPDATE, DELETE) for replication, with versions supporting different column counts and compression.
- [START\_ENCRYPTION\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/start_encryption_event.md): This event marks the beginning of encrypted data in the binary log, defining the encryption scheme and key version for subsequent events.
- [STOP\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/stop_event.md): The STOP\_EVENT is written to the binary log when the server shuts down, serving as a marker for a clean stop.
- [TABLE\_MAP\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/table_map_event.md): This event provides a mapping between a table ID and its table definition, preceding row events to interpret the row data correctly.
- [USER\_VAR\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/user_var_event.md): The USER\_VAR\_EVENT logs the value of a user-defined variable, ensuring that statements using variables replicate consistently.
- [XA\_PREPARE\_LOG\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/xa_prepare_log_event.md): This event records the preparation phase of an XA transaction, storing the XID to support two-phase commit and recovery.
- [XID\_EVENT](/docs/server/reference/clientserver-protocol/replication-protocol/xid_event.md): The XID\_EVENT signifies the commit of a transaction, containing the transaction ID (XID) to ensure atomicity across replication.
- [Product Development](/docs/server/reference/product-development.md): Provides background information and high-level resources aimed at engineers developing new MariaDB features and contributing to the ecosystem.
- [MariaDB Quality Development Rules](/docs/server/reference/product-development/mariadb-quality-development-rules.md): Outlines strict quality standards for new features, including requirements for design specifications, testability, and mandatory Worklog quality checklists.
- [Uploading Package to PPA](/docs/server/reference/product-development/uploading-package-to-ppa.md): Provides instructions for developers to upload MariaDB source packages to a Personal Package Archive (PPA) using tools like dput for Ubuntu-based distributions.
- [Debugging & Troubleshooting](/docs/server/reference/product-development/mariadb-fault-finding.md): Offers deep-dive technical guides for diagnosing server issues, including trace file generation, debugger usage, and analyzing core dumps or memory usage.
- [Troubleshooting Overview](/docs/server/reference/product-development/mariadb-fault-finding/checking-mariadb.md): A starting guide for DBAs and developers to diagnose server issues, focusing on initial checks and systemic health verification.
- [MariaDB Crashes](/docs/server/reference/product-development/mariadb-fault-finding/mariadb-crashes.md): Provides specialized guidance on identifying the causes of server crashes and gathering the necessary data for reporting bugs.
- [MariaDB Error Messages](/docs/server/reference/product-development/mariadb-fault-finding/mariadb-error-messages.md): Explains how to interpret server error codes and messages to quickly identify configuration or runtime failures.
- [Debugging Memory Usage](/docs/server/reference/product-development/mariadb-fault-finding/debugging-memory-usage.md): Instructions for monitoring and analyzing memory allocation to identify leaks or excessive consumption within the server.
- [Compiling MariaDB for Debugging](/docs/server/reference/product-development/mariadb-fault-finding/compiling-mariadb-for-debugging.md): Explains how to build the MariaDB source code with specific flags enabled to allow for deep-level internal debugging.
- [Creating a Trace File](/docs/server/reference/product-development/mariadb-fault-finding/creating-a-trace-file.md): Details the process of generating a trace file to record the internal execution flow of the server for developer analysis.
- [Debugging a Running Server (on Linux)](/docs/server/reference/product-development/mariadb-fault-finding/debugging-a-running-server-on-linux.md): Explains how to attach debugging tools to a live MariaDB process on Linux systems without restarting the service.
- [Debugging MariaDB With a Debugger](/docs/server/reference/product-development/mariadb-fault-finding/debugging-mariadb-with-a-debugger.md): A technical guide on using standard debuggers like GDB to step through code and inspect the state of a MariaDB instance.
- [Enabling Core Dumps](/docs/server/reference/product-development/mariadb-fault-finding/enabling-core-dumps.md): How to configure the operating system and MariaDB to produce a core dump file when a crash occurs for post-mortem analysis.
- [Producing a Full Stack Trace for mariadbd](/docs/server/reference/product-development/mariadb-fault-finding/how-to-produce-a-full-stack-trace-for-mariadbd.md): Steps to generate a complete stack trace for the main server daemon, essential for pinpointing the location of software faults.
- [Using procmon to Trace mysqld.exe Filesystem Access](/docs/server/reference/product-development/mariadb-fault-finding/how-to-use-procmon-to-trace-mysqldexe-filesystem-access.md): Covers using Process Monitor on Windows to trace filesystem and registry access for the MariaDB server executable.
- [Limitations/Differences with a MariaDB Server Compiled for Debugging](/docs/server/reference/product-development/mariadb-fault-finding/limitationsdifferences-with-a-mariadb-server-compiled-for-debugging.md): Highlights the performance impacts and behavioral changes to expect when running a MariaDB server compiled with debug options.
- [Plugin Development](/docs/server/reference/product-development/plugin-development.md): Details the APIs and processes for extending MariaDB functionality through custom plugins, such as authentication, logging, or specialized server enhancements.
- [Writing Plugins for MariaDB](/docs/server/reference/product-development/plugin-development/development-writing-plugins-for-mariadb.md): A comprehensive guide on the basic structure and necessary components for creating a new plugin from scratch.
- [Encryption Plugin Development](/docs/server/reference/product-development/plugin-development/encryption-plugin-api.md): Details the API used to develop encryption plugins for protecting data at rest, including key management and encryption schemes.
- [Audit Plugin Development](/docs/server/reference/product-development/plugin-development/audit-plugin-development.md): Provides instructions for developing plugins that track and log server activity for security and compliance monitoring.
- [Authentication Plugin Development](/docs/server/reference/product-development/plugin-development/authentication-plugin-development.md): Details how to implement custom authentication methods, allowing users to connect using external credentials or protocols.
- [Information Schema Plugins: SHOW and FLUSH Statements](/docs/server/reference/product-development/plugin-development/information-schema-plugins-show-and-flush-statements.md): Explains how to create plugins that expose internal server data through virtual tables in the Information Schema.
- [Replication & Cluster Plugin Development](/docs/server/reference/product-development/plugin-development/replication-and-cluster-plugin-development.md): Focuses on building plugins that interact with the server's replication stream or manage cluster-level synchronization.
- [Password Validation Plugin Development](/docs/server/reference/product-development/plugin-development/password-validation-plugin-development.md): Implementation guide specifically for developers creating logic to intercept and validate password changes in the server.
- [Storage Engine Development](/docs/server/reference/product-development/plugin-development/storage-engines-storage-engine-development.md): A dedicated resource for engineers to learn how to build or modify storage engines, detailing the pluggable API and data handling at the physical level.
- [Engine-defined New Table/Field/Index Attributes](/docs/server/reference/product-development/plugin-development/storage-engines-storage-engine-development/engine-defined-new-tablefieldindex-attributes.md): Explains how storage engines can define and use custom attributes for tables, fields, and indexes within the MariaDB server framework.
- [Table Discovery](/docs/server/reference/product-development/plugin-development/storage-engines-storage-engine-development/table-discovery.md): Details the modern table discovery API that allows storage engines to automatically report existing tables to the server without explicit .frm files.
- [Server Development](/docs/server/reference/product-development/server-development.md): Covers foundational engineering topics, including the server roadmap, GitHub collaboration workflows, and quality assurance protocols for core contributions.
- [MariaDB Server Roadmap](/docs/server/reference/product-development/server-development/mariadb-server-roadmap.md): Provides a high-level view of upcoming features, version release schedules, and the strategic direction for MariaDB Server development.
- [Working with GitHub](/docs/server/reference/product-development/server-development/working-with-github.md): Outlines the workflow for contributing to MariaDB via GitHub, including branch management, pull requests, and coding standards for developers.
- [Quality Assurance](/docs/server/reference/product-development/server-development/quality.md): Details the processes and methodologies used to ensure code quality, focusing on testing frameworks and bug verification during development.
- [Code Coverage](/docs/server/reference/product-development/server-development/quality/code-coverage.md): Provides an overview of how code coverage is measured to ensure that testing suites effectively exercise the MariaDB source code.
- [Code Coverage With dgcov](/docs/server/reference/product-development/server-development/quality/code-coverage-with-dgcov.md): Technical instructions on using the dgcov tool to generate and analyze code coverage reports for the MariaDB server.
- [QA Tests](/docs/server/reference/product-development/server-development/quality/qa-tests.md): A repository of various test suites and scripts used in the daily quality assurance workflow to catch regressions.
- [QA Metrics](/docs/server/reference/product-development/server-development/quality/qa-metrics.md): Defines the key performance indicators and metrics used by the QA team to track the stability and health of the server over time.
- [QA Tools](/docs/server/reference/product-development/server-development/quality/qa-tools.md): Documentation for the internal and external utilities utilized by engineers to perform automated and manual quality testing.
- [Optimizer Quality](/docs/server/reference/product-development/server-development/quality/optimizer-quality.md): Details the specific quality assurance processes and testing strategies used to validate the MariaDB query optimizer's performance.
- [QA - Aria Recovery](/docs/server/reference/product-development/server-development/quality/qa-aria-recovery.md): Focuses on testing the crash recovery capabilities of the Aria storage engine to ensure data integrity after unexpected shutdowns.
- [Worklog Quality Checklist Template](/docs/server/reference/product-development/server-development/quality/worklog-quality-checklist-template.md): Provides a standardized template for developers to ensure every new feature meets mandatory quality and documentation requirements.
- [Random Query Generator Tests](/docs/server/reference/product-development/server-development/quality/random-query-generator-tests.md): Explains how to use the Random Query Generator (RQG) to find edge-case bugs by executing automatically generated SQL queries.
- [RQG Extensions for MariaDB](/docs/server/reference/product-development/server-development/quality/rqg-extensions-for-mariadb.md): Describes MariaDB-specific enhancements to the Random Query Generator tool for testing unique features and syntax.
- [Benchmarks and Long Running Tests](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests.md): Outlines the procedures for executing performance benchmarks and extended duration tests to identify stability issues or leaks.
- [Benchmark Results](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results.md)
- [sysbench v0.5 - Single Five Minute Runs on T500 Laptop](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-single-five-minute-runs-on-t500-laptop.md)
- [sysbench v0.5 - Three Times Five Minutes Runs on work with 5.1.42](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-three-times-five-minutes-runs-on-work-with-5.1.42.md)
- [sysbench v0.5 - 3x Five Minute Runs on work with 5.2-wl86](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-3x-five-minute-runs-on-work-with-5.2-wl86.md)
- [sysbench v0.5 - 3x Five Minute Runs on work with 5.1 vs. 5.2-wl86](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-3x-five-minute-runs-on-work-with-5.1-vs.-5.2-wl86.md)
- [sysbench v0.5 - 3x 15 Minute Runs on perro with 5.2-wl86 a](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-3x-15-minute-runs-on-perro-with-5.2-wl86-a.md)
- [sysbench v0.5 - 3x 15 Minute Runs on perro with 5.2-wl86 b](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-3x-15-minute-runs-on-perro-with-5.2-wl86-b.md)
- [Select Random Ranges and Select Random Point](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/select-random-ranges-and-select-random-point.md)
- [Sysbench Results](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-results.md)
- [sysbench v0.5 - Single Five Minute Runs on perro](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-single-five-minute-runs-on-perro.md)
- [sysbench v0.5 - Single Five Minute Runs on work](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/sysbench-v0.5-single-five-minute-runs-on-work.md)
- [Threadpool Benchmarks](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmark-results/threadpool-benchmarks.md)
- [Benchmarks](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks.md)
- [Benchmark Builds](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/benchmark-builds.md)
- [Benchmarking Aria](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/benchmarking-aria.md)
- [DBT3 Automation Scripts](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/dbt3-automation-scripts.md)
- [DBT3 Benchmark Results InnoDB](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/dbt3-benchmark-results-innodb.md)
- [DBT3 Benchmark Results MyISAM](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/dbt3-benchmark-results-myisam.md)
- [DBT3 Example Preparation Time](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/dbt3-example-preparation-time.md)
- [MariaDB 5.3 - Asynchronous I/O on Windows with InnoDB](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/mariadb-53-asynchronous-io-on-windows-with-innodb.md)
- [MariaDB 5.3/MySQL 5.5 Windows performance patches](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/mariadb-53mysql-55-windows-performance-patches.md)
- [mariadb-tools](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/mariadb-tools.md)
- [Performance of MEMORY Tables](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/performance-of-memory-tables.md): Example of benchmarking the MEMORY table using perl to generate the data and SQL for the benchmark
- [Recommended Settings for Benchmarks](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/recommended-settings-for-benchmarks.md)
- [RQG Performance Comparisons](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/rqg-performance-comparisons.md)
- [run-sql-bench.pl](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/run-sql-benchpl.md)
- [Segmented Key Cache Performance](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/segmented-key-cache-performance.md)
- [sysbench Benchmark Setup](/docs/server/reference/product-development/server-development/quality/benchmarks-and-long-running-tests/benchmarks/sysbench-benchmark-setup.md)
- [InnoDB Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests.md): Dedicated testing protocols for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.0.32 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10032-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.0.34 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10034-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.0.36 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10036-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.22 Pre-release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10122-pre-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.25 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10125-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.26 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10.1.26-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.30 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10130-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.32 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10132-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.1.36 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10136-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.12 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10212-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.13 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10213-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.14 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10214-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.17 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10217-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.18 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10218-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.5 Pre-release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1025-pre-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.2.7 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1027-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.10 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/10310-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.3-beta Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1033-beta-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.4-beta Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1034-beta-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.5-gamma Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1035-gamma-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.6-gamma Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1036-gamma-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [10.3.9 Release Upgrade Tests](/docs/server/reference/product-development/server-development/quality/innodb-upgrade-tests/1039-release-upgrade-tests.md): Dedicated testing results for verifying that the InnoDB storage engine can safely upgrade data from older server versions.
- [QA Datasets](/docs/server/reference/product-development/server-development/quality/qa-datasets.md): Information on the standardized datasets and database dumps used across different testing environments for consistent results.
- [DBT-3 Dataset](/docs/server/reference/product-development/server-development/quality/qa-datasets/dbt-3-dataset.md): Information on the standardized datasets and database dumps used for DBT-3 Dataset tests.
- [DBT-3 Queries](/docs/server/reference/product-development/server-development/quality/qa-datasets/dbt-3-queries.md): Information on the standardized datasets and database dumps used for DBT-3 Queries tests.
- [OpenStreetMap Dataset](/docs/server/reference/product-development/server-development/quality/qa-datasets/openstreetmap-dataset.md): Information on the standardized datasets and database dumps used for OpenStreetMap tests.
- [osmdb06.sql](/docs/server/reference/product-development/server-development/quality/qa-datasets/osmdb06sql.md): Information on the standardized datasets and database dumps used for OpenStreetMap.
- [MariaDB Development Tools](/docs/server/reference/product-development/server-development/tools.md): A guide to the essential software and utilities recommended for building, testing, and optimizing MariaDB Server code.
- [Jira - Status and Transition Definitions](/docs/server/reference/product-development/server-development/tools/jira-status-and-transition-definitions.md): Explains the various lifecycle statuses and workflow transitions used for issue tracking in MariaDB's Jira instance.
- [Jira - Project Planning and Tracking](/docs/server/reference/product-development/server-development/tools/jira.md): Details how Jira is utilized for roadmap scheduling, sprint planning, and managing the overall progress of development tasks.
- [Profiling with Linux perf tool](/docs/server/reference/product-development/server-development/tools/profiling-with-linux-perf-tool.md): A technical guide on using the Linux perf utility to analyze server performance and identify code bottlenecks.
- [Worklog](/docs/server/reference/product-development/server-development/tools/worklog.md): Documentation regarding the MariaDB Worklog system, used to define, track, and review the progress of new feature implementations.
- [Buildbot](/docs/server/reference/product-development/server-development/tools/buildbot.md): Overview of the continuous integration system used to automate the building and testing of MariaDB across various platforms.
- [About Buildbot](/docs/server/reference/product-development/server-development/tools/buildbot/about-buildbot.md): Provides a high-level overview of the Buildbot continuous integration system and its role in testing MariaDB.
- [Branch Protection Using Buildbot](/docs/server/reference/product-development/server-development/tools/buildbot/branch-protection-using-buildbot.md): Details the policies and automated checks used to protect core branches from unstable or unverified code submissions.
- [Buildbot Database Schema](/docs/server/reference/product-development/server-development/tools/buildbot/buildbot-buildbot-database-schema.md): Technical documentation describing the internal database structure used by Buildbot to store build history and metadata.
- [Buildbot Development](/docs/server/reference/product-development/server-development/tools/buildbot/buildbot-buildbot-development.md): Instructions for engineers contributing to or modifying the MariaDB-specific Buildbot configuration and infrastructure.
- [Buildbot ToDo](/docs/server/reference/product-development/server-development/tools/buildbot/buildbot-todo.md): A roadmap and list of pending tasks, improvements, and known issues currently tracked for the Buildbot environment.
- [Package Testing with Buildbot and KVM](/docs/server/reference/product-development/server-development/tools/buildbot/package-testing-with-buildbot-and-kvm.md): Explains how Buildbot utilizes Kernel-based Virtual Machines (KVM) to automate the testing of installation packages.
- [Buildbot runvm](/docs/server/reference/product-development/server-development/tools/buildbot/runvm.md): Documentation for the runvm script, which manages virtual machine lifecycles during the Buildbot testing process.
- [Buildbot Setup](/docs/server/reference/product-development/server-development/tools/buildbot/setup.md): A comprehensive guide on the requirements and steps necessary to configure and deploy a Buildbot instance for MariaDB.
- [Buildbot Setup Notes](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-buildbot-setup-notes.md): A collection of miscellaneous technical notes and best practices for troubleshooting Buildbot installations.
- [Buildbot Setup for macOS](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-buildbot-setup-for-macosx.md): Specific instructions and requirements for configuring a Buildbot worker on macOS systems.
- [Buildbot Setup for Windows](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-buildbot-setup-for-windows.md): A guide to setting up Buildbot build environments on Windows, covering dependencies and configuration steps.
- [Buildbot Setup for BSD](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-bsd.md): Outlines the necessary steps to install and configure Buildbot on various BSD distributions.
- [Buildbot Setup for Solaris Sparc](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-solaris-sparc.md): Technical requirements and installation procedures for running Buildbot on Solaris Sparc architecture.
- [Buildbot Setup for Solaris x86](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-solaris-x86.md): Detailed configuration steps for setting up Buildbot workers on Solaris x86 platforms.
- [Buildbot Setup for Ubuntu-Debian](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-ubuntu-debian.md): Standard procedures for deploying Buildbot workers on Ubuntu and Debian-based Linux distributions.
- [Buildbot Setup for VM Host](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-vm-host.md): Instructions for configuring the host machine that manages virtualized Buildbot workers.
- [Setup of a Buildbot Build Slave](/docs/server/reference/product-development/server-development/tools/buildbot/setup/how-do-i-setup-a-buildbot-build-slave.md): A foundational tutorial on the general process of creating and connecting a new build worker (slave).
- [Buildbot Setup for Virtual Machines](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - FreeBSD 9.2](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-freebsd-92.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - General Principles](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-general-principles.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Additional Steps](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Install Cassandra on Fulltest VMs](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/install-cassandra-on-fulltest-vms.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Install cmake on Build VMs](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/install-cmake-on-build-vms.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Installing Correct Libraries for PAM and readline](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/installing-correct-libraries-for-pam-and-readline.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Installing the Boost Library Needed for the OQGraph Storage Engine](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/installing-the-boost-library-needed-for-the-oqgraph-storage-engine.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Installing VM Images for Testing .deb Upgrade Between Versions](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/installing-vm-images-for-testing-deb-upgrade-between-versions.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Resizing a Virtual Machine Image](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/resizing-a-virtual-machine-image.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Update Debian 4 Mirrors for Buildbot VMs](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-additional-steps/update-debian-4-mirrors-for-buildbot-vms.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 4 amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-4-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 4 i386](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-4-i386.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 5 amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-5-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 5 i386](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-5-i386.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 6 amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-6-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Debian 6 i386](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-debian/buildbot-setup-for-virtual-machines-debian-6-i386.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Red Hat](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Centos 5 amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-centos-5-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - CentOS 5 i386](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-centos-5-i386.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - CentOS 6.2](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-centos-62.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Fedora 16](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-fedora-16.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Fedora 17](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-fedora-17.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Fedora 18](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-fedora-18.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Fedora 19](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-fedora-19.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Fedora 20](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-fedora-20.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Red Hat 6 x86](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-red-hat/buildbot-setup-for-virtual-machines-red-hat-6-x86.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 10.04 (alpha), i386 and amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1004-alpha-i386-and-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 10.10 "maverick"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1010-maverick.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 11.04 "natty"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1104-natty.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 11.10 "oneiric"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1110-oneiric.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 12.04 "precise"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1204-precise.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 12.10 "quantal"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1210-quantal.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 13.04 "raring"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1304-raring.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 13.10 "saucy"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1310-saucy.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 14.04 "trusty"](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-1404-trusty.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 8.04, 8.10, and 9.10](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-804-810-and-910.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 9.04 amd64](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-904-amd64.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Buildbot Setup for Virtual Machines - Ubuntu 9.04 i386](/docs/server/reference/product-development/server-development/tools/buildbot/setup/buildbot-setup-for-virtual-machines/buildbot-setup-for-virtual-machines-ubuntu/buildbot-setup-for-virtual-machines-ubuntu-904-i386.md): Explains how to provision and configure virtual machine instances specifically for Buildbot testing.
- [Using Git With MariaDB](/docs/server/reference/product-development/server-development/tools/using-git-with-mariadb.md): Outlines the best practices and mandatory procedures for using Git to manage source code contributions and version control.
- [Using Git](/docs/server/reference/product-development/server-development/tools/using-git-with-mariadb/using-git.md): Provides essential instructions and best practices for developers using Git to manage source code and contribute to MariaDB.
- [Configuring Git to Send Commit Notices](/docs/server/reference/product-development/server-development/tools/using-git-with-mariadb/configuring-git-to-send-commit-notices.md): Explains how to set up Git to automatically notify relevant mailing lists or systems when new commits are pushed to the repository.
- [MariaDB Internals](/docs/server/reference/product-development/mariadb-internals.md): Explores the low-level architecture of MariaDB, documenting source code internals, merging procedures, and how to use internal APIs in external programs.
- [Merging into MariaDB](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb.md): Serves as the primary category overview explaining the processes and strategies used to merge various source trees into the MariaDB codebase.
- [Creating a New Merge Tree](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb/creating-a-new-merge-tree.md): Provides technical instructions on how to set up a new source tree specifically for the purpose of merging external updates into MariaDB.
- [Merging from MySQL (obsolete)](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb/merging-from-mysql-obsolete.md): Documents the legacy process previously used to incorporate upstream changes from MySQL into the MariaDB server.
- [Merging New XtraDB Releases (obsolete)](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb/merging-new-xtradb-releases-obsolete.md): Details the now-obsolete workflow for integrating updated releases of the XtraDB storage engine into MariaDB.
- [Merging TokuDB (obsolete)](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb/merging-tokudb-obsolete.md): Covers the historic procedures for merging updates from the TokuDB storage engine source tree into MariaDB.
- [Merging with a Merge Tree](/docs/server/reference/product-development/mariadb-internals/mariadb-internals-documentation-merging-into-mariadb/merging-with-a-merge-tree.md): Explains the operational steps and commands required to execute a code merge using a pre-configured merge tree.
- [MariaDB Source Code Internals](/docs/server/reference/product-development/mariadb-internals/mariadb-source-code-internals.md): Serves as the main landing page for articles detailing the low-level source code architecture and internal logic of the MariaDB server.
- [Stored Procedure Internals](/docs/server/reference/product-development/mariadb-internals/mariadb-source-code-internals/stored-procedure-internals.md): Explores the internal implementation and execution flow of stored procedures, including how they are parsed and stored by the server.
- [Connection Memory Usage](/docs/server/reference/product-development/mariadb-internals/mariadb-source-code-internals/connect-memory-usage.md): Provides a technical breakdown of how the server allocates and manages memory for each client connection and thread.
- [Using MariaDB with Your Programs (API)](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api.md): This main page serves as a landing hub for developers looking to integrate MariaDB functionality into external applications using internal APIs.
- [Progress Reporting](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/progress-reporting.md): Describes the API and mechanisms that allow client applications to receive real-time progress updates for long-running server-side operations.
- [libmysqld](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/libmysqld.md): Documentation for the embedded MariaDB server library, which allows for a full MariaDB server to run inside a client application process.
- [Embedded MariaDB Interface](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/libmysqld/embedded-mariadb-interface.md): Detailed guide on the C API functions and requirements for initializing, using, and terminating the embedded MariaDB server library.
- [The mariadb-test and mariadb-test-embedded Programs](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/libmysqld/mariadb-test-and-mariadb-test-embedded.md): Explains the differences and usage of the standard testing tool versus the version specifically designed for the embedded server.
- [Non-Blocking Client Library](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/non-blocking-client-library.md): Details the asynchronous API used to perform database operations without blocking the execution thread, improving performance in high-concurrency applications.
- [Non-Blocking Operation in the Client Library](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/non-blocking-client-library/about-non-blocking-operation-in-the-client-library.md): Explains the concepts behind non-blocking operations, which allow applications to process other tasks while waiting for database network I/O.
- [Non-Blocking API Reference](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/non-blocking-client-library/non-blocking-api-reference.md): Provides a comprehensive list of the specific functions and parameters available in the MariaDB non-blocking client interface.
- [Using the Non-Blocking Library](/docs/server/reference/product-development/mariadb-internals/using-mariadb-with-your-programs-api/non-blocking-client-library/using-the-non-blocking-library.md): A practical guide on how to integrate and implement the non-blocking API within a C application to handle asynchronous database connections.