| Node |
Parent |
Last Updated |
Type |
| Error 1837: When GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLLBACK |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1838: The system variable cannot be set in stored procedures |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1839: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1840: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1841: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients) |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1842: @@GLOBAL.GTID_PURGED was changed from to |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1843: @@GLOBAL.GTID_EXECUTED was changed from to |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1844: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1845: is not supported for this operation. Try |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1846: is not supported. Reason: Try |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1847: COPY algorithm requires a lock |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1848: Partition specific operations do not yet support LOCK/ALGORITHM |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1849: Columns participating in a foreign key are renamed |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1850: Cannot change column type INPLACE |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1851: Adding foreign keys needs foreign_key_checks=OFF |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1852: Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1853: Dropping a primary key is not allowed without also adding a new primary key |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1854: Adding an auto-increment column requires a lock |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1855: Cannot replace hidden FTS_DOC_ID with a user-visible one |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1856: Cannot drop or rename FTS_DOC_ID |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1857: Fulltext index creation requires a lock |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1858: sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1859: Duplicate entry for key |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1860: Long database name and identifier for object resulted in path length exceeding characters |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1861: cannot silently convert NULL values, as required in this SQL_MODE |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1862: Your password has expired. To log in you must change it using a client that supports expired passwords |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1863: Found a row in wrong partition |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1864: Cannot schedule event, relay-log name, position to Worker thread because its size exceeds of slave_pending_jobs_size_max |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1865: Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1866: The binary log file is logically corrupted |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1867: file was not purged because it was being read by thread(s), purged only out of |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1868: file was not purged because it is the active log file |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1869: Auto-increment value in UPDATE conflicts with internally generated values |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1870: Row events are not logged for statements that modify BLACKHOLE tables in row format |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1871: Slave failed to initialize master info structure from the repository |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1872: Slave failed to initialize relay log info structure from the repository |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1873: Access denied trying to change to user (using password). Disconnecting. |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1874: InnoDB is in read only mode |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1875: STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1876: STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1877: Operation cannot be performed. The table is missing, corrupt or contains bad data |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1878: Temporary file write failure |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1879: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1880: " |
MariaDB Error Codes 1800 to 1899 |
7 ヶ月, 3 週間 ago |
article |
| Error 1900: " |
MariaDB Error Codes 1900 to 1999 |
7 ヶ月, 3 週間 ago |
article |
| Error 1901: Function or expression cannot be used in the clause of |
MariaDB Error Codes 1900 to 1999 |
7 ヶ月, 3 週間 ago |
article |
| Error 1902: " |
MariaDB Error Codes 1900 to 1999 |
7 ヶ月, 3 週間 ago |
article |
| Error 1903: Primary key cannot be defined upon a generated column |
MariaDB Error Codes 1900 to 1999 |
7 ヶ月, 3 週間 ago |
article |
| Error 1904: Key/Index cannot be defined on a virtual generated column |
MariaDB Error Codes 1900 to 1999 |
7 ヶ月, 3 週間 ago |
article |
| Error 1905: Cannot define foreign key with clause on a generated column |
MariaDB Error Codes 1900 to 1999 |
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.
