B.1.服务器错误代码和消息 服务器错误信息来自下述源文件: · 错误消息信息列在 share/errmsg.txt 文件中 。“ %d” 和 “%s” 分别代表编号和字符串,显示时,它们将被消息取代。 · 错误列在 share/errmsg.txt 文件中,用于生成 include/mysqld_error.h
B.1. 服务器错误代码和消息
服务器错误信息来自下述源文件:
· 错误消息信息列在share/errmsg.txt文件中。“%d”和“%s”分别代表编号和字符串,显示时,它们将被消息值取代。
· 错误值列在share/errmsg.txt文件中,用于生成include/mysqld_error.h和include/mysqld_ername.h MySQL源文件中的定义。
· SQLSTATE值列在share/errmsg.txt文件中,用于生成include/sql_state.h MySQL源文件中的定义。
由于更新很频繁,这些文件中可能包含这里未列出的额外错误消息。
· 错误:1000 SQLSTATE: HY000 (ER_HASHCHK)
消息:hashchk
· 错误:1001 SQLSTATE: HY000 (ER_NISAMCHK)
消息:isamchk
· 错误:1002 SQLSTATE: HY000 (ER_NO)
消息:NO
· 错误:1003 SQLSTATE: HY000 (ER_YES)
消息:YES
· 错误:1004 SQLSTATE: HY000 (ER_CANT_CREATE_FILE)
消息:无法创建文件'%s' (errno: %d)
· 错误:1005 SQLSTATE: HY000 (ER_CANT_CREATE_TABLE)
消息:无法创建表'%s' (errno: %d)
· 错误:1006 SQLSTATE: HY000 (ER_CANT_CREATE_DB)
消息:无法创建数据库'%s' (errno: %d)
· 错误:1007 SQLSTATE: HY000 (ER_DB_CREATE_EXISTS)
消息:无法创建数据库'%s',数据库已存在。
· 错误:1008 SQLSTATE: HY000 (ER_DB_DROP_EXISTS)
消息:无法撤销数据库'%s',数据库不存在。
· 错误:1009 SQLSTATE: HY000 (ER_DB_DROP_DELETE)
消息:撤销数据库时出错(无法删除'%s',errno: %d)
· 错误:1010 SQLSTATE: HY000 (ER_DB_DROP_RMDIR)
消息:撤销数据库时出错(can't rmdir '%s', errno: %d)
· 错误:1011 SQLSTATE: HY000 (ER_CANT_DELETE_FILE)
消息:删除'%s'时出错 (errno: %d)
· 错误:1012 SQLSTATE: HY000 (ER_CANT_FIND_SYSTEM_REC)
消息:无法读取系统表中的记录。
· 错误:1013 SQLSTATE: HY000 (ER_CANT_GET_STAT)
消息:无法获取'%s'的状态(errno: %d)
· 错误:1014 SQLSTATE: HY000 (ER_CANT_GET_WD)
消息:无法获得工作目录(errno: %d)
· 错误:1015 SQLSTATE: HY000 (ER_CANT_LOCK)
消息:无法锁定文件(errno: %d)
· 错误:1016 SQLSTATE: HY000 (ER_CANT_OPEN_FILE)
消息:无法打开文件:'%s' (errno: %d)
· 错误:1017 SQLSTATE: HY000 (ER_FILE_NOT_FOUND)
消息:无法找到文件: '%s' (errno: %d)
· 错误:1018 SQLSTATE: HY000 (ER_CANT_READ_DIR)
消息:无法读取'%s'的目录 (errno: %d)
· 错误:1019 SQLSTATE: HY000 (ER_CANT_SET_WD)
消息:无法为'%s'更改目录 (errno: %d)
· 错误:1020 SQLSTATE: HY000 (ER_CHECKREAD)
消息:自上次读取以来表'%s'中的记录已改变。
· 错误:1021 SQLSTATE: HY000 (ER_DISK_FULL)
消息:磁盘满(%s);等待某人释放一些空间...
· 错误:1022 SQLSTATE: 23000 (ER_DUP_KEY)
消息:无法写入;复制表'%s'的 键。
· 错误:1023 SQLSTATE: HY000 (ER_ERROR_ON_CLOSE)
消息:关闭'%s'时出错 (errno: %d)
· 错误:1024 SQLSTATE: HY000 (ER_ERROR_ON_READ)
消息:读取文件'%s'时出错 (errno: %d)
· 错误:1025 SQLSTATE: HY000 (ER_ERROR_ON_RENAME)
消息:将'%s'重命名为'%s'时出错 (errno: %d)
· 错误:1026 SQLSTATE: HY000 (ER_ERROR_ON_WRITE)
消息:写入文件'%s'时出错 (errno: %d)
· 错误:1027 SQLSTATE: HY000 (ER_FILE_USED)
消息:'%s'已锁定,拒绝更改。
· 错误:1028 SQLSTATE: HY000 (ER_FILSORT_ABORT)
消息:分类失败
· 错误:1029 SQLSTATE: HY000 (ER_FORM_NOT_FOUND)
消息:对于'%s',视图'%s'不存在。
· 错误:1030 SQLSTATE: HY000 (ER_GET_ERRNO)
消息:从存储引擎中获得错误%d。
· 错误:1031 SQLSTATE: HY000 (ER_ILLEGAL_HA)
消息:关于'%s'的表存储引擎不含该选项。
· 错误:1032 SQLSTATE: HY000 (ER_KEY_NOT_FOUND)
消息:无法在'%s'中找到记录。
· 错误:1033 SQLSTATE: HY000 (ER_NOT_FORM_FILE)
消息:文件中的不正确信息:'%s'
· 错误:1034 SQLSTATE: HY000 (ER_NOT_KEYFILE)
消息:对于表'%s', 键文件不正确,请尝试修复。
· 错误:1035 SQLSTATE: HY000 (ER_OLD_KEYFILE)
消息:旧的键文件,对于表'%s',请修复之!
· 错误:1036 SQLSTATE: HY000 (ER_OPEN_AS_READONLY)
消息:表'%s'是只读的。
· 错误:1037 SQLSTATE: HY001 (ER_OUTOFMEMORY)
消息:内存溢出,重启服务器并再次尝试(需要%d字节)。
· 错误:1038 SQLSTATE: HY001 (ER_OUT_OF_SORTMEMORY)
消息:分类内存溢出,增加服务器的分类缓冲区大小。
· 错误:1039 SQLSTATE: HY000 (ER_UNEXPECTED_EOF)
消息:读取文件'%s'时出现意外EOF (errno: %d)
· 错误:1040 SQLSTATE: 08004 (ER_CON_COUNT_ERROR)
消息:连接过多。
· 错误:1041 SQLSTATE: HY000 (ER_OUT_OF_RESOURCES)
消息:内存溢出,请检查是否mysqld或其他进程使用了所有可用内存,如不然,或许应使用'ulimit'允许mysqld使用更多内存,或增加交换空间的大小。
· 错误:1042 SQLSTATE: 08S01 (ER_BAD_HOST_ERROR)
消息:无法获得该地址给出的主机名。
· 错误:1043 SQLSTATE: 08S01 (ER_HANDSHAKE_ERROR)
消息:不良握手
· 错误:1044 SQLSTATE: 42000 (ER_DBACCESS_DENIED_ERROR)
消息:拒绝用户'%s'@'%s'访问数据库'%s'。
· 错误:1045 SQLSTATE: 28000 (ER_ACCESS_DENIED_ERROR)
消息:拒绝用户'%s'@'%s'的访问(使用密码:%s)
· 错误:1046 SQLSTATE: 3D000 (ER_NO_DB_ERROR)
消息:未选择数据库。
· 错误:1047 SQLSTATE: 08S01 (ER_UNKNOWN_COM_ERROR)
消息:未知命令。
· 错误:1048 SQLSTATE: 23000 (ER_BAD_NULL_ERROR)
消息:列'%s'不能为空。
· 错误:1049 SQLSTATE: 42000 (ER_BAD_DB_ERROR)
消息:未知数据库'%s'。
· 错误:1050 SQLSTATE: 42S01 (ER_TABLE_EXISTS_ERROR)
消息:表'%s'已存在。
· 错误:1051 SQLSTATE: 42S02 (ER_BAD_TABLE_ERROR)
消息:未知表'%s'。
· 错误:1052 SQLSTATE: 23000 (ER_NON_UNIQ_ERROR)
消息:%s中的列'%s'不明确。
· 错误:1053 SQLSTATE: 08S01 (ER_SERVER_SHUTDOWN)
消息:在操作过程中服务器关闭。
· 错误:1054 SQLSTATE: 42S22 (ER_BAD_FIELD_ERROR)
消息:'%s'中的未知列'%s'。
· 错误:1055 SQLSTATE: 42000 (ER_WRONG_FIELD_WITH_GROUP)
消息:'%s'不在GROUP BY中。
· 错误:1056 SQLSTATE: 42000 (ER_WRONG_GROUP_FIELD)
消息:无法在'%s'上创建组。
· 错误:1057 SQLSTATE: 42000 (ER_WRONG_SUM_SELECT)
消息:语句中有sum函数和相同语句中的列。
· 错误:1058 SQLSTATE: 21S01 (ER_WRONG_VALUE_COUNT)
消息:列计数不匹配值计数。
· 错误:1059 SQLSTATE: 42000 (ER_TOO_LONG_IDENT)
消息:ID名称'%s'过长。
· 错误:1060 SQLSTATE: 42S21 (ER_DUP_FIELDNAME)
消息:重复列名'%s'。
· 错误:1061 SQLSTATE: 42000 (ER_DUP_KEYNAME)
消息:重复键名称'%s'。
· 错误:1062 SQLSTATE: 23000 (ER_DUP_ENTRY)
消息:键%d的重复条目'%s'。
· 错误:1063 SQLSTATE: 42000 (ER_WRONG_FIELD_SPEC)
消息:对于列'%s',列分类符不正确。
· 错误:1064 SQLSTATE: 42000 (ER_PARSE_ERROR)
消息:在行%d上,%s靠近'%s'。
· 错误:1065 SQLSTATE: 42000 (ER_EMPTY_QUERY)
消息:查询为空。
· 错误:1066 SQLSTATE: 42000 (ER_NONUNIQ_TABLE)
消息:非唯一的表/别名:'%s'
· 错误:1067 SQLSTATE: 42000 (ER_INVALID_DEFAULT)
消息:关于'%s'的无效默认值。
· 错误:1068 SQLSTATE: 42000 (ER_MULTIPLE_PRI_KEY)
消息:定义了多个主键。
· 错误:1069 SQLSTATE: 42000 (ER_TOO_MANY_KEYS)
消息:指定了过多键:允许的最大键数是%d。
· 错误:1070 SQLSTATE: 42000 (ER_TOO_MANY_KEY_PARTS)
消息:指定了过多键部分:允许的最大键部分是%d。
· 错误:1071 SQLSTATE: 42000 (ER_TOO_LONG_KEY)
消息:指定的键过长,最大键长度是%d字节。
· 错误:1072 SQLSTATE: 42000 (ER_KEY_COLUMN_DOES_NOT_EXITS)
消息:键列'%s'在表中不存在。
· 错误:

ACID attributes include atomicity, consistency, isolation and durability, and are the cornerstone of database design. 1. Atomicity ensures that the transaction is either completely successful or completely failed. 2. Consistency ensures that the database remains consistent before and after a transaction. 3. Isolation ensures that transactions do not interfere with each other. 4. Persistence ensures that data is permanently saved after transaction submission.

MySQL is not only a database management system (DBMS) but also closely related to programming languages. 1) As a DBMS, MySQL is used to store, organize and retrieve data, and optimizing indexes can improve query performance. 2) Combining SQL with programming languages, embedded in Python, using ORM tools such as SQLAlchemy can simplify operations. 3) Performance optimization includes indexing, querying, caching, library and table division and transaction management.

MySQL uses SQL commands to manage data. 1. Basic commands include SELECT, INSERT, UPDATE and DELETE. 2. Advanced usage involves JOIN, subquery and aggregate functions. 3. Common errors include syntax, logic and performance issues. 4. Optimization tips include using indexes, avoiding SELECT* and using LIMIT.

MySQL is an efficient relational database management system suitable for storing and managing data. Its advantages include high-performance queries, flexible transaction processing and rich data types. In practical applications, MySQL is often used in e-commerce platforms, social networks and content management systems, but attention should be paid to performance optimization, data security and scalability.

The relationship between SQL and MySQL is the relationship between standard languages and specific implementations. 1.SQL is a standard language used to manage and operate relational databases, allowing data addition, deletion, modification and query. 2.MySQL is a specific database management system that uses SQL as its operating language and provides efficient data storage and management.

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Atom editor mac version download
The most popular open source editor

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

Dreamweaver Mac version
Visual web development tools

Notepad++7.3.1
Easy-to-use and free code editor