This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

Needs Translation - 日本語

Nodes that need to be translated

Node Parent Last Updated Type
Error 1906: The value specified for generated column in table has been ignored MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1907: This is not yet supported for generated columns MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1908: " MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1909: " MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1910: storage engine does not support generated columns MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1911: Unknown option MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1912: Incorrect value for option MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1913: You should never see it MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1914: You should never see it MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1915: You should never see it MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1916: Got overflow when converting to. Value truncated MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1917: Truncated value when converting to MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1918: Encountered illegal value when converting to MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1919: Encountered illegal format of dynamic column string MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1920: Dynamic column implementation limit reached MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1921: Illegal value used as argument of dynamic column function MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1922: Dynamic column contains unknown character set MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1923: At least one of the 'in_to_exists' or 'materialization' optimizer_switch flags must be 'on'. MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1924: Query cache is disabled (resize or similar command in progress); repeat this command later MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1925: Query cache is globally disabled and you can't enable it only for this session MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1926: View ORDER BY clause ignored because there is other ORDER BY clause already MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1927: Connection was killed MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
error 1928 with 5.3.3 RC Release Notes - MariaDB 5.3 Series 12 年, 9 ヶ月 ago question
Error 1928: You should never see it MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1929: Cannot modify @@session.skip_replication inside a transaction MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1930: Cannot modify @@session.skip_replication inside a stored function or trigger MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1931: Query execution was interrupted. The query exceeded. The query result may be incomplete MariaDB Error Codes 1900 to 1999 7 ヶ月, 2 週間 ago article
ERROR 1932 on a table with recently added VIRTUAL column CREATE 9 年, 3 ヶ月 ago question
Error 1932: Table doesn't exist in engine MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1933: Target is not running an EXPLAINable command MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1934: Connection conflicts with existing connection MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1935: Master MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1936: Can't %s SLAVE MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1937: SLAVE started MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1938: SLAVE stopped MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1939: Engine failed to discover table with MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1940: Failed initializing replication GTID state MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1941: Could not parse GTID list MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1942: Could not update replication slave gtid state MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1943: GTID conflict (duplicate domain id) MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1944: Failed to open MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1945: Connecting slave requested to start from GTID, which is not in the master's binlog MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1946: Failed to load replication slave GTID position from table MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1947: Specified GTID conflicts with the binary log which contains a more recent GTID MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1948: Specified value for @@gtid_slave_pos contains no value for replication domain MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1949: START SLAVE UNTIL master_gtid_pos requires that slave is using GTID MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1950: An attempt was made to binlog GTID which would create an out-of-order sequence number with existing GTID MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1951: The binlog on the master is missing the GTID requested by the slave MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1952: Unexpected GTID received from master after reconnect MariaDB Error Codes 1900 to 1999 7 ヶ月, 3 週間 ago article
Error 1953: Cannot modify @@session.gtid_domain_id or @@session.gtid_seq_no inside a transaction 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.