Error 1646: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

Error Code	SQLSTATE	Error	Description
1646	HY000	ER_SIGNAL_BAD_CONDITION_TYPE	SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

Possible Causes and Solutions

Possible Causes and Solutions

This article doesn't currently contain any content. You can help!

Comments

Comments loading...

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.

↑ 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 allowed
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 Reference Manual
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 engines and statement-incapable engines are involved.
Error 1662: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.
Error 1663: Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED
Error 1664: Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging
Error 1665: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging
Error 1666: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT
Error 1667: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging
Error 1668: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted
Error 1669: The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted
Error 1670: The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves
Error 1671: Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly
Error 1672: Statement is unsafe because it uses a UDF which may not return the same value on the slave
Error 1673: Statement is unsafe because it uses a system variable that may have a different value on the slave
Error 1674: Statement is unsafe because it uses a system function that may return a different value on the slave
Error 1675: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction
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, and writes to any of them.
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

Error 1646: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE

Contents

Possible Causes and Solutions

Comments

Products

Services

Pricing

Resources

About Us

Download MariaDB