7-day MaxScale Trial: Explore the latest version of our advanced database proxy!
Start Trial Now
LogoLogo
Download MariaDBContact Us
  • Home
  • MariaDB Platform
  • Server
  • MaxScale
  • ColumnStore
  • Galera Cluster
  • Connectors
  • Tools
  • Release Notes
  • General Resources
  • About
    • About MariaDB Documentation
      • Contributing Documentation
      • Documentation Style Guide
      • Reporting Documentation Issues
    • About MariaDB
    • Contact Us
  • Community
    • Joining the Community
    • MariaDB Community
      • Bug Tracking
        • Reporting Software Bugs
        • Bug Processing
        • Security Bug Fixing
        • Building MariaDB Server for Debugging
        • Extracting Entries from the Binary Log
        • Profiling Memory Usage
      • Legal Documents
        • MariaDB Contributor Agreement
        • MariaDB Contributor Agreement FAQ
      • Frequently Asked Questions
        • MariaDB Community Server
        • The mariadb-backup Tool
        • Community Questions
          • How Can I Contribute to MariaDB?
        • DBA Questions
        • Developer Questions
          • How can a VBA Application Connect to MariaDB?
          • How can I Learn about Developing MariaDB?
          • How many JOIN Clauses are Allowed in a Query?
          • Remote connection work but often get error HY000/2002 connection timed out
          • Tools Available for Developing on the MariaDB Code
          • Where is the table_cache in MariaDB?
          • Why is ORDER BY in a FROM Subquery Ignored?
        • General Questions
          • Does the Password Prompt Appear Before or After Establishing a Connection?
          • What is the Goal of MariaDB?
          • Why is the Software Called MariaDB?
        • High Availability Questions
        • Licensing Questions
          • Licensing FAQ
          • MariaDB Licenses
        • MariaDB Software Questions
          • What is MariaDB?
          • What is MariaDB's Release Policy and Schedule?
          • What will be in MariaDB version X?
          • When will MariaDB version X be released?
        • Migrating to MariaDB Questions
          • How can I Import Only a Table's Structure?
          • How do I migrate a MySQL database to Amazon RDS?
          • Red Hat 6 Process Limit a Errors
        • Public Questions
        • Support Questions
          • Getting Help With MariaDB
        • Supported Software & Features
    • Contributing & Participating
      • Contributing Code
      • Contributing to the MariaDB Project
      • MariaDB Public FTP Server
      • Sponsoring the MariaDB Project
      • Log of MariaDB Contributions
      • Google Summer of Code
        • Google Summer of Code 2025
        • Google Summer of Code 2024
        • Google Summer of Code 2023
        • Google Summer of Code 2022
        • Google Summer of Code 2021
        • Google Summer of Code 2020
        • Google Summer of Code 2019
        • Google Summer of Code 2018
        • Google Summer of Code 2017
        • Google Summer of Code 2016
        • Google Summer of Code 2015
        • Google Summer of Code 2014
        • Google Summer of Code 2013
      • Google Season of Docs
        • Google Season of Docs 2019
        • Google Season of Docs 2020
  • Product Development
    • MariaDB Quality Development Rules
    • Uploading Package to PPA
    • Debugging MariaDB
      • Compiling MariaDB for Debugging
      • Creating a Trace File
      • Debugging a Running Server (on Linux)
      • Debugging MariaDB With a Debugger
      • Debugging Memory Usage
      • Enabling Core Dumps
      • How to Produce a Full Stack Trace for mariadbd
      • How to Use procmon to Trace mysqld.exe Filesystem Access
      • Limitations/Differences with a MariaDB Server Compiled for Debugging
    • MariaDB Development
      • MariaDB Server Roadmap
      • Quality Assurance
        • Code Coverage
        • Code Coverage with dgcov
        • Optimizer Quality
        • QA - Aria Recovery
        • QA Metrics
        • QA Tests
        • QA Tools
        • Random Query Generator Tests
        • RQG Extensions for MariaDB
        • Worklog Quality Checklist Template
        • Benchmarks and Long Running Tests
          • Benchmark Results
            • sysbench v0.5 - Single Five Minute Runs on T500 Laptop
            • sysbench v0.5 - Three Times Five Minutes Runs on work with 5.1.42
            • sysbench v0.5 - 3x Five Minute Runs on work with 5.2-wl86
            • sysbench v0.5 - 3x Five Minute Runs on work with 5.1 vs. 5.2-wl86
            • sysbench v0.5 - 3x 15 Minute Runs on perro with 5.2-wl86 a
            • sysbench v0.5 - 3x 15 Minute Runs on perro with 5.2-wl86 b
            • Select Random Ranges and Select Random Point
            • Sysbench Results
            • sysbench v0.5 - Single Five Minute Runs on perro
            • sysbench v0.5 - Single Five Minute Runs on work
            • Threadpool Benchmarks
          • Benchmarks
            • Benchmark Builds
            • Benchmarking Aria
            • DBT3 Automation Scripts
            • DBT3 Benchmark Results InnoDB
            • DBT3 Benchmark Results MyISAM
            • DBT3 Example Preparation Time
            • MariaDB 5.3 - Asynchronous I/O on Windows with InnoDB
            • MariaDB 5.3/MySQL 5.5 Windows performance patches
            • mariadb-tools
            • Performance of MEMORY Tables
            • Recommended Settings for Benchmarks
            • RQG Performance Comparisons
            • run-sql-bench.pl
            • Segmented Key Cache Performance
            • sysbench Benchmark Setup
        • InnoDB Upgrade Tests
          • 10.0.32 Release Upgrade Tests
          • 10.0.34 Release Upgrade Tests
          • 10.0.36 Release Upgrade Tests
          • 10.1.22 Pre-release Upgrade Tests
          • 10.1.25 Release Upgrade Tests
          • 10.1.26 Release Upgrade Tests
          • 10.1.30 Release Upgrade Tests
          • 10.1.32 Release Upgrade Tests
          • 10.1.36 Release Upgrade Tests
          • 10.2.12 Release Upgrade Tests
          • 10.2.13 Release Upgrade Tests
          • 10.2.14 Release Upgrade Tests
          • 10.2.17 Release Upgrade Tests
          • 10.2.18 Release Upgrade Tests
          • 10.2.5 Pre-release Upgrade Tests
          • 10.2.7 Release Upgrade Tests
          • 10.3.10 Release Upgrade Tests
          • 10.3.3-beta Release Upgrade Tests
          • 10.3.4-beta Release Upgrade Tests
          • 10.3.5-gamma Release Upgrade Tests
          • 10.3.6-gamma Release Upgrade Tests
          • 10.3.9 Release Upgrade Tests
        • QA Datasets
          • DBT-3 Dataset
          • DBT-3 Queries
          • OpenStreetMap Dataset
          • osmdb06.sql
      • MariaDB Development Tools
        • Jira - Status and Transition Definitions
        • Jira - Project Planning and Tracking
        • Profiling with Linux perf tool
        • Worklog
        • Buildbot
          • About Buildbot
          • Branch Protection Using Buildbot
          • Buildbot Database Schema
          • Buildbot Development
          • Buildbot ToDo
          • Package Testing with Buildbot and KVM
          • Buildbot runvm
          • Buildbot Setup
            • Buildbot Setup for MacOSX
            • buildbot-setup-buildbot-setup-for-windows
            • Buildbot Setup Notes
            • Buildbot Setup for BSD
            • Buildbot Setup for Solaris Sparc
            • Buildbot Setup for Solaris x86
            • Buildbot Setup for Ubuntu-Debian
            • Buildbot Setup for VM host
            • How do I setup a Buildbot build slave?
            • Buildbot Setup for Virtual Machines
              • Buildbot Setup for Virtual Machines - FreeBSD 9.2
              • Buildbot Setup for Virtual Machines - General Principles
              • Buildbot Setup for Virtual Machines - Additional Steps
                • Install Cassandra on Fulltest VMs
                • Install cmake on build VMs
                • Installing correct libraries for PAM and readline
                • Installing the Boost library needed for the OQGraph storage engine
                • Installing VM images for testing .deb upgrade between versions
                • Resizing a Virtual Machine Image
                • Update Debian 4 mirrors for Buildbot VMs
              • Buildbot Setup for Virtual Machines - Debian
                • Buildbot Setup for Virtual Machines - Debian 4 amd64
                • Buildbot Setup for Virtual Machines - Debian 4 i386
                • Buildbot Setup for Virtual Machines - Debian 5 amd64
                • Buildbot Setup for Virtual Machines - Debian 5 i386
                • Buildbot Setup for Virtual Machines - Debian 6 amd64
                • Buildbot Setup for Virtual Machines - Debian 6 i386
                • Buildbot Setup for Virtual Machines - Debian 7 "wheezy"
              • Buildbot Setup for Virtual Machines - Red Hat
                • Buildbot Setup for Virtual Machines - Centos 5 amd64
                • Buildbot Setup for Virtual Machines - CentOS 5 i386
                • Buildbot Setup for Virtual Machines - CentOS 6.2
                • Buildbot Setup for Virtual Machines - Fedora 16
                • Buildbot Setup for Virtual Machines - Fedora 17
                • Buildbot Setup for Virtual Machines - Fedora 18
                • Buildbot Setup for Virtual Machines - Fedora 19
                • Buildbot Setup for Virtual Machines - Fedora 20
                • Buildbot Setup for Virtual Machines - Red Hat 6 x86
              • Buildbot Setup for Virtual Machines - Ubuntu
                • Buildbot Setup for Virtual Machines - Ubuntu 10.04 (alpha), i386 and amd64
                • Buildbot Setup for Virtual Machines - Ubuntu 10.10 "maverick"
                • Buildbot Setup for Virtual Machines - Ubuntu 11.04 "natty"
                • Buildbot Setup for Virtual Machines - Ubuntu 11.10 "oneiric"
                • Buildbot Setup for Virtual Machines - Ubuntu 12.04 "precise"
                • Buildbot Setup for Virtual Machines - Ubuntu 12.10 "quantal"
                • Buildbot Setup for Virtual Machines - Ubuntu 13.04 "raring"
                • Buildbot Setup for Virtual Machines - Ubuntu 13.10 "saucy"
                • Buildbot Setup for Virtual Machines - Ubuntu 14.04 "trusty"
                • Buildbot Setup for Virtual Machines - Ubuntu 8.04, 8.10, and 9.10
                • Buildbot Setup for Virtual Machines - Ubuntu 9.04 amd64
                • Buildbot Setup for Virtual Machines - Ubuntu 9.04 i386
        • Using Git with MariaDB
          • Configuring Git to Send Commit Notices
          • Using Git
      • Working with GitHub
      • Debugging
        • Checking MariaDB
        • MariaDB Crashes
        • MariaDB Error Messages
        • Memory is Leaking
    • MariaDB Internals
      • Writing Plugins for MariaDB
      • Encryption Plugin API
      • Information Schema plugins: SHOW and FLUSH statements
      • Password Validation Plugin API
      • Merging into MariaDB
        • Creating a New Merge Tree
        • Merging from MySQL (obsolete)
        • Merging New XtraDB Releases (obsolete)
        • Merging TokuDB (obsolete)
        • Merging with a Merge Tree
      • Query Optimizer
        • Block-Based Join Algorithms
        • Condition Selectivity Computation Internals
        • Extended Keys
        • MIN/MAX optimization
        • Notes When an Index Cannot Be Used
        • Optimizer Debugging With GDB
        • Optimizer Development
        • optimizer_max_sel_arg_weight
        • Range Optimizer
        • The Optimizer Cost Model from MariaDB 11.0
        • Optimizer Trace
          • Basic Optimizer Trace Example
          • How to Collect Large Optimizer Traces
          • Optimizer Trace for Developers
          • optimizer-trace-guide
          • Optimizer Trace Overview
          • Optimizer Trace Resources
      • MariaDB Source Code Internals
        • Stored Procedure Internals
        • MariaDB Memory Usage
          • Connect Memory Usage
      • Using MariaDB with Your Programs (API)
        • Progress Reporting
        • Error Codes
          • MariaDB Error Code Reference
          • Operating System Error Codes
          • MariaDB Error Codes 1000 to 1099
            • Error 1000: hashchk
            • Error 1001: isamchk
            • Error 1002: NO
            • Error 1003: YES
            • Error 1004: Can't create file
            • Error 1005: Can't create table
            • Error 1006: Can't create database
            • Error 1007: Can't create database, database exists
            • Error 1008: Can't drop database; database doesn't exist
            • Error 1009: Error dropping database (can't delete)
            • Error 1010: Error dropping database (can't rmdir)
            • Error 1011: Error on delete of
            • Error 1012: Can't read record in system table
            • Error 1013: Can't get status of
            • Error 1014: Can't get working directory
            • Error 1015: Can't lock file
            • Error 1016: Can't open file
            • Error 1017: Can't find file
            • Error 1018: Can't read dir of
            • Error 1019: Can't change dir to
            • Error 1020: Record has changed since last read in table
            • Error 1021: Disk full (%s); waiting for someone to free some space
            • Error 1022: Can't write; duplicate key in table
            • Error 1023: Error on close of
            • Error 1024: Error reading file
            • Error 1025: Error on rename of
            • Error 1026: Error writing file
            • Error 1027: is locked against change
            • Error 1028: Sort aborted
            • Error 1029: View doesn't exist for
            • Error 1030: Got error from storage engine
            • Error 1031: Table storage engine doesn't have this option
            • Error 1032: Can't find record in
            • Error 1033: Incorrect information in file
            • Error 1034: Incorrect key file for table; try to repair it
            • Error 1035: Old key file for table; repair it!
            • Error 1036: Table is read only
            • Error 1037: Out of memory; restart server and try again
            • Error 1038: Out of sort memory, consider increasing server sort buffer size
            • Error 1039: Unexpected EOF found when reading file
            • Error 1040: Too many connections
            • Error 1041: Out of memory
            • Error 1042: Can't get hostname for your address
            • Error 1043: Bad handshake
            • Error 1044: Access denied for user
            • Error 1045: Access denied for user (using password)
            • Error 1046: No database selected
            • Error 1047: Unknown command
            • Error 1048: Column cannot be null
            • Error 1049: Unknown database
            • Error 1050: Table already exists
            • Error 1051: Unknown table
            • Error 1052: Column is ambiguous
            • Error 1053: Server shutdown in progress
            • Error 1054: Unknown column
            • Error 1055: isn't in GROUP BY
            • Error 1056: Can't group on
            • Error 1057: Statement has sum functions and columns in same statement
            • Error 1058: Column count doesn't match value count
            • Error 1059: Identifier name is too long
            • Error 1060: Duplicate column name
            • Error 1061: Duplicate key name
            • Error 1062: Duplicate entry for key
            • Error 1063: Incorrect column specifier for column
            • Error 1064: near at line
            • Error 1065: Query was empty
            • Error 1066: Not unique table/alias
            • Error 1067: Invalid default value for
            • Error 1068: Multiple primary key defined
            • Error 1069: Too many keys specified; max keys allowed
            • Error 1070: Too many key parts specified; max parts allowed
            • Error 1071: Specified key was too long; max key length is
            • Error 1072: Key column doesn't exist in table
            • Error 1073: BLOB column can't be used in key specification with the used table type
            • Error 1074: Column length too big for column; use BLOB or TEXT instead
            • Error 1075: Incorrect table definition; there can be only one auto column and it must be defined as
            • Error 1076: ready for connections
            • Error 1077: Normal shutdown
            • Error 1078: Got signal. Aborting!
            • Error 1079: Shutdown complete
            • Error 1080: Forcing close of thread
            • Error 1081: Can't create IP socket
            • Error 1082: Table has no index like the one used in CREATE INDEX; recreate the table
            • Error 1083: Field separator argument is not what is expected; check the manual
            • Error 1084: You can't use fixed rowlength with BLOBs; please use 'fields terminated by'
            • Error 1085: The file must be in the database directory or be readable by all
            • Error 1086: File already exists
            • Error 1087: Records Deleted Skipped Warnings
            • Error 1088: Records Duplicates
            • Error 1089: Incorrect prefix key; the used key part isn't a string, the used length is longer than t
            • Error 1090: You can't delete all columns with ALTER TABLE; use DROP TABLE instead
            • Error 1091: Can't DROP; check that column/key exists
            • Error 1092: Records Duplicates Warnings
            • Error 1093: You can't specify target table for update in FROM clause
            • Error 1094: Unknown thread id
            • Error 1095: You are not owner of thread
            • Error 1096: No tables used
            • Error 1097: Too many strings for column and SET
            • Error 1098: Can't generate a unique log-filename
            • Error 1099: Table was locked with a READ lock and can't be updated
          • MariaDB Error Codes 1100 to 1199
            • Error 1100: Table was not locked with LOCK TABLES
            • Error 1101: You should never see it
            • Error 1102: Incorrect database name
            • Error 1103: Incorrect table name
            • e1104
            • Error 1105: Unknown error
            • Error 1106: Unknown procedure
            • Error 1107: Incorrect parameter count to procedure
            • Error 1108: Incorrect parameters to procedure
            • Error 1109: Unknown table
            • Error 1110: Column specified twice
            • Error 1111: Invalid use of group function
            • Error 1112: Table uses an extension that doesn't exist in this MariaDB version
            • Error 1113: A table must have at least 1 column
            • Error 1114: The table is full
            • Error 1115: Unknown character set
            • Error 1116: Too many tables; MariaDB can only use tables in a join
            • Error 1117: Too many columns
            • Error 1118: Row size too large
            • Error 1119: Thread stack overrun
            • Error 1120: Cross dependency found in OUTER JOIN; examine your ON conditions
            • Error 1121: Table handler doesn't support NULL in given index
            • Error 1122: Can't load function
            • Error 1123: Can't initialize function
            • Error 1124: No paths allowed for shared library
            • Error 1125: Function already exists
            • Error 1126: Can't open shared library
            • Error 1127: Can't find symbol in library
            • Error 1128: Function is not defined
            • Error 1129: Host is blocked because of many connection errors
            • Error 1130: Host is not allowed to connect to this MariaDB server
            • Error 1131: You are using MariaDB as an anonymous user
            • Error 1132: You must have privileges to update tables in the mysql database
            • Error 1133: Can't find any matching row in the user table
            • Error 1134: Rows matched Changed Warnings
            • Error 1135: Can't create a new thread
            • Error 1136: Column count doesn't match value count at row
            • Error 1137: Can't reopen table
            • Error 1138: Invalid use of NULL value
            • Error 1139: Got error from regexp
            • Error 1140: Mixing of GROUP columns with no GROUP columns
            • Error 1141: There is no such grant defined for user on host
            • Error 1142: command denied to user for table
            • Error 1143: command denied to user for column in table
            • Error 1144: Illegal GRANT/REVOKE command
            • Error 1145: The host or user argument to GRANT is too long
            • Error 1146: Table doesn't exist
            • Error 1147: There is no such grant defined for user on host on table
            • Error 1148: The used command is not allowed with this MariaDB version
            • Error 1149: You have an error in your SQL syntax
            • Error 1150: Delayed insert thread couldn't get requested lock for table
            • Error 1151: Too many delayed threads in use
            • Error 1152: Aborted connection to db user
            • Error 1153: Got a packet bigger than 'max_allowed_packet' bytes
            • Error 1154: Got a read error from the connection pipe
            • Error 1155: Got an error from fcntl()
            • Error 1156: Got packets out of order
            • Error 1157: Couldn't uncompress communication packet
            • Error 1158: Got an error reading communication packets
            • Error 1159: Got timeout reading communication packets
            • Error 1160: Got an error writing communication packets
            • Error 1161: Got timeout writing communication packets
            • Error 1162: Result string is longer than 'max_allowed_packet' bytes
            • Error 1163: The used table type doesn't support BLOB/TEXT columns
            • Error 1164: The used table type doesn't support AUTO_INCREMENT columns
            • Error 1165: INSERT DELAYED can't be used with table because it is locked
            • Error 1166: Incorrect column name
            • Error 1167: The used storage engine can't index column
            • Error 1168: Unable to open underlying table which is differently defined or of non-MyISAM type or do
            • Error 1169: Can't write, because of unique constraint, to table
            • Error 1170: BLOB/TEXT column used in key specification without a key length
            • Error 1171: All parts of a PRIMARY KEY must be NOT NULL
            • Error 1172: Result consisted of more than one row
            • Error 1173: This table type requires a primary key
            • Error 1174: This version of MariaDB is not compiled with RAID support
            • Error 1175: You are using safe update mode and you tried to update a table without a WHERE that uses
            • Error 1176: Key doesn't exist in table
            • Error 1177: Can't open table
            • Error 1178: The storage engine for the table doesn't support
            • Error 1179: You are not allowed to execute this command in a transaction
            • Error 1180: Got error during COMMIT
            • Error 1181: Got error during ROLLBACK
            • Error 1182: Got error during FLUSH_LOGS
            • Error 1183: Got error during CHECKPOINT
            • Error 1184: Aborted connection to db user host
            • Error 1185: You should never see it
            • Error 1186: Binlog closed, cannot RESET MASTER
            • Error 1187: Failed rebuilding the index of dumped table
            • Error 1188: Error from master
            • Error 1189: Net error reading from master
            • Error 1190: Net error writing to master
            • Error 1191: Can't find FULLTEXT index matching the column list
            • Error 1192: Can't execute the given command because you have active locked tables or an active trans
            • Error 1193: Unknown system variable
            • Error 1194: Table is marked as crashed and should be repaired
            • Error 1195: Table is marked as crashed and last (automatic?) repair failed
            • Error 1196: Some non-transactional changed tables couldn't be rolled back
            • Error 1197: Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage
            • Error 1198: This operation cannot be performed with a running slave; run STOP SLAVE first
            • Error 1199: This operation requires a running slave; configure slave and do START SLAVE
          • MariaDB Error Codes 1200 to 1299
            • Error 1200: The server is not configured as slave
            • Error 1201: Could not initialize master info structure
            • Error 1202: Could not create slave thread; check system resources
            • Error 1203: User already has more than 'max_user_connections' active connections
            • Error 1204: You may only use constant expressions with SET
            • Error 1205: Lock wait timeout exceeded; try restarting transaction
            • Error 1206: The total number of locks exceeds the lock table size
            • Error 1207: Update locks cannot be acquired during a READ UNCOMMITTED transaction
            • Error 1208: DROP DATABASE not allowed while thread is holding global read lock
            • Error 1209: CREATE DATABASE not allowed while thread is holding global read lock
            • Error 1210: Incorrect arguments to
            • Error 1211: is not allowed to create new users
            • Error 1212: Incorrect table definition; all MERGE tables must be in the same database
            • Error 1213: Deadlock found when trying to get lock; try restarting transaction
            • Error 1214: The used table type doesn't support FULLTEXT indexes
            • Error 1215: Cannot add foreign key constraint
            • Error 1216: Cannot add or update a child row: a foreign key constraint fails
            • Error 1217: Cannot delete or update a parent row: a foreign key constraint fails
            • Error 1218: Error connecting to master
            • Error 1219: Error running query on master
            • Error 1220: Error when executing command
            • Error 1221: Incorrect usage of
            • Error 1222: The used SELECT statements have a different number of columns
            • Error 1223: Can't execute the query because you have a conflicting read lock
            • Error 1224: Mixing of transactional and non-transactional tables is disabled
            • Error 1225: Option used twice in statement
            • Error 1226: User has exceeded the resource
            • Error 1227: Access denied; you need (at least one of) the privilege(s) for this operation
            • Error 1228: Variable is a SESSION variable and can't be used with SET GLOBAL
            • Error 1229: Variable is a GLOBAL variable and should be set with SET GLOBAL
            • Error 1230: Variable doesn't have a default value
            • Error 1231: Variable can't be set to the value of
            • Error 1232: Incorrect argument type to variable
            • Error 1233: Variable can only be set, not read
            • Error 1234: Incorrect usage/placement
            • Error 1235: This version of MariaDB doesn't yet support
            • Error 1236: Got fatal error from master when reading data from binary log
            • Error 1237: Slave SQL thread ignored the query because of replicate-*-table rules
            • Error 1238: Variable is a
            • Error 1239: Incorrect foreign key definition
            • Error 1240: Key reference and table reference don't match
            • Error 1241: Operand should contain column(s)
            • Error 1242: Subquery returns more than 1 row
            • Error 1243: Unknown prepared statement handler given
            • Error 1244: Help database is corrupt or does not exist
            • Error 1245: Cyclic reference on subqueries
            • Error 1246: Converting column from to
            • Error 1247: Reference not supported
            • Error 1248: Every derived table must have its own alias
            • Error 1249: Select was reduced during optimization
            • Error 1250: Table from one of the SELECTs cannot be used
            • Error 1251: Client does not support authentication protocol requested by server
            • Error 1252: All parts of a SPATIAL index must be NOT NULL
            • Error 1253: COLLATION is not valid for CHARACTER SET
            • Error 1254: Slave is already running
            • Error 1255: Slave already has been stopped
            • Error 1256: Uncompressed data size too large
            • Error 1257: ZLIB: Not enough memory
            • Error 1258: ZLIB: Not enough room in the output buffer
            • Error 1259: ZLIB: Input data corrupted
            • Error 1260: Row was cut by GROUP_CONCAT()
            • Error 1261: Row doesn't contain data for all columns
            • Error 1262: Row was truncated; it contained more data than there were input columns
            • Error 1263: Column set to default value; NULL supplied to NOT NULL columnError 1263: Column set to d
            • Error 1264: Out of range value for column
            • Error 1265: Data truncated for column
            • Error 1266: Using storage engine for table
            • Error 1267: Illegal mix of collations for operation
            • Error 1268: Cannot drop one or more of the requested users
            • Error 1269: Can't revoke all privileges for one or more of the requested users
            • Error 1270: Illegal mix of collations for operation
            • Error 1271: Illegal mix of collations for operation
            • Error 1272: Variable is not a variable component (can't be used as XXXX.variable_name)
            • Error 1273: Unknown collation
            • Error 1274: SSL parameters in CHANGE MASTER are ignored because this MariaDB slave was compiled with
            • Error 1275: Server is running in --secure-auth mode, but has a password in the old format
            • Error 1276: Field or reference of SELECT was resolved in SELECT
            • Error 1277: Incorrect parameter or combination of parameters for START SLAVE UNTIL
            • Error 1278: It is recommended to use --skip-slave-start when doing step-by-step replication with STA
            • Error 1279: SQL thread is not to be started so UNTIL options are ignored
            • Error 1280: Incorrect index name
            • Error 1281: Incorrect catalog name
            • Error 1282: Query cache failed to set size; new query cache size is
            • Error 1283: Column cannot be part of FULLTEXT index
            • Error 1284: Unknown key cache
            • Error 1285: MariaDB is started in --skip-name-resolve mode
            • Error 1286: Unknown storage engine
            • Error 1287: is deprecated and will be removed in a future release. Please use instead
            • Error 1288: The target table of the is not updatable
            • Error 1289: The feature is disabled; you need MariaDB built with to have it working
            • Error 1290: The MariaDB server is running with the option so it cannot execute this statement
            • Error 1291: Column has duplicated value
            • Error 1292: Truncated incorrect value
            • Error 1293: Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAM
            • Error 1294: Invalid ON UPDATE clause
            • Error 1295: This command is not supported in the prepared statement protocol yet
            • Error 1296: Got error from
            • Error 1297: Got temporary error from
            • Error 1298: Unknown or incorrect time zone
            • Error 1299: Invalid TIMESTAMP value in column at row
          • MariaDB Error Codes 1300 to 1399
            • Error 1300: Invalid character string
            • Error 1301: Result was larger than max_allowed_packet - truncated
            • Error 1302: Conflicting declarations
            • Error 1303: Can't create from within another stored routine
            • Error 1304: already exists
            • Error 1305: does not exist
            • Error 1306: Failed to DROP
            • Error 1307: Failed to CREATE
            • Error 1308: with no matching label
            • Error 1309: Redefining label
            • Error 1310: End-label without match
            • Error 1311: Referring to uninitialized variable
            • Error 1312: PROCEDURE can't return a result set in the given context
            • Error 1313: RETURN is only allowed in a FUNCTION
            • Error 1314: is not allowed in stored procedures
            • Error 1315: The update log is deprecated and replaced by the binary log
            • Error 1316: The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been
            • Error 1317: Query execution was interrupted
            • Error 1318: Incorrect number of arguments; expected, got
            • Error 1319: Undefined CONDITION
            • Error 1320: No RETURN found in FUNCTION
            • Error 1321: FUNCTION ended without RETURN
            • Error 1322: Cursor statement must be a SELECT
            • Error 1323: Cursor SELECT must not have INTO
            • Error 1324: Undefined CURSOR
            • Error 1325: Cursor is already open
            • Error 1326: Cursor is not open
            • Error 1327: Undeclared variable
            • Error 1328: Incorrect number of FETCH variables
            • Error 1329: No data - zero rows fetched, selected, or processed
            • Error 1330: Duplicate parameter
            • Error 1331: Duplicate variable
            • Error 1332: Duplicate condition
            • Error 1333: Duplicate cursor
            • Error 1334: Failed to ALTER
            • Error 1335: Subquery value not supported
            • Error 1336: is not allowed in stored function or trigger
            • Error 1337: Variable or condition declaration after cursor or handler declaration
            • Error 1338: Cursor declaration after handler declaration
            • Error 1339: Case not found for CASE statement
            • Error 1340: Configuration file is too big
            • Error 1341: Malformed file type header in file
            • Error 1342: Unexpected end of file while parsing comment
            • Error 1343: Error while parsing parameter
            • Error 1344: Unexpected end of file while skipping unknown parameter
            • Error 1345: EXPLAIN/SHOW can not be issued; lacking privileges for underlying table
            • Error 1346: File has unknown type in its header
            • Error 1347: '%s.%s' is not %s
            • Error 1348: Column is not updatable
            • Error 1349: View's SELECT contains a subquery in the FROM clause
            • Error 1350: View's SELECT contains clause
            • Error 1351: View's SELECT contains a variable or parameter
            • Error 1352: View's SELECT refers to a temporary table'
            • Error 1353: View's SELECT and view's field list have different column counts
            • Error 1354: View merge algorithm can't be used here for now
            • Error 1355: View being updated does not have complete key of underlying table in it
            • Error 1356: View references invalid table(s) or column(s) or function(s) or definer/invoker of view
            • Error 1357: Can't drop or alter from within another stored routine
            • Error 1358: GOTO is not allowed in a stored procedure handler
            • Error 1359: Trigger already exists
            • Error 1360: Trigger does not exist
            • Error 1361: Trigger's is view or temporary table
            • Error 1362: Updating of row is not allowed in trigger
            • Error 1363: There is no row in trigger
            • Error 1364: Field doesn't have a default value
            • Error 1365: Division by 0
            • Error 1366: Incorrect value for column at row
            • Error 1367: Illegal value found during parsing
            • Error 1368: CHECK OPTION on non-updatable view
            • Error 1369: CHECK OPTION failed
            • Error 1370: command denied to user for routine
            • Error 1371: Failed purging old relay logs
            • Error 1372: Password hash should be a %d-digit hexadecimal number
            • Error 1373: Target log not found in binlog index
            • Error 1374: I/O error reading log index file
            • Error 1375: Server configuration does not permit binlog purge
            • Error 1376: Failed on fseek()
            • Error 1377: Fatal error during log purge
            • Error 1378: A purgeable log is in use, will not purge
            • Error 1379: Unknown error during log purge
            • Error 1380: Failed initializing relay log position
            • Error 1381: You are not using binary logging
            • Error 1382: The syntax is reserved for purposes internal to the MariaDB server
            • Error 1383: WSAStartup Failed
            • Error 1384: Can't handle procedures with different groups yet
            • Error 1385: Select must have a group with this procedure
            • Error 1386: Can't use ORDER clause with this procedure
            • Error 1387: Binary logging and replication forbid changing the global server
            • Error 1388: Can't map file
            • Error 1389: Wrong magic in
            • Error 1390: Prepared statement contains too many placeholders
            • Error 1391: Key part length cannot be 0
            • Error 1392: View text checksum failed
            • Error 1393: Can not modify more than one base table through a join view
            • Error 1394: Can not insert into join view without fields list
            • Error 1395: Can not delete from join view
            • Error 1396: Operation failed for
            • Error 1397: XAER_NOTA: Unknown XID
            • Error 1398: XAER_INVAL: Invalid arguments (or unsupported command)
            • Error 1399: XAER_RMFAIL: The command cannot be executed when global transaction is in the state
          • MariaDB Error Codes 1400 to 1499
            • Error 1400: XAER_OUTSIDE: Some work is done outside global transaction
            • Error 1401: XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consist
            • Error 1402: XA_RBROLLBACK: Transaction branch was rolled back
            • Error 1403: There is no such grant defined for user on host on routine
            • Error 1404: Failed to grant EXECUTE and ALTER ROUTINE privileges
            • Error 1405: Failed to revoke all privileges to dropped routine
            • Error 1406: Data too long for column at row
            • Error 1407: Bad SQLSTATE
            • Error 1408: ready for connections. Version: socket: port:
            • Error 1409: Can't load value from file with fixed size rows to variable
            • Error 1410: You are not allowed to create a user with GRANT
            • Error 1411: Incorrect value for function
            • Error 1412: Table definition has changed, please retry transaction
            • Error 1413: Duplicate handler declared in the same block
            • Error 1414: OUT or INOUT argument for routine is not a variable or NEW pseudo-variable in BEFORE tri
            • Error 1415: Not allowed to return a result set from
            • Error 1416: Cannot get geometry object from data you send to the GEOMETRY field
            • Error 1417: A routine failed and has neither NO SQL nor READS SQL DATA in its declaration
            • Error 1418: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration an
            • Error 1419: You do not have the SUPER privilege and binary logging is enabled
            • Error 1420: You can't execute a prepared statement which has an open cursor associated with it
            • Error 1421: The statement has no open cursor
            • Error 1422: Explicit or implicit commit is not allowed in stored function or trigger
            • Error 1423: Field of view underlying table doesn't have a default value
            • Error 1424: Recursive stored functions and triggers are not allowed.
            • Error 1425: Too big scale specified for column
            • Error 1426: Too big precision specified for column
            • Error 1427: For float(M,D, double(M,D or decimal(M,D, M must be >= D
            • Error 1428: You can't combine write-locking of system tables with other tables or lock types
            • Error 1429: Unable to connect to foreign data source
            • Error 1430: There was a problem processing the query on the foreign data source
            • Error 1431: The foreign data source you are trying to reference does not exist
            • Error 1432: Can't create federated table. The data source connection string is not in the correct fo
            • Error 1433: The data source connection string is not in the correct format
            • Error 1434: Can't create federated table. Foreign data src error
            • Error 1435: Trigger in wrong schema
            • Error 1436: Thread stack overrun
            • Error 1437: Routine body is too long
            • Error 1438: Cannot drop default keycache
            • Error 1439: Display width out of range for column
            • Error 1440: XAER_DUPID: The XID already exists
            • Error 1441: Datetime function: field overflow
            • Error 1442: Can't update table in stored function/trigger because it is already used by statement wh
            • Error 1443: The definition of table prevents operation on table
            • Error 1444: The prepared statement contains a stored routine call that refers to that same statement
            • Error 1445: Not allowed to set autocommit from a stored function or trigger
            • Error 1446: Definer is not fully qualified
            • Error 1447: View has no definer information (old table format)
            • Error 1448: You need the SUPER privilege for creation view with definer
            • Error 1449: The user specified as a definer does not exist
            • Error 1450: Changing schema from is not allowed.
            • Error 1451: Cannot delete or update a parent row: a foreign key constraint fails
            • Error 1452: Cannot add or update a child row: a foreign key constraint fails
            • Error 1453: Variable must be quoted with ..., or renamed
            • Error 1454: No definer attribute for trigger
            • Error 1455: has an old format, you should re-create the object(s)
            • Error 1456: Recursive limit (as set by the max_sp_recursion_depth variable) was exceeded for routine
            • Error 1457: Failed to load routine
            • Error 1458: Incorrect routine name
            • Error 1459: Table upgrade required. Please do "REPAIR TABLE" or dump/reload to fix it!
            • Error 1460: AGGREGATE is not supported for stored functions
            • Error 1461: Can't create more than max_prepared_stmt_count statements
            • Error 1462: contains view recursion
            • Error 1463: Non-grouping field is used in clause
            • Error 1464: The used table type doesn't support SPATIAL indexes
            • Error 1465: Triggers can not be created on system tables
            • Error 1466: Leading spaces are removed from name
            • Error 1467: Failed to read auto-increment value from storage engine
            • Error 1468: user name
            • Error 1469: host name
            • Error 1470: String is too long for (should be no longer than )
            • Error 1471: The target table of the is not insertable-into
            • Error 1472: Table is differently defined or of non-MyISAM type or doesn't exist
            • Error 1473: Too high level of nesting for select
            • Error 1474: Name has become ''
            • Error 1475: First character of the FIELDS TERMINATED string is ambiguous
            • Error 1476: The foreign server you are trying to create already exists
            • Error 1477: The foreign server name you are trying to reference does not exist. Data source error
            • Error 1478: Table storage engine does not support the create option
            • Error 1479: Syntax error: PARTITIONING requires definition of VALUES for each partition
            • Error 1480: Only PARTITIONING can use VALUES in partition definition
            • Error 1481: MAXVALUE can only be used in last partition definition
            • Error 1482: Subpartitions can only be hash partitions and by key
            • Error 1483: Must define subpartitions on all partitions if on one partition
            • Error 1484: Wrong number of partitions defined, mismatch with previous setting
            • Error 1485: Wrong number of subpartitions defined, mismatch with previous setting
            • Error 1486: Constant/Random expression in (sub)partitioning function is not allowed
            • Error 1487: Expression in RANGE/LIST VALUES must be constant
            • Error 1488: Field in list of fields for partition function not found in table
            • Error 1489: List of fields is only allowed in KEY partitions
            • Error 1490: The partition info in the frm file is not consistent with what can be written into the f
            • Error 1491: The function returns the wrong type
            • Error 1492: For partitions each partition must be defined
            • Error 1493: VALUES LESS THAN value must be strictly increasing for each partition
            • Error 1494: VALUES value must be of same type as partition function
            • Error 1495: Multiple definition of same constant in list partitioning
            • Error 1496: Partitioning can not be used stand-alone in query
            • Error 1497: The mix of handlers in the partitions is not allowed in this version of MariaDB
            • Error 1498: For the partitioned engine it is necessary to define all
            • Error 1499: Too many partitions (including subpartitions) were defined
          • MariaDB Error Codes 1500 to 1599
            • Error 1500: It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpar
            • Error 1501: Failed to create specific handler file
            • Error 1502: A BLOB field is not allowed in partition function
            • Error 1503: must include all columns in the table's partitioning function
            • Error 1504: Number of = 0 is not an allowed value
            • Error 1505: Partition management on a not partitioned table is not possible
            • Error 1506: Foreign key clause is not yet supported in conjunction with partitioning
            • Error 1507: Error in list of partitions to
            • Error 1508: Cannot remove all partitions, use DROP TABLE instead
            • Error 1509: COALESCE PARTITION can only be used on HASH/KEY partitions
            • Error 1510: REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbe
            • Error 1511: REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables usin
            • Error 1512: PARTITION can only be used on RANGE/LIST partitions
            • Error 1513: Trying to Add partition(s) with wrong number of subpartitions
            • Error 1514: At least one partition must be added
            • Error 1515: At least one partition must be coalesced
            • Error 1516: More partitions to reorganize than there are partitions
            • Error 1517: Duplicate partition name
            • Error 1518: It is not allowed to shut off binlog on this command
            • Error 1519: When reorganizing a set of partitions they must be in consecutive order
            • Error 1520: Reorganize of range partitions cannot change total ranges except for last partition wher
            • Error 1521: Partition function not supported in this version for this handler
            • Error 1522: Partition state cannot be defined from CREATE/ALTER TABLE
            • Error 1523: The handler only supports 32 bit integers in VALUES
            • Error 1524: Plugin is not loaded
            • Error 1525: Incorrect value
            • Error 1526: Table has no partition for value
            • Error 1527: It is not allowed to specify more than once
            • Error 1528: Failed to create
            • Error 1529: Failed to drop
            • Error 1530: The handler doesn't support autoextend of tablespaces
            • Error 1531: A size parameter was incorrectly specified, either number or on the form 10M
            • Error 1532: The size number was correct but we don't allow the digit part to be more than 2 billion
            • Error 1533: Failed to alter
            • Error 1534: Writing one row to the row-based binary log failed
            • Error 1535: Table definition on master and slave does not match
            • Error 1536: Slave running with --log-slave-updates must use row-based binary logging to be able to r
            • Error 1537: Event already exists
            • Error 1538: Failed to store event. Error code from storage engine.
            • Error 1539: Unknown event
            • Error 1540: Failed to alter event
            • Error 1541: Failed to drop
            • Error 1542: INTERVAL is either not positive or too big
            • Error 1543: ENDS is either invalid or before STARTS
            • Error 1544: Event execution time is in the past. Event has been disabled
            • Error 1545: Failed to open mysql.event
            • Error 1546: No datetime expression provided
            • Error 1547: Column count is wrong. Expected found. The table is probably corrupted
            • Error 1548: Cannot load from mysql. The table is probably corrupted
            • Error 1549: Failed to delete the event from mysql.event
            • Error 1550: Error during compilation of event's body
            • Error 1551: Same old and new event name
            • Error 1552: Data for column too long
            • Error 1553: Cannot drop index needed in a foreign key constraint
            • Error 1554: The syntax is deprecated and will be removed in MariaDB
            • Error 1555: You can't write-lock a log table. Only read access is possible
            • Error 1556: You can't use locks with log tables
            • Error 1557: Upholding foreign key constraints for table, entry, key would lead to a duplicate entry
            • Error 1558: Column count is wrong. Expected found. Created with MariaDB now running. Please use mysq
            • Error 1559: Cannot switch out of the row-based binary log format when the session has open temporary
            • Error 1560: Cannot change the binary logging format inside a stored function or trigger
            • Error 1561: You should never see it
            • Error 1562: Cannot create temporary table with partitions
            • Error 1563: Partition constant is out of partition function domain
            • Error 1564: This partition function is not allowed
            • Error 1565: Error in DDL log
            • Error 1566: Not allowed to use NULL value in VALUES LESS THAN
            • Error 1567: Incorrect partition name
            • Error 1568: Transaction isolation level can't be changed while a transaction is in progress
            • Error 1569: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry for key
            • Error 1570: Internal scheduler error
            • Error 1571: Error during starting/stopping of the scheduler
            • Error 1572: Engine cannot be used in partitioned tables
            • Error 1573: Cannot activate log
            • Error 1574: The server was not built with row-based replication
            • Error 1575: Decoding of base64 string failed
            • Error 1576: Recursion of EVENT DDL statements is forbidden when body is present
            • Error 1577: Cannot proceed because system tables used by Event Scheduler were found damaged at serve
            • Error 1578: Only integers allowed as number here
            • Error 1579: This storage engine cannot be used for log tables
            • Error 1580: You cannot '%s' a log table if logging is enabled
            • Error 1581: Cannot rename. When logging enabled, rename to/from log table must rename two tables
            • Error 1582: Incorrect parameter count in the call to native function
            • Error 1583: Incorrect parameters in the call to native function
            • Error 1584: Incorrect parameters in the call to stored function
            • Error 1585: This function has the same name as a native function
            • Error 1586: Duplicate entry for key
            • Error 1587: Too many files opened, please execute the command again
            • Error 1588: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set
            • Error 1589: Event execution time is in the past and ON COMPLETION NOT PRESERVE is set
            • Error 1590: The incident occured on the master
            • Error 1591: Table has no partition for some existing values
            • Error 1592: Unsafe statement written to the binary log using statement format since BINLOG_FORMAT =
            • Error 1593: Fatal error
            • Error 1594: Relay log read failure
            • Error 1595: Relay log write failure
            • Error 1596: Failed to create
            • Error 1597: Master command failed
            • Error 1598: Binary logging not possible
            • Error 1599: View has no creation context
          • MariaDB Error Codes 1600 to 1699
            • Error 1600: Creation context of view is invalid
            • Error 1601: Creation context of stored routine is invalid
            • Error 1602: Corrupted TRG file for table
            • Error 1603: Triggers for table have no creation context
            • Error 1604: Trigger creation context of table is invalid
            • Error 1605: Creation context of event is invalid
            • Error 1606: Cannot open table for trigger
            • Error 1607: Cannot create stored routine. Check warnings
            • Error 1608: You should never see it
            • Error 1609: The BINLOG statement of type was not preceded by a format description BINLOG statement.
            • Error 1610: Corrupted replication event was detected
            • Error 1611: Invalid column reference in LOAD DATA
            • Error 1612: Being purged log was not found
            • Error 1613: XA_RBTIMEOUT: Transaction branch was rolled back: took too long
            • Error 1614: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
            • Error 1615: Prepared statement needs to be re-prepared
            • Error 1616: DELAYED option not supported for table
            • Error 1617: The master info structure does not exist
            • Error 1618: option ignored
            • Error 1619: Built-in plugins cannot be deleted
            • Error 1620: Plugin is busy and will be uninstalled on shutdown
            • Error 1621: variable is read-only. Use SET to assign the value
            • Error 1622: Storage engine does not support rollback for this statement
            • Error 1623: Unexpected master's heartbeat data
            • Error 1624: The requested value for the heartbeat period is either negative or exceeds the maximum a
            • Error 1625: You should never see it
            • Error 1626: Error in parsing conflict function
            • Error 1627: Write to exceptions table failed
            • Error 1628: Comment for table is too long
            • Error 1629: Comment for field is too long
            • Error 1630: FUNCTION does not exist. Check the 'Function Name Parsing and Resolution' section in the
            • Error 1631: Database
            • Error 1632: Table
            • Error 1633: Partition
            • Error 1634: Subpartition
            • Error 1635: Temporary
            • Error 1636: Renamed
            • Error 1637: Too many active concurrent transactions
            • Error 1638: Non-ASCII separator arguments are not fully supported
            • Error 1639: debug sync point wait timed out
            • Error 1640: debug sync point hit limit reached
            • Error 1641: Duplicate condition information item
            • Error 1642: Unhandled user-defined warning condition
            • Error 1643: Unhandled user-defined not found condition
            • Error 1644: Unhandled user-defined exception condition
            • Error 1645: RESIGNAL when handler not active
            • Error 1646: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE
            • Error 1647: Data truncated for condition item
            • Error 1648: Data too long for condition item
            • Error 1649: Unknown locale
            • Error 1650: The requested server id clashes with the slave startup option --replicate-same-server-id
            • Error 1651: Query cache is disabled; restart the server with query_cache_type=1 to enable it
            • Error 1652: Duplicate partition field name
            • Error 1653: Inconsistency in usage of column lists for partitioning
            • Error 1654: Partition column values of incorrect type
            • Error 1655: Too many fields
            • Error 1656: Cannot use MAXVALUE as value in VALUES IN
            • Error 1657: Cannot have more than one value for this type of partitioning
            • Error 1658: Row expressions in VALUES IN only allowed for multi-field column partitioning
            • Error 1659: Field is of a not allowed type for this type of partitioning
            • Error 1660: The total length of the partitioning fields is too large
            • Error 1661: Cannot execute statement: impossible to write to binary log since both row-incapable eng
            • Error 1662: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW an
            • Error 1663: Cannot execute statement: impossible to write to binary log since statement is unsafe, s
            • Error 1664: Cannot execute statement: impossible to write to binary log since statement is in row fo
            • Error 1665: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEM
            • Error 1666: Cannot execute statement: impossible to write to binary log since statement is in row fo
            • Error 1667: Cannot execute statement: impossible to write to binary log since more than one engine i
            • Error 1668: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set o
            • Error 1669: The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times
            • Error 1670: The statement is unsafe because it uses the general log, slow query log, or performance_
            • Error 1671: Statement is unsafe because it invokes a trigger or a stored function that inserts into
            • Error 1672: Statement is unsafe because it uses a UDF which may not return the same value on the sla
            • Error 1673: Statement is unsafe because it uses a system variable that may have a different value on
            • Error 1674: Statement is unsafe because it uses a system function that may return a different value
            • Error 1675: Statement is unsafe because it accesses a non-transactional table after accessing a tran
            • Error 1676: Statement
            • Error 1677: Column of table cannot be converted from type to type
            • Error 1678: Can't create conversion table for table
            • Error 1679: Cannot modify @@session.binlog_format inside a transaction
            • Error 1680: The path specified is too long
            • Error 1681: is deprecated and will be removed in a future release.
            • Error 1682: Native table has the wrong structure
            • Error 1683: Invalid performance_schema usage
            • Error 1684: Table was skipped since its definition is being modified by concurrent DDL statement
            • Error 1685: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction
            • Error 1686: Cannot change the binlog direct flag inside a stored function or trigger
            • Error 1687: A SPATIAL index may only contain a geometrical type column
            • Error 1688: Comment for index is too long
            • Error 1689: Wait on a lock was aborted due to a pending exclusive lock
            • Error 1690: value is out of range in
            • Error 1691: A variable of a non-integer based type in LIMIT clause
            • Error 1692: Mixing self-logging and non-self-logging engines in a statement is unsafe.
            • Error 1693: Statement accesses nontransactional table as well as transactional or temporary table, a
            • Error 1694: Cannot modify @@session.sql_log_bin inside a transaction
            • Error 1695: Cannot change the sql_log_bin inside a stored function or trigger
            • Error 1696: Failed to read from the .par file
            • Error 1697: VALUES value for partition must have type INT
            • Error 1698: Access denied for user
            • Error 1699: SET PASSWORD has no significance for users authenticating via plugins
          • MariaDB Error Codes 1700 to 1799
            • Error 1700: GRANT with IDENTIFIED WITH is illegal because the user already exists
            • Error 1701: Cannot truncate a table referenced in a foreign key constraint
            • Error 1702: Plugin is force_plus_permanent and can not be unloaded
            • Error 1703: The requested value for the heartbeat period is less than 1 millisecond
            • Error 1704: The requested value for the heartbeat period exceeds the value of slave_net_timeout seco
            • Error 1705: Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; i
            • Error 1706: Primary key/partition key update is not allowed since the table is updated both as and
            • Error 1707: Table rebuild required. Please do "ALTER TABLE FORCE" or dump/reload to fix it!
            • Error 1708: The value of should be no less than the value of
            • Error 1709: Index column size too large. The maximum column size is bytes.
            • Error 1710: Trigger has an error in its body
            • Error 1711: Unknown trigger has an error in its body
            • Error 1712: Index is corrupted
            • Error 1713: Undo log record is too big
            • Error 1714: INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the S
            • Error 1715: INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows ar
            • Error 1716: REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT
            • Error 1717: CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the S
            • Error 1718: CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the
            • Error 1719: UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if
            • Error 1720: You should never see it
            • Error 1721: You should never see it
            • Error 1722: Statements writing to a table with an auto-increment column after selecting from another
            • Error 1723: CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the
            • Error 1724: INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe
            • Error 1725: Table is being used in foreign key check.
            • Error 1726: Storage engine does not support system tables
            • Error 1727: INSERT into autoincrement field which is not the first part in the composed primary key
            • Error 1728: Cannot load from. The table is probably corrupted
            • Error 1729: The requested value for the master delay exceeds the maximum
            • Error 1730: Only Format_description_log_event and row events are allowed in BINLOG statements
            • Error 1731: Non matching attribute between partition and table
            • Error 1732: Table to exchange with partition is partitioned
            • Error 1733: Table to exchange with partition is temporary
            • Error 1734: Subpartitioned table, use subpartition instead of partition
            • Error 1735: Unknown partition in table
            • Error 1736: Tables have different definitions
            • Error 1737: Found a row that does not match the partition
            • Error 1738: Option binlog_cache_size is greater than max_binlog_cache_size; setting binlog_cache_siz
            • Error 1739: Cannot use access on index due to type or collation conversion on field
            • Error 1740: Table to exchange with partition has foreign key references
            • Error 1741: Key value was not found in table
            • Error 1742: Data for column too long
            • Error 1743: Replication event checksum verification failed while reading from network.
            • Error 1744: Replication event checksum verification failed while reading from a log file
            • Error 1745: Option binlog_stmt_cache_size is greater than max_binlog_stmt_cache_size
            • Error 1746: Can't update table while is being created
            • Error 1747: PARTITION () clause on non partitioned table
            • Error 1748: Found a row not matching the given partition set
            • Error 1749: partition doesn't exist
            • Error 1750: Failure while changing the type of replication repository
            • Error 1751: The creation of some temporary tables could not be rolled back.
            • Error 1752: Some temporary tables were dropped, but these operations could not be rolled back.
            • Error 1753: is not supported in multi-threaded slave mode
            • Error 1754: The number of modified databases exceeds the maximum
            • Error 1755: Cannot execute the current event group in the parallel mode
            • Error 1756: %s
            • Error 1757: FULLTEXT index is not supported for partitioned tables
            • Error 1758: Invalid condition number
            • Error 1759: Sending passwords in plain text without SSL/TLS is extremely insecure
            • Error 1760: Storing MariaDB user name or password information in the master.info repository is not s
            • Error 1761: Foreign key constraint for table, record would lead to a duplicate entry in table
            • Error 1762: Foreign key constraint for table, record would lead to a duplicate entry in a child tabl
            • Error 1763: Setting authentication options is not possible when only the Slave SQL Thread is being s
            • Error 1764: The table does not have FULLTEXT index to support this query
            • Error 1765: The system variable cannot be set in stored functions or triggers
            • Error 1766: The system variable cannot be set when there is an ongoing transaction
            • Error 1767: The system variable @@SESSION.GTID_NEXT has the value which is not listed in @@SESSION.G
            • Error 1768: The system variable @@SESSION.GTID_NEXT cannot change inside a transaction
            • Error 1769: The statement 'SET' cannot invoke a stored function
            • Error 1770: The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_L
            • Error 1771: Skipping transaction because it has already been executed and logged
            • Error 1772: Malformed GTID set specification
            • Error 1773: Malformed GTID set encoding
            • Error 1774: Malformed GTID specification
            • Error 1775: Impossible to generate Global Transaction Identifier: the integer component reached the
            • Error 1776: Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be s
            • Error 1777: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE =
            • Error 1778: Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_
            • Error 1779: GTID_MODE = ON or GTID_MODE = UPGRADE_STEP_2 requires DISABLE_GTID_UNSAFE_STATEMENTS = 1
            • Error 1780: @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log
            • Error 1781: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF
            • Error 1782: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON
            • Error 1783: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF
            • Error 1784: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF
            • Error 1785: When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only
            • Error 1786: CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1
            • Error 1787: When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DR
            • Error 1788: The value of @@GLOBAL.GTID_MODE can only change one step at a time
            • Error 1789: The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master
            • Error 1790: @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID
            • Error 1791: Unknown EXPLAIN format name
            • Error 1792: Cannot execute statement in a READ ONLY transaction
            • Error 1793: Comment for table partition is too long
            • Error 1794: Slave is not configured or failed to initialize properly. You must at least set --server
            • Error 1795: InnoDB presently supports one FULLTEXT index creation at a time
            • Error 1796: Cannot create FULLTEXT index on temporary InnoDB table
            • Error 1797: Column is of wrong type for an InnoDB FULLTEXT index
            • Error 1798: Index '%s' is of wrong type for an InnoDB FULLTEXT index
            • Error 1799: Creating index required more than 'innodb_online_alter_log_max_size' bytes of modificati
          • MariaDB Error Codes 1800 to 1899
            • Error 1800: Unknown ALGORITHM
            • Error 1801: Unknown LOCK type
            • Error 1802: CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in M
            • Error 1803: Cannot recover after SLAVE errored out in parallel execution mode
            • Error 1804: Cannot clean up worker info tables
            • Error 1805: Column count of is wrong. Expected, found. The table is probably corrupted
            • Error 1806: Slave must silently retry current transaction
            • Error 1807: There is a foreign key check running on table
            • Error 1808: Schema mismatch
            • Error 1809: Table in system tablespace
            • Error 1810: IO Read error
            • Error 1811: IO Write error
            • Error 1812: Tablespace is missing for table
            • Error 1813: Tablespace for table exists. Please DISCARD the tablespace before IMPORT
            • Error 1814: Tablespace has been discarded for table
            • Error 1815: Internal error
            • Error 1816: ALTER TABLE IMPORT TABLESPACE failed with error
            • Error 1817: Index corrupt
            • Error 1818: YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.
            • Error 1819: Your password does not satisfy the current policy requirements
            • Error 1820: You must SET PASSWORD before executing this statement
            • Error 1821: Failed to add the foreign key constaint. Missing index for constraint in the foreign tab
            • Error 1822: Failed to add the foreign key constaint. Missing index for constraint in the referenced
            • Error 1823: Failed to add the foreign key constraint to system tables
            • Error 1824: Failed to open the referenced table
            • Error 1825: Failed to add the foreign key constraint on table. Incorrect options in FOREIGN KEY cons
            • Error 1826: Duplicate foreign key constraint name
            • Error 1827: The password hash doesn't have the expected format
            • Error 1828: Cannot drop column: needed in a foreign key constraint
            • Error 1829: Cannot drop column: needed in a foreign key constraint of table
            • Error 1831: Duplicate index defined on the table. This is deprecated and will be disallowed in a fut
            • Error 1832: Cannot change column: used in a foreign key constraint
            • Error 1833: Cannot change column: used in a foreign key constraint of table
            • Error 1834: Cannot delete rows from table which is parent in a foreign key constraint of table
            • Error 1835: Malformed communication packet.
            • Error 1836: Running in read-only mode
            • Error 1837: When GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLL
            • Error 1838: The system variable cannot be set in stored procedures
            • Error 1839: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON
            • Error 1840: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty
            • Error 1842: @@GLOBAL.GTID_PURGED was changed from to
            • Error 1843: @@GLOBAL.GTID_EXECUTED was changed from to
            • Error 1844: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEM
            • Error 1845: is not supported for this operation. Try
            • Error 1846: is not supported. Reason: Try
            • Error 1847: COPY algorithm requires a lock
            • Error 1848: Partition specific operations do not yet support LOCK/ALGORITHM
            • Error 1849: Columns participating in a foreign key are renamed
            • Error 1850: Cannot change column type INPLACE
            • Error 1851: Adding foreign keys needs foreign_key_checks=OFF
            • Error 1852: Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows
            • Error 1853: Dropping a primary key is not allowed without also adding a new primary key
            • Error 1854: Adding an auto-increment column requires a lock
            • Error 1855: Cannot replace hidden FTS_DOC_ID with a user-visible one
            • Error 1856: Cannot drop or rename FTS_DOC_ID
            • Error 1857: Fulltext index creation requires a lock
            • Error 1858: sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE
            • Error 1859: Duplicate entry for key
            • Error 1860: Long database name and identifier for object resulted in path length exceeding character
            • Error 1861: cannot silently convert NULL values, as required in this SQL_MODE
            • Error 1862: Your password has expired. To log in you must change it using a client that supports exp
            • Error 1863: Found a row in wrong partition
            • Error 1864: Cannot schedule event, relay-log name, position to Worker thread because its size exceed
            • Error 1865: Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table
            • Error 1866: The binary log file is logically corrupted
            • Error 1867: file was not purged because it was being read by thread(s), purged only out of
            • Error 1868: file was not purged because it is the active log file
            • Error 1869: Auto-increment value in UPDATE conflicts with internally generated values
            • Error 1870: Row events are not logged for statements that modify BLACKHOLE tables in row format
            • Error 1871: Slave failed to initialize master info structure from the repository
            • Error 1872: Slave failed to initialize relay log info structure from the repository
            • Error 1873: Access denied trying to change to user (using password). Disconnecting.
            • Error 1874: InnoDB is in read only mode
            • Error 1875: STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal
            • Error 1876: STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal
            • Error 1877: Operation cannot be performed. The table is missing, corrupt or contains bad data
            • Error 1878: Temporary file write failure
            • Error 1879: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuil
            • Error 1880: "
            • Error 1830: Column cannot be NOT NULL: needed in a foreign key constraint SET NULL
            • Error 1841: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in
          • MariaDB Error Codes 1900 to 1999
            • Error 1900: "
            • Error 1901: Function or expression cannot be used in the clause of
            • Error 1902: "
            • Error 1903: Primary key cannot be defined upon a generated column
            • Error 1904: Key/Index cannot be defined on a virtual generated column
            • Error 1905: Cannot define foreign key with clause on a generated column
            • Error 1906: The value specified for generated column in table has been ignored
            • Error 1907: This is not yet supported for generated columns
            • Error 1908: "
            • Error 1909: "
            • Error 1910: storage engine does not support generated columns
            • Error 1911: Unknown option
            • Error 1912: Incorrect value for option
            • Error 1913: You should never see it
            • Error 1914: You should never see it
            • Error 1915: You should never see it
            • Error 1916: Got overflow when converting to. Value truncated
            • Error 1917: Truncated value when converting to
            • Error 1918: Encountered illegal value when converting to
            • Error 1919: Encountered illegal format of dynamic column string
            • Error 1920: Dynamic column implementation limit reached
            • Error 1921: Illegal value used as argument of dynamic column function
            • Error 1922: Dynamic column contains unknown character set
            • Error 1923: At least one of the 'in_to_exists' or 'materialization' optimizer_switch flags must be '
            • Error 1924: Query cache is disabled (resize or similar command in progress); repeat this command lat
            • Error 1925: Query cache is globally disabled and you can't enable it only for this session
            • Error 1926: View ORDER BY clause ignored because there is other ORDER BY clause already
            • Error 1927: Connection was killed
            • Error 1928: You should never see it
            • Error 1929: Cannot modify @@session.skip_replication inside a transaction
            • Error 1930: Cannot modify @@session.skip_replication inside a stored function or trigger
            • Error 1931: Query execution was interrupted. The query exceeded. The query result may be incomplete
            • Error 1932: Table doesn't exist in engine
            • Error 1933: Target is not running an EXPLAINable command
            • Error 1934: Connection conflicts with existing connection
            • Error 1935: Master
            • Error 1936: Can't %s SLAVE
            • Error 1937: SLAVE started
            • Error 1938: SLAVE stopped
            • Error 1939: Engine failed to discover table with
            • Error 1940: Failed initializing replication GTID state
            • Error 1941: Could not parse GTID list
            • Error 1942: Could not update replication slave gtid state
            • Error 1943: GTID conflict (duplicate domain id)
            • Error 1944: Failed to open
            • Error 1945: Connecting slave requested to start from GTID, which is not in the master's binlog
            • Error 1946: Failed to load replication slave GTID position from table
            • Error 1947: Specified GTID conflicts with the binary log which contains a more recent GTID
            • Error 1948: Specified value for @@gtid_slave_pos contains no value for replication domain
            • Error 1949: START SLAVE UNTIL master_gtid_pos requires that slave is using GTID
            • Error 1950: An attempt was made to binlog GTID which would create an out-of-order sequence number wi
            • Error 1951: The binlog on the master is missing the GTID requested by the slave
            • Error 1952: Unexpected GTID received from master after reconnect
            • Error 1953: Cannot modify @@session.gtid_domain_id or @@session.gtid_seq_no inside a transaction
            • Error 1954: Cannot modify @@session.gtid_domain_id or @@session.gtid_seq_no inside a stored function
            • Error 1955: Connecting slave requested to start from GTID which is not in the master's binlog
            • Error 1956: This operation is not allowed if any GTID has been logged to the binary log
            • Error 1957: Unknown query id
            • Error 1958: Bad base64 data as position
            • Error 1959: Invalid role specification
            • Error 1960: The current user is invalid
            • Error 1961: Cannot grant role to
            • Error 1962: Cannot revoke role from
            • Error 1963: Cannot change @@slave_parallel_threads while another change is in progress
            • Error 1964: Commit failed due to failure of an earlier commit on which this one depends
            • Error 1965: is a view
            • Error 1966: When using GTID, @@sql_slave_skip_counter can not be used
            • Error 1967: The definition for table is too big
            • Error 1968: Plugin already installed
            • Error 1969: Query execution was interrupted (max_statement_time exceeded)
            • Error 1970: does not support subqueries or stored functions
            • Error 1971: The system variable cannot be set in SET STATEMENT
            • Error 1972: You should never see it
            • Error 1973: Can't create user; it already exists
            • Error 1974: Can't drop user; it doesn't exist
            • Error 1975: Can't create role; it already exists
            • Error 1976: Can't drop role; it doesn't exist
            • Error 1977: Cannot convert character to
            • Error 1978: Incorrect default value for column
            • Error 1979: You are not owner of query
            • Error 1980: Engine-independent statistics are not collected for column
            • Error 1981: Aggregate function of SELECT belongs to SELECT
            • Error 1982: option ignored for InnoDB partition
          • MariaDB Error Codes 3000 to 3099
            • Error 3000: File is corrupted
            • Error 3001: Query partially completed on the master (error on master) and was aborted
            • Error 3002: Query caused different errors on master and slave
            • Error 3003: Storage engine for table is not loaded
            • Error 3004: GET STACKED DIAGNOSTICS when handler not active
            • Error 3005: is no longer supported. The statement was converted to
            • Error 3006: Statement is unsafe because it uses a fulltext parser plugin which may not return the sa
            • Error 3007: Cannot DISCARD/IMPORT tablespace associated with temporary table
            • Error 3008: Foreign key cascade delete/update exceeds max depth of
            • Error 3009: Column count of is wrong
            • Error 3010: Trigger does not have CREATED attribute
            • Error 3011: Referenced trigger for the given action time and event type does not exist
            • Error 3012: EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE
            • Error 3013: Invalid size for column
            • Error 3014: Table storage engine found required create option missing
            • Error 3015: Out of memory in storage engine
            • Error 3016: The password for anonymous user cannot be expired
            • Error 3017: This operation cannot be performed with a running slave sql thread
            • Error 3018: Cannot create FULLTEXT index on materialized subquery
            • Error 3019: Undo Log error
            • Error 3020: Invalid argument for logarithm
            • Error 3021: This operation cannot be performed with a running slave io thread
            • Error 3022: This operation may not be safe when the slave has temporary tables
            • Error 3023: CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be s
            • Error 3024: Query execution was interrupted, maximum statement execution time exceeded
            • Error 3025: Select is not a read only statement, disabling timer
            • Error 3026: Duplicate entry
            • Error 3027: mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.
            • Error 3028: Expression of ORDER BY contains aggregate function and applies to a UNION
            • Error 3029: Expression of ORDER BY contains aggregate function and applies to the result of a non-ag
            • Error 3030: Slave worker has stopped after at least one previous worker encountered an error when sl
            • Error 3031: slave_preserve_commit_order is not supported
            • Error 3032: The server is currently in offline mode
            • Error 3033: Binary geometry function given two geometries of different srids
            • Error 3034: Calling geometry function with unsupported types of arguments
            • Error 3035: Unknown GIS error occurred in function
            • Error 3036: Unknown exception caught in GIS function
            • Error 3037: Invalid GIS data provided to function
            • Error 3038: The geometry has no data in function
            • Error 3039: Unable to calculate centroid because geometry is empty in function
            • Error 3040: Geometry overlay calculation error: geometry data is invalid in function
            • Error 3041: Geometry turn info calculation error: geometry data is invalid in function
            • Error 3042: Analysis procedures of intersection points interrupted unexpectedly in function
            • Error 3043: Unknown exception thrown in function
            • Error 3044: Memory allocation error
            • Error 3045: Domain error
            • Error 3046: Length error
            • Error 3047: Invalid argument error
            • Error 3048: Out of range error
            • Error 3049: Overflow error error
            • Error 3050: Range error
            • Error 3051: Underflow error
            • Error 3052: Logic error
            • Error 3053: Runtime error
            • Error 3054: Unknown exception
            • Error 3055: Geometry byte string must be little endian
            • Error 3056: The password provided for the replication user exceeds the maximum length of 32 characte
            • Error 3057: Incorrect user-level lock name
            • Error 3058: Deadlock found when trying to get user-level lock
            • Error 3059: REPLACE cannot be executed as it requires deleting rows that are not in the view
            • Error 3060: Do not support online operation on table with GIS index
          • MariaDB Error Codes 4000 to 4099
            • Error 4000: COM_MULTI can't return a result set in the given context
            • Error 4001: Command is not allowed for COM_MULTI
            • Error 4002: WITH column list and SELECT field list have different column counts
            • Error 4003: Too many WITH elements in WITH clause
            • Error 4004: Duplicate query name in WITH clause
            • Error 4005: No anchors for recursive WITH element
            • Error 4006: Unacceptable mutual recursion with anchored table
            • Error 4007: Reference to recursive WITH table in materialized derived
            • Error 4008: Restrictions imposed on recursive definitions are violated for table
            • Error 4009: Window specification with name is not defined
            • Error 4010: Multiple window specifications with the same name
            • Error 4011: Window specification referencing another one cannot contain partition list
            • Error 4012: Referenced window specification already contains order list
            • Error 4013: Referenced window specification cannot contain window frame
            • Error 4014: Unacceptable combination of window frame bound specifications
            • Error 4015: Window function is allowed only in SELECT list and ORDER BY clause
            • Error 4016: Window function is not allowed in window specification
            • Error 4017: Window frame is not allowed with
            • Error 4018: No order list in window specification for
            • Error 4019: RANGE-type frame requires ORDER BY clause with single sort key
            • Error 4020: Integer is required for ROWS-type frame
            • Error 4021: Numeric datatype is required for RANGE-type frame
            • Error 4022: Frame exclusion is not supported yet
            • Error 4023: This window function may not have a window frame
            • Error 4024: Argument of NTILE must be greater than 0
            • Error 4025: CONSTRAINT failed for
            • Error 4026: Expression in the clause is too big
            • Error 4027: Got an error evaluating stored expression
            • Error 4028: Got an error when calculating default value for
            • Error 4029: Expression for field is referring to uninitialized field
            • Error 4030: Only one DEFAULT partition allowed
            • Error 4031: Referenced trigger for the given action time and event type does not exist
            • Error 4032: Default/ignore value is not supported for such parameter usage
            • Error 4033: Only row based replication supported for bulk operations
            • Error 4034: Uncompress the compressed binlog failed
            • Error 4035: Broken JSON string in argument to function at position
            • Error 4036: Character disallowed in JSON in argument to function at position
            • Error 4037: Unexpected end of JSON text in argument to function
            • Error 4038: Syntax error in JSON text in argument to function at position
            • Error 4039: Incorrect escaping in JSON text in argument to function at position
            • Error 4040: Limit on JSON nested strucures depth is reached in argument to function at position
            • Error 4041: Unexpected end of JSON path in argument to function
            • Error 4042: Syntax error in JSON path in argument to function at position
            • Error 4043: Limit on JSON path depth is reached in argument to function at position
            • Error 4044: Wildcards in JSON path not allowed in argument to function
            • Error 4045: JSON path should end with an array identifier in argument to function
            • Error 4046: Argument 2 to function must be "one" or "all".
            • Error 4047: CREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.
            • Error 4048: Incorrect GeoJSON format specified for st_geomfromgeojson function
            • Error 4049: Incorrect GeoJSON format - too few points for linestring specified
            • Error 4050: Incorrect GeoJSON format - polygon not closed
            • Error 4051: Path expression '$' is not allowed in argument to function
            • Error 4052: A slave with the same server_uuid/server_id as this slave has connected to the master
            • Error 4053: Flashback does not support
            • Error 4054: Keys are out order during bulk load
            • Error 4055: Bulk load rows overlap existing rows
            • Error 4056: Can't execute updates on master with binlog_format != ROW
            • Error 4057: MyRocks supports only READ COMMITTED and REPEATABLE READ isolation levels
            • Error 4058: When unique checking is disabled in MyRocks, INSERT,UPDATE,LOAD statements with clauses
            • Error 4059: Can't execute updates when you started a transaction with START TRANSACTION WITH CONSIST
            • Error 4060: This transaction was rolled back and cannot be committed. Only supported operation is to
            • Error 4061: MyRocks currently does not support ROLLBACK TO SAVEPOINT if modifying rows
            • Error 4062: Only REPEATABLE READ isolation level is supported for START TRANSACTION WITH CONSISTENT
            • Error 4063: Unsupported collation on string indexed column
            • Error 4064: Table '%s' does not exist, but metadata information exists inside MyRocks. This is a sig
            • Error 4065: Column family flag is different from an existing flag
            • Error 4066: TTL duration in MyRocks must be an unsigned non-null 64-bit integer
            • Error 4067: Status error received from RocksDB
            • Error 4068: Status error received from RocksDB
            • Error 4069: TTL support is currently disabled when table has a hidden PK
            • Error 4070: TTL column in MyRocks must be an unsigned non-null 64-bit integer, exist inside the tabl
            • Error 4071: The per-index column family option has been deprecated
            • Error 4072: MyRocks failed creating new key definitions during alter
            • Error 4073: MyRocks failed populating secondary key during alter
            • Error 4074: Window functions can not be used as arguments to group functions
            • Error 4075: OK packet too large
            • Error 4076: Incorrect GeoJSON format - empty 'coordinates' array
            • Error 4077: MyRocks doesn't currently support collations with "No pad" attribute
            • Error 4078: Illegal parameter data types for operation
            • Error 4079: Illegal parameter data type for operation
            • Error 4080: Incorrect parameter count to cursor
            • Error 4081: Unknown structured system variable or ROW routine variable
            • Error 4082: Row variable does not have a field
            • Error 4083: END identifier does not match
            • Error 4084: Sequence has run out
            • Error 4085: Sequence values are conflicting
            • Error 4086: Sequence table structure is invalid
            • Error 4087: Sequence access error
            • Error 4088: Sequences requires binlog_format mixed or row
            • Error 4089: is not a SEQUENCE
            • Error 4090: is not a SEQUENCE
            • Error 4091: Unknown SEQUENCE
            • Error 4092: Unknown VIEW
            • Error 4093: Wrong INSERT into a SEQUENCE. One can only do single table INSERT into a sequence object
            • Error 4094: At line in
            • Error 4095: Subroutine is declared in the package specification but is not defined in the package bo
            • Error 4096: Subroutine has a forward declaration but is not defined
            • Error 4097: Compressed column can't be used in key specification
            • Error 4098: Unknown compression method
            • Error 4099: The used table value constructor has a different number of values
          • MariaDB Error Codes 4100 to 4199
            • Error 4100: Field reference can't be used in table value constructor
            • Error 4101: Numeric datatype is required for function
            • Error 4102: Argument to the function is not a constant for a partition
            • Error 4103: Argument to the function does not belong to the range [0,1]
            • Error 4104: function only accepts arguments that can be converted to numerical types
            • Error 4105: Aggregate specific instruction (FETCH GROUP NEXT ROW) used in a wrong context
            • Error 4106: Aggregate specific instruction(FETCH GROUP NEXT ROW) missing from the aggregate function
            • Error 4107: Limit only accepts integer values
            • Error 4108: Invisible column must have a default value
            • Error 4109: Rows matched: Changed: Inserted: Warnings:
            • Error 4110: must be of type for system-versioned table
            • Error 4111: Transaction-precise system versioning for is not supported
            • Error 4112: You should never see it
            • Error 4113: Wrong partitioning type, expected type
            • Error 4114: Versioned table last HISTORY partition is out of, need more HISTORY partitions
            • Error 4115: Maybe missing parameters
            • Error 4116: Can only drop oldest partitions when rotating by INTERVAL
            • Error 4117: You should never see it
            • Error 4118: Partition contains non-historical data
            • Error 4119: Not allowed for system-versioned. Change @@system_versioning_alter_history to proceed wi
            • Error 4120: Not allowed for system-versioned. Change to/from native system versioning engine is not
            • Error 4121: SYSTEM_TIME range selector is not allowed
            • Error 4122: Conflicting FOR SYSTEM_TIME clauses in WITH RECURSIVE
            • Error 4123: Table must have at least one versioned column
            • Error 4124: Table is not system-versioned
            • Error 4125: Wrong parameters for: missing
            • Error 4126: PERIOD FOR SYSTEM_TIME must use columns
            • Error 4127: Wrong parameters for partitioned: wrong value for
            • Error 4128: Wrong partitions for: must have at least one HISTORY and exactly one last CURRENT
            • Error 4129: TRX_ID not found in mysql.transaction_registry
            • Error 4130: Can not change system versioning field
            • Error 4131: Can not DROP SYSTEM VERSIONING for table partitioned BY SYSTEM_TIME
            • Error 4132: System-versioned tables in the database are not supported
            • Error 4133: Transaction registry is disabled
            • Error 4134: Duplicate ROW column
            • Error 4135: Table is already system-versioned
            • Error 4136: You should never see it
            • Error 4137: System-versioned tables do not support
            • Error 4138: Transaction-precise system-versioned tables do not support partitioning by ROW START or
            • Error 4139: The index file for table is full
            • Error 4140: The column cannot be changed more than once in a single UPDATE statement
            • Error 4141: Row with no elements is not allowed in table value constructor in this context
            • Error 4142: SYSTEM_TIME partitions in table does not support historical query
            • Error 4143: index does not support this operation
            • Error 4144: Changing table options requires the table to be rebuilt
            • Error 4145: Can't execute the command as you have a BACKUP STAGE active
            • Error 4146: You must start backup with "BACKUP STAGE START"
            • Error 4147: Backup stage is same or before current backup stage
            • Error 4148: Backup stage failed
            • Error 4149: Unknown backup stage: Stage should be one of START, FLUSH, BLOCK_DDL, BLOCK_COMMIT or EN
            • Error 4150: User is blocked because of too many credential errors; unblock with 'FLUSH PRIVILEGES'
            • Error 4151: Access denied, this account is locked
            • Error 4152: Application-time period table cannot be temporary
            • Error 4153: Fields of PERIOD FOR have different types
            • Error 4154: Cannot specify more than one application-time period
            • Error 4155: Period field cannot be
            • Error 4156: Period is not found in table
            • Error 4157: Column used in period specified in update SET list
            • Error 4158: Can't DROP CONSTRAINT. Use DROP PERIOD for this
            • Error 4159: Specified key part was too long; max key part length is
            • Error 4160: Comment for database is too long
            • Error 4161: Unknown data type
            • Error 4162: Operator does not exists
            • Error 4163: Table history row start is later than row end
            • Error 4164: STARTS is later than query time, first history partition may exceed INTERVAL value
            • Error 4165: DDL-statement is forbidden as table storage engine does not support Galera replication
            • Error 4166: The used command is not allowed because the MariaDB server or client has disabled the lo
            • Error 4167: No secure transports are configured, unable to set --require_secure_transport=ON
            • Error 4168: Slave SQL thread ignored the '%s' because table is shared
            • Error 4169: AUTO_INCREMENT column cannot be used in the UNIQUE index
            • Error 4170: Key cannot explicitly include column
            • Error 4171: Key cannot have WITHOUT OVERLAPS
            • Error 4172: is not allowed in this context
            • Error 4173: Engine does not support rollback. Changes where commited during rollback call
            • Error 4174: A primary key cannot be marked as IGNORE
            • Error 4175: SKIP LOCKED makes this statement unsafe
            • Error 4176: Field can't be set for JSON_TABLE
            • Error 4177: Every table function must have an alias
            • Error 4178: Can't store an array or an object in the scalar column of JSON_TABLE
            • Error 4179: Can't store multiple matches of the path in the column of JSON_TABLE
            • Error 4180: FETCH ... WITH TIES requires ORDER BY clause to be present
            • Error 4181: Dropped orphan trigger, originally created for table
            • Error 4182: Storage engine is disabled
            • Error 4183: SFORMAT error
            • Error 4184: Convert partition is not supported for subpartitioned table
            • Error 4185: MariaDB tried to use the %s, but its provider plugin is not loaded
            • Error 4186: Failed to parse histogram for table at offset
            • Error 4187: OUT or INOUT argument for function is not allowed here
            • Error 4188: Replicated query table can not be temporary
            • Error 4189: Versioned table: adding HISTORY partition(s) failed
            • Error 4190: is implicitly changing the value of from to
            • Error 4191: CHANGE MASTER TO option is missing requirement
            • Error 4192: Slave log event execution was interrupted (slave_max_statement_time exceeded)
            • Error 4193: Invalid value for keyword
            • Error 4194: keyword is not supported
            • Error 4195: Variable schema is not supported
            • Error 4196: Pseudo thread id should not be modified by the client as it will be overwritten
            • Error 4197: Wrong number of columns
            • Error 4198: Sequence tables cannot have any keys
            • Error 4199: Sequence tables cannot have any constraints
          • MariaDB Error Codes 4200 to 4299
            • Error 4200: ORDER BY
            • Error 4201: The variable is ignored
            • Error 4202: Incorrect column name count for derived table
            • Error 4203: Values were longer than max_sort_length. Sorting used only the first bytes
            • Error 4204: Invalid binary vector format
            • Error 4205: Invalid vector format at offset
            • Error 4206: Cannot determine distance type for VEC_DISTANCE, index is not found
        • libMariaDB
        • libmysqld
          • Embedded MariaDB Interface
          • The mariadb-test and mariadb-test-embedded Programs
        • Non-Blocking Client Library
          • About Non-blocking Operation in the Client Library
          • Non-blocking API Reference
          • Using the Non-blocking Library
  • Additional Resources
    • Customer Stories
    • Blogs
  • Books
  • Database Theory
    • ACID: Concurrency Control with Transactions
    • Exploring Early Database Models
    • Introduction to Relational Databases
    • Relational Databases: Basic Terms
    • Relational Databases: Foreign Keys
    • Relational Databases: Table Keys
    • Relational Databases: Views
    • Understanding the Hierarchical Database Model
    • Understanding the Network Database Model
    • Understanding the Relational Database Model
    • Database Design
      • Database Design Example Phase 1: Analysis
      • Database Design Example Phase 2: Design
      • Database Design Example Phase 3: Implementation
      • Database Design Example Phases 4-6: Testing, Operation and Maintenance
      • Database Design: Overview
      • Database Design Phase 1: Analysis
      • Database Design Phase 2: Conceptual Design
      • Database Design Phase 2: Logical and Physical Design
      • Database Design Phase 3: Implementation
      • Database Design Phase 4: Testing
      • Database Design Phase 5: Operation
      • Database Design Phase 6: Maintenance
      • Database Lifecycle
    • Database Normalization
      • Database Normalization: 1st Normal Form
      • Database Normalization: 2nd Normal Form
      • Database Normalization: 3rd Normal Form
      • Database Normalization: 4th Normal Form
      • Database Normalization: 5th Normal Form and Beyond
      • Database Normalization: Boyce-Codd Normal Form
      • Database Normalization Overview
      • Understanding Denormalization
  • Events
  • Quickstart Guides
  • Support
  • Tutorials
  • Videos
  • White Papers
  • Distributions Including MariaDB
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Product Development
  2. MariaDB Internals
  3. MariaDB Source Code Internals

MariaDB Memory Usage

How MariaDB uses memory

Connect Memory Usage
PreviousStored Procedure InternalsNextConnect Memory Usage

Last updated 10 days ago

Was this helpful?

LogoLogo

Products

  • Enterprise Platform
  • Community Server
  • Download MariaDB
  • Pricing

Support

  • Customer Login
  • Technical Support
  • Remote DBA
  • Professional Services

Resources

  • MariaDB Blog
  • Webinars
  • Customer Stories
  • MariaDB Events
  • Documentation
  • Developer Hub

Company

  • About MariaDB
  • Newsroom
  • Leadership
  • MariaDB Careers
  • Legal
  • Privacy Policy

© 2025 MariaDB. All rights reserved.