| Node |
Parent |
Last Updated |
Type |
| Error 1638: Non-ASCII separator arguments are not fully supported |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1639: debug sync point wait timed out |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1640: debug sync point hit limit reached |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1641: Duplicate condition information item |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1642: Unhandled user-defined warning condition |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1643: Unhandled user-defined not found condition |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1644: Unhandled user-defined exception condition |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1645: RESIGNAL when handler not active |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1646: SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1647: Data truncated for condition item |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1648: Data too long for condition item |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1649: Unknown locale |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1650: The requested server id clashes with the slave startup option --replicate-same-server-id |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1651: Query cache is disabled; restart the server with query_cache_type=1 to enable it |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1652: Duplicate partition field name |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1653: Inconsistency in usage of column lists for partitioning |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1654: Partition column values of incorrect type |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1655: Too many fields |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1656: Cannot use MAXVALUE as value in VALUES IN |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1657: Cannot have more than one value for this type of partitioning |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1658: Row expressions in VALUES IN only allowed for multi-field column partitioning |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1659: Field is of a not allowed type for this type of partitioning |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1660: The total length of the partitioning fields is too large |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1661: Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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. |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1666: Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1668: The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1669: The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| 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 |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1672: Statement is unsafe because it uses a UDF which may not return the same value on the slave |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1673: Statement is unsafe because it uses a system variable that may have a different value on the slave |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1674: Statement is unsafe because it uses a system function that may return a different value on the slave |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1675: Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1676: Statement |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1677: Column of table cannot be converted from type to type |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1678: Can't create conversion table for table |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1679: Cannot modify @@session.binlog_format inside a transaction |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1680: The path specified is too long |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1681: is deprecated and will be removed in a future release. |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1682: Native table has the wrong structure |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1683: Invalid performance_schema usage |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1684: Table was skipped since its definition is being modified by concurrent DDL statement |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1685: Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1686: Cannot change the binlog direct flag inside a stored function or trigger |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
| Error 1687: A SPATIAL index may only contain a geometrical type column |
MariaDB Error Codes 1600 to 1699 |
7 ヶ月, 3 週間 ago |
article |
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.
