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 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 committed 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