При возникновении ошибок в работе, MySQL сервер возвращает соответствующие сообщения.
Сообщения об ошибках состоят из трех типов данных:
Ниже приведенна таблица ошибок MySQL сервера с кодами ошибок, значением SQLSTATE и описанием ошибок.
Код
SQLSTATE
Ошибка
Описание ошибки
Описание ошибки
Sometimes you need a good reference, and this is one of those times. MySQL’s perror command returns many error codes, and I’ve provided a listing here. To find errors individually, just run:
1 2 |
# perror 28 OS error code 28: No space left on device |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 |
OS error code 1: Operation not permitted OS error code 2: No such file or directory OS error code 3: No such process OS error code 4: Interrupted system call OS error code 5: Input/output error OS error code 6: No such device or address OS error code 7: Argument list too long OS error code 8: Exec format error OS error code 9: Bad file descriptor OS error code 10: No child processes OS error code 11: Resource temporarily unavailable OS error code 12: Cannot allocate memory OS error code 13: Permission denied OS error code 14: Bad address OS error code 15: Block device required OS error code 16: Device or resource busy OS error code 17: File exists OS error code 18: Invalid cross-device link OS error code 19: No such device OS error code 20: Not a directory OS error code 21: Is a directory OS error code 22: Invalid argument OS error code 23: Too many open files in system OS error code 24: Too many open files OS error code 25: Inappropriate ioctl for device OS error code 26: Text file busy OS error code 27: File too large OS error code 28: No space left on device OS error code 30: Read-only file system OS error code 31: Too many links OS error code 32: Broken pipe OS error code 33: Numerical argument out of domain OS error code 34: Numerical result out of range OS error code 35: Resource deadlock avoided OS error code 36: File name too long OS error code 37: No locks available OS error code 38: Function not implemented OS error code 39: Directory not empty OS error code 40: Too many levels of symbolic links OS error code 42: No message of desired type OS error code 43: Identifier removed OS error code 44: Channel number out of range OS error code 45: Level 2 not synchronized OS error code 46: Level 3 halted OS error code 47: Level 3 reset OS error code 48: Link number out of range OS error code 49: Protocol driver not attached OS error code 50: No CSI structure available OS error code 51: Level 2 halted OS error code 52: Invalid exchange OS error code 53: Invalid request descriptor OS error code 54: Exchange full OS error code 55: No anode OS error code 56: Invalid request code OS error code 57: Invalid slot OS error code 59: Bad font file format OS error code 60: Device not a stream OS error code 61: No data available OS error code 62: Timer expired OS error code 63: Out of streams resources OS error code 64: Machine is not on the network OS error code 65: Package not installed OS error code 66: Object is remote OS error code 67: Link has been severed OS error code 68: Advertise error OS error code 69: Srmount error OS error code 70: Communication error on send OS error code 71: Protocol error OS error code 72: Multihop attempted OS error code 73: RFS specific error OS error code 74: Bad message OS error code 75: Value too large for defined data type OS error code 76: Name not unique on network OS error code 77: File descriptor in bad state OS error code 78: Remote address changed OS error code 79: Can not access a needed shared library OS error code 80: Accessing a corrupted shared library OS error code 81: .lib section in a.out corrupted OS error code 82: Attempting to link in too many shared libraries OS error code 83: Cannot exec a shared library directly OS error code 84: Invalid or incomplete multibyte or wide character OS error code 85: Interrupted system call should be restarted OS error code 86: Streams pipe error OS error code 87: Too many users OS error code 88: Socket operation on non-socket OS error code 89: Destination address required OS error code 90: Message too long OS error code 91: Protocol wrong type for socket OS error code 92: Protocol not available OS error code 93: Protocol not supported OS error code 94: Socket type not supported OS error code 95: Operation not supported OS error code 96: Protocol family not supported OS error code 97: Address family not supported by protocol OS error code 98: Address already in use OS error code 99: Cannot assign requested address OS error code 100: Network is down OS error code 101: Network is unreachable OS error code 102: Network dropped connection on reset OS error code 103: Software caused connection abort OS error code 104: Connection reset by peer OS error code 105: No buffer space available OS error code 106: Transport endpoint is already connected OS error code 107: Transport endpoint is not connected OS error code 108: Cannot send after transport endpoint shutdown OS error code 109: Too many references: cannot splice OS error code 110: Connection timed out OS error code 111: Connection refused OS error code 112: Host is down OS error code 113: No route to host OS error code 114: Operation already in progress OS error code 115: Operation now in progress OS error code 116: Stale NFS file handle OS error code 117: Structure needs cleaning OS error code 118: Not a XENIX named type file OS error code 119: No XENIX semaphores available OS error code 120: Is a named type file OS error code 121: Remote I/O error OS error code 122: Disk quota exceeded OS error code 123: No medium found OS error code 124: Wrong medium type OS error code 125: Operation canceled MySQL error code 126: Index file is crashed MySQL error code 127: Record-file is crashed MySQL error code 128: Out of memory MySQL error code 130: Incorrect file format MySQL error code 131: Command not supported by database MySQL error code 132: Old database file MySQL error code 133: No record read before update MySQL error code 134: Record was already deleted (or record file crashed) MySQL error code 135: No more room in record file MySQL error code 136: No more room in index file MySQL error code 137: No more records (read after end of file) MySQL error code 138: Unsupported extension used for table MySQL error code 139: Too big row MySQL error code 140: Wrong create options MySQL error code 141: Duplicate unique key or constraint on write or update MySQL error code 142: Unknown character set used MySQL error code 143: Conflicting table definitions in sub-tables of MERGE table MySQL error code 144: Table is crashed and last repair failed MySQL error code 145: Table was marked as crashed and should be repaired MySQL error code 146: Lock timed out; Retry transaction MySQL error code 147: Lock table is full; Restart program with a larger locktable MySQL error code 148: Updates are not allowed under a read only transactions MySQL error code 149: Lock deadlock; Retry transaction MySQL error code 150: Foreign key constraint is incorrectly formed MySQL error code 151: Cannot add a child row MySQL error code 152: Cannot delete a parent row |
OS error code 1: Operation not permitted
OS error code 2: No such file or directory
OS error code 3: No such process
OS error code 4: Interrupted system call
OS error code 5: Input/output error
OS error code 6: No such device or address
OS error code 7: Argument list too long
OS error code 8: Exec format error
OS error code 9: Bad file descriptor
OS error code 10: No child processes
OS error code 11: Resource temporarily unavailable
OS error code 12: Cannot allocate memory
OS error code 13: Permission denied
OS error code 14: Bad address
OS error code 15: Block device required
OS error code 16: Device or resource busy
OS error code 17: File exists
OS error code 18: Invalid cross-device link
OS error code 19: No such device
OS error code 20: Not a directory
OS error code 21: Is a directory
OS error code 22: Invalid argument
OS error code 23: Too many open files in system
OS error code 24: Too many open files
OS error code 25: Inappropriate ioctl for device
OS error code 26: Text file busy
OS error code 27: File too large
OS error code 28: No space left on device
OS error code 29: Illegal seek
OS error code 30: Read-only file system
OS error code 31: Too many links
OS error code 32: Broken pipe
OS error code 33: Numerical argument out of domain
OS error code 34: Numerical result out of range
OS error code 35: Resource deadlock avoided
OS error code 36: File name too long
OS error code 37: No locks available
OS error code 38: Function not implemented
OS error code 39: Directory not empty
OS error code 40: Too many levels of symbolic links
OS error code 42: No message of desired type
OS error code 43: Identifier removed
OS error code 44: Channel number out of range
OS error code 45: Level 2 not synchronized
OS error code 46: Level 3 halted
OS error code 47: Level 3 reset
OS error code 48: Link number out of range
OS error code 49: Protocol driver not attached
OS error code 50: No CSI structure available
OS error code 51: Level 2 halted
OS error code 52: Invalid exchange
OS error code 53: Invalid request descriptor
OS error code 54: Exchange full
OS error code 55: No anode
OS error code 56: Invalid request code
OS error code 57: Invalid slot
OS error code 59: Bad font file format
OS error code 60: Device not a stream
OS error code 61: No data available
OS error code 62: Timer expired
OS error code 63: Out of streams resources
OS error code 64: Machine is not on the network
OS error code 65: Package not installed
OS error code 66: Object is remote
OS error code 67: Link has been severed
OS error code 68: Advertise error
OS error code 69: Srmount error
OS error code 70: Communication error on send
OS error code 71: Protocol error
OS error code 72: Multihop attempted
OS error code 73: RFS specific error
OS error code 74: Bad message
OS error code 75: Value too large for defined data type
OS error code 76: Name not unique on network
OS error code 77: File descriptor in bad state
OS error code 78: Remote address changed
OS error code 79: Can not access a needed shared library
OS error code 80: Accessing a corrupted shared library
OS error code 81: .lib section in a.out corrupted
OS error code 82: Attempting to link in too many shared libraries
OS error code 83: Cannot exec a shared library directly
OS error code 84: Invalid or incomplete multibyte or wide character
OS error code 85: Interrupted system call should be restarted
OS error code 86: Streams pipe error
OS error code 87: Too many users
OS error code 88: Socket operation on non-socket
OS error code 89: Destination address required
OS error code 90: Message too long
OS error code 91: Protocol wrong type for socket
OS error code 92: Protocol not available
OS error code 93: Protocol not supported
OS error code 94: Socket type not supported
OS error code 95: Operation not supported
OS error code 96: Protocol family not supported
OS error code 97: Address family not supported by protocol
OS error code 98: Address already in use
OS error code 99: Cannot assign requested address
OS error code 100: Network is down
OS error code 101: Network is unreachable
OS error code 102: Network dropped connection on reset
OS error code 103: Software caused connection abort
OS error code 104: Connection reset by peer
OS error code 105: No buffer space available
OS error code 106: Transport endpoint is already connected
OS error code 107: Transport endpoint is not connected
OS error code 108: Cannot send after transport endpoint shutdown
OS error code 109: Too many references: cannot splice
OS error code 110: Connection timed out
OS error code 111: Connection refused
OS error code 112: Host is down
OS error code 113: No route to host
OS error code 114: Operation already in progress
OS error code 115: Operation now in progress
OS error code 116: Stale file handle
OS error code 117: Structure needs cleaning
OS error code 118: Not a XENIX named type file
OS error code 119: No XENIX semaphores available
OS error code 120: Is a named type file
MySQL error code 120: Didn't find key on read or update
OS error code 121: Remote I/O error
MySQL error code 121: Duplicate key on write or update
OS error code 122: Disk quota exceeded
MySQL error code 122: Internal (unspecified) error in handler
OS error code 123: No medium found
MySQL error code 123: Someone has changed the row since it was read (while the table was locked to prevent it)
OS error code 124: Wrong medium type
MySQL error code 124: Wrong index given to function
OS error code 125: Operation canceled
MySQL error code 125: Undefined handler error 125
OS error code 126: Required key not available
MySQL error code 126: Index file is crashed
OS error code 127: Key has expired
MySQL error code 127: Record file is crashed
OS error code 128: Key has been revoked
MySQL error code 128: Out of memory in engine
OS error code 129: Key was rejected by service
MySQL error code 129: Undefined handler error 129
OS error code 130: Owner died
MySQL error code 130: Incorrect file format
OS error code 131: State not recoverable
MySQL error code 131: Command not supported by database
OS error code 132: Operation not possible due to RF-kill
MySQL error code 132: Old database file
MySQL error code 133: No record read before update
MySQL error code 134: Record was already deleted (or record file crashed)
MySQL error code 135: No more room in record file
MySQL error code 136: No more room in index file
MySQL error code 137: No more records (read after end of file)
MySQL error code 138: Unsupported extension used for table
MySQL error code 139: Too big row
MySQL error code 140: Wrong create options
MySQL error code 141: Duplicate unique key or constraint on write or update
MySQL error code 142: Unknown character set used in table
MySQL error code 143: Conflicting table definitions in sub-tables of MERGE table
MySQL error code 144: Table is crashed and last repair failed
MySQL error code 145: Table was marked as crashed and should be repaired
MySQL error code 146: Lock timed out; Retry transaction
MySQL error code 147: Lock table is full; Restart program with a larger locktable
MySQL error code 148: Updates are not allowed under a read only transactions
MySQL error code 149: Lock deadlock; Retry transaction
MySQL error code 150: Foreign key constraint is incorrectly formed
MySQL error code 151: Cannot add a child row
MySQL error code 152: Cannot delete a parent row
MySQL error code 153: No savepoint with that name
MySQL error code 154: Non unique key block size
MySQL error code 155: The table does not exist in engine
MySQL error code 156: The table already existed in storage engine
MySQL error code 157: Could not connect to storage engine
MySQL error code 158: Unexpected null pointer found when using spatial index
MySQL error code 159: The table changed in storage engine
MySQL error code 160: There's no partition in table for the given value
MySQL error code 161: Row-based binlogging of row failed
MySQL error code 162: Index needed in foreign key constraint
MySQL error code 163: Upholding foreign key constraints would lead to a duplicate key error in some other table
MySQL error code 164: Table needs to be upgraded before it can be used
MySQL error code 165: Table is read only
MySQL error code 166: Failed to get next auto increment value
MySQL error code 167: Failed to set row auto increment value
MySQL error code 168: Unknown (generic) error from engine
MySQL error code 169: Record is the same
MySQL error code 170: It is not possible to log this statement
MySQL error code 171: The event was corrupt, leading to illegal data being read
MySQL error code 172: The table is of a new format not supported by this version
MySQL error code 173: The event could not be processed no other hanlder error happened
MySQL error code 174: Got a fatal error during initialzaction of handler
MySQL error code 175: File to short; Expected more data in file
MySQL error code 176: Read page with wrong checksum
MySQL error code 177: Too many active concurrent transactions
MySQL error code 178: Record not matching the given partition set
MySQL error code 179: Index column length exceeds limit
MySQL error code 180: Index corrupted
MySQL error code 181: Undo record too big
MySQL error code 182: Invalid InnoDB FTS Doc ID
MySQL error code 183: Table is being used in foreign key check
MySQL error code 184: Tablespace already exists
MySQL error code 185: Too many columns
MySQL error code 186: Row in wrong partition
MySQL error code 187: InnoDB is in read only mode
MySQL error code 188: FTS query exceeds result cache memory limit
MySQL error code 189: Temporary file write failure
MySQL error code 190: Operation not allowed when innodb_forced_recovery > 0
MySQL error code 191: Too many words in a FTS phrase or proximity search
MySQL error code 1000 (ER_HASHCHK): hashchk
MySQL error code 1001 (ER_NISAMCHK): isamchk
MySQL error code 1002 (ER_NO): NO
MySQL error code 1003 (ER_YES): YES
MySQL error code 1004 (ER_CANT_CREATE_FILE): Can't create file '%-.200s' (errno: %d - %s)
MySQL error code 1005 (ER_CANT_CREATE_TABLE): Can't create table '%-.200s' (errno: %d)
MySQL error code 1006 (ER_CANT_CREATE_DB): Can't create database '%-.192s' (errno: %d)
MySQL error code 1007 (ER_DB_CREATE_EXISTS): Can't create database '%-.192s'; database exists
MySQL error code 1008 (ER_DB_DROP_EXISTS): Can't drop database '%-.192s'; database doesn't exist
MySQL error code 1009 (ER_DB_DROP_DELETE): Error dropping database (can't delete '%-.192s', errno: %d)
MySQL error code 1010 (ER_DB_DROP_RMDIR): Error dropping database (can't rmdir '%-.192s', errno: %d)
MySQL error code 1011 (ER_CANT_DELETE_FILE): Error on delete of '%-.192s' (errno: %d - %s)
MySQL error code 1012 (ER_CANT_FIND_SYSTEM_REC): Can't read record in system table
MySQL error code 1013 (ER_CANT_GET_STAT): Can't get status of '%-.200s' (errno: %d - %s)
MySQL error code 1014 (ER_CANT_GET_WD): Can't get working directory (errno: %d - %s)
MySQL error code 1015 (ER_CANT_LOCK): Can't lock file (errno: %d - %s)
MySQL error code 1016 (ER_CANT_OPEN_FILE): Can't open file: '%-.200s' (errno: %d - %s)
MySQL error code 1017 (ER_FILE_NOT_FOUND): Can't find file: '%-.200s' (errno: %d - %s)
MySQL error code 1018 (ER_CANT_READ_DIR): Can't read dir of '%-.192s' (errno: %d - %s)
MySQL error code 1019 (ER_CANT_SET_WD): Can't change dir to '%-.192s' (errno: %d - %s)
MySQL error code 1020 (ER_CHECKREAD): Record has changed since last read in table '%-.192s'
MySQL error code 1021 (ER_DISK_FULL): Disk full (%s); waiting for someone to free some space... (errno: %d - %s)
MySQL error code 1022 (ER_DUP_KEY): Can't write; duplicate key in table '%-.192s'
MySQL error code 1023 (ER_ERROR_ON_CLOSE): Error on close of '%-.192s' (errno: %d - %s)
MySQL error code 1024 (ER_ERROR_ON_READ): Error reading file '%-.200s' (errno: %d - %s)
MySQL error code 1025 (ER_ERROR_ON_RENAME): Error on rename of '%-.210s' to '%-.210s' (errno: %d - %s)
MySQL error code 1026 (ER_ERROR_ON_WRITE): Error writing file '%-.200s' (errno: %d - %s)
MySQL error code 1027 (ER_FILE_USED): '%-.192s' is locked against change
MySQL error code 1028 (ER_FILSORT_ABORT): Sort aborted
MySQL error code 1029 (ER_FORM_NOT_FOUND): View '%-.192s' doesn't exist for '%-.192s'
MySQL error code 1030 (ER_GET_ERRNO): Got error %d from storage engine
MySQL error code 1031 (ER_ILLEGAL_HA): Table storage engine for '%-.192s' doesn't have this option
MySQL error code 1032 (ER_KEY_NOT_FOUND): Can't find record in '%-.192s'
MySQL error code 1033 (ER_NOT_FORM_FILE): Incorrect information in file: '%-.200s'
MySQL error code 1034 (ER_NOT_KEYFILE): Incorrect key file for table '%-.200s'; try to repair it
MySQL error code 1035 (ER_OLD_KEYFILE): Old key file for table '%-.192s'; repair it!
MySQL error code 1036 (ER_OPEN_AS_READONLY): Table '%-.192s' is read only
MySQL error code 1037 (ER_OUTOFMEMORY): Out of memory; restart server and try again (needed %d bytes)
MySQL error code 1038 (ER_OUT_OF_SORTMEMORY): Out of sort memory, consider increasing server sort buffer size
MySQL error code 1039 (ER_UNEXPECTED_EOF): Unexpected EOF found when reading file '%-.192s' (errno: %d - %s)
MySQL error code 1040 (ER_CON_COUNT_ERROR): Too many connections
MySQL error code 1041 (ER_OUT_OF_RESOURCES): Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
MySQL error code 1042 (ER_BAD_HOST_ERROR): Can't get hostname for your address
MySQL error code 1043 (ER_HANDSHAKE_ERROR): Bad handshake
MySQL error code 1044 (ER_DBACCESS_DENIED_ERROR): Access denied for user '%-.48s'@'%-.64s' to database '%-.192s'
MySQL error code 1045 (ER_ACCESS_DENIED_ERROR): Access denied for user '%-.48s'@'%-.64s' (using password: %s)
MySQL error code 1046 (ER_NO_DB_ERROR): No database selected
MySQL error code 1047 (ER_UNKNOWN_COM_ERROR): Unknown command
MySQL error code 1048 (ER_BAD_NULL_ERROR): Column '%-.192s' cannot be null
MySQL error code 1049 (ER_BAD_DB_ERROR): Unknown database '%-.192s'
MySQL error code 1050 (ER_TABLE_EXISTS_ERROR): Table '%-.192s' already exists
MySQL error code 1051 (ER_BAD_TABLE_ERROR): Unknown table '%-.100s'
MySQL error code 1052 (ER_NON_UNIQ_ERROR): Column '%-.192s' in %-.192s is ambiguous
MySQL error code 1053 (ER_SERVER_SHUTDOWN): Server shutdown in progress
MySQL error code 1054 (ER_BAD_FIELD_ERROR): Unknown column '%-.192s' in '%-.192s'
MySQL error code 1055 (ER_WRONG_FIELD_WITH_GROUP): '%-.192s' isn't in GROUP BY
MySQL error code 1056 (ER_WRONG_GROUP_FIELD): Can't group on '%-.192s'
MySQL error code 1057 (ER_WRONG_SUM_SELECT): Statement has sum functions and columns in same statement
MySQL error code 1058 (ER_WRONG_VALUE_COUNT): Column count doesn't match value count
MySQL error code 1059 (ER_TOO_LONG_IDENT): Identifier name '%-.100s' is too long
MySQL error code 1060 (ER_DUP_FIELDNAME): Duplicate column name '%-.192s'
MySQL error code 1061 (ER_DUP_KEYNAME): Duplicate key name '%-.192s'
MySQL error code 1062 (ER_DUP_ENTRY): Duplicate entry '%-.192s' for key %d
MySQL error code 1063 (ER_WRONG_FIELD_SPEC): Incorrect column specifier for column '%-.192s'
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d
MySQL error code 1065 (ER_EMPTY_QUERY): Query was empty
MySQL error code 1066 (ER_NONUNIQ_TABLE): Not unique table/alias: '%-.192s'
MySQL error code 1067 (ER_INVALID_DEFAULT): Invalid default value for '%-.192s'
MySQL error code 1068 (ER_MULTIPLE_PRI_KEY): Multiple primary key defined
MySQL error code 1069 (ER_TOO_MANY_KEYS): Too many keys specified; max %d keys allowed
MySQL error code 1070 (ER_TOO_MANY_KEY_PARTS): Too many key parts specified; max %d parts allowed
MySQL error code 1071 (ER_TOO_LONG_KEY): Specified key was too long; max key length is %d bytes
MySQL error code 1072 (ER_KEY_COLUMN_DOES_NOT_EXITS): Key column '%-.192s' doesn't exist in table
MySQL error code 1073 (ER_BLOB_USED_AS_KEY): BLOB column '%-.192s' can't be used in key specification with the used table type
MySQL error code 1074 (ER_TOO_BIG_FIELDLENGTH): Column length too big for column '%-.192s' (max = %lu); use BLOB or TEXT instead
MySQL error code 1075 (ER_WRONG_AUTO_KEY): Incorrect table definition; there can be only one auto column and it must be defined as a key
MySQL error code 1076 (ER_READY): %s: ready for connections.
Version: '%s' socket: '%s' port: %d
MySQL error code 1077 (ER_NORMAL_SHUTDOWN): %s: Normal shutdown
MySQL error code 1078 (ER_GOT_SIGNAL): %s: Got signal %d. Aborting!
MySQL error code 1079 (ER_SHUTDOWN_COMPLETE): %s: Shutdown complete
MySQL error code 1080 (ER_FORCING_CLOSE): %s: Forcing close of thread %ld user: '%-.48s'
MySQL error code 1081 (ER_IPSOCK_ERROR): Can't create IP socket
MySQL error code 1082 (ER_NO_SUCH_INDEX): Table '%-.192s' has no index like the one used in CREATE INDEX; recreate the table
MySQL error code 1083 (ER_WRONG_FIELD_TERMINATORS): Field separator argument is not what is expected; check the manual
MySQL error code 1084 (ER_BLOBS_AND_NO_TERMINATED): You can't use fixed rowlength with BLOBs; please use 'fields terminated by'
MySQL error code 1085 (ER_TEXTFILE_NOT_READABLE): The file '%-.128s' must be in the database directory or be readable by all
MySQL error code 1086 (ER_FILE_EXISTS_ERROR): File '%-.200s' already exists
MySQL error code 1087 (ER_LOAD_INFO): Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
MySQL error code 1088 (ER_ALTER_INFO): Records: %ld Duplicates: %ld
MySQL error code 1089 (ER_WRONG_SUB_KEY): Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys
MySQL error code 1090 (ER_CANT_REMOVE_ALL_FIELDS): You can't delete all columns with ALTER TABLE; use DROP TABLE instead
MySQL error code 1091 (ER_CANT_DROP_FIELD_OR_KEY): Can't DROP '%-.192s'; check that column/key exists
MySQL error code 1092 (ER_INSERT_INFO): Records: %ld Duplicates: %ld Warnings: %ld
MySQL error code 1093 (ER_UPDATE_TABLE_USED): You can't specify target table '%-.192s' for update in FROM clause
MySQL error code 1094 (ER_NO_SUCH_THREAD): Unknown thread id: %lu
MySQL error code 1095 (ER_KILL_DENIED_ERROR): You are not owner of thread %lu
MySQL error code 1096 (ER_NO_TABLES_USED): No tables used
MySQL error code 1097 (ER_TOO_BIG_SET): Too many strings for column %-.192s and SET
MySQL error code 1098 (ER_NO_UNIQUE_LOGFILE): Can't generate a unique log-filename %-.200s.(1-999)
MySQL error code 1099 (ER_TABLE_NOT_LOCKED_FOR_WRITE): Table '%-.192s' was locked with a READ lock and can't be updated
MySQL error code 1100 (ER_TABLE_NOT_LOCKED): Table '%-.192s' was not locked with LOCK TABLES
MySQL error code 1101 (ER_BLOB_CANT_HAVE_DEFAULT): BLOB/TEXT column '%-.192s' can't have a default value
MySQL error code 1102 (ER_WRONG_DB_NAME): Incorrect database name '%-.100s'
MySQL error code 1103 (ER_WRONG_TABLE_NAME): Incorrect table name '%-.100s'
MySQL error code 1104 (ER_TOO_BIG_SELECT): The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
MySQL error code 1105 (ER_UNKNOWN_ERROR): Unknown error
MySQL error code 1106 (ER_UNKNOWN_PROCEDURE): Unknown procedure '%-.192s'
MySQL error code 1107 (ER_WRONG_PARAMCOUNT_TO_PROCEDURE): Incorrect parameter count to procedure '%-.192s'
MySQL error code 1108 (ER_WRONG_PARAMETERS_TO_PROCEDURE): Incorrect parameters to procedure '%-.192s'
MySQL error code 1109 (ER_UNKNOWN_TABLE): Unknown table '%-.192s' in %-.32s
MySQL error code 1110 (ER_FIELD_SPECIFIED_TWICE): Column '%-.192s' specified twice
MySQL error code 1111 (ER_INVALID_GROUP_FUNC_USE): Invalid use of group function
MySQL error code 1112 (ER_UNSUPPORTED_EXTENSION): Table '%-.192s' uses an extension that doesn't exist in this MySQL version
MySQL error code 1113 (ER_TABLE_MUST_HAVE_COLUMNS): A table must have at least 1 column
MySQL error code 1114 (ER_RECORD_FILE_FULL): The table '%-.192s' is full
MySQL error code 1115 (ER_UNKNOWN_CHARACTER_SET): Unknown character set: '%-.64s'
MySQL error code 1116 (ER_TOO_MANY_TABLES): Too many tables; MySQL can only use %d tables in a join
MySQL error code 1117 (ER_TOO_MANY_FIELDS): Too many columns
MySQL error code 1118 (ER_TOO_BIG_ROWSIZE): Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
MySQL error code 1119 (ER_STACK_OVERRUN): Thread stack overrun: Used: %ld of a %ld stack. Use 'mysqld --thread_stack=#' to specify a bigger stack if needed
MySQL error code 1120 (ER_WRONG_OUTER_JOIN): Cross dependency found in OUTER JOIN; examine your ON conditions
MySQL error code 1121 (ER_NULL_COLUMN_IN_INDEX): Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler
MySQL error code 1122 (ER_CANT_FIND_UDF): Can't load function '%-.192s'
MySQL error code 1123 (ER_CANT_INITIALIZE_UDF): Can't initialize function '%-.192s'; %-.80s
MySQL error code 1124 (ER_UDF_NO_PATHS): No paths allowed for shared library
MySQL error code 1125 (ER_UDF_EXISTS): Function '%-.192s' already exists
MySQL error code 1126 (ER_CANT_OPEN_LIBRARY): Can't open shared library '%-.192s' (errno: %d %-.128s)
MySQL error code 1127 (ER_CANT_FIND_DL_ENTRY): Can't find symbol '%-.128s' in library
MySQL error code 1128 (ER_FUNCTION_NOT_DEFINED): Function '%-.192s' is not defined
MySQL error code 1129 (ER_HOST_IS_BLOCKED): Host '%-.64s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
MySQL error code 1130 (ER_HOST_NOT_PRIVILEGED): Host '%-.64s' is not allowed to connect to this MySQL server
MySQL error code 1131 (ER_PASSWORD_ANONYMOUS_USER): You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords
MySQL error code 1132 (ER_PASSWORD_NOT_ALLOWED): You must have privileges to update tables in the mysql database to be able to change passwords for others
MySQL error code 1133 (ER_PASSWORD_NO_MATCH): Can't find any matching row in the user table
MySQL error code 1134 (ER_UPDATE_INFO): Rows matched: %ld Changed: %ld Warnings: %ld
MySQL error code 1135 (ER_CANT_CREATE_THREAD): Can't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
MySQL error code 1136 (ER_WRONG_VALUE_COUNT_ON_ROW): Column count doesn't match value count at row %ld
MySQL error code 1137 (ER_CANT_REOPEN_TABLE): Can't reopen table: '%-.192s'
MySQL error code 1138 (ER_INVALID_USE_OF_NULL): Invalid use of NULL value
MySQL error code 1139 (ER_REGEXP_ERROR): Got error '%-.64s' from regexp
MySQL error code 1140 (ER_MIX_OF_GROUP_FUNC_AND_FIELDS): Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause
MySQL error code 1141 (ER_NONEXISTING_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s'
MySQL error code 1142 (ER_TABLEACCESS_DENIED_ERROR): %-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'
MySQL error code 1143 (ER_COLUMNACCESS_DENIED_ERROR): %-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'
MySQL error code 1144 (ER_ILLEGAL_GRANT_FOR_TABLE): Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used
MySQL error code 1145 (ER_GRANT_WRONG_HOST_OR_USER): The host or user argument to GRANT is too long
MySQL error code 1146 (ER_NO_SUCH_TABLE): Table '%-.192s.%-.192s' doesn't exist
MySQL error code 1147 (ER_NONEXISTING_TABLE_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s' on table '%-.192s'
MySQL error code 1148 (ER_NOT_ALLOWED_COMMAND): The used command is not allowed with this MySQL version
MySQL error code 1149 (ER_SYNTAX_ERROR): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use
MySQL error code 1150 (ER_DELAYED_CANT_CHANGE_LOCK): Delayed insert thread couldn't get requested lock for table %-.192s
MySQL error code 1151 (ER_TOO_MANY_DELAYED_THREADS): Too many delayed threads in use
MySQL error code 1152 (ER_ABORTING_CONNECTION): Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)
MySQL error code 1153 (ER_NET_PACKET_TOO_LARGE): Got a packet bigger than 'max_allowed_packet' bytes
MySQL error code 1154 (ER_NET_READ_ERROR_FROM_PIPE): Got a read error from the connection pipe
MySQL error code 1155 (ER_NET_FCNTL_ERROR): Got an error from fcntl()
MySQL error code 1156 (ER_NET_PACKETS_OUT_OF_ORDER): Got packets out of order
MySQL error code 1157 (ER_NET_UNCOMPRESS_ERROR): Couldn't uncompress communication packet
MySQL error code 1158 (ER_NET_READ_ERROR): Got an error reading communication packets
MySQL error code 1159 (ER_NET_READ_INTERRUPTED): Got timeout reading communication packets
MySQL error code 1160 (ER_NET_ERROR_ON_WRITE): Got an error writing communication packets
MySQL error code 1161 (ER_NET_WRITE_INTERRUPTED): Got timeout writing communication packets
MySQL error code 1162 (ER_TOO_LONG_STRING): Result string is longer than 'max_allowed_packet' bytes
MySQL error code 1163 (ER_TABLE_CANT_HANDLE_BLOB): The used table type doesn't support BLOB/TEXT columns
MySQL error code 1164 (ER_TABLE_CANT_HANDLE_AUTO_INCREMENT): The used table type doesn't support AUTO_INCREMENT columns
MySQL error code 1165 (ER_DELAYED_INSERT_TABLE_LOCKED): INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES
MySQL error code 1166 (ER_WRONG_COLUMN_NAME): Incorrect column name '%-.100s'
MySQL error code 1167 (ER_WRONG_KEY_COLUMN): The used storage engine can't index column '%-.192s'
MySQL error code 1168 (ER_WRONG_MRG_TABLE): Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist
MySQL error code 1169 (ER_DUP_UNIQUE): Can't write, because of unique constraint, to table '%-.192s'
MySQL error code 1170 (ER_BLOB_KEY_WITHOUT_LENGTH): BLOB/TEXT column '%-.192s' used in key specification without a key length
MySQL error code 1171 (ER_PRIMARY_CANT_HAVE_NULL): All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead
MySQL error code 1172 (ER_TOO_MANY_ROWS): Result consisted of more than one row
MySQL error code 1173 (ER_REQUIRES_PRIMARY_KEY): This table type requires a primary key
MySQL error code 1174 (ER_NO_RAID_COMPILED): This version of MySQL is not compiled with RAID support
MySQL error code 1175 (ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE): You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
MySQL error code 1176 (ER_KEY_DOES_NOT_EXITS): Key '%-.192s' doesn't exist in table '%-.192s'
MySQL error code 1177 (ER_CHECK_NO_SUCH_TABLE): Can't open table
MySQL error code 1178 (ER_CHECK_NOT_IMPLEMENTED): The storage engine for the table doesn't support %s
MySQL error code 1179 (ER_CANT_DO_THIS_DURING_AN_TRANSACTION): You are not allowed to execute this command in a transaction
MySQL error code 1180 (ER_ERROR_DURING_COMMIT): Got error %d during COMMIT
MySQL error code 1181 (ER_ERROR_DURING_ROLLBACK): Got error %d during ROLLBACK
MySQL error code 1182 (ER_ERROR_DURING_FLUSH_LOGS): Got error %d during FLUSH_LOGS
MySQL error code 1183 (ER_ERROR_DURING_CHECKPOINT): Got error %d during CHECKPOINT
MySQL error code 1184 (ER_NEW_ABORTING_CONNECTION): Aborted connection %ld to db: '%-.192s' user: '%-.48s' host: '%-.64s' (%-.64s)
MySQL error code 1185 (ER_DUMP_NOT_IMPLEMENTED): The storage engine for the table does not support binary table dump
MySQL error code 1186 (ER_FLUSH_MASTER_BINLOG_CLOSED): Binlog closed, cannot RESET MASTER
MySQL error code 1187 (ER_INDEX_REBUILD): Failed rebuilding the index of dumped table '%-.192s'
MySQL error code 1188 (ER_MASTER): Error from master: '%-.64s'
MySQL error code 1189 (ER_MASTER_NET_READ): Net error reading from master
MySQL error code 1190 (ER_MASTER_NET_WRITE): Net error writing to master
MySQL error code 1191 (ER_FT_MATCHING_KEY_NOT_FOUND): Can't find FULLTEXT index matching the column list
MySQL error code 1192 (ER_LOCK_OR_ACTIVE_TRANSACTION): Can't execute the given command because you have active locked tables or an active transaction
MySQL error code 1193 (ER_UNKNOWN_SYSTEM_VARIABLE): Unknown system variable '%-.64s'
MySQL error code 1194 (ER_CRASHED_ON_USAGE): Table '%-.192s' is marked as crashed and should be repaired
MySQL error code 1195 (ER_CRASHED_ON_REPAIR): Table '%-.192s' is marked as crashed and last (automatic?) repair failed
MySQL error code 1196 (ER_WARNING_NOT_COMPLETE_ROLLBACK): Some non-transactional changed tables couldn't be rolled back
MySQL error code 1197 (ER_TRANS_CACHE_FULL): Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again
MySQL error code 1198 (ER_SLAVE_MUST_STOP): This operation cannot be performed with a running slave; run STOP SLAVE first
MySQL error code 1199 (ER_SLAVE_NOT_RUNNING): This operation requires a running slave; configure slave and do START SLAVE
MySQL error code 1200 (ER_BAD_SLAVE): The server is not configured as slave; fix in config file or with CHANGE MASTER TO
MySQL error code 1201 (ER_MASTER_INFO): Could not initialize master info structure; more error messages can be found in the MySQL error log
MySQL error code 1202 (ER_SLAVE_THREAD): Could not create slave thread; check system resources
MySQL error code 1203 (ER_TOO_MANY_USER_CONNECTIONS): User %-.64s already has more than 'max_user_connections' active connections
MySQL error code 1204 (ER_SET_CONSTANTS_ONLY): You may only use constant expressions with SET
MySQL error code 1205 (ER_LOCK_WAIT_TIMEOUT): Lock wait timeout exceeded; try restarting transaction
MySQL error code 1206 (ER_LOCK_TABLE_FULL): The total number of locks exceeds the lock table size
MySQL error code 1207 (ER_READ_ONLY_TRANSACTION): Update locks cannot be acquired during a READ UNCOMMITTED transaction
MySQL error code 1208 (ER_DROP_DB_WITH_READ_LOCK): DROP DATABASE not allowed while thread is holding global read lock
MySQL error code 1209 (ER_CREATE_DB_WITH_READ_LOCK): CREATE DATABASE not allowed while thread is holding global read lock
MySQL error code 1210 (ER_WRONG_ARGUMENTS): Incorrect arguments to %s
MySQL error code 1211 (ER_NO_PERMISSION_TO_CREATE_USER): '%-.48s'@'%-.64s' is not allowed to create new users
MySQL error code 1212 (ER_UNION_TABLES_IN_DIFFERENT_DIR): Incorrect table definition; all MERGE tables must be in the same database
MySQL error code 1213 (ER_LOCK_DEADLOCK): Deadlock found when trying to get lock; try restarting transaction
MySQL error code 1214 (ER_TABLE_CANT_HANDLE_FT): The used table type doesn't support FULLTEXT indexes
MySQL error code 1215 (ER_CANNOT_ADD_FOREIGN): Cannot add foreign key constraint
MySQL error code 1216 (ER_NO_REFERENCED_ROW): Cannot add or update a child row: a foreign key constraint fails
MySQL error code 1217 (ER_ROW_IS_REFERENCED): Cannot delete or update a parent row: a foreign key constraint fails
MySQL error code 1218 (ER_CONNECT_TO_MASTER): Error connecting to master: %-.128s
MySQL error code 1219 (ER_QUERY_ON_MASTER): Error running query on master: %-.128s
MySQL error code 1220 (ER_ERROR_WHEN_EXECUTING_COMMAND): Error when executing command %s: %-.128s
MySQL error code 1221 (ER_WRONG_USAGE): Incorrect usage of %s and %s
MySQL error code 1222 (ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT): The used SELECT statements have a different number of columns
MySQL error code 1223 (ER_CANT_UPDATE_WITH_READLOCK): Can't execute the query because you have a conflicting read lock
MySQL error code 1224 (ER_MIXING_NOT_ALLOWED): Mixing of transactional and non-transactional tables is disabled
MySQL error code 1225 (ER_DUP_ARGUMENT): Option '%s' used twice in statement
MySQL error code 1226 (ER_USER_LIMIT_REACHED): User '%-.64s' has exceeded the '%s' resource (current value: %ld)
MySQL error code 1227 (ER_SPECIFIC_ACCESS_DENIED_ERROR): Access denied; you need (at least one of) the %-.128s privilege(s) for this operation
MySQL error code 1228 (ER_LOCAL_VARIABLE): Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL
MySQL error code 1229 (ER_GLOBAL_VARIABLE): Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL
MySQL error code 1230 (ER_NO_DEFAULT): Variable '%-.64s' doesn't have a default value
MySQL error code 1231 (ER_WRONG_VALUE_FOR_VAR): Variable '%-.64s' can't be set to the value of '%-.200s'
MySQL error code 1232 (ER_WRONG_TYPE_FOR_VAR): Incorrect argument type to variable '%-.64s'
MySQL error code 1233 (ER_VAR_CANT_BE_READ): Variable '%-.64s' can only be set, not read
MySQL error code 1234 (ER_CANT_USE_OPTION_HERE): Incorrect usage/placement of '%s'
MySQL error code 1235 (ER_NOT_SUPPORTED_YET): This version of MySQL doesn't yet support '%s'
MySQL error code 1236 (ER_MASTER_FATAL_ERROR_READING_BINLOG): Got fatal error %d from master when reading data from binary log: '%-.320s'
MySQL error code 1237 (ER_SLAVE_IGNORED_TABLE): Slave SQL thread ignored the query because of replicate-*-table rules
MySQL error code 1238 (ER_INCORRECT_GLOBAL_LOCAL_VAR): Variable '%-.192s' is a %s variable
MySQL error code 1239 (ER_WRONG_FK_DEF): Incorrect foreign key definition for '%-.192s': %s
MySQL error code 1240 (ER_KEY_REF_DO_NOT_MATCH_TABLE_REF): Key reference and table reference don't match
MySQL error code 1241 (ER_OPERAND_COLUMNS): Operand should contain %d column(s)
MySQL error code 1242 (ER_SUBQUERY_NO_1_ROW): Subquery returns more than 1 row
MySQL error code 1243 (ER_UNKNOWN_STMT_HANDLER): Unknown prepared statement handler (%.*s) given to %s
MySQL error code 1244 (ER_CORRUPT_HELP_DB): Help database is corrupt or does not exist
MySQL error code 1245 (ER_CYCLIC_REFERENCE): Cyclic reference on subqueries
MySQL error code 1246 (ER_AUTO_CONVERT): Converting column '%s' from %s to %s
MySQL error code 1247 (ER_ILLEGAL_REFERENCE): Reference '%-.64s' not supported (%s)
MySQL error code 1248 (ER_DERIVED_MUST_HAVE_ALIAS): Every derived table must have its own alias
MySQL error code 1249 (ER_SELECT_REDUCED): Select %u was reduced during optimization
MySQL error code 1250 (ER_TABLENAME_NOT_ALLOWED_HERE): Table '%-.192s' from one of the SELECTs cannot be used in %-.32s
MySQL error code 1251 (ER_NOT_SUPPORTED_AUTH_MODE): Client does not support authentication protocol requested by server; consider upgrading MySQL client
MySQL error code 1252 (ER_SPATIAL_CANT_HAVE_NULL): All parts of a SPATIAL index must be NOT NULL
MySQL error code 1253 (ER_COLLATION_CHARSET_MISMATCH): COLLATION '%s' is not valid for CHARACTER SET '%s'
MySQL error code 1254 (ER_SLAVE_WAS_RUNNING): Slave is already running
MySQL error code 1255 (ER_SLAVE_WAS_NOT_RUNNING): Slave already has been stopped
MySQL error code 1256 (ER_TOO_BIG_FOR_UNCOMPRESS): Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)
MySQL error code 1257 (ER_ZLIB_Z_MEM_ERROR): ZLIB: Not enough memory
MySQL error code 1258 (ER_ZLIB_Z_BUF_ERROR): ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)
MySQL error code 1259 (ER_ZLIB_Z_DATA_ERROR): ZLIB: Input data corrupted
MySQL error code 1260 (ER_CUT_VALUE_GROUP_CONCAT): Row %u was cut by GROUP_CONCAT()
MySQL error code 1261 (ER_WARN_TOO_FEW_RECORDS): Row %ld doesn't contain data for all columns
MySQL error code 1262 (ER_WARN_TOO_MANY_RECORDS): Row %ld was truncated; it contained more data than there were input columns
MySQL error code 1263 (ER_WARN_NULL_TO_NOTNULL): Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld
MySQL error code 1264 (ER_WARN_DATA_OUT_OF_RANGE): Out of range value for column '%s' at row %ld
MySQL error code 1265 (WARN_DATA_TRUNCATED): Data truncated for column '%s' at row %ld
MySQL error code 1266 (ER_WARN_USING_OTHER_HANDLER): Using storage engine %s for table '%s'
MySQL error code 1267 (ER_CANT_AGGREGATE_2COLLATIONS): Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'
MySQL error code 1268 (ER_DROP_USER): Cannot drop one or more of the requested users
MySQL error code 1269 (ER_REVOKE_GRANTS): Can't revoke all privileges for one or more of the requested users
MySQL error code 1270 (ER_CANT_AGGREGATE_3COLLATIONS): Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'
MySQL error code 1271 (ER_CANT_AGGREGATE_NCOLLATIONS): Illegal mix of collations for operation '%s'
MySQL error code 1272 (ER_VARIABLE_IS_NOT_STRUCT): Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)
MySQL error code 1273 (ER_UNKNOWN_COLLATION): Unknown collation: '%-.64s'
MySQL error code 1274 (ER_SLAVE_IGNORED_SSL_PARAMS): SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started
MySQL error code 1275 (ER_SERVER_IS_IN_SECURE_AUTH_MODE): Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format
MySQL error code 1276 (ER_WARN_FIELD_RESOLVED): Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d
MySQL error code 1277 (ER_BAD_SLAVE_UNTIL_COND): Incorrect parameter or combination of parameters for START SLAVE UNTIL
MySQL error code 1278 (ER_MISSING_SKIP_SLAVE): It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave's mysqld restart
MySQL error code 1279 (ER_UNTIL_COND_IGNORED): SQL thread is not to be started so UNTIL options are ignored
MySQL error code 1280 (ER_WRONG_NAME_FOR_INDEX): Incorrect index name '%-.100s'
MySQL error code 1281 (ER_WRONG_NAME_FOR_CATALOG): Incorrect catalog name '%-.100s'
MySQL error code 1282 (ER_WARN_QC_RESIZE): Query cache failed to set size %lu; new query cache size is %lu
MySQL error code 1283 (ER_BAD_FT_COLUMN): Column '%-.192s' cannot be part of FULLTEXT index
MySQL error code 1284 (ER_UNKNOWN_KEY_CACHE): Unknown key cache '%-.100s'
MySQL error code 1285 (ER_WARN_HOSTNAME_WONT_WORK): MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work
MySQL error code 1286 (ER_UNKNOWN_STORAGE_ENGINE): Unknown storage engine '%s'
MySQL error code 1287 (ER_WARN_DEPRECATED_SYNTAX): '%s' is deprecated and will be removed in a future release. Please use %s instead
MySQL error code 1288 (ER_NON_UPDATABLE_TABLE): The target table %-.100s of the %s is not updatable
MySQL error code 1289 (ER_FEATURE_DISABLED): The '%s' feature is disabled; you need MySQL built with '%s' to have it working
MySQL error code 1290 (ER_OPTION_PREVENTS_STATEMENT): The MySQL server is running with the %s option so it cannot execute this statement
MySQL error code 1291 (ER_DUPLICATED_VALUE_IN_TYPE): Column '%-.100s' has duplicated value '%-.64s' in %s
MySQL error code 1292 (ER_TRUNCATED_WRONG_VALUE): Truncated incorrect %-.32s value: '%-.128s'
MySQL error code 1293 (ER_TOO_MUCH_AUTO_TIMESTAMP_COLS): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
MySQL error code 1294 (ER_INVALID_ON_UPDATE): Invalid ON UPDATE clause for '%-.192s' column
MySQL error code 1295 (ER_UNSUPPORTED_PS): This command is not supported in the prepared statement protocol yet
MySQL error code 1296 (ER_GET_ERRMSG): Got error %d '%-.100s' from %s
MySQL error code 1297 (ER_GET_TEMPORARY_ERRMSG): Got temporary error %d '%-.100s' from %s
MySQL error code 1298 (ER_UNKNOWN_TIME_ZONE): Unknown or incorrect time zone: '%-.64s'
MySQL error code 1299 (ER_WARN_INVALID_TIMESTAMP): Invalid TIMESTAMP value in column '%s' at row %ld
MySQL error code 1300 (ER_INVALID_CHARACTER_STRING): Invalid %s character string: '%.64s'
MySQL error code 1301 (ER_WARN_ALLOWED_PACKET_OVERFLOWED): Result of %s() was larger than max_allowed_packet (%ld) - truncated
MySQL error code 1302 (ER_CONFLICTING_DECLARATIONS): Conflicting declarations: '%s%s' and '%s%s'
MySQL error code 1303 (ER_SP_NO_RECURSIVE_CREATE): Can't create a %s from within another stored routine
MySQL error code 1304 (ER_SP_ALREADY_EXISTS): %s %s already exists
MySQL error code 1305 (ER_SP_DOES_NOT_EXIST): %s %s does not exist
MySQL error code 1306 (ER_SP_DROP_FAILED): Failed to DROP %s %s
MySQL error code 1307 (ER_SP_STORE_FAILED): Failed to CREATE %s %s
MySQL error code 1308 (ER_SP_LILABEL_MISMATCH): %s with no matching label: %s
MySQL error code 1309 (ER_SP_LABEL_REDEFINE): Redefining label %s
MySQL error code 1310 (ER_SP_LABEL_MISMATCH): End-label %s without match
MySQL error code 1311 (ER_SP_UNINIT_VAR): Referring to uninitialized variable %s
MySQL error code 1312 (ER_SP_BADSELECT): PROCEDURE %s can't return a result set in the given context
MySQL error code 1313 (ER_SP_BADRETURN): RETURN is only allowed in a FUNCTION
MySQL error code 1314 (ER_SP_BADSTATEMENT): %s is not allowed in stored procedures
MySQL error code 1315 (ER_UPDATE_LOG_DEPRECATED_IGNORED): The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.
MySQL error code 1316 (ER_UPDATE_LOG_DEPRECATED_TRANSLATED): The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.
MySQL error code 1317 (ER_QUERY_INTERRUPTED): Query execution was interrupted
MySQL error code 1318 (ER_SP_WRONG_NO_OF_ARGS): Incorrect number of arguments for %s %s; expected %u, got %u
MySQL error code 1319 (ER_SP_COND_MISMATCH): Undefined CONDITION: %s
MySQL error code 1320 (ER_SP_NORETURN): No RETURN found in FUNCTION %s
MySQL error code 1321 (ER_SP_NORETURNEND): FUNCTION %s ended without RETURN
MySQL error code 1322 (ER_SP_BAD_CURSOR_QUERY): Cursor statement must be a SELECT
MySQL error code 1323 (ER_SP_BAD_CURSOR_SELECT): Cursor SELECT must not have INTO
MySQL error code 1324 (ER_SP_CURSOR_MISMATCH): Undefined CURSOR: %s
MySQL error code 1325 (ER_SP_CURSOR_ALREADY_OPEN): Cursor is already open
MySQL error code 1326 (ER_SP_CURSOR_NOT_OPEN): Cursor is not open
MySQL error code 1327 (ER_SP_UNDECLARED_VAR): Undeclared variable: %s
MySQL error code 1328 (ER_SP_WRONG_NO_OF_FETCH_ARGS): Incorrect number of FETCH variables
MySQL error code 1329 (ER_SP_FETCH_NO_DATA): No data - zero rows fetched, selected, or processed
MySQL error code 1330 (ER_SP_DUP_PARAM): Duplicate parameter: %s
MySQL error code 1331 (ER_SP_DUP_VAR): Duplicate variable: %s
MySQL error code 1332 (ER_SP_DUP_COND): Duplicate condition: %s
MySQL error code 1333 (ER_SP_DUP_CURS): Duplicate cursor: %s
MySQL error code 1334 (ER_SP_CANT_ALTER): Failed to ALTER %s %s
MySQL error code 1335 (ER_SP_SUBSELECT_NYI): Subquery value not supported
MySQL error code 1336 (ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG): %s is not allowed in stored function or trigger
MySQL error code 1337 (ER_SP_VARCOND_AFTER_CURSHNDLR): Variable or condition declaration after cursor or handler declaration
MySQL error code 1338 (ER_SP_CURSOR_AFTER_HANDLER): Cursor declaration after handler declaration
MySQL error code 1339 (ER_SP_CASE_NOT_FOUND): Case not found for CASE statement
MySQL error code 1340 (ER_FPARSER_TOO_BIG_FILE): Configuration file '%-.192s' is too big
MySQL error code 1341 (ER_FPARSER_BAD_HEADER): Malformed file type header in file '%-.192s'
MySQL error code 1342 (ER_FPARSER_EOF_IN_COMMENT): Unexpected end of file while parsing comment '%-.200s'
MySQL error code 1343 (ER_FPARSER_ERROR_IN_PARAMETER): Error while parsing parameter '%-.192s' (line: '%-.192s')
MySQL error code 1344 (ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER): Unexpected end of file while skipping unknown parameter '%-.192s'
MySQL error code 1345 (ER_VIEW_NO_EXPLAIN): EXPLAIN/SHOW can not be issued; lacking privileges for underlying table
MySQL error code 1346 (ER_FRM_UNKNOWN_TYPE): File '%-.192s' has unknown type '%-.64s' in its header
MySQL error code 1347 (ER_WRONG_OBJECT): '%-.192s.%-.192s' is not %s
MySQL error code 1348 (ER_NONUPDATEABLE_COLUMN): Column '%-.192s' is not updatable
MySQL error code 1349 (ER_VIEW_SELECT_DERIVED): View's SELECT contains a subquery in the FROM clause
MySQL error code 1350 (ER_VIEW_SELECT_CLAUSE): View's SELECT contains a '%s' clause
MySQL error code 1351 (ER_VIEW_SELECT_VARIABLE): View's SELECT contains a variable or parameter
MySQL error code 1352 (ER_VIEW_SELECT_TMPTABLE): View's SELECT refers to a temporary table '%-.192s'
MySQL error code 1353 (ER_VIEW_WRONG_LIST): View's SELECT and view's field list have different column counts
MySQL error code 1354 (ER_WARN_VIEW_MERGE): View merge algorithm can't be used here for now (assumed undefined algorithm)
MySQL error code 1355 (ER_WARN_VIEW_WITHOUT_KEY): View being updated does not have complete key of underlying table in it
MySQL error code 1356 (ER_VIEW_INVALID): View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
MySQL error code 1357 (ER_SP_NO_DROP_SP): Can't drop or alter a %s from within another stored routine
MySQL error code 1358 (ER_SP_GOTO_IN_HNDLR): GOTO is not allowed in a stored procedure handler
MySQL error code 1359 (ER_TRG_ALREADY_EXISTS): Trigger already exists
MySQL error code 1360 (ER_TRG_DOES_NOT_EXIST): Trigger does not exist
MySQL error code 1361 (ER_TRG_ON_VIEW_OR_TEMP_TABLE): Trigger's '%-.192s' is view or temporary table
MySQL error code 1362 (ER_TRG_CANT_CHANGE_ROW): Updating of %s row is not allowed in %strigger
MySQL error code 1363 (ER_TRG_NO_SUCH_ROW_IN_TRG): There is no %s row in %s trigger
MySQL error code 1364 (ER_NO_DEFAULT_FOR_FIELD): Field '%-.192s' doesn't have a default value
MySQL error code 1365 (ER_DIVISION_BY_ZERO): Division by 0
MySQL error code 1366 (ER_TRUNCATED_WRONG_VALUE_FOR_FIELD): Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld
MySQL error code 1367 (ER_ILLEGAL_VALUE_FOR_TYPE): Illegal %s '%-.192s' value found during parsing
MySQL error code 1368 (ER_VIEW_NONUPD_CHECK): CHECK OPTION on non-updatable view '%-.192s.%-.192s'
MySQL error code 1369 (ER_VIEW_CHECK_FAILED): CHECK OPTION failed '%-.192s.%-.192s'
MySQL error code 1370 (ER_PROCACCESS_DENIED_ERROR): %-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'
MySQL error code 1371 (ER_RELAY_LOG_FAIL): Failed purging old relay logs: %s
MySQL error code 1372 (ER_PASSWD_LENGTH): Password hash should be a %d-digit hexadecimal number
MySQL error code 1373 (ER_UNKNOWN_TARGET_BINLOG): Target log not found in binlog index
MySQL error code 1374 (ER_IO_ERR_LOG_INDEX_READ): I/O error reading log index file
MySQL error code 1375 (ER_BINLOG_PURGE_PROHIBITED): Server configuration does not permit binlog purge
MySQL error code 1376 (ER_FSEEK_FAIL): Failed on fseek()
MySQL error code 1377 (ER_BINLOG_PURGE_FATAL_ERR): Fatal error during log purge
MySQL error code 1378 (ER_LOG_IN_USE): A purgeable log is in use, will not purge
MySQL error code 1379 (ER_LOG_PURGE_UNKNOWN_ERR): Unknown error during log purge
MySQL error code 1380 (ER_RELAY_LOG_INIT): Failed initializing relay log position: %s
MySQL error code 1381 (ER_NO_BINARY_LOGGING): You are not using binary logging
MySQL error code 1382 (ER_RESERVED_SYNTAX): The '%-.64s' syntax is reserved for purposes internal to the MySQL server
MySQL error code 1383 (ER_WSAS_FAILED): WSAStartup Failed
MySQL error code 1384 (ER_DIFF_GROUPS_PROC): Can't handle procedures with different groups yet
MySQL error code 1385 (ER_NO_GROUP_FOR_PROC): Select must have a group with this procedure
MySQL error code 1386 (ER_ORDER_WITH_PROC): Can't use ORDER clause with this procedure
MySQL error code 1387 (ER_LOGGING_PROHIBIT_CHANGING_OF): Binary logging and replication forbid changing the global server %s
MySQL error code 1388 (ER_NO_FILE_MAPPING): Can't map file: %-.200s, errno: %d
MySQL error code 1389 (ER_WRONG_MAGIC): Wrong magic in %-.64s
MySQL error code 1390 (ER_PS_MANY_PARAM): Prepared statement contains too many placeholders
MySQL error code 1391 (ER_KEY_PART_0): Key part '%-.192s' length cannot be 0
MySQL error code 1392 (ER_VIEW_CHECKSUM): View text checksum failed
MySQL error code 1393 (ER_VIEW_MULTIUPDATE): Can not modify more than one base table through a join view '%-.192s.%-.192s'
MySQL error code 1394 (ER_VIEW_NO_INSERT_FIELD_LIST): Can not insert into join view '%-.192s.%-.192s' without fields list
MySQL error code 1395 (ER_VIEW_DELETE_MERGE_VIEW): Can not delete from join view '%-.192s.%-.192s'
MySQL error code 1396 (ER_CANNOT_USER): Operation %s failed for %.256s
MySQL error code 1397 (ER_XAER_NOTA): XAER_NOTA: Unknown XID
MySQL error code 1398 (ER_XAER_INVAL): XAER_INVAL: Invalid arguments (or unsupported command)
MySQL error code 1399 (ER_XAER_RMFAIL): XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state
MySQL error code 1400 (ER_XAER_OUTSIDE): XAER_OUTSIDE: Some work is done outside global transaction
MySQL error code 1401 (ER_XAER_RMERR): XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency
MySQL error code 1402 (ER_XA_RBROLLBACK): XA_RBROLLBACK: Transaction branch was rolled back
MySQL error code 1403 (ER_NONEXISTING_PROC_GRANT): There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'
MySQL error code 1404 (ER_PROC_AUTO_GRANT_FAIL): Failed to grant EXECUTE and ALTER ROUTINE privileges
MySQL error code 1405 (ER_PROC_AUTO_REVOKE_FAIL): Failed to revoke all privileges to dropped routine
MySQL error code 1406 (ER_DATA_TOO_LONG): Data too long for column '%s' at row %ld
MySQL error code 1407 (ER_SP_BAD_SQLSTATE): Bad SQLSTATE: '%s'
MySQL error code 1408 (ER_STARTUP): %s: ready for connections.
Version: '%s' socket: '%s' port: %d %s
MySQL error code 1409 (ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR): Can't load value from file with fixed size rows to variable
MySQL error code 1410 (ER_CANT_CREATE_USER_WITH_GRANT): You are not allowed to create a user with GRANT
MySQL error code 1411 (ER_WRONG_VALUE_FOR_TYPE): Incorrect %-.32s value: '%-.128s' for function %-.32s
MySQL error code 1412 (ER_TABLE_DEF_CHANGED): Table definition has changed, please retry transaction
MySQL error code 1413 (ER_SP_DUP_HANDLER): Duplicate handler declared in the same block
MySQL error code 1414 (ER_SP_NOT_VAR_ARG): OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger
MySQL error code 1415 (ER_SP_NO_RETSET): Not allowed to return a result set from a %s
MySQL error code 1416 (ER_CANT_CREATE_GEOMETRY_OBJECT): Cannot get geometry object from data you send to the GEOMETRY field
MySQL error code 1417 (ER_FAILED_ROUTINE_BREAK_BINLOG): A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes
MySQL error code 1418 (ER_BINLOG_UNSAFE_ROUTINE): This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
MySQL error code 1419 (ER_BINLOG_CREATE_ROUTINE_NEED_SUPER): You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
MySQL error code 1420 (ER_EXEC_STMT_WITH_OPEN_CURSOR): You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.
MySQL error code 1421 (ER_STMT_HAS_NO_OPEN_CURSOR): The statement (%lu) has no open cursor.
MySQL error code 1422 (ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG): Explicit or implicit commit is not allowed in stored function or trigger.
MySQL error code 1423 (ER_NO_DEFAULT_FOR_VIEW_FIELD): Field of view '%-.192s.%-.192s' underlying table doesn't have a default value
MySQL error code 1424 (ER_SP_NO_RECURSION): Recursive stored functions and triggers are not allowed.
MySQL error code 1425 (ER_TOO_BIG_SCALE): Too big scale %d specified for column '%-.192s'. Maximum is %lu.
MySQL error code 1426 (ER_TOO_BIG_PRECISION): Too big precision %d specified for column '%-.192s'. Maximum is %lu.
MySQL error code 1427 (ER_M_BIGGER_THAN_D): For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').
MySQL error code 1428 (ER_WRONG_LOCK_OF_SYSTEM_TABLE): You can't combine write-locking of system tables with other tables or lock types
MySQL error code 1429 (ER_CONNECT_TO_FOREIGN_DATA_SOURCE): Unable to connect to foreign data source: %.64s
MySQL error code 1430 (ER_QUERY_ON_FOREIGN_DATA_SOURCE): There was a problem processing the query on the foreign data source. Data source error: %-.64s
MySQL error code 1431 (ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST): The foreign data source you are trying to reference does not exist. Data source error: %-.64s
MySQL error code 1432 (ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE): Can't create federated table. The data source connection string '%-.64s' is not in the correct format
MySQL error code 1433 (ER_FOREIGN_DATA_STRING_INVALID): The data source connection string '%-.64s' is not in the correct format
MySQL error code 1434 (ER_CANT_CREATE_FEDERATED_TABLE): Can't create federated table. Foreign data src error: %-.64s
MySQL error code 1435 (ER_TRG_IN_WRONG_SCHEMA): Trigger in wrong schema
MySQL error code 1436 (ER_STACK_OVERRUN_NEED_MORE): Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack.
MySQL error code 1437 (ER_TOO_LONG_BODY): Routine body for '%-.100s' is too long
MySQL error code 1438 (ER_WARN_CANT_DROP_DEFAULT_KEYCACHE): Cannot drop default keycache
MySQL error code 1439 (ER_TOO_BIG_DISPLAYWIDTH): Display width out of range for column '%-.192s' (max = %lu)
MySQL error code 1440 (ER_XAER_DUPID): XAER_DUPID: The XID already exists
MySQL error code 1441 (ER_DATETIME_FUNCTION_OVERFLOW): Datetime function: %-.32s field overflow
MySQL error code 1442 (ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG): Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.
MySQL error code 1443 (ER_VIEW_PREVENT_UPDATE): The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.
MySQL error code 1444 (ER_PS_NO_RECURSION): The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner
MySQL error code 1445 (ER_SP_CANT_SET_AUTOCOMMIT): Not allowed to set autocommit from a stored function or trigger
MySQL error code 1446 (ER_MALFORMED_DEFINER): Definer is not fully qualified
MySQL error code 1447 (ER_VIEW_FRM_NO_USER): View '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!
MySQL error code 1448 (ER_VIEW_OTHER_USER): You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definer
MySQL error code 1449 (ER_NO_SUCH_USER): The user specified as a definer ('%-.64s'@'%-.64s') does not exist
MySQL error code 1450 (ER_FORBID_SCHEMA_CHANGE): Changing schema from '%-.192s' to '%-.192s' is not allowed.
MySQL error code 1451 (ER_ROW_IS_REFERENCED_2): Cannot delete or update a parent row: a foreign key constraint fails (%.192s)
MySQL error code 1452 (ER_NO_REFERENCED_ROW_2): Cannot add or update a child row: a foreign key constraint fails (%.192s)
MySQL error code 1453 (ER_SP_BAD_VAR_SHADOW): Variable '%-.64s' must be quoted with `...`, or renamed
MySQL error code 1454 (ER_TRG_NO_DEFINER): No definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.
MySQL error code 1455 (ER_OLD_FILE_FORMAT): '%-.192s' has an old format, you should re-create the '%s' object(s)
MySQL error code 1456 (ER_SP_RECURSION_LIMIT): Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s
MySQL error code 1457 (ER_SP_PROC_TABLE_CORRUPT): Failed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)
MySQL error code 1458 (ER_SP_WRONG_NAME): Incorrect routine name '%-.192s'
MySQL error code 1459 (ER_TABLE_NEEDS_UPGRADE): Table upgrade required. Please do "REPAIR TABLE `%-.32s`" or dump/reload to fix it!
MySQL error code 1460 (ER_SP_NO_AGGREGATE): AGGREGATE is not supported for stored functions
MySQL error code 1461 (ER_MAX_PREPARED_STMT_COUNT_REACHED): Can't create more than max_prepared_stmt_count statements (current value: %lu)
MySQL error code 1462 (ER_VIEW_RECURSIVE): `%-.192s`.`%-.192s` contains view recursion
MySQL error code 1463 (ER_NON_GROUPING_FIELD_USED): Non-grouping field '%-.192s' is used in %-.64s clause
MySQL error code 1464 (ER_TABLE_CANT_HANDLE_SPKEYS): The used table type doesn't support SPATIAL indexes
MySQL error code 1465 (ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA): Triggers can not be created on system tables
MySQL error code 1466 (ER_REMOVED_SPACES): Leading spaces are removed from name '%s'
MySQL error code 1467 (ER_AUTOINC_READ_FAILED): Failed to read auto-increment value from storage engine
MySQL error code 1468 (ER_USERNAME): user name
MySQL error code 1469 (ER_HOSTNAME): host name
MySQL error code 1470 (ER_WRONG_STRING_LENGTH): String '%-.70s' is too long for %s (should be no longer than %d)
MySQL error code 1471 (ER_NON_INSERTABLE_TABLE): The target table %-.100s of the %s is not insertable-into
MySQL error code 1472 (ER_ADMIN_WRONG_MRG_TABLE): Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist
MySQL error code 1473 (ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT): Too high level of nesting for select
MySQL error code 1474 (ER_NAME_BECOMES_EMPTY): Name '%-.64s' has become ''
MySQL error code 1475 (ER_AMBIGUOUS_FIELD_TERM): First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
MySQL error code 1476 (ER_FOREIGN_SERVER_EXISTS): The foreign server, %s, you are trying to create already exists.
MySQL error code 1477 (ER_FOREIGN_SERVER_DOESNT_EXIST): The foreign server name you are trying to reference does not exist. Data source error: %-.64s
MySQL error code 1478 (ER_ILLEGAL_HA_CREATE_OPTION): Table storage engine '%-.64s' does not support the create option '%.64s'
MySQL error code 1479 (ER_PARTITION_REQUIRES_VALUES_ERROR): Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition
MySQL error code 1480 (ER_PARTITION_WRONG_VALUES_ERROR): Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition
MySQL error code 1481 (ER_PARTITION_MAXVALUE_ERROR): MAXVALUE can only be used in last partition definition
MySQL error code 1482 (ER_PARTITION_SUBPARTITION_ERROR): Subpartitions can only be hash partitions and by key
MySQL error code 1483 (ER_PARTITION_SUBPART_MIX_ERROR): Must define subpartitions on all partitions if on one partition
MySQL error code 1484 (ER_PARTITION_WRONG_NO_PART_ERROR): Wrong number of partitions defined, mismatch with previous setting
MySQL error code 1485 (ER_PARTITION_WRONG_NO_SUBPART_ERROR): Wrong number of subpartitions defined, mismatch with previous setting
MySQL error code 1486 (ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR): Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed
MySQL error code 1487 (ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR): Expression in RANGE/LIST VALUES must be constant
MySQL error code 1488 (ER_FIELD_NOT_FOUND_PART_ERROR): Field in list of fields for partition function not found in table
MySQL error code 1489 (ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR): List of fields is only allowed in KEY partitions
MySQL error code 1490 (ER_INCONSISTENT_PARTITION_INFO_ERROR): The partition info in the frm file is not consistent with what can be written into the frm file
MySQL error code 1491 (ER_PARTITION_FUNC_NOT_ALLOWED_ERROR): The %-.192s function returns the wrong type
MySQL error code 1492 (ER_PARTITIONS_MUST_BE_DEFINED_ERROR): For %-.64s partitions each partition must be defined
MySQL error code 1493 (ER_RANGE_NOT_INCREASING_ERROR): VALUES LESS THAN value must be strictly increasing for each partition
MySQL error code 1494 (ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR): VALUES value must be of same type as partition function
MySQL error code 1495 (ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR): Multiple definition of same constant in list partitioning
MySQL error code 1496 (ER_PARTITION_ENTRY_ERROR): Partitioning can not be used stand-alone in query
MySQL error code 1497 (ER_MIX_HANDLER_ERROR): The mix of handlers in the partitions is not allowed in this version of MySQL
MySQL error code 1498 (ER_PARTITION_NOT_DEFINED_ERROR): For the partitioned engine it is necessary to define all %-.64s
MySQL error code 1499 (ER_TOO_MANY_PARTITIONS_ERROR): Too many partitions (including subpartitions) were defined
MySQL error code 1500 (ER_SUBPARTITION_ERROR): It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning
MySQL error code 1501 (ER_CANT_CREATE_HANDLER_FILE): Failed to create specific handler file
MySQL error code 1502 (ER_BLOB_FIELD_IN_PART_FUNC_ERROR): A BLOB field is not allowed in partition function
MySQL error code 1503 (ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF): A %-.192s must include all columns in the table's partitioning function
MySQL error code 1504 (ER_NO_PARTS_ERROR): Number of %-.64s = 0 is not an allowed value
MySQL error code 1505 (ER_PARTITION_MGMT_ON_NONPARTITIONED): Partition management on a not partitioned table is not possible
MySQL error code 1506 (ER_FOREIGN_KEY_ON_PARTITIONED): Foreign key clause is not yet supported in conjunction with partitioning
MySQL error code 1507 (ER_DROP_PARTITION_NON_EXISTENT): Error in list of partitions to %-.64s
MySQL error code 1508 (ER_DROP_LAST_PARTITION): Cannot remove all partitions, use DROP TABLE instead
MySQL error code 1509 (ER_COALESCE_ONLY_ON_HASH_PARTITION): COALESCE PARTITION can only be used on HASH/KEY partitions
MySQL error code 1510 (ER_REORG_HASH_ONLY_ON_SAME_NO): REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers
MySQL error code 1511 (ER_REORG_NO_PARAM_ERROR): REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs
MySQL error code 1512 (ER_ONLY_ON_RANGE_LIST_PARTITION): %-.64s PARTITION can only be used on RANGE/LIST partitions
MySQL error code 1513 (ER_ADD_PARTITION_SUBPART_ERROR): Trying to Add partition(s) with wrong number of subpartitions
MySQL error code 1514 (ER_ADD_PARTITION_NO_NEW_PARTITION): At least one partition must be added
MySQL error code 1515 (ER_COALESCE_PARTITION_NO_PARTITION): At least one partition must be coalesced
MySQL error code 1516 (ER_REORG_PARTITION_NOT_EXIST): More partitions to reorganize than there are partitions
MySQL error code 1517 (ER_SAME_NAME_PARTITION): Duplicate partition name %-.192s
MySQL error code 1518 (ER_NO_BINLOG_ERROR): It is not allowed to shut off binlog on this command
MySQL error code 1519 (ER_CONSECUTIVE_REORG_PARTITIONS): When reorganizing a set of partitions they must be in consecutive order
MySQL error code 1520 (ER_REORG_OUTSIDE_RANGE): Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range
MySQL error code 1521 (ER_PARTITION_FUNCTION_FAILURE): Partition function not supported in this version for this handler
MySQL error code 1522 (ER_PART_STATE_ERROR): Partition state cannot be defined from CREATE/ALTER TABLE
MySQL error code 1523 (ER_LIMITED_PART_RANGE): The %-.64s handler only supports 32 bit integers in VALUES
MySQL error code 1524 (ER_PLUGIN_IS_NOT_LOADED): Plugin '%-.192s' is not loaded
MySQL error code 1525 (ER_WRONG_VALUE): Incorrect %-.32s value: '%-.128s'
MySQL error code 1526 (ER_NO_PARTITION_FOR_GIVEN_VALUE): Table has no partition for value %-.64s
MySQL error code 1527 (ER_FILEGROUP_OPTION_ONLY_ONCE): It is not allowed to specify %s more than once
MySQL error code 1528 (ER_CREATE_FILEGROUP_FAILED): Failed to create %s
MySQL error code 1529 (ER_DROP_FILEGROUP_FAILED): Failed to drop %s
MySQL error code 1530 (ER_TABLESPACE_AUTO_EXTEND_ERROR): The handler doesn't support autoextend of tablespaces
MySQL error code 1531 (ER_WRONG_SIZE_NUMBER): A size parameter was incorrectly specified, either number or on the form 10M
MySQL error code 1532 (ER_SIZE_OVERFLOW_ERROR): The size number was correct but we don't allow the digit part to be more than 2 billion
MySQL error code 1533 (ER_ALTER_FILEGROUP_FAILED): Failed to alter: %s
MySQL error code 1534 (ER_BINLOG_ROW_LOGGING_FAILED): Writing one row to the row-based binary log failed
MySQL error code 1535 (ER_BINLOG_ROW_WRONG_TABLE_DEF): Table definition on master and slave does not match: %s
MySQL error code 1536 (ER_BINLOG_ROW_RBR_TO_SBR): Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events
MySQL error code 1537 (ER_EVENT_ALREADY_EXISTS): Event '%-.192s' already exists
MySQL error code 1538 (ER_EVENT_STORE_FAILED): Failed to store event %s. Error code %d from storage engine.
MySQL error code 1539 (ER_EVENT_DOES_NOT_EXIST): Unknown event '%-.192s'
MySQL error code 1540 (ER_EVENT_CANT_ALTER): Failed to alter event '%-.192s'
MySQL error code 1541 (ER_EVENT_DROP_FAILED): Failed to drop %s
MySQL error code 1542 (ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG): INTERVAL is either not positive or too big
MySQL error code 1543 (ER_EVENT_ENDS_BEFORE_STARTS): ENDS is either invalid or before STARTS
MySQL error code 1544 (ER_EVENT_EXEC_TIME_IN_THE_PAST): Event execution time is in the past. Event has been disabled
MySQL error code 1545 (ER_EVENT_OPEN_TABLE_FAILED): Failed to open mysql.event
MySQL error code 1546 (ER_EVENT_NEITHER_M_EXPR_NOR_M_AT): No datetime expression provided
MySQL error code 1547 (ER_OBSOLETE_COL_COUNT_DOESNT_MATCH_CORRUPTED): Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted
MySQL error code 1548 (ER_OBSOLETE_CANNOT_LOAD_FROM_TABLE): Cannot load from mysql.%s. The table is probably corrupted
MySQL error code 1549 (ER_EVENT_CANNOT_DELETE): Failed to delete the event from mysql.event
MySQL error code 1550 (ER_EVENT_COMPILE_ERROR): Error during compilation of event's body
MySQL error code 1551 (ER_EVENT_SAME_NAME): Same old and new event name
MySQL error code 1552 (ER_EVENT_DATA_TOO_LONG): Data for column '%s' too long
MySQL error code 1553 (ER_DROP_INDEX_FK): Cannot drop index '%-.192s': needed in a foreign key constraint
MySQL error code 1554 (ER_WARN_DEPRECATED_SYNTAX_WITH_VER): The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead
MySQL error code 1555 (ER_CANT_WRITE_LOCK_LOG_TABLE): You can't write-lock a log table. Only read access is possible
MySQL error code 1556 (ER_CANT_LOCK_LOG_TABLE): You can't use locks with log tables.
MySQL error code 1557 (ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED): Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry
MySQL error code 1558 (ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE): Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.
MySQL error code 1559 (ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR): Cannot switch out of the row-based binary log format when the session has open temporary tables
MySQL error code 1560 (ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT): Cannot change the binary logging format inside a stored function or trigger
MySQL error code 1561 (ER_NDB_CANT_SWITCH_BINLOG_FORMAT): The NDB cluster engine does not support changing the binlog format on the fly yet
MySQL error code 1562 (ER_PARTITION_NO_TEMPORARY): Cannot create temporary table with partitions
MySQL error code 1563 (ER_PARTITION_CONST_DOMAIN_ERROR): Partition constant is out of partition function domain
MySQL error code 1564 (ER_PARTITION_FUNCTION_IS_NOT_ALLOWED): This partition function is not allowed
MySQL error code 1565 (ER_DDL_LOG_ERROR): Error in DDL log
MySQL error code 1566 (ER_NULL_IN_VALUES_LESS_THAN): Not allowed to use NULL value in VALUES LESS THAN
MySQL error code 1567 (ER_WRONG_PARTITION_NAME): Incorrect partition name
MySQL error code 1568 (ER_CANT_CHANGE_TX_CHARACTERISTICS): Transaction characteristics can't be changed while a transaction is in progress
MySQL error code 1569 (ER_DUP_ENTRY_AUTOINCREMENT_CASE): ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'
MySQL error code 1570 (ER_EVENT_MODIFY_QUEUE_ERROR): Internal scheduler error %d
MySQL error code 1571 (ER_EVENT_SET_VAR_ERROR): Error during starting/stopping of the scheduler. Error code %u
MySQL error code 1572 (ER_PARTITION_MERGE_ERROR): Engine cannot be used in partitioned tables
MySQL error code 1573 (ER_CANT_ACTIVATE_LOG): Cannot activate '%-.64s' log
MySQL error code 1574 (ER_RBR_NOT_AVAILABLE): The server was not built with row-based replication
MySQL error code 1575 (ER_BASE64_DECODE_ERROR): Decoding of base64 string failed
MySQL error code 1576 (ER_EVENT_RECURSION_FORBIDDEN): Recursion of EVENT DDL statements is forbidden when body is present
MySQL error code 1577 (ER_EVENTS_DB_ERROR): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
MySQL error code 1578 (ER_ONLY_INTEGERS_ALLOWED): Only integers allowed as number here
MySQL error code 1579 (ER_UNSUPORTED_LOG_ENGINE): This storage engine cannot be used for log tables"
MySQL error code 1580 (ER_BAD_LOG_STATEMENT): You cannot '%s' a log table if logging is enabled
MySQL error code 1581 (ER_CANT_RENAME_LOG_TABLE): Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'
MySQL error code 1582 (ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT): Incorrect parameter count in the call to native function '%-.192s'
MySQL error code 1583 (ER_WRONG_PARAMETERS_TO_NATIVE_FCT): Incorrect parameters in the call to native function '%-.192s'
MySQL error code 1584 (ER_WRONG_PARAMETERS_TO_STORED_FCT): Incorrect parameters in the call to stored function '%-.192s'
MySQL error code 1585 (ER_NATIVE_FCT_NAME_COLLISION): This function '%-.192s' has the same name as a native function
MySQL error code 1586 (ER_DUP_ENTRY_WITH_KEY_NAME): Duplicate entry '%-.64s' for key '%-.192s'
MySQL error code 1587 (ER_BINLOG_PURGE_EMFILE): Too many files opened, please execute the command again
MySQL error code 1588 (ER_EVENT_CANNOT_CREATE_IN_THE_PAST): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
MySQL error code 1589 (ER_EVENT_CANNOT_ALTER_IN_THE_PAST): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.
MySQL error code 1590 (ER_SLAVE_INCIDENT): The incident %s occured on the master. Message: %-.64s
MySQL error code 1591 (ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT): Table has no partition for some existing values
MySQL error code 1592 (ER_BINLOG_UNSAFE_STATEMENT): Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s
MySQL error code 1593 (ER_SLAVE_FATAL_ERROR): Fatal error: %s
MySQL error code 1594 (ER_SLAVE_RELAY_LOG_READ_FAILURE): Relay log read failure: %s
MySQL error code 1595 (ER_SLAVE_RELAY_LOG_WRITE_FAILURE): Relay log write failure: %s
MySQL error code 1596 (ER_SLAVE_CREATE_EVENT_FAILURE): Failed to create %s
MySQL error code 1597 (ER_SLAVE_MASTER_COM_FAILURE): Master command %s failed: %s
MySQL error code 1598 (ER_BINLOG_LOGGING_IMPOSSIBLE): Binary logging not possible. Message: %s
MySQL error code 1599 (ER_VIEW_NO_CREATION_CTX): View `%-.64s`.`%-.64s` has no creation context
MySQL error code 1600 (ER_VIEW_INVALID_CREATION_CTX): Creation context of view `%-.64s`.`%-.64s' is invalid
MySQL error code 1601 (ER_SR_INVALID_CREATION_CTX): Creation context of stored routine `%-.64s`.`%-.64s` is invalid
MySQL error code 1602 (ER_TRG_CORRUPTED_FILE): Corrupted TRG file for table `%-.64s`.`%-.64s`
MySQL error code 1603 (ER_TRG_NO_CREATION_CTX): Triggers for table `%-.64s`.`%-.64s` have no creation context
MySQL error code 1604 (ER_TRG_INVALID_CREATION_CTX): Trigger creation context of table `%-.64s`.`%-.64s` is invalid
MySQL error code 1605 (ER_EVENT_INVALID_CREATION_CTX): Creation context of event `%-.64s`.`%-.64s` is invalid
MySQL error code 1606 (ER_TRG_CANT_OPEN_TABLE): Cannot open table for trigger `%-.64s`.`%-.64s`
MySQL error code 1607 (ER_CANT_CREATE_SROUTINE): Cannot create stored routine `%-.64s`. Check warnings
MySQL error code 1608 (ER_NEVER_USED): Ambiguous slave modes combination. %s
MySQL error code 1609 (ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT): The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.
MySQL error code 1610 (ER_SLAVE_CORRUPT_EVENT): Corrupted replication event was detected
MySQL error code 1611 (ER_LOAD_DATA_INVALID_COLUMN): Invalid column reference (%-.64s) in LOAD DATA
MySQL error code 1612 (ER_LOG_PURGE_NO_FILE): Being purged log %s was not found
MySQL error code 1613 (ER_XA_RBTIMEOUT): XA_RBTIMEOUT: Transaction branch was rolled back: took too long
MySQL error code 1614 (ER_XA_RBDEADLOCK): XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
MySQL error code 1615 (ER_NEED_REPREPARE): Prepared statement needs to be re-prepared
MySQL error code 1616 (ER_DELAYED_NOT_SUPPORTED): DELAYED option not supported for table '%-.192s'
MySQL error code 1617 (WARN_NO_MASTER_INFO): The master info structure does not exist
MySQL error code 1618 (WARN_OPTION_IGNORED): <%-.64s> option ignored
MySQL error code 1619 (WARN_PLUGIN_DELETE_BUILTIN): Built-in plugins cannot be deleted
MySQL error code 1620 (WARN_PLUGIN_BUSY): Plugin is busy and will be uninstalled on shutdown
MySQL error code 1621 (ER_VARIABLE_IS_READONLY): %s variable '%s' is read-only. Use SET %s to assign the value
MySQL error code 1622 (ER_WARN_ENGINE_TRANSACTION_ROLLBACK): Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted
MySQL error code 1623 (ER_SLAVE_HEARTBEAT_FAILURE): Unexpected master's heartbeat data: %s
MySQL error code 1624 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE): The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).
MySQL error code 1625 (ER_NDB_REPLICATION_SCHEMA_ERROR): Bad schema for mysql.ndb_replication table. Message: %-.64s
MySQL error code 1626 (ER_CONFLICT_FN_PARSE_ERROR): Error in parsing conflict function. Message: %-.64s
MySQL error code 1627 (ER_EXCEPTIONS_WRITE_ERROR): Write to exceptions table failed. Message: %-.128s"
MySQL error code 1628 (ER_TOO_LONG_TABLE_COMMENT): Comment for table '%-.64s' is too long (max = %lu)
MySQL error code 1629 (ER_TOO_LONG_FIELD_COMMENT): Comment for field '%-.64s' is too long (max = %lu)
MySQL error code 1630 (ER_FUNC_INEXISTENT_NAME_COLLISION): FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual
MySQL error code 1631 (ER_DATABASE_NAME): Database
MySQL error code 1632 (ER_TABLE_NAME): Table
MySQL error code 1633 (ER_PARTITION_NAME): Partition
MySQL error code 1634 (ER_SUBPARTITION_NAME): Subpartition
MySQL error code 1635 (ER_TEMPORARY_NAME): Temporary
MySQL error code 1636 (ER_RENAMED_NAME): Renamed
MySQL error code 1637 (ER_TOO_MANY_CONCURRENT_TRXS): Too many active concurrent transactions
MySQL error code 1638 (WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED): Non-ASCII separator arguments are not fully supported
MySQL error code 1639 (ER_DEBUG_SYNC_TIMEOUT): debug sync point wait timed out
MySQL error code 1640 (ER_DEBUG_SYNC_HIT_LIMIT): debug sync point hit limit reached
MySQL error code 1641 (ER_DUP_SIGNAL_SET): Duplicate condition information item '%s'
MySQL error code 1642 (ER_SIGNAL_WARN): Unhandled user-defined warning condition
MySQL error code 1643 (ER_SIGNAL_NOT_FOUND): Unhandled user-defined not found condition
MySQL error code 1644 (ER_SIGNAL_EXCEPTION): Unhandled user-defined exception condition
MySQL error code 1645 (ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER): RESIGNAL when handler not active
MySQL error code 1646 (ER_SIGNAL_BAD_CONDITION_TYPE): SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE
MySQL error code 1647 (WARN_COND_ITEM_TRUNCATED): Data truncated for condition item '%s'
MySQL error code 1648 (ER_COND_ITEM_TOO_LONG): Data too long for condition item '%s'
MySQL error code 1649 (ER_UNKNOWN_LOCALE): Unknown locale: '%-.64s'
MySQL error code 1650 (ER_SLAVE_IGNORE_SERVER_IDS): The requested server id %d clashes with the slave startup option --replicate-same-server-id
MySQL error code 1651 (ER_QUERY_CACHE_DISABLED): Query cache is disabled; restart the server with query_cache_type=1 to enable it
MySQL error code 1652 (ER_SAME_NAME_PARTITION_FIELD): Duplicate partition field name '%-.192s'
MySQL error code 1653 (ER_PARTITION_COLUMN_LIST_ERROR): Inconsistency in usage of column lists for partitioning
MySQL error code 1654 (ER_WRONG_TYPE_COLUMN_VALUE_ERROR): Partition column values of incorrect type
MySQL error code 1655 (ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR): Too many fields in '%-.192s'
MySQL error code 1656 (ER_MAXVALUE_IN_VALUES_IN): Cannot use MAXVALUE as value in VALUES IN
MySQL error code 1657 (ER_TOO_MANY_VALUES_ERROR): Cannot have more than one value for this type of %-.64s partitioning
MySQL error code 1658 (ER_ROW_SINGLE_PARTITION_FIELD_ERROR): Row expressions in VALUES IN only allowed for multi-field column partitioning
MySQL error code 1659 (ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD): Field '%-.192s' is of a not allowed type for this type of partitioning
MySQL error code 1660 (ER_PARTITION_FIELDS_TOO_LONG): The total length of the partitioning fields is too large
MySQL error code 1661 (ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE): Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.
MySQL error code 1662 (ER_BINLOG_ROW_MODE_AND_STMT_ENGINE): 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.
MySQL error code 1663 (ER_BINLOG_UNSAFE_AND_STMT_ENGINE): 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. %s
MySQL error code 1664 (ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE): 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.
MySQL error code 1665 (ER_BINLOG_STMT_MODE_AND_ROW_ENGINE): 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.%s
MySQL error code 1666 (ER_BINLOG_ROW_INJECTION_AND_STMT_MODE): Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.
MySQL error code 1667 (ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE): Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.
MySQL error code 1668 (ER_BINLOG_UNSAFE_LIMIT): The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
MySQL error code 1669 (ER_BINLOG_UNSAFE_INSERT_DELAYED): The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.
MySQL error code 1670 (ER_BINLOG_UNSAFE_SYSTEM_TABLE): 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.
MySQL error code 1671 (ER_BINLOG_UNSAFE_AUTOINC_COLUMNS): 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.
MySQL error code 1672 (ER_BINLOG_UNSAFE_UDF): Statement is unsafe because it uses a UDF which may not return the same value on the slave.
MySQL error code 1673 (ER_BINLOG_UNSAFE_SYSTEM_VARIABLE): Statement is unsafe because it uses a system variable that may have a different value on the slave.
MySQL error code 1674 (ER_BINLOG_UNSAFE_SYSTEM_FUNCTION): Statement is unsafe because it uses a system function that may return a different value on the slave.
MySQL error code 1675 (ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS): Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.
MySQL error code 1676 (ER_MESSAGE_AND_STATEMENT): %s Statement: %s
MySQL error code 1677 (ER_SLAVE_CONVERSION_FAILED): Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'
MySQL error code 1678 (ER_SLAVE_CANT_CREATE_CONVERSION): Can't create conversion table for table '%-.192s.%-.192s'
MySQL error code 1679 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT): Cannot modify @@session.binlog_format inside a transaction
MySQL error code 1680 (ER_PATH_LENGTH): The path specified for %.64s is too long.
MySQL error code 1681 (ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT): '%s' is deprecated and will be removed in a future release.
MySQL error code 1682 (ER_WRONG_NATIVE_TABLE_STRUCTURE): Native table '%-.64s'.'%-.64s' has the wrong structure
MySQL error code 1683 (ER_WRONG_PERFSCHEMA_USAGE): Invalid performance_schema usage.
MySQL error code 1684 (ER_WARN_I_S_SKIPPED_TABLE): Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement
MySQL error code 1685 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT): Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction
MySQL error code 1686 (ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT): Cannot change the binlog direct flag inside a stored function or trigger
MySQL error code 1687 (ER_SPATIAL_MUST_HAVE_GEOM_COL): A SPATIAL index may only contain a geometrical type column
MySQL error code 1688 (ER_TOO_LONG_INDEX_COMMENT): Comment for index '%-.64s' is too long (max = %lu)
MySQL error code 1689 (ER_LOCK_ABORTED): Wait on a lock was aborted due to a pending exclusive lock
MySQL error code 1690 (ER_DATA_OUT_OF_RANGE): %s value is out of range in '%s'
MySQL error code 1691 (ER_WRONG_SPVAR_TYPE_IN_LIMIT): A variable of a non-integer based type in LIMIT clause
MySQL error code 1692 (ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE): Mixing self-logging and non-self-logging engines in a statement is unsafe.
MySQL error code 1693 (ER_BINLOG_UNSAFE_MIXED_STATEMENT): Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
MySQL error code 1694 (ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN): Cannot modify @@session.sql_log_bin inside a transaction
MySQL error code 1695 (ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN): Cannot change the sql_log_bin inside a stored function or trigger
MySQL error code 1696 (ER_FAILED_READ_FROM_PAR_FILE): Failed to read from the .par file
MySQL error code 1697 (ER_VALUES_IS_NOT_INT_TYPE_ERROR): VALUES value for partition '%-.64s' must have type INT
MySQL error code 1698 (ER_ACCESS_DENIED_NO_PASSWORD_ERROR): Access denied for user '%-.48s'@'%-.64s'
MySQL error code 1699 (ER_SET_PASSWORD_AUTH_PLUGIN): SET PASSWORD has no significance for users authenticating via plugins
MySQL error code 1700 (ER_GRANT_PLUGIN_USER_EXISTS): GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists
MySQL error code 1701 (ER_TRUNCATE_ILLEGAL_FK): Cannot truncate a table referenced in a foreign key constraint (%.192s)
MySQL error code 1702 (ER_PLUGIN_IS_PERMANENT): Plugin '%s' is force_plus_permanent and can not be unloaded
MySQL error code 1703 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN): The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.
MySQL error code 1704 (ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX): The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.
MySQL error code 1705 (ER_STMT_CACHE_FULL): Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again
MySQL error code 1706 (ER_MULTI_UPDATE_KEY_CONFLICT): Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.
MySQL error code 1707 (ER_TABLE_NEEDS_REBUILD): Table rebuild required. Please do "ALTER TABLE `%-.32s` FORCE" or dump/reload to fix it!
MySQL error code 1708 (WARN_OPTION_BELOW_LIMIT): The value of '%s' should be no less than the value of '%s'
MySQL error code 1709 (ER_INDEX_COLUMN_TOO_LONG): Index column size too large. The maximum column size is %lu bytes.
MySQL error code 1710 (ER_ERROR_IN_TRIGGER_BODY): Trigger '%-.64s' has an error in its body: '%-.256s'
MySQL error code 1711 (ER_ERROR_IN_UNKNOWN_TRIGGER_BODY): Unknown trigger has an error in its body: '%-.256s'
MySQL error code 1712 (ER_INDEX_CORRUPT): Index %s is corrupted
MySQL error code 1713 (ER_UNDO_RECORD_TOO_BIG): Undo log record is too big.
MySQL error code 1714 (ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT): INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1715 (ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE): INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1716 (ER_BINLOG_UNSAFE_REPLACE_SELECT): REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1717 (ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT): CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1718 (ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT): CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1719 (ER_BINLOG_UNSAFE_UPDATE_IGNORE): UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1720 (ER_PLUGIN_NO_UNINSTALL): Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.
MySQL error code 1721 (ER_PLUGIN_NO_INSTALL): Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.
MySQL error code 1722 (ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT): Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1723 (ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC): CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.
MySQL error code 1724 (ER_BINLOG_UNSAFE_INSERT_TWO_KEYS): INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe
MySQL error code 1725 (ER_TABLE_IN_FK_CHECK): Table is being used in foreign key check.
MySQL error code 1726 (ER_UNSUPPORTED_ENGINE): Storage engine '%s' does not support system tables. [%s.%s]
MySQL error code 1727 (ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST): INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.
MySQL error code 1728 (ER_CANNOT_LOAD_FROM_TABLE_V2): Cannot load from %s.%s. The table is probably corrupted
MySQL error code 1729 (ER_MASTER_DELAY_VALUE_OUT_OF_RANGE): The requested value %s for the master delay exceeds the maximum %u
MySQL error code 1730 (ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT): Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)
MySQL error code 1731 (ER_PARTITION_EXCHANGE_DIFFERENT_OPTION): Non matching attribute '%-.64s' between partition and table
MySQL error code 1732 (ER_PARTITION_EXCHANGE_PART_TABLE): Table to exchange with partition is partitioned: '%-.64s'
MySQL error code 1733 (ER_PARTITION_EXCHANGE_TEMP_TABLE): Table to exchange with partition is temporary: '%-.64s'
MySQL error code 1734 (ER_PARTITION_INSTEAD_OF_SUBPARTITION): Subpartitioned table, use subpartition instead of partition
MySQL error code 1735 (ER_UNKNOWN_PARTITION): Unknown partition '%-.64s' in table '%-.64s'
MySQL error code 1736 (ER_TABLES_DIFFERENT_METADATA): Tables have different definitions
MySQL error code 1737 (ER_ROW_DOES_NOT_MATCH_PARTITION): Found a row that does not match the partition
MySQL error code 1738 (ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX): Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.
MySQL error code 1739 (ER_WARN_INDEX_NOT_APPLICABLE): Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'
MySQL error code 1740 (ER_PARTITION_EXCHANGE_FOREIGN_KEY): Table to exchange with partition has foreign key references: '%-.64s'
MySQL error code 1741 (ER_NO_SUCH_KEY_VALUE): Key value '%-.192s' was not found in table '%-.192s.%-.192s'
MySQL error code 1742 (ER_RPL_INFO_DATA_TOO_LONG): Data for column '%s' too long
MySQL error code 1743 (ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE): Replication event checksum verification failed while reading from network.
MySQL error code 1744 (ER_BINLOG_READ_EVENT_CHECKSUM_FAILURE): Replication event checksum verification failed while reading from a log file.
MySQL error code 1745 (ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX): Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.
MySQL error code 1746 (ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT): Can't update table '%-.192s' while '%-.192s' is being created.
MySQL error code 1747 (ER_PARTITION_CLAUSE_ON_NONPARTITIONED): PARTITION () clause on non partitioned table
MySQL error code 1748 (ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET): Found a row not matching the given partition set
MySQL error code 1749 (ER_NO_SUCH_PARTITION__UNUSED): partition '%-.64s' doesn't exist
MySQL error code 1750 (ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE): Failure while changing the type of replication repository: %s.
MySQL error code 1751 (ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE): The creation of some temporary tables could not be rolled back.
MySQL error code 1752 (ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE): Some temporary tables were dropped, but these operations could not be rolled back.
MySQL error code 1753 (ER_MTS_FEATURE_IS_NOT_SUPPORTED): %s is not supported in multi-threaded slave mode. %s
MySQL error code 1754 (ER_MTS_UPDATED_DBS_GREATER_MAX): The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.
MySQL error code 1755 (ER_MTS_CANT_PARALLEL): Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.
MySQL error code 1756 (ER_MTS_INCONSISTENT_DATA): %s
MySQL error code 1757 (ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING): FULLTEXT index is not supported for partitioned tables.
MySQL error code 1758 (ER_DA_INVALID_CONDITION_NUMBER): Invalid condition number
MySQL error code 1759 (ER_INSECURE_PLAIN_TEXT): Sending passwords in plain text without SSL/TLS is extremely insecure.
MySQL error code 1760 (ER_INSECURE_CHANGE_MASTER): Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
MySQL error code 1761 (ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO): Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'
MySQL error code 1762 (ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO): Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child table
MySQL error code 1763 (ER_SQLTHREAD_WITH_SECURE_SLAVE): Setting authentication options is not possible when only the Slave SQL Thread is being started.
MySQL error code 1764 (ER_TABLE_HAS_NO_FT): The table does not have FULLTEXT index to support this query
MySQL error code 1765 (ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER): The system variable %.200s cannot be set in stored functions or triggers.
MySQL error code 1766 (ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION): The system variable %.200s cannot be set when there is an ongoing transaction.
MySQL error code 1767 (ER_GTID_NEXT_IS_NOT_IN_GTID_NEXT_LIST): The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.
MySQL error code 1768 (ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION_WHEN_GTID_NEXT_LIST_IS_NULL): The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.
MySQL error code 1769 (ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION): The statement 'SET %.200s' cannot invoke a stored function.
MySQL error code 1770 (ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL): The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.
MySQL error code 1771 (ER_SKIPPING_LOGGED_TRANSACTION): Skipping transaction %.200s because it has already been executed and logged.
MySQL error code 1772 (ER_MALFORMED_GTID_SET_SPECIFICATION): Malformed GTID set specification '%.200s'.
MySQL error code 1773 (ER_MALFORMED_GTID_SET_ENCODING): Malformed GTID set encoding.
MySQL error code 1774 (ER_MALFORMED_GTID_SPECIFICATION): Malformed GTID specification '%.200s'.
MySQL error code 1775 (ER_GNO_EXHAUSTED): Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.
MySQL error code 1776 (ER_BAD_SLAVE_AUTO_POSITION): Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.
MySQL error code 1777 (ER_AUTO_POSITION_REQUIRES_GTID_MODE_ON): CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be executed when @@GLOBAL.GTID_MODE = ON.
MySQL error code 1778 (ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET): Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT != AUTOMATIC.
MySQL error code 1779 (ER_GTID_MODE_2_OR_3_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON): @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.
MySQL error code 1780 (ER_GTID_MODE_REQUIRES_BINLOG): @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log-slave-updates.
MySQL error code 1781 (ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF): @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1782 (ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON): @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.
MySQL error code 1783 (ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF): @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1784 (ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF): Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF.
MySQL error code 1785 (ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE): When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.
MySQL error code 1786 (ER_GTID_UNSAFE_CREATE_SELECT): CREATE TABLE ... SELECT is forbidden when @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.
MySQL error code 1787 (ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION): When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1.
MySQL error code 1788 (ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME): The value of @@GLOBAL.GTID_MODE can only change one step at a time: OFF <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2 <-> ON. Also note that this value must be stepped up or down simultaneously on all servers; see the Manual for instructions.
MySQL error code 1789 (ER_MASTER_HAS_PURGED_REQUIRED_GTIDS): The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.
MySQL error code 1790 (ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID): @@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.
MySQL error code 1791 (ER_UNKNOWN_EXPLAIN_FORMAT): Unknown EXPLAIN format name: '%s'
MySQL error code 1792 (ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION): Cannot execute statement in a READ ONLY transaction.
MySQL error code 1793 (ER_TOO_LONG_TABLE_PARTITION_COMMENT): Comment for table partition '%-.64s' is too long (max = %lu)
MySQL error code 1794 (ER_SLAVE_CONFIGURATION): Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.
MySQL error code 1795 (ER_INNODB_FT_LIMIT): InnoDB presently supports one FULLTEXT index creation at a time
MySQL error code 1796 (ER_INNODB_NO_FT_TEMP_TABLE): Cannot create FULLTEXT index on temporary InnoDB table
MySQL error code 1797 (ER_INNODB_FT_WRONG_DOCID_COLUMN): Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index
MySQL error code 1798 (ER_INNODB_FT_WRONG_DOCID_INDEX): Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index
MySQL error code 1799 (ER_INNODB_ONLINE_LOG_TOO_BIG): Creating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.
MySQL error code 1800 (ER_UNKNOWN_ALTER_ALGORITHM): Unknown ALGORITHM '%s'
MySQL error code 1801 (ER_UNKNOWN_ALTER_LOCK): Unknown LOCK type '%s'
MySQL error code 1802 (ER_MTS_CHANGE_MASTER_CANT_RUN_WITH_GAPS): CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.
MySQL error code 1803 (ER_MTS_RECOVERY_FAILURE): Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.
MySQL error code 1804 (ER_MTS_RESET_WORKERS): Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.
MySQL error code 1805 (ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2): Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted
MySQL error code 1806 (ER_SLAVE_SILENT_RETRY_TRANSACTION): Slave must silently retry current transaction
MySQL error code 1807 (ER_DISCARD_FK_CHECKS_RUNNING): There is a foreign key check running on table '%-.192s'. Cannot discard the table.
MySQL error code 1808 (ER_TABLE_SCHEMA_MISMATCH): Schema mismatch (%s)
MySQL error code 1809 (ER_TABLE_IN_SYSTEM_TABLESPACE): Table '%-.192s' in system tablespace
MySQL error code 1810 (ER_IO_READ_ERROR): IO Read error: (%lu, %s) %s
MySQL error code 1811 (ER_IO_WRITE_ERROR): IO Write error: (%lu, %s) %s
MySQL error code 1812 (ER_TABLESPACE_MISSING): Tablespace is missing for table '%-.192s'
MySQL error code 1813 (ER_TABLESPACE_EXISTS): Tablespace for table '%-.192s' exists. Please DISCARD the tablespace before IMPORT.
MySQL error code 1814 (ER_TABLESPACE_DISCARDED): Tablespace has been discarded for table '%-.192s'
MySQL error code 1815 (ER_INTERNAL_ERROR): Internal error: %s
MySQL error code 1816 (ER_INNODB_IMPORT_ERROR): ALTER TABLE '%-.192s' IMPORT TABLESPACE failed with error %lu : '%s'
MySQL error code 1817 (ER_INNODB_INDEX_CORRUPT): Index corrupt: %s
MySQL error code 1818 (ER_INVALID_YEAR_COLUMN_LENGTH): YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.
MySQL error code 1819 (ER_NOT_VALID_PASSWORD): Your password does not satisfy the current policy requirements
MySQL error code 1820 (ER_MUST_CHANGE_PASSWORD): You must SET PASSWORD before executing this statement
MySQL error code 1821 (ER_FK_NO_INDEX_CHILD): Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'
MySQL error code 1822 (ER_FK_NO_INDEX_PARENT): Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'
MySQL error code 1823 (ER_FK_FAIL_ADD_SYSTEM): Failed to add the foreign key constraint '%s' to system tables
MySQL error code 1824 (ER_FK_CANNOT_OPEN_PARENT): Failed to open the referenced table '%s'
MySQL error code 1825 (ER_FK_INCORRECT_OPTION): Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'
MySQL error code 1826 (ER_FK_DUP_NAME): Duplicate foreign key constraint name '%s'
MySQL error code 1827 (ER_PASSWORD_FORMAT): The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.
MySQL error code 1828 (ER_FK_COLUMN_CANNOT_DROP): Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'
MySQL error code 1829 (ER_FK_COLUMN_CANNOT_DROP_CHILD): Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1830 (ER_FK_COLUMN_NOT_NULL): Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULL
MySQL error code 1831 (ER_DUP_INDEX): Duplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.
MySQL error code 1832 (ER_FK_COLUMN_CANNOT_CHANGE): Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'
MySQL error code 1833 (ER_FK_COLUMN_CANNOT_CHANGE_CHILD): Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1834 (ER_FK_CANNOT_DELETE_PARENT): Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'
MySQL error code 1835 (ER_MALFORMED_PACKET): Malformed communication packet.
MySQL error code 1836 (ER_READ_ONLY_MODE): Running in read-only mode
MySQL error code 1837 (ER_GTID_NEXT_TYPE_UNDEFINED_GROUP): When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.
MySQL error code 1838 (ER_VARIABLE_NOT_SETTABLE_IN_SP): The system variable %.200s cannot be set in stored procedures.
MySQL error code 1839 (ER_CANT_SET_GTID_PURGED_WHEN_GTID_MODE_IS_OFF): @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.
MySQL error code 1840 (ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY): @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.
MySQL error code 1841 (ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY): @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).
MySQL error code 1842 (ER_GTID_PURGED_WAS_CHANGED): @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.
MySQL error code 1843 (ER_GTID_EXECUTED_WAS_CHANGED): @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.
MySQL error code 1844 (ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.
MySQL error code 1845 (ER_ALTER_OPERATION_NOT_SUPPORTED): %s is not supported for this operation. Try %s.
MySQL error code 1846 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON): %s is not supported. Reason: %s. Try %s.
MySQL error code 1847 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY): COPY algorithm requires a lock
MySQL error code 1848 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION): Partition specific operations do not yet support LOCK/ALGORITHM
MySQL error code 1849 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME): Columns participating in a foreign key are renamed
MySQL error code 1850 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE): Cannot change column type INPLACE
MySQL error code 1851 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK): Adding foreign keys needs foreign_key_checks=OFF
MySQL error code 1852 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_IGNORE): Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows
MySQL error code 1853 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK): Dropping a primary key is not allowed without also adding a new primary key
MySQL error code 1854 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC): Adding an auto-increment column requires a lock
MySQL error code 1855 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS): Cannot replace hidden FTS_DOC_ID with a user-visible one
MySQL error code 1856 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS): Cannot drop or rename FTS_DOC_ID
MySQL error code 1857 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS): Fulltext index creation requires a lock
MySQL error code 1858 (ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE): sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction
MySQL error code 1859 (ER_DUP_UNKNOWN_IN_INDEX): Duplicate entry for key '%-.192s'
MySQL error code 1860 (ER_IDENT_CAUSES_TOO_LONG_PATH): Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.
MySQL error code 1861 (ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL): cannot silently convert NULL values, as required in this SQL_MODE
MySQL error code 1862 (ER_MUST_CHANGE_PASSWORD_LOGIN): Your password has expired. To log in you must change it using a client that supports expired passwords.
MySQL error code 1863 (ER_ROW_IN_WRONG_PARTITION): Found a row in wrong partition %s
MySQL error code 1864 (ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX): Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.
MySQL error code 1865 (ER_INNODB_NO_FT_USES_PARSER): Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table
MySQL error code 1866 (ER_BINLOG_LOGICAL_CORRUPTION): The binary log file '%s' is logically corrupted: %s
MySQL error code 1867 (ER_WARN_PURGE_LOG_IN_USE): file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.
MySQL error code 1868 (ER_WARN_PURGE_LOG_IS_ACTIVE): file %s was not purged because it is the active log file.
MySQL error code 1869 (ER_AUTO_INCREMENT_CONFLICT): Auto-increment value in UPDATE conflicts with internally generated values
MySQL error code 1870 (WARN_ON_BLOCKHOLE_IN_RBR): Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'
MySQL error code 1871 (ER_SLAVE_MI_INIT_REPOSITORY): Slave failed to initialize master info structure from the repository
MySQL error code 1872 (ER_SLAVE_RLI_INIT_REPOSITORY): Slave failed to initialize relay log info structure from the repository
MySQL error code 1873 (ER_ACCESS_DENIED_CHANGE_USER_ERROR): Access denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.
MySQL error code 1874 (ER_INNODB_READ_ONLY): InnoDB is in read only mode.
MySQL error code 1875 (ER_STOP_SLAVE_SQL_THREAD_TIMEOUT): STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.
MySQL error code 1876 (ER_STOP_SLAVE_IO_THREAD_TIMEOUT): STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.
MySQL error code 1877 (ER_TABLE_CORRUPT): Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.
MySQL error code 1878 (ER_TEMP_FILE_WRITE_FAILURE): Temporary file write failure.
MySQL error code 1879 (ER_INNODB_FT_AUX_NOT_HEX_ID): Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.
MySQL error code 1880 (ER_OLD_TEMPORALS_UPGRADED): TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.
MySQL error code 1881 (ER_INNODB_FORCED_RECOVERY): Operation not allowed when innodb_forced_recovery > 0.
MySQL error code 1882 (ER_AES_INVALID_IV): The initialization vector supplied to %s is too short. Must be at least %d bytes long
MySQL error code 1883 (ER_PLUGIN_CANNOT_BE_UNINSTALLED): Plugin '%s' cannot be uninstalled now. %s
MySQL error code 1884 (ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_GTID_GROUP): Cannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
MySQL error code 1885 (ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER): Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.
MySQL error code 1886 (ER_QUERY_TIMEOUT): Query execution was interrupted, max_statement_time exceeded
MySQL error code 1887 (ER_CANT_EXECUTE_WITH_BACKUP_LOCK): Can't execute the query because you have a conflicting backup lock
This appendix describes the types of error information MySQL
provides and how to obtain information about them. The final section
is for troubleshooting. It describes common problems and errors that
may occur and potential resolutions.
B.1 Error Message Sources and Elements
This section discusses how error messages originate within MySQL
and the elements they contain.
-
Error Message Sources
-
Error Message Elements
-
Error Code Ranges
Error Message Sources
Error messages can originate on the server side or the client
side:
-
On the server side, error messages may occur during the
startup and shutdown processes, as a result of issues that
occur during SQL statement execution, and so forth.-
The MySQL server writes some error messages to its error
log. These indicate issues of interest to database
administrators or that require DBA action. -
The server sends other error messages to client
programs. These indicate issues pertaining only to a
particular client. The MySQL client library takes errors
received from the server and makes them available to the
host client program.
-
-
Client-side error messages are generated from within the
MySQL client library, usually involving problems
communicating with the server.
Example server-side error messages written to the error log:
-
This message produced during the startup process provides a
status or progress indicator:2018-10-28T13:01:32.735983Z 0 [Note] [MY-010303] [Server] Skipping generation of SSL certificates as options related to SSL are specified.
-
This message indicates an issue that requires DBA action:
2018-10-02T03:20:39.410387Z 768 [ERROR] [MY-010045] [Server] Event Scheduler: [evtuser@localhost][myschema.e_daily] Unknown database 'mydb'
Example server-side error message sent to client programs, as
displayed by the mysql client:
mysql> SELECT * FROM no_such_table;
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist
Example client-side error message originating from within the
client library, as displayed by the mysql
client:
shell> mysql -h no-such-host
ERROR 2005 (HY000): Unknown MySQL server host 'no-such-host' (0)
Whether an error originates from within the client library or is
received from the server, a MySQL client program may respond in
varying ways. As just illustrated, the client may display the
error message so the user can take corrective measures. The
client may instead internally attempt to resolve or retry a
failed operation, or take other action.
Error Message Elements
When an error occurs, error information includes several
elements: an error code, SQLSTATE value, and message string.
These elements have the following characteristics:
-
Error code: This value is numeric. It is MySQL-specific and
is not portable to other database systems.Each error number has a corresponding symbolic value.
Examples:-
The symbol for server error number
1146
is
ER_NO_SUCH_TABLE
. -
The symbol for client error number
2005
is
CR_UNKNOWN_HOST
.
The set of error codes used in error messages is partitioned
into distinct ranges; see
Error Code Ranges.Error codes are stable across General Availability (GA)
releases of a given MySQL series. Before a series reaches GA
status, new codes may still be under development and are
subject to change. -
-
SQLSTATE value: This value is a five-character string (for
example,'42S02'
). SQLSTATE values are
taken from ANSI SQL and ODBC and are more standardized than
the numeric error codes. The first two characters of an
SQLSTATE value indicate the error class:-
Class =
'00'
indicates success. -
Class =
'01'
indicates a warning. -
Class =
'02'
indicates “not
found.” This is relevant within the context of
cursors and is used to control what happens when a
cursor reaches the end of a data set. This condition
also occurs forSELECT ... INTO
statements
var_list
that retrieve no rows. -
Class >
'02'
indicates an
exception.
For server-side errors, not all MySQL error numbers have
corresponding SQLSTATE values. In these cases,
'HY000'
(general error) is used.For client-side errors, the SQLSTATE value is always
'HY000'
(general error), so it is not
meaningful for distinguishing one client error from another. -
-
Message string: This string provides a textual description
of the error.
Error Code Ranges
The set of error codes used in error messages is partitioned
into distinct ranges, each with its own purpose:
-
1 to 999: Global error codes. This error code range is
called “global” because it is a shared range
that is used by the server as well as by clients.When an error in this range originates on the server side,
the server writes it to the error log, padding the error
code with leading zeros to six digits and adding a prefix of
MY-
.When an error in this range originates on the client side,
the client library makes it available to the client program
with no zero-padding or prefix. -
1,000 to 1,999: Server error codes reserved for messages
sent to clients. -
2,000 to 2,999: Client error codes reserved for use by the
client library. -
3,000 to 4,999: Server error codes reserved for messages
sent to clients. -
5,000 to 5,999: Error codes reserved for use by X Plugin
for messages sent to clients. -
10,000 to 49,999: Server error codes reserved for messages
to be written to the error log (not sent to clients).When an error in this range occurs, the server writes it to
the error log, padding the error code with leading zeros to
six digits and adding a prefix ofMY-
. -
50,000 to 51,999: Error codes reserved for use by third
parties.
The server handles error messages written to the error log
differently from error messages sent to clients:
-
When the server writes a message to the error log, it pads
the error code with leading zeros to six digits and adds a
prefix ofMY-
(examples:
MY-000022
,
MY-010048
). -
When the server sends a message to a client program, it adds
no zero-padding or prefix to the error code (examples:
1036
,
3013
).
B.2 Error Information Interfaces
Error messages can originate on the server side or the client
side, and each error message includes an error code, SQLSTATE
value, and message string, as described in
Section B.1, “Error Message Sources and Elements”. For lists of
server-side, client-side, and global (shared between server and
clients) errors, see MySQL 8.0 Error Message Reference.
For error checking from within programs, use error code numbers or
symbols, not error message strings. Message strings do not change
often, but it is possible. Also, if the database administrator
changes the language setting, that affects the language of message
strings; see Section 10.12, “Setting the Error Message Language”.
Error information in MySQL is available in the server error log,
at the SQL level, from within client programs, and at the command
line.
-
Error Log
-
SQL Error Message Interface
-
Client Error Message Interface
-
Command-Line Error Message Interface
Error Log
On the server side, some messages are intended for the error
log. For information about configuring where and how the server
writes the log, see Section 5.4.2, “The Error Log”.
Other server error messages are intended to be sent to client
programs and are available as described in
Client Error Message Interface.
The range within which a particular error code lies determines
whether the server writes an error message to the error log or
sends it to clients. For information about these ranges, see
Error Code Ranges.
SQL Error Message Interface
At the SQL level, there are several sources of error information
in MySQL:
-
SQL statement warning and error information is available
through theSHOW WARNINGS
and
SHOW ERRORS
statements. The
warning_count
system
variable indicates the number of errors, warnings, and notes
(with notes excluded if the
sql_notes
system variable
is disabled). The
error_count
system variable
indicates the number of errors. Its value excludes warnings
and notes. -
The
GET DIAGNOSTICS
statement
may be used to inspect the diagnostic information in the
diagnostics area. See Section 13.6.7.3, “GET DIAGNOSTICS Statement”. -
SHOW SLAVE STATUS
statement
output includes information about replication errors
occurring on replica servers. -
SHOW ENGINE
statement output includes
INNODB STATUS
information about the most recent foreign key error if a
CREATE TABLE
statement for an
InnoDB
table fails.
Client Error Message Interface
Client programs receive errors from two sources:
-
Errors that originate on the client side from within the
MySQL client library. -
Errors that originate on the server side and are sent to the
client by the server. These are received within the client
library, which makes them available to the host client
program.
The range within which a particular error code lies determines
whether it originated from within the client library or was
received by the client from the server. For information about
these ranges, see Error Code Ranges.
Regardless of whether an error originates from within the client
library or is received from the server, a MySQL client program
obtains the error code, SQLSTATE value, message string, and
other related information by calling C API functions in the
client library:
-
mysql_errno()
returns the
MySQL error code. -
mysql_sqlstate()
returns the
SQLSTATE value. -
mysql_error()
returns the
message string. -
mysql_stmt_errno()
,
mysql_stmt_sqlstate()
, and
mysql_stmt_error()
are the
corresponding error functions for prepared statements. -
mysql_warning_count()
returns the number of errors, warnings, and notes for the
most recent statement.
For descriptions of the client library error functions, see
MySQL 8.0 C API Developer Guide.
A MySQL client program may respond to an error in varying ways.
The client may display the error message so the user can take
corrective measures, internally attempt to resolve or retry a
failed operation, or take other action. For example, (using the
mysql client), a failure to connect to the
server might result in this message:
shell> mysql -h no-such-host
ERROR 2005 (HY000): Unknown MySQL server host 'no-such-host' (0)
B.3 Problems and Common Errors
This section lists some common problems and error messages that
you may encounter. It describes how to determine the causes of the
problems and what to do to solve them.
B.3.1 How to Determine What Is Causing a Problem
When you run into a problem, the first thing you should do is to
find out which program or piece of equipment is causing it:
-
If you have one of the following symptoms, then it is
probably a hardware problems (such as memory, motherboard,
CPU, or hard disk) or kernel problem:-
The keyboard does not work. This can normally be checked
by pressing the Caps Lock key. If the Caps Lock light
does not change, you have to replace your keyboard.
(Before doing this, you should try to restart your
computer and check all cables to the keyboard.) -
The mouse pointer does not move.
-
The machine does not answer to a remote machine’s pings.
-
Other programs that are not related to MySQL do not
behave correctly. -
Your system restarted unexpectedly. (A faulty user-level
program should never be able to take down your system.)
In this case, you should start by checking all your cables
and run some diagnostic tool to check your hardware! You
should also check whether there are any patches, updates, or
service packs for your operating system that could likely
solve your problem. Check also that all your libraries (such
asglibc
) are up to date.It is always good to use a machine with ECC memory to
discover memory problems early. -
-
If your keyboard is locked up, you may be able to recover by
logging in to your machine from another machine and
executingkbd_mode -a
. -
Please examine your system log file
(/var/log/messages
or similar) for
reasons for your problem. If you think the problem is in
MySQL, you should also examine MySQL’s log files. See
Section 5.4, “MySQL Server Logs”. -
If you do not think you have hardware problems, you should
try to find out which program is causing problems. Try using
top, ps, Task Manager,
or some similar program, to check which program is taking
all CPU or is locking the machine. -
Use top, df, or a
similar program to check whether you are out of memory, disk
space, file descriptors, or some other critical resource. -
If the problem is some runaway process, you can always try
to kill it. If it does not want to die, there is probably a
bug in the operating system.
If you have examined all other possibilities and concluded that
the MySQL server or a MySQL client is causing the problem, it is
time to create a bug report, see Section 1.6, “How to Report Bugs or Problems”.
In the bug report, try to give a complete description of how the
system is behaving and what you think is happening. Also state
why you think that MySQL is causing the problem. Take into
consideration all the situations described in this chapter.
State any problems exactly how they appear when you examine your
system. Use the “copy and paste” method for any
output and error messages from programs and log files.
Try to describe in detail which program is not working and all
symptoms you see. We have in the past received many bug reports
that state only “the system does not work.” This
provides us with no information about what could be the problem.
If a program fails, it is always useful to know the following
information:
-
Has the program in question made a segmentation fault (did
it dump core)? -
Is the program taking up all available CPU time? Check with
top. Let the program run for a while, it
may simply be evaluating something computationally
intensive. -
If the mysqld server is causing problems,
can you get any response from it with mysqladmin -u
root ping or mysqladmin -u root
processlist? -
What does a client program say when you try to connect to
the MySQL server? (Try with mysql, for
example.) Does the client jam? Do you get any output from
the program?
When sending a bug report, you should follow the outline
described in Section 1.6, “How to Report Bugs or Problems”.
B.3.2 Common Errors When Using MySQL Programs
This section lists some errors that users frequently encounter
when running MySQL programs. Although the problems show up when
you try to run client programs, the solutions to many of the
problems involves changing the configuration of the MySQL
server.
B.3.2.2 Can’t connect to [local] MySQL server
A MySQL client on Unix can connect to the
mysqld server in two different ways: By
using a Unix socket file to connect through a file in the file
system (default /tmp/mysql.sock
), or by
using TCP/IP, which connects through a port number. A Unix
socket file connection is faster than TCP/IP, but can be used
only when connecting to a server on the same computer. A Unix
socket file is used if you do not specify a host name or if
you specify the special host name
localhost
.
If the MySQL server is running on Windows, you can connect
using TCP/IP. If the server is started with the
named_pipe
system variable
enabled, you can also connect with named pipes if you run the
client on the host where the server is running. The name of
the named pipe is MySQL
by default. If you
do not give a host name when connecting to
mysqld, a MySQL client first tries to
connect to the named pipe. If that does not work, it connects
to the TCP/IP port. You can force the use of named pipes on
Windows by using .
as the host name.
The error (2002) Can't connect to ...
normally means that there is no MySQL server running on the
system or that you are using an incorrect Unix socket file
name or TCP/IP port number when trying to connect to the
server. You should also check that the TCP/IP port you are
using has not been blocked by a firewall or port blocking
service.
The error (2003) Can't connect to MySQL server on
'server
' (10061)
indicates that the network connection has been refused. You
should check that there is a MySQL server running, that it has
network connections enabled, and that the network port you
specified is the one configured on the server.
Start by checking whether there is a process named
mysqld running on your server host. (Use
ps xa | grep mysqld on Unix or the Task
Manager on Windows.) If there is no such process, you should
start the server. See Section 2.10.2, “Starting the Server”.
If a mysqld process is running, you can
check it by trying the following commands. The port number or
Unix socket file name might be different in your setup.
host_ip
represents the IP address of the
machine where the server is running.
shell>mysqladmin version
shell>mysqladmin variables
shell>mysqladmin -h `hostname` version variables
shell>mysqladmin -h `hostname` --port=3306 version
shell>mysqladmin -h host_ip version
shell>mysqladmin --protocol=SOCKET --socket=/tmp/mysql.sock version
Note the use of backticks rather than forward quotation marks
with the hostname command; these cause the
output of hostname (that is, the current
host name) to be substituted into the
mysqladmin command. If you have no
hostname command or are running on Windows,
you can manually type the host name of your machine (without
backticks) following the -h
option. You can
also try -h 127.0.0.1
to connect with
TCP/IP to the local host.
Make sure that the server has not been configured to ignore
network connections or (if you are attempting to connect
remotely) that it has not been configured to listen only
locally on its network interfaces. If the server was started
with the skip_networking
system variable enabled, it cannot accept TCP/IP connections
at all. If the server was started with the
bind_address
system variable
set to 127.0.0.1
, it listens for TCP/IP
connections only locally on the loopback interface and does
not accept remote connections.
Check to make sure that there is no firewall blocking access
to MySQL. Your firewall may be configured on the basis of the
application being executed, or the port number used by MySQL
for communication (3306 by default). Under Linux or Unix,
check your IP tables (or similar) configuration to ensure that
the port has not been blocked. Under Windows, applications
such as ZoneAlarm or Windows Firewall may need to be
configured not to block the MySQL port.
Here are some reasons the Can't connect to local
error might occur:
MySQL server
-
mysqld is not running on the local
host. Check your operating system’s process list to ensure
the mysqld process is present. -
You’re running a MySQL server on Windows with many TCP/IP
connections to it. If you’re experiencing that quite often
your clients get that error, you can find a workaround
here:
Section B.3.2.2.1, “Connection to MySQL Server Failing on Windows”. -
Someone has removed the Unix socket file that
mysqld uses
(/tmp/mysql.sock
by default). For
example, you might have a cron job that
removes old files from the/tmp
directory. You can always run mysqladmin
version to check whether the Unix socket file
that mysqladmin is trying to use really
exists. The fix in this case is to change the
cron job to not remove
mysql.sock
or to place the socket
file somewhere else. See
Section B.3.3.6, “How to Protect or Change the MySQL Unix Socket File”. -
You have started the mysqld server with
the
--socket=/path/to/socket
option, but forgotten to tell client programs the new name
of the socket file. If you change the socket path name for
the server, you must also notify the MySQL clients. You
can do this by providing the same
--socket
option when you
run client programs. You also need to ensure that clients
have permission to access the
mysql.sock
file. To find out where
the socket file is, you can do:shell>
netstat -ln | grep mysql
See Section B.3.3.6, “How to Protect or Change the MySQL Unix Socket File”.
-
You are using Linux and one server thread has died (dumped
core). In this case, you must kill the other
mysqld threads (for example, with
kill) before you can restart the MySQL
server. See Section B.3.3.3, “What to Do If MySQL Keeps Crashing”. -
The server or client program might not have the proper
access privileges for the directory that holds the Unix
socket file or the socket file itself. In this case, you
must either change the access privileges for the directory
or socket file so that the server and clients can access
them, or restart mysqld with a
--socket
option that
specifies a socket file name in a directory where the
server can create it and where client programs can access
it.
If you get the error message Can't connect to MySQL
, you can try the following
server on some_host
things to find out what the problem is:
-
Check whether the server is running on that host by
executingtelnet some_host 3306
and
pressing the Enter key a couple of times. (3306 is the
default MySQL port number. Change the value if your server
is listening to a different port.) If there is a MySQL
server running and listening to the port, you should get a
response that includes the server’s version number. If you
get an error such astelnet: Unable to connect to
, then there is
remote host: Connection refused
no server running on the given port. -
If the server is running on the local host, try using
mysqladmin -h localhost variables to
connect using the Unix socket file. Verify the TCP/IP port
number that the server is configured to listen to (it is
the value of theport
variable.) -
If you are running under Linux and Security-Enhanced Linux
(SELinux) is enabled, see Section 6.7, “SELinux”.
B.3.2.2.1 Connection to MySQL Server Failing on Windows
When you’re running a MySQL server on Windows with many
TCP/IP connections to it, and you’re experiencing that quite
often your clients get a Can't connect to MySQL
error, the reason might be that Windows
server
does not allow for enough ephemeral (short-lived) ports to
serve those connections.
The purpose of TIME_WAIT
is to keep a
connection accepting packets even after the connection has
been closed. This is because Internet routing can cause a
packet to take a slow route to its destination and it may
arrive after both sides have agreed to close. If the port is
in use for a new connection, that packet from the old
connection could break the protocol or compromise personal
information from the original connection. The
TIME_WAIT
delay prevents this by ensuring
that the port cannot be reused until after some time has
been permitted for those delayed packets to arrive.
It is safe to reduce TIME_WAIT
greatly on
LAN connections because there is little chance of packets
arriving at very long delays, as they could through the
Internet with its comparatively large distances and
latencies.
Windows permits ephemeral (short-lived) TCP ports to the
user. After any port is closed, it remains in a
TIME_WAIT
status for 120 seconds. The
port is not available again until this time expires. The
default range of port numbers depends on the version of
Windows, with a more limited number of ports in older
versions:
-
Windows through Server 2003: Ports in range
1025–5000 -
Windows Vista, Server 2008, and newer: Ports in range
49152–65535
With a small stack of available TCP ports (5000) and a high
number of TCP ports being open and closed over a short
period of time along with the TIME_WAIT
status you have a good chance for running out of ports.
There are two ways to address this problem:
-
Reduce the number of TCP ports consumed quickly by
investigating connection pooling or persistent
connections where possible -
Tune some settings in the Windows registry (see below)
Important
The following procedure involves modifying the Windows
registry. Before you modify the registry, make sure to
back it up and make sure that you understand how to
restore it if a problem occurs. For information about how
to back up, restore, and edit the registry, view the
following article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/256986/EN-US/.
-
Start Registry Editor
(Regedt32.exe
). -
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
-
On the
Edit
menu, clickAdd
, and then add the following registry
Value
value:Value Name: MaxUserPort Data Type: REG_DWORD Value: 65534
This sets the number of ephemeral ports available to any
user. The valid range is between 5000 and 65534
(decimal). The default value is 0x1388 (5000 decimal). -
On the
Edit
menu, clickAdd
, and then add the following registry
Value
value:Value Name: TcpTimedWaitDelay Data Type: REG_DWORD Value: 30
This sets the number of seconds to hold a TCP port
connection inTIME_WAIT
state before
closing. The valid range is between 30 and 300 decimal,
although you may wish to check with Microsoft for the
latest permitted values. The default value is 0x78 (120
decimal). -
Quit Registry Editor.
-
Reboot the machine.
Note: Undoing the above should be as simple as deleting the
registry entries you’ve created.
B.3.2.3 Lost connection to MySQL server
There are three likely causes for this error message.
Usually it indicates network connectivity trouble and you
should check the condition of your network if this error
occurs frequently. If the error message includes “during
query,” this is probably the case you are experiencing.
Sometimes the “during query” form happens when
millions of rows are being sent as part of one or more
queries. If you know that this is happening, you should try
increasing net_read_timeout
from its default of 30 seconds to 60 seconds or longer,
sufficient for the data transfer to complete.
More rarely, it can happen when the client is attempting the
initial connection to the server. In this case, if your
connect_timeout
value is set
to only a few seconds, you may be able to resolve the problem
by increasing it to ten seconds, perhaps more if you have a
very long distance or slow connection. You can determine
whether you are experiencing this more uncommon cause by using
SHOW GLOBAL STATUS LIKE 'Aborted_connects'
.
It increases by one for each initial connection attempt that
the server aborts. You may see “reading authorization
packet” as part of the error message; if so, that also
suggests that this is the solution that you need.
If the cause is none of those just described, you may be
experiencing a problem with
BLOB
values that are larger
than max_allowed_packet
,
which can cause this error with some clients. Sometime you may
see an ER_NET_PACKET_TOO_LARGE
error, and that confirms that you need to increase
max_allowed_packet
.
B.3.2.4 Password Fails When Entered Interactively
MySQL client programs prompt for a password when invoked with
a --password
or
-p
option that has no following password
value:
shell> mysql -u user_name
-p
Enter password:
On some systems, you may find that your password works when
specified in an option file or on the command line, but not
when you enter it interactively at the Enter
prompt. This occurs when the library
password:
provided by the system to read passwords limits password
values to a small number of characters (typically eight). That
is a problem with the system library, not with MySQL. To work
around it, change your MySQL password to a value that is eight
or fewer characters long, or put your password in an option
file.
B.3.2.5 Too many connections
If clients encounter Too many connections
errors when attempting to connect to the
mysqld server, all available connections
are in use by other clients.
The permitted number of connections is controlled by the
max_connections
system
variable. To support more connections, set
max_connections
to a larger
value.
mysqld actually permits
max_connections
+ 1 client connections. The extra connection is reserved for
use by accounts that have the
CONNECTION_ADMIN
privilege (or
the deprecated SUPER
privilege). By granting the privilege to administrators and
not to normal users (who should not need it), an administrator
can connect to the server and use SHOW
to diagnose problems even if the maximum
PROCESSLIST
number of unprivileged clients are connected. See
Section 13.7.7.29, “SHOW PROCESSLIST Statement”.
The server also permits administrative connections on a
dedicated interface. For more information about how the server
handles client connections, see
Section 5.1.12.1, “Connection Interfaces”.
B.3.2.6 Out of memory
If you issue a query using the mysql client
program and receive an error like the following one, it means
that mysql does not have enough memory to
store the entire query result:
mysql: Out of memory at line 42, 'malloc.c' mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k) ERROR 2008: MySQL client ran out of memory
To remedy the problem, first check whether your query is
correct. Is it reasonable that it should return so many rows?
If not, correct the query and try again. Otherwise, you can
invoke mysql with the
--quick
option. This causes it
to use the mysql_use_result()
C API function to retrieve the result set, which places less
of a load on the client (but more on the server).
B.3.2.7 MySQL server has gone away
This section also covers the related Lost connection
error.
to server during query
The most common reason for the MySQL server has gone
error is that the server timed out and closed
away
the connection. In this case, you normally get one of the
following error codes (which one you get is operating
system-dependent).
Error Code | Description |
---|---|
CR_SERVER_GONE_ERROR |
The client couldn’t send a question to the server. |
CR_SERVER_LOST |
The client didn’t get an error when writing to the server, but it didn’t get a full answer (or any answer) to the question. |
By default, the server closes the connection after eight hours
if nothing has happened. You can change the time limit by
setting the wait_timeout
variable when you start mysqld. See
Section 5.1.8, “Server System Variables”.
If you have a script, you just have to issue the query again
for the client to do an automatic reconnection. This assumes
that you have automatic reconnection in the client enabled
(which is the default for the mysql
command-line client).
Some other common reasons for the MySQL server has
error are:
gone away
-
You (or the db administrator) has killed the running
thread with aKILL
statement or a mysqladmin kill command. -
You tried to run a query after closing the connection to
the server. This indicates a logic error in the
application that should be corrected. -
A client application running on a different host does not
have the necessary privileges to connect to the MySQL
server from that host. -
You got a timeout from the TCP/IP connection on the client
side. This may happen if you have been using the commands:
mysql_options(...,
or
MYSQL_OPT_READ_TIMEOUT,...)
mysql_options(...,
. In this case
MYSQL_OPT_WRITE_TIMEOUT,...)
increasing the timeout may help solve the problem. -
You have encountered a timeout on the server side and the
automatic reconnection in the client is disabled (the
reconnect
flag in the
MYSQL
structure is equal to 0). -
You are using a Windows client and the server had dropped
the connection (probably because
wait_timeout
expired)
before the command was issued.The problem on Windows is that in some cases MySQL does
not get an error from the OS when writing to the TCP/IP
connection to the server, but instead gets the error when
trying to read the answer from the connection.The solution to this is to either do a
mysql_ping()
on the
connection if there has been a long time since the last
query (this is what Connector/ODBC does) or set
wait_timeout
on the
mysqld server so high that it in
practice never times out. -
You can also get these errors if you send a query to the
server that is incorrect or too large. If
mysqld receives a packet that is too
large or out of order, it assumes that something has gone
wrong with the client and closes the connection. If you
need big queries (for example, if you are working with big
BLOB
columns), you can
increase the query limit by setting the server’s
max_allowed_packet
variable, which has a default value of 64MB. You may also
need to increase the maximum packet size on the client
end. More information on setting the packet size is given
in Section B.3.2.8, “Packet Too Large”.An
INSERT
or
REPLACE
statement that
inserts a great many rows can also cause these sorts of
errors. Either one of these statements sends a single
request to the server irrespective of the number of rows
to be inserted; thus, you can often avoid the error by
reducing the number of rows sent per
INSERT
or
REPLACE
. -
It is also possible to see this error if host name lookups
fail (for example, if the DNS server on which your server
or network relies goes down). This is because MySQL is
dependent on the host system for name resolution, but has
no way of knowing whether it is working—from MySQL’s
point of view the problem is indistinguishable from any
other network timeout.You may also see the
MySQL server has gone
error if MySQL is started with the
away
skip_networking
system
variable enabled.Another networking issue that can cause this error occurs
if the MySQL port (default 3306) is blocked by your
firewall, thus preventing any connections at all to the
MySQL server. -
You can also encounter this error with applications that
fork child processes, all of which try to use the same
connection to the MySQL server. This can be avoided by
using a separate connection for each child process. -
You have encountered a bug where the server died while
executing the query.
You can check whether the MySQL server died and restarted by
executing mysqladmin version and examining
the server’s uptime. If the client connection was broken
because mysqld crashed and restarted, you
should concentrate on finding the reason for the crash. Start
by checking whether issuing the query again kills the server
again. See Section B.3.3.3, “What to Do If MySQL Keeps Crashing”.
You can obtain more information about lost connections by
starting mysqld with the
log_error_verbosity
system
variable set to 3. This logs some of the disconnection
messages in the hostname.err
file. See
Section 5.4.2, “The Error Log”.
If you want to create a bug report regarding this problem, be
sure that you include the following information:
-
Indicate whether the MySQL server died. You can find
information about this in the server error log. See
Section B.3.3.3, “What to Do If MySQL Keeps Crashing”. -
If a specific query kills mysqld and
the tables involved were checked with
CHECK TABLE
before you ran
the query, can you provide a reproducible test case? See
Section 5.9, “Debugging MySQL”. -
What is the value of the
wait_timeout
system
variable in the MySQL server? (mysqladmin
variables gives you the value of this variable.) -
Have you tried to run mysqld with the
general query log enabled to determine whether the problem
query appears in the log? (See
Section 5.4.3, “The General Query Log”.)
See also Section B.3.2.9, “Communication Errors and Aborted Connections”, and
Section 1.6, “How to Report Bugs or Problems”.
B.3.2.8 Packet Too Large
A communication packet is a single SQL statement sent to the
MySQL server, a single row that is sent to the client, or a
binary log event sent from a source replication server to a
replica.
The largest possible packet that can be transmitted to or from
a MySQL 8.0 server or client is 1GB.
When a MySQL client or the mysqld server
receives a packet bigger than
max_allowed_packet
bytes, it
issues an
ER_NET_PACKET_TOO_LARGE
error
and closes the connection. With some clients, you may also get
a Lost connection to MySQL server during
error if the communication packet is too
query
large.
Both the client and the server have their own
max_allowed_packet
variable,
so if you want to handle big packets, you must increase this
variable both in the client and in the server.
If you are using the mysql client program,
its default
max_allowed_packet
variable
is 16MB. To set a larger value, start mysql
like this:
shell> mysql --max_allowed_packet=32M
That sets the packet size to 32MB.
The server’s default
max_allowed_packet
value is
64MB. You can increase this if the server needs to handle big
queries (for example, if you are working with big
BLOB
columns). For example, to
set the variable to 128MB, start the server like this:
shell> mysqld --max_allowed_packet=128M
You can also use an option file to set
max_allowed_packet
. For
example, to set the size for the server to 128MB, add the
following lines in an option file:
[mysqld] max_allowed_packet=128M
It is safe to increase the value of this variable because the
extra memory is allocated only when needed. For example,
mysqld allocates more memory only when you
issue a long query or when mysqld must
return a large result row. The small default value of the
variable is a precaution to catch incorrect packets between
the client and server and also to ensure that you do not run
out of memory by using large packets accidentally.
You can also get strange problems with large packets if you
are using large BLOB
values but
have not given mysqld access to enough
memory to handle the query. If you suspect this is the case,
try adding ulimit -d 256000 to the
beginning of the mysqld_safe script and
restarting mysqld.
B.3.2.9 Communication Errors and Aborted Connections
If connection problems occur such as communication errors or
aborted connections, use these sources of information to
diagnose problems:
-
The error log. See Section 5.4.2, “The Error Log”.
-
The general query log. See Section 5.4.3, “The General Query Log”.
-
The
Aborted_
xxx
and
Connection_errors_
xxx
status variables. See
Section 5.1.10, “Server Status Variables”. -
The host cache, which is accessible using the Performance
Schemahost_cache
table. See
Section 5.1.12.3, “DNS Lookups and the Host Cache”, and
Section 27.12.19.5, “The host_cache Table”.
If the log_error_verbosity
system variable is set to 3, you might find messages like this
in your error log:
[Note] Aborted connection 854 to db: 'employees' user: 'josh'
If a client is unable even to connect, the server increments
the Aborted_connects
status
variable. Unsuccessful connection attempts can occur for the
following reasons:
-
A client attempts to access a database but has no
privileges for it. -
A client uses an incorrect password.
-
A connection packet does not contain the right
information. -
It takes more than
connect_timeout
seconds
to obtain a connect packet. See
Section 5.1.8, “Server System Variables”.
If these kinds of things happen, it might indicate that
someone is trying to break into your server! If the general
query log is enabled, messages for these types of problems are
logged to it.
If a client successfully connects but later disconnects
improperly or is terminated, the server increments the
Aborted_clients
status
variable, and logs an Aborted
connection message to the error log. The cause can
be any of the following:
-
The client program did not call
mysql_close()
before
exiting. -
The client had been sleeping more than
wait_timeout
or
interactive_timeout
seconds without issuing any requests to the server. See
Section 5.1.8, “Server System Variables”. -
The client program ended abruptly in the middle of a data
transfer.
Other reasons for problems with aborted connections or aborted
clients:
-
The
max_allowed_packet
variable value is too small or queries require more memory
than you have allocated for mysqld. See
Section B.3.2.8, “Packet Too Large”. -
Use of Ethernet protocol with Linux, both half and full
duplex. Some Linux Ethernet drivers have this bug. You
should test for this bug by transferring a huge file using
FTP between the client and server machines. If a transfer
goes in burst-pause-burst-pause mode, you are experiencing
a Linux duplex syndrome. Switch the duplex mode for both
your network card and hub/switch to either full duplex or
to half duplex and test the results to determine the best
setting. -
A problem with the thread library that causes interrupts
on reads. -
Badly configured TCP/IP.
-
Faulty Ethernets, hubs, switches, cables, and so forth.
This can be diagnosed properly only by replacing hardware.
See also Section B.3.2.7, “MySQL server has gone away”.
B.3.2.10 The table is full
If a table-full error occurs, it may be that the disk is full
or that the table has reached its maximum size. The effective
maximum table size for MySQL databases is usually determined
by operating system constraints on file sizes, not by MySQL
internal limits. See Section 8.4.6, “Limits on Table Size”.
B.3.2.11 Can’t create/write to file
If you get an error of the following type for some queries, it
means that MySQL cannot create a temporary file for the result
set in the temporary directory:
Can't create/write to file '\\sqla3fe_0.ism'.
The preceding error is a typical message for Windows; the Unix
message is similar.
One fix is to start mysqld with the
--tmpdir
option or to add the
option to the [mysqld]
section of your
option file. For example, to specify a directory of
C:\temp
, use these lines:
[mysqld] tmpdir=C:/temp
The C:\temp
directory must exist and have
sufficient space for the MySQL server to write to. See
Section 4.2.2.2, “Using Option Files”.
Another cause of this error can be permissions issues. Make
sure that the MySQL server can write to the
tmpdir
directory.
Check also the error code that you get with
perror. One reason the server cannot write
to a table is that the file system is full:
shell> perror 28
OS error code 28: No space left on device
If you get an error of the following type during startup, it
indicates that the file system or directory used for storing
data files is write protected. Provided that the write error
is to a test file, the error is not serious and can be safely
ignored.
Can't create test file /usr/local/mysql/data/master.lower-test
B.3.2.12 Commands out of sync
If you get Commands out of sync; you can't run this
in your client code, you are calling
command now
client functions in the wrong order.
This can happen, for example, if you are using
mysql_use_result()
and try to
execute a new query before you have called
mysql_free_result()
. It can
also happen if you try to execute two queries that return data
without calling
mysql_use_result()
or
mysql_store_result()
in
between.
B.3.2.13 Ignoring user
If you get the following error, it means that when
mysqld was started or when it reloaded the
grant tables, it found an account in the
user
table that had an invalid password.
Found wrong password for user
'some_user
'@'some_host
';
ignoring user
As a result, the account is simply ignored by the permission
system. To fix this problem, assign a new, valid password to
the account.
B.3.2.14 Table ‘tbl_name’ doesn’t exist
If you get either of the following errors, it usually means
that no table exists in the default database with the given
name:
Table 'tbl_name
' doesn't exist Can't find file: 'tbl_name
' (errno: 2)
In some cases, it may be that the table does exist but that
you are referring to it incorrectly:
-
Because MySQL uses directories and files to store
databases and tables, database and table names are
case-sensitive if they are located on a file system that
has case-sensitive file names. -
Even for file systems that are not case-sensitive, such as
on Windows, all references to a given table within a query
must use the same lettercase.
You can check which tables are in the default database with
SHOW TABLES
. See
Section 13.7.7, “SHOW Statements”.
B.3.2.15 Can’t initialize character set
You might see an error like this if you have character set
problems:
MySQL Connection Failed: Can't initialize character set charset_name
This error can have any of the following causes:
-
The character set is a multibyte character set and you
have no support for the character set in the client. In
this case, you need to recompile the client by running
CMake with the
-DDEFAULT_CHARSET=
charset_name
option. See
Section 2.9.7, “MySQL Source-Configuration Options”.All standard MySQL binaries are compiled with support for
all multibyte character sets. -
The character set is a simple character set that is not
compiled into mysqld, and the character
set definition files are not in the place where the client
expects to find them.In this case, you need to use one of the following methods
to solve the problem:-
Recompile the client with support for the character
set. See
Section 2.9.7, “MySQL Source-Configuration Options”. -
Specify to the client the directory where the
character set definition files are located. For many
clients, you can do this with the
--character-sets-dir
option. -
Copy the character definition files to the path where
the client expects them to be.
-
B.3.2.16 File Not Found and Similar Errors
If you get ERROR
,
'file_name
' not found (errno:
23)Can't open file:
, or
file_name
(errno: 24)
any other error with errno 23
or
errno 24
from MySQL, it means that you have
not allocated enough file descriptors for the MySQL server.
You can use the perror utility to get a
description of what the error number means:
shell>perror 23
OS error code 23: File table overflow shell>perror 24
OS error code 24: Too many open files shell>perror 11
OS error code 11: Resource temporarily unavailable
The problem here is that mysqld is trying
to keep open too many files simultaneously. You can either
tell mysqld not to open so many files at
once or increase the number of file descriptors available to
mysqld.
To tell mysqld to keep open fewer files at
a time, you can make the table cache smaller by reducing the
value of the table_open_cache
system variable (the default value is 64). This may not
entirely prevent running out of file descriptors because in
some circumstances the server may attempt to extend the cache
size temporarily, as described in
Section 8.4.3.1, “How MySQL Opens and Closes Tables”. Reducing the value of
max_connections
also reduces
the number of open files (the default value is 100).
To change the number of file descriptors available to
mysqld, you can use the
--open-files-limit
option
to mysqld_safe or set the
open_files_limit
system
variable. See Section 5.1.8, “Server System Variables”. The
easiest way to set these values is to add an option to your
option file. See Section 4.2.2.2, “Using Option Files”. If you have
an old version of mysqld that does not
support setting the open files limit, you can edit the
mysqld_safe script. There is a
commented-out line ulimit -n 256 in the
script. You can remove the #
character to
uncomment this line, and change the number
256
to set the number of file descriptors
to be made available to mysqld.
--open-files-limit
and
ulimit can increase the number of file
descriptors, but only up to the limit imposed by the operating
system. There is also a “hard” limit that can be
overridden only if you start mysqld_safe or
mysqld as root
(just
remember that you also need to start the server with the
--user
option in this case so
that it does not continue to run as root
after it starts up). If you need to increase the operating
system limit on the number of file descriptors available to
each process, consult the documentation for your system.
Note
If you run the tcsh shell,
ulimit does not work!
tcsh also reports incorrect values when
you ask for the current limits. In this case, you should
start mysqld_safe using
sh.
B.3.2.17 Table-Corruption Issues
If you have started mysqld with the
myisam_recover_options
system
variable set, MySQL automatically checks and tries to repair
MyISAM
tables if they are marked as ‘not
closed properly’ or ‘crashed’. If this happens, MySQL writes
an entry in the hostname.err
file
'Warning: Checking table ...'
which is
followed by Warning: Repairing table
if the
table needs to be repaired. If you get a lot of these errors,
without mysqld having died unexpectedly
just before, then something is wrong and needs to be
investigated further.
When the server detects MyISAM
table
corruption, it writes additional information to the error log,
such as the name and line number of the source file, and the
list of threads accessing the table. Example: Got an
. This is
error from thread_id=1, mi_dynrec.c:368
useful information to include in bug reports.
See also Section 5.1.7, “Server Command Options”, and
Section 5.9.1.7, “Making a Test Case If You Experience Table Corruption”.
B.3.3 Administration-Related Issues
B.3.3.1 Problems with File Permissions
If you have problems with file permissions, the
UMASK
or UMASK_DIR
environment variable might be set incorrectly when
mysqld starts. For example,
mysqld might issue the following error
message when you create a table:
ERROR: Can't find file: 'path/with/file_name
' (Errcode: 13)
The default UMASK
and
UMASK_DIR
values are
0640
and 0750
,
respectively. mysqld assumes that the value
for UMASK
or UMASK_DIR
is in octal if it starts with a zero. For example, setting
UMASK=0600
is equivalent to
UMASK=384
because 0600 octal is 384
decimal.
Assuming that you start mysqld using
mysqld_safe, change the default
UMASK
value as follows:
UMASK=384 # = 600 in octal export UMASK mysqld_safe &
Note
An exception applies for the error log file if you start
mysqld using
mysqld_safe, which does not respect
UMASK
: mysqld_safe may
create the error log file if it does not exist prior to
starting mysqld, and
mysqld_safe uses a umask set to a strict
value of 0137
. If this is unsuitable,
create the error file manually with the desired access mode
prior to executing mysqld_safe.
By default, mysqld creates database
directories with an access permission value of
0750
. To modify this behavior, set the
UMASK_DIR
variable. If you set its value,
new directories are created with the combined
UMASK
and UMASK_DIR
values. For example, to give group access to all new
directories, start mysqld_safe as follows:
UMASK_DIR=504 # = 770 in octal export UMASK_DIR mysqld_safe &
For additional details, see
Section 4.9, “Environment Variables”.
B.3.3.2 How to Reset the Root Password
If you have never assigned a root
password
for MySQL, the server does not require a password at all for
connecting as root
. However, this is
insecure. For instructions on assigning a password, see
Section 2.10.4, “Securing the Initial MySQL Account”.
If you know the root
password and want to
change it, see Section 13.7.1.1, “ALTER USER Statement”, and
Section 13.7.1.10, “SET PASSWORD Statement”.
If you assigned a root
password previously
but have forgotten it, you can assign a new password. The
following sections provide instructions for Windows and Unix
and Unix-like systems, as well as generic instructions that
apply to any system.
B.3.3.2.1 Resetting the Root Password: Windows Systems
On Windows, use the following procedure to reset the
password for the MySQL 'root'@'localhost'
account. To change the password for a
root
account with a different host name
part, modify the instructions to use that host name.
-
Log on to your system as Administrator.
-
Stop the MySQL server if it is running. For a server
that is running as a Windows service, go to the Services
manager: From the menu, select
, then
, then
. Find the MySQL
service in the list and stop it.If your server is not running as a service, you may need
to use the Task Manager to force it to stop. -
Create a text file containing the password-assignment
statement on a single line. Replace the password with
the password that you want to use.ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
-
Save the file. This example assumes that you name the
fileC:\mysql-init.txt
. -
Open a console window to get to the command prompt: From
the menu, select
, then enter
cmd as the command to be run. -
Start the MySQL server with the
init_file
system
variable set to name the file (notice that the backslash
in the option value is doubled):C:\>
cd "C:\Program Files\MySQL\MySQL Server 8.0\bin"
C:\>mysqld --init-file=C:\\mysql-init.txt
If you installed MySQL to a different location, adjust
the cd command accordingly.The server executes the contents of the file named by
theinit_file
system
variable at startup, changing the
'root'@'localhost'
account password.To have server output to appear in the console window
rather than in a log file, add the
--console
option to the
mysqld command.If you installed MySQL using the MySQL Installation
Wizard, you may need to specify a
--defaults-file
option.
For example:C:\>
mysqld
--defaults-file="C:\\ProgramData\\MySQL\\MySQL Server 8.0\\my.ini"
--init-file=C:\\mysql-init.txt
The appropriate
--defaults-file
setting
can be found using the Services Manager: From the
menu, select
, then
, then
. Find the MySQL
service in the list, right-click it, and choose the
Properties
option. ThePath
field contains the
to executable
--defaults-file
setting. -
After the server has started successfully, delete
C:\mysql-init.txt
.
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
MySQL server and restart it normally. If you run the server
as a service, start it from the Windows Services window. If
you start the server manually, use whatever command you
normally use.
B.3.3.2.2 Resetting the Root Password: Unix and Unix-Like Systems
On Unix, use the following procedure to reset the password
for the MySQL 'root'@'localhost'
account.
To change the password for a root
account
with a different host name part, modify the instructions to
use that host name.
The instructions assume that you start the MySQL server from
the Unix login account that you normally use for running it.
For example, if you run the server using the
mysql
login account, you should log in as
mysql
before using the instructions.
Alternatively, you can log in as root
,
but in this case you must start
mysqld with the
--user=mysql
option. If you
start the server as root
without using
--user=mysql
, the server may
create root
-owned files in the data
directory, such as log files, and these may cause
permission-related problems for future server startups. If
that happens, you must either change the ownership of the
files to mysql
or remove them.
-
Log on to your system as the Unix user that the MySQL
server runs as (for example,mysql
). -
Stop the MySQL server if it is running. Locate the
.pid
file that contains the
server’s process ID. The exact location and name of this
file depend on your distribution, host name, and
configuration. Common locations are
/var/lib/mysql/
,
/var/run/mysqld/
, and
/usr/local/mysql/data/
. Generally,
the file name has an extension of
.pid
and begins with either
mysqld
or your system’s host name.Stop the MySQL server by sending a normal
kill
(notkill -9
)
to the mysqld process. Use the actual
path name of the.pid
file in the
following command:shell>
kill `cat /mysql-data-directory/host_name.pid`
Use backticks (not forward quotation marks) with the
cat
command. These cause the output
ofcat
to be substituted into the
kill
command. -
Create a text file containing the password-assignment
statement on a single line. Replace the password with
the password that you want to use.ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
-
Save the file. This example assumes that you name the
file/home/me/mysql-init
. The file
contains the password, so do not save it where it can be
read by other users. If you are not logged in as
mysql
(the user the server runs as),
make sure that the file has permissions that permit
mysql
to read it. -
Start the MySQL server with the
init_file
system
variable set to name the file:shell>
mysqld --init-file=/home/me/mysql-init &
The server executes the contents of the file named by
theinit_file
system
variable at startup, changing the
'root'@'localhost'
account password.Other options may be necessary as well, depending on how
you normally start your server. For example,
--defaults-file
may be
needed before the
init_file
argument. -
After the server has started successfully, delete
/home/me/mysql-init
.
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
server and restart it normally.
B.3.3.2.3 Resetting the Root Password: Generic Instructions
The preceding sections provide password-resetting
instructions specifically for Windows and Unix and Unix-like
systems. Alternatively, on any platform, you can reset the
password using the mysql client (but this
approach is less secure):
-
Stop the MySQL server if necessary, then restart it with
the--skip-grant-tables
option. This enables anyone to connect without a
password and with all privileges, and disables
account-management statements such as
ALTER USER
and
SET PASSWORD
. Because
this is insecure, if the server is started with the
--skip-grant-tables
option, it also disables remote connections by enabling
skip_networking
. -
Connect to the MySQL server using the
mysql client; no password is
necessary because the server was started with
--skip-grant-tables
:shell>
mysql
-
In the
mysql
client, tell the server
to reload the grant tables so that account-management
statements work:mysql>
FLUSH PRIVILEGES;
Then change the
'root'@'localhost'
account password. Replace the password with the password
that you want to use. To change the password for a
root
account with a different host
name part, modify the instructions to use that host
name.mysql>
ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';
You should now be able to connect to the MySQL server as
root
using the new password. Stop the
server and restart it normally (without the
--skip-grant-tables
option
and without enabling the
skip_networking
system
variable).
B.3.3.3 What to Do If MySQL Keeps Crashing
Each MySQL version is tested on many platforms before it is
released. This does not mean that there are no bugs in MySQL,
but if there are bugs, they should be very few and can be hard
to find. If you have a problem, it always helps if you try to
find out exactly what crashes your system, because you have a
much better chance of getting the problem fixed quickly.
First, you should try to find out whether the problem is that
the mysqld server dies or whether your
problem has to do with your client. You can check how long
your mysqld server has been up by executing
mysqladmin version. If
mysqld has died and restarted, you may find
the reason by looking in the server’s error log. See
Section 5.4.2, “The Error Log”.
On some systems, you can find in the error log a stack trace
of where mysqld died. Note that the
variable values written in the error log may not always be
100% correct.
Many unexpected server exits are caused by corrupted data
files or index files. MySQL updates the files on disk with the
write()
system call after every SQL
statement and before the client is notified about the result.
(This is not true if you are running with the
delay_key_write
system
variable enabled, in which case data files are written but not
index files.) This means that data file contents are safe even
if mysqld crashes, because the operating
system ensures that the unflushed data is written to disk. You
can force MySQL to flush everything to disk after every SQL
statement by starting mysqld with the
--flush
option.
The preceding means that normally you should not get corrupted
tables unless one of the following happens:
-
The MySQL server or the server host was killed in the
middle of an update. -
You have found a bug in mysqld that
caused it to die in the middle of an update. -
Some external program is manipulating data files or index
files at the same time as mysqld
without locking the table properly. -
You are running many mysqld servers
using the same data directory on a system that does not
support good file system locks (normally handled by the
lockd
lock manager), or you are running
multiple servers with external locking disabled. -
You have a crashed data file or index file that contains
very corrupt data that confused mysqld. -
You have found a bug in the data storage code. This isn’t
likely, but it is at least possible. In this case, you can
try to change the storage engine to another engine by
usingALTER TABLE
on a
repaired copy of the table.
Because it is very difficult to know why something is
crashing, first try to check whether things that work for
others result in an unexpected exit for you. Try the following
things:
-
Stop the mysqld server with
mysqladmin shutdown, run
myisamchk —silent —force */*.MYI from
the data directory to check allMyISAM
tables, and restart mysqld. This
ensures that you are running from a clean state. See
Chapter 5, MySQL Server Administration. -
Start mysqld with the general query log
enabled (see Section 5.4.3, “The General Query Log”). Then try to
determine from the information written to the log whether
some specific query kills the server. About 95% of all
bugs are related to a particular query. Normally, this is
one of the last queries in the log file just before the
server restarts. See Section 5.4.3, “The General Query Log”. If you
can repeatedly kill MySQL with a specific query, even when
you have checked all tables just before issuing it, then
you have isolated the bug and should submit a bug report
for it. See Section 1.6, “How to Report Bugs or Problems”. -
Try to make a test case that we can use to repeat the
problem. See Section 5.9, “Debugging MySQL”. -
Try the
fork_big.pl
script. (It is
located in thetests
directory of
source distributions.) -
Configuring MySQL for debugging makes it much easier to
gather information about possible errors if something goes
wrong. Reconfigure MySQL with the
-DWITH_DEBUG=1
option to
CMake and then recompile. See
Section 5.9, “Debugging MySQL”. -
Make sure that you have applied the latest patches for
your operating system. -
Use the
--skip-external-locking
option to mysqld. On some systems, the
lockd
lock manager does not work
properly; the
--skip-external-locking
option tells mysqld not to use external
locking. (This means that you cannot run two
mysqld servers on the same data
directory and that you must be careful if you use
myisamchk. Nevertheless, it may be
instructive to try the option as a test.) -
If mysqld appears to be running but not
responding, try mysqladmin -u root
processlist. Sometimes mysqld
is not hung even though it seems unresponsive. The problem
may be that all connections are in use, or there may be
some internal lock problem. mysqladmin -u root
processlist usually is able to make a connection
even in these cases, and can provide useful information
about the current number of connections and their status. -
Run the command mysqladmin -i 5 status
or mysqladmin -i 5 -r status in a
separate window to produce statistics while running other
queries. -
Try the following:
-
Start mysqld from
gdb (or another debugger). See
Section 5.9, “Debugging MySQL”. -
Run your test scripts.
-
Print the backtrace and the local variables at the
three lowest levels. In gdb, you
can do this with the following commands when
mysqld has crashed inside
gdb:backtrace info local up info local up info local
With gdb, you can also examine
which threads exist withinfo
and switch to a specific thread with
threads
thread
, where
N
N
is the thread ID.
-
-
Try to simulate your application with a Perl script to
force MySQL to exit or misbehave. -
Send a normal bug report. See
Section 1.6, “How to Report Bugs or Problems”. Be even more detailed than
usual. Because MySQL works for many people, the crash
might result from something that exists only on your
computer (for example, an error that is related to your
particular system libraries). -
If you have a problem with tables containing
dynamic-length rows and you are using only
VARCHAR
columns (not
BLOB
or
TEXT
columns), you can try
to change allVARCHAR
to
CHAR
with
ALTER TABLE
. This forces
MySQL to use fixed-size rows. Fixed-size rows take a
little extra space, but are much more tolerant to
corruption.The current dynamic row code has been in use for several
years with very few problems, but dynamic-length rows are
by nature more prone to errors, so it may be a good idea
to try this strategy to see whether it helps. -
Consider the possibility of hardware faults when
diagnosing problems. Defective hardware can be the cause
of data corruption. Pay particular attention to your
memory and disk subsystems when troubleshooting hardware.
B.3.3.4 How MySQL Handles a Full Disk
This section describes how MySQL responds to disk-full errors
(such as “no space left on device”), and to
quota-exceeded errors (such as “write failed” or
“user block limit reached”).
This section is relevant for writes to
MyISAM
tables. It also applies for writes
to binary log files and binary log index file, except that
references to “row” and “record”
should be understood to mean “event.”
When a disk-full condition occurs, MySQL does the following:
-
It checks once every minute to see whether there is enough
space to write the current row. If there is enough space,
it continues as if nothing had happened. -
Every 10 minutes it writes an entry to the log file,
warning about the disk-full condition.
To alleviate the problem, take the following actions:
-
To continue, you only have to free enough disk space to
insert all records. -
Alternatively, to abort the thread, use
mysqladmin kill. The thread is aborted
the next time it checks the disk (in one minute). -
Other threads might be waiting for the table that caused
the disk-full condition. If you have several
“locked” threads, killing the one thread that
is waiting on the disk-full condition enables the other
threads to continue.
Exceptions to the preceding behavior are when you use
REPAIR TABLE
or
OPTIMIZE TABLE
or when the
indexes are created in a batch after LOAD
or after an
DATAALTER
statement. All of these statements may create
TABLE
large temporary files that, if left to themselves, would cause
big problems for the rest of the system. If the disk becomes
full while MySQL is doing any of these operations, it removes
the big temporary files and mark the table as crashed. The
exception is that for ALTER
, the old table is left unchanged.
TABLE
B.3.3.5 Where MySQL Stores Temporary Files
On Unix, MySQL uses the value of the TMPDIR
environment variable as the path name of the directory in
which to store temporary files. If TMPDIR
is not set, MySQL uses the system default, which is usually
/tmp
, /var/tmp
, or
/usr/tmp
.
On Windows, MySQL checks in order the values of the
TMPDIR
, TEMP
, and
TMP
environment variables. For the first
one found to be set, MySQL uses it and does not check those
remaining. If none of TMPDIR
,
TEMP
, or TMP
are set,
MySQL uses the Windows system default, which is usually
C:\windows\temp\
.
If the file system containing your temporary file directory is
too small, you can use the mysqld
--tmpdir
option to specify a
directory in a file system where you have enough space.
The --tmpdir
option can be set
to a list of several paths that are used in round-robin
fashion. Paths should be separated by colon characters
(:
) on Unix and semicolon characters
(;
) on Windows.
Note
To spread the load effectively, these paths should be
located on different physical disks,
not different partitions of the same disk.
If the MySQL server is acting as a replica, you can set the
slave_load_tmpdir
system
variable to specify a separate directory for holding temporary
files when replicating LOAD
statements. This directory should be in a
DATA
disk-based file system (not a memory-based file system) so
that the temporary files used to replicate LOAD DATA can
survive machine restarts. The directory also should not be one
that is cleared by the operating system during the system
startup process. However, replication can now continue after a
restart if the temporary files have been removed.
MySQL arranges that temporary files are removed if
mysqld is terminated. On platforms that
support it (such as Unix), this is done by unlinking the file
after opening it. The disadvantage of this is that the name
does not appear in directory listings and you do not see a big
temporary file that fills up the file system in which the
temporary file directory is located. (In such cases,
lsof +L1 may be helpful in identifying
large files associated with mysqld.)
When sorting (ORDER BY
or GROUP
), MySQL normally uses one or two temporary files.
BY
The maximum disk space required is determined by the following
expression:
(length of what is sorted + sizeof(row pointer)) * number of matched rows * 2
The row pointer size is usually four bytes, but may grow in
the future for really big tables.
For some statements, MySQL creates temporary SQL tables that
are not hidden and have names that begin with
#sql
.
Some SELECT
queries creates
temporary SQL tables to hold intermediate results.
DDL operations that rebuild the table and are not performed
online using the ALGORITHM=INPLACE
technique create a temporary copy of the original table in the
same directory as the original table.
Online DDL operations may use temporary log files for
recording concurrent DML, temporary sort files when creating
an index, and temporary intermediate tables files when
rebuilding the table. For more information, see
Section 15.12.3, “Online DDL Space Requirements”.
InnoDB
user-created temporary tables and
on-disk internal temporary tables are created in a temporary
tablespace file named ibtmp1
in the MySQL
data directory. For more information, see
Section 15.6.3.5, “Temporary Tablespaces”.
See also
Section 15.15.7, “InnoDB INFORMATION_SCHEMA Temporary Table Info Table”.
The optional EXTENDED
modifier causes
SHOW TABLES
to list hidden
tables created by failed ALTER
statements. See Section 13.7.7.39, “SHOW TABLES Statement”.
TABLE
B.3.3.6 How to Protect or Change the MySQL Unix Socket File
The default location for the Unix socket file that the server
uses for communication with local clients is
/tmp/mysql.sock
. (For some distribution
formats, the directory might be different, such as
/var/lib/mysql
for RPMs.)
On some versions of Unix, anyone can delete files in the
/tmp
directory or other similar
directories used for temporary files. If the socket file is
located in such a directory on your system, this might cause
problems.
On most versions of Unix, you can protect your
/tmp
directory so that files can be
deleted only by their owners or the superuser
(root
). To do this, set the
sticky
bit on the /tmp
directory by logging in as root
and using
the following command:
shell> chmod +t /tmp
You can check whether the sticky
bit is set
by executing ls -ld /tmp
. If the last
permission character is t
, the bit is set.
Another approach is to change the place where the server
creates the Unix socket file. If you do this, you should also
let client programs know the new location of the file. You can
specify the file location in several ways:
-
Specify the path in a global or local option file. For
example, put the following lines in
/etc/my.cnf
:[mysqld] socket=/path/to/socket [client] socket=/path/to/socket
See Section 4.2.2.2, “Using Option Files”.
-
Specify a
--socket
option
on the command line to mysqld_safe and
when you run client programs. -
Set the
MYSQL_UNIX_PORT
environment
variable to the path of the Unix socket file. -
Recompile MySQL from source to use a different default
Unix socket file location. Define the path to the file
with theMYSQL_UNIX_ADDR
option when you run CMake. See
Section 2.9.7, “MySQL Source-Configuration Options”.
You can test whether the new socket location works by
attempting to connect to the server with this command:
shell> mysqladmin --socket=/path/to/socket version
B.3.3.7 Time Zone Problems
If you have a problem with SELECT NOW()
returning values in UTC and not your local time, you have to
tell the server your current time zone. The same applies if
UNIX_TIMESTAMP()
returns the
wrong value. This should be done for the environment in which
the server runs (for example, in
mysqld_safe or
mysql.server). See
Section 4.9, “Environment Variables”.
You can set the time zone for the server with the
--timezone=
timezone_name
option to mysqld_safe. You can also set it
by setting the TZ
environment variable
before you start mysqld.
The permissible values for
--timezone
or
TZ
are system dependent. Consult your
operating system documentation to see what values are
acceptable.
B.3.4 Query-Related Issues
B.3.4.1 Case Sensitivity in String Searches
For nonbinary strings (CHAR
,
VARCHAR
,
TEXT
), string searches use the
collation of the comparison operands. For binary strings
(BINARY
,
VARBINARY
,
BLOB
), comparisons use the
numeric values of the bytes in the operands; this means that
for alphabetic characters, comparisons are case-sensitive.
A comparison between a nonbinary string and binary string is
treated as a comparison of binary strings.
Simple comparison operations (>=, >, =, <,
, sorting, and grouping) are based on each
<=
character’s “sort value.” Characters with the
same sort value are treated as the same character. For
example, if e
and
é
have the same sort value in a
given collation, they compare as equal.
The default character set and collation are
utf8mb4
and
utf8mb4_0900_ai_ci
, so nonbinary string
comparisons are case-insensitive by default. This means that
if you search with
, you get all column values that start withcol_name
LIKE
'a%'
A
or a
. To make this
search case-sensitive, make sure that one of the operands has
a case-sensitive or binary collation. For example, if you are
comparing a column and a string that both have the
utf8mb4
character set, you can use the
COLLATE
operator to cause either operand to
have the utf8mb4_0900_as_cs
or
utf8mb4_bin
collation:
col_name
COLLATE utf8mb4_0900_as_cs LIKE 'a%'col_name
LIKE 'a%' COLLATE utf8mb4_0900_as_cscol_name
COLLATE utf8mb4_bin LIKE 'a%'col_name
LIKE 'a%' COLLATE utf8mb4_bin
If you want a column always to be treated in case-sensitive
fashion, declare it with a case-sensitive or binary collation.
See Section 13.1.20, “CREATE TABLE Statement”.
To cause a case-sensitive comparison of nonbinary strings to
be case-insensitive, use COLLATE
to name a
case-insensitive collation. The strings in the following
example normally are case-sensitive, but
COLLATE
changes the comparison to be
case-insensitive:
mysql>SET NAMES 'utf8mb4';
mysql>SET @s1 = 'MySQL' COLLATE utf8mb4_bin,
@s2 = 'mysql' COLLATE utf8mb4_bin;
mysql>SELECT @s1 = @s2;
+-----------+ | @s1 = @s2 | +-----------+ | 0 | +-----------+ mysql>SELECT @s1 COLLATE utf8mb4_0900_ai_ci = @s2;
+--------------------------------------+ | @s1 COLLATE utf8mb4_0900_ai_ci = @s2 | +--------------------------------------+ | 1 | +--------------------------------------+
A binary string is case-sensitive in comparisons. To compare
the string as case-insensitive, convert it to a nonbinary
string and use COLLATE
to name a
case-insensitive collation:
mysql>SET @s = BINARY 'MySQL';
mysql>SELECT @s = 'mysql';
+--------------+ | @s = 'mysql' | +--------------+ | 0 | +--------------+ mysql>SELECT CONVERT(@s USING utf8mb4) COLLATE utf8mb4_0900_ai_ci = 'mysql';
+----------------------------------------------------------------+ | CONVERT(@s USING utf8mb4) COLLATE utf8mb4_0900_ai_ci = 'mysql' | +----------------------------------------------------------------+ | 1 | +----------------------------------------------------------------+
To determine whether a value is compared as a nonbinary or
binary string, use the
COLLATION()
function. This
example shows that VERSION()
returns a string that has a case-insensitive collation, so
comparisons are case-insensitive:
mysql> SELECT COLLATION(VERSION());
+----------------------+
| COLLATION(VERSION()) |
+----------------------+
| utf8_general_ci |
+----------------------+
For binary strings, the collation value is
binary
, so comparisons are case sensitive.
One context in which you can expect to see
binary
is for compression functions, which
return binary strings as a general rule: string:
mysql> SELECT COLLATION(COMPRESS('x'));
+--------------------------+
| COLLATION(COMPRESS('x')) |
+--------------------------+
| binary |
+--------------------------+
To check the sort value of a string, the
WEIGHT_STRING()
may be helpful.
See Section 12.8, “String Functions and Operators”.
B.3.4.2 Problems Using DATE Columns
The format of a DATE
value is
'
.YYYY-MM-DD
'
According to standard SQL, no other format is permitted. You
should use this format in
UPDATE
expressions and in the
WHERE
clause of
SELECT
statements. For example:
SELECT * FROM t1 WHERE date >= '2003-05-05';
As a convenience, MySQL automatically converts a date to a
number if the date is used in numeric context and vice versa.
MySQL also permits a “relaxed” string format when
updating and in a WHERE
clause that
compares a date to a DATE
,
DATETIME
, or
TIMESTAMP
column.
“Relaxed” format means that any punctuation
character may be used as the separator between parts. For
example, '2004-08-15'
and
'2004#08#15'
are equivalent. MySQL can also
convert a string containing no separators (such as
'20040815'
), provided it makes sense as a
date.
When you compare a DATE
,
TIME
,
DATETIME
, or
TIMESTAMP
to a constant string
with the <
, <=
,
=
, >=
,
>
, or BETWEEN
operators, MySQL normally converts the string to an internal
long integer for faster comparison (and also for a bit more
“relaxed” string checking). However, this
conversion is subject to the following exceptions:
-
When you compare two columns
-
When you compare a
DATE
,
TIME
,
DATETIME
, or
TIMESTAMP
column to an
expression -
When you use any comparison method other than those just
listed, such asIN
or
STRCMP()
.
For those exceptions, the comparison is done by converting the
objects to strings and performing a string comparison.
To be on the safe side, assume that strings are compared as
strings and use the appropriate string functions if you want
to compare a temporal value to a string.
The special “zero” date
'0000-00-00'
can be stored and retrieved as
'0000-00-00'.
When a
'0000-00-00'
date is used through
Connector/ODBC, it is automatically converted to
NULL
because ODBC cannot handle that kind
of date.
Because MySQL performs the conversions just described, the
following statements work (assume that
idate
is a
DATE
column):
INSERT INTO t1 (idate) VALUES (19970505); INSERT INTO t1 (idate) VALUES ('19970505'); INSERT INTO t1 (idate) VALUES ('97-05-05'); INSERT INTO t1 (idate) VALUES ('1997.05.05'); INSERT INTO t1 (idate) VALUES ('1997 05 05'); INSERT INTO t1 (idate) VALUES ('0000-00-00'); SELECT idate FROM t1 WHERE idate >= '1997-05-05'; SELECT idate FROM t1 WHERE idate >= 19970505; SELECT MOD(idate,100) FROM t1 WHERE idate >= 19970505; SELECT idate FROM t1 WHERE idate >= '19970505';
However, the following statement does not work:
SELECT idate FROM t1 WHERE STRCMP(idate,'20030505')=0;
STRCMP()
is a string function,
so it converts idate
to a string in
'
YYYY-MM-DD
'
format and performs a string comparison. It does not convert
'20030505'
to the date
'2003-05-05'
and perform a date comparison.
If you enable the
ALLOW_INVALID_DATES
SQL
mode, MySQL permits you to store dates that are given only
limited checking: MySQL requires only that the day is in the
range from 1 to 31 and the month is in the range from 1 to 12.
This makes MySQL very convenient for Web applications where
you obtain year, month, and day in three different fields and
you want to store exactly what the user inserted (without date
validation).
MySQL permits you to store dates where the day or month and
day are zero. This is convenient if you want to store a
birthdate in a DATE
column and
you know only part of the date. To disallow zero month or day
parts in dates, enable the
NO_ZERO_IN_DATE
mode.
MySQL permits you to store a “zero” value of
'0000-00-00'
as a “dummy
date.” This is in some cases more convenient than using
NULL
values. If a date to be stored in a
DATE
column cannot be converted
to any reasonable value, MySQL stores
'0000-00-00'
. To disallow
'0000-00-00'
, enable the
NO_ZERO_DATE
mode.
To have MySQL check all dates and accept only legal dates
(unless overridden by IGNORE
), set the
sql_mode
system variable to
"NO_ZERO_IN_DATE,NO_ZERO_DATE"
.
B.3.4.3 Problems with NULL Values
The concept of the NULL
value is a common
source of confusion for newcomers to SQL, who often think that
NULL
is the same thing as an empty string
''
. This is not the case. For example, the
following statements are completely different:
mysql>INSERT INTO my_table (phone) VALUES (NULL);
mysql>INSERT INTO my_table (phone) VALUES ('');
Both statements insert a value into the
phone
column, but the first inserts a
NULL
value and the second inserts an empty
string. The meaning of the first can be regarded as
“phone number is not known” and the meaning of
the second can be regarded as “the person is known to
have no phone, and thus no phone number.”
To help with NULL
handling, you can use the
IS NULL
and IS
operators and the
NOT NULL
IFNULL()
function.
In SQL, the NULL
value is never true in
comparison to any other value, even NULL
.
An expression that contains NULL
always
produces a NULL
value unless otherwise
indicated in the documentation for the operators and functions
involved in the expression. All columns in the following
example return NULL
:
mysql> SELECT NULL, 1+NULL, CONCAT('Invisible',NULL);
To search for column values that are NULL
,
you cannot use an expr = NULL
test. The
following statement returns no rows, because expr =
is never true for any expression:
NULL
mysql> SELECT * FROM my_table WHERE phone = NULL;
To look for NULL
values, you must use the
IS NULL
test. The following
statements show how to find the NULL
phone
number and the empty phone number:
mysql>SELECT * FROM my_table WHERE phone IS NULL;
mysql>SELECT * FROM my_table WHERE phone = '';
See Section 3.3.4.6, “Working with NULL Values”, for additional
information and examples.
You can add an index on a column that can have
NULL
values if you are using the
MyISAM
, InnoDB
, or
MEMORY
storage engine. Otherwise, you must
declare an indexed column NOT NULL
, and you
cannot insert NULL
into the column.
When reading data with LOAD
, empty or missing columns are updated with
DATA
''
. To load a NULL
value
into a column, use \N
in the data file. The
literal word NULL
may also be used under
some circumstances. See Section 13.2.7, “LOAD DATA Statement”.
When using DISTINCT
, GROUP
, or
BYORDER BY
, all
NULL
values are regarded as equal.
When using ORDER BY
,
NULL
values are presented first, or last if
you specify DESC
to sort in descending
order.
Aggregate (group) functions such as
COUNT()
,
MIN()
, and
SUM()
ignore
NULL
values. The exception to this is
COUNT(*)
, which counts rows and
not individual column values. For example, the following
statement produces two counts. The first is a count of the
number of rows in the table, and the second is a count of the
number of non-NULL
values in the
age
column:
mysql> SELECT COUNT(*), COUNT(age) FROM person;
For some data types, MySQL handles NULL
values specially. If you insert NULL
into a
TIMESTAMP
column, the current
date and time is inserted. If you insert
NULL
into an integer or floating-point
column that has the AUTO_INCREMENT
attribute, the next number in the sequence is inserted.
B.3.4.4 Problems with Column Aliases
An alias can be used in a query select list to give a column a
different name. You can use the alias in GROUP
,
BYORDER BY
, or
HAVING
clauses to refer to the column:
SELECT SQRT(a*b) AS root FROMtbl_name
GROUP BY root HAVING root > 0; SELECT id, COUNT(*) AS cnt FROMtbl_name
GROUP BY id HAVING cnt > 0; SELECT id AS 'Customer identity' FROMtbl_name
;
Standard SQL disallows references to column aliases in a
WHERE
clause. This restriction is imposed
because when the WHERE
clause is evaluated,
the column value may not yet have been determined. For
example, the following query is illegal:
SELECT id, COUNT(*) AS cnt FROM tbl_name
WHERE cnt > 0 GROUP BY id;
The WHERE
clause determines which rows
should be included in the GROUP BY
clause,
but it refers to the alias of a column value that is not known
until after the rows have been selected, and grouped by the
GROUP BY
.
In the select list of a query, a quoted column alias can be
specified using identifier or string quoting characters:
SELECT 1 AS `one`, 2 AS 'two';
Elsewhere in the statement, quoted references to the alias
must use identifier quoting or the reference is treated as a
string literal. For example, this statement groups by the
values in column id
, referenced using the
alias `a`
:
SELECT id AS 'a', COUNT(*) AS cnt FROM tbl_name
GROUP BY `a`;
This statement groups by the literal string
'a'
and does not work as you may expect:
SELECT id AS 'a', COUNT(*) AS cnt FROM tbl_name
GROUP BY 'a';
B.3.4.5 Rollback Failure for Nontransactional Tables
If you receive the following message when trying to perform a
ROLLBACK
, it
means that one or more of the tables you used in the
transaction do not support transactions:
Warning: Some non-transactional changed tables couldn't be rolled back
These nontransactional tables are not affected by the
ROLLBACK
statement.
If you were not deliberately mixing transactional and
nontransactional tables within the transaction, the most
likely cause for this message is that a table you thought was
transactional actually is not. This can happen if you try to
create a table using a transactional storage engine that is
not supported by your mysqld server (or
that was disabled with a startup option). If
mysqld does not support a storage engine,
it instead creates the table as a MyISAM
table, which is nontransactional.
You can check the storage engine for a table by using either
of these statements:
SHOW TABLE STATUS LIKE 'tbl_name
'; SHOW CREATE TABLEtbl_name
;
See Section 13.7.7.38, “SHOW TABLE STATUS Statement”, and
Section 13.7.7.10, “SHOW CREATE TABLE Statement”.
To check which storage engines your mysqld
server supports, use this statement:
SHOW ENGINES;
See Section 13.7.7.16, “SHOW ENGINES Statement” for full details.
B.3.4.6 Deleting Rows from Related Tables
If the total length of the
DELETE
statement for
related_table
is more than the default
value of the
max_allowed_packet
system
variable, you should split it into smaller parts and execute
multiple DELETE
statements. You
probably get the fastest DELETE
by specifying only 100 to 1,000
related_column
values per statement if the
related_column
is indexed. If the
related_column
isn’t indexed, the speed is
independent of the number of arguments in the
IN
clause.
B.3.4.7 Solving Problems with No Matching Rows
If you have a complicated query that uses many tables but that
returns no rows, you should use the following procedure to
find out what is wrong:
-
Test the query with
EXPLAIN
to check whether you can find something that is obviously
wrong. See Section 13.8.2, “EXPLAIN Statement”. -
Select only those columns that are used in the
WHERE
clause. -
Remove one table at a time from the query until it returns
some rows. If the tables are large, it is a good idea to
useLIMIT 10
with the query. -
Issue a
SELECT
for the
column that should have matched a row against the table
that was last removed from the query. -
If you are comparing
FLOAT
orDOUBLE
columns with
numbers that have decimals, you cannot use equality
(=
) comparisons. This problem is common
in most computer languages because not all floating-point
values can be stored with exact precision. In some cases,
changing theFLOAT
to a
DOUBLE
fixes this. See
Section B.3.4.8, “Problems with Floating-Point Values”. -
If you still cannot figure out what is wrong, create a
minimal test that can be run withmysql test <
that shows your problems. You can
query.sql
create a test file by dumping the tables with
mysqldump —quick db_name
tbl_name_1
…
tbl_name_n
>
query.sql. Open the file in an editor, remove
some insert lines (if there are more than needed to
demonstrate the problem), and add your
SELECT
statement at the end
of the file.Verify that the test file demonstrates the problem by
executing these commands:shell>
mysqladmin create test2
shell>mysql test2 < query.sql
Attach the test file to a bug report, which you can file
using the instructions in Section 1.6, “How to Report Bugs or Problems”.
B.3.4.8 Problems with Floating-Point Values
Floating-point numbers sometimes cause confusion because they
are approximate and not stored as exact values. A
floating-point value as written in an SQL statement may not be
the same as the value represented internally. Attempts to
treat floating-point values as exact in comparisons may lead
to problems. They are also subject to platform or
implementation dependencies. The
FLOAT
and
DOUBLE
data types are subject
to these issues. For DECIMAL
columns, MySQL performs operations with a precision of 65
decimal digits, which should solve most common inaccuracy
problems.
The following example uses
DOUBLE
to demonstrate how
calculations that are done using floating-point operations are
subject to floating-point error.
mysql>CREATE TABLE t1 (i INT, d1 DOUBLE, d2 DOUBLE);
mysql>INSERT INTO t1 VALUES (1, 101.40, 21.40), (1, -80.00, 0.00),
->(2, 0.00, 0.00), (2, -13.20, 0.00), (2, 59.60, 46.40),
->(2, 30.40, 30.40), (3, 37.00, 7.40), (3, -29.60, 0.00),
->(4, 60.00, 15.40), (4, -10.60, 0.00), (4, -34.00, 0.00),
->(5, 33.00, 0.00), (5, -25.80, 0.00), (5, 0.00, 7.20),
->(6, 0.00, 0.00), (6, -51.40, 0.00);
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b
->FROM t1 GROUP BY i HAVING a <> b;
+------+-------+------+ | i | a | b | +------+-------+------+ | 1 | 21.4 | 21.4 | | 2 | 76.8 | 76.8 | | 3 | 7.4 | 7.4 | | 4 | 15.4 | 15.4 | | 5 | 7.2 | 7.2 | | 6 | -51.4 | 0 | +------+-------+------+
The result is correct. Although the first five records look
like they should not satisfy the comparison (the values of
a
and b
do not appear to
be different), they may do so because the difference between
the numbers shows up around the tenth decimal or so, depending
on factors such as computer architecture or the compiler
version or optimization level. For example, different CPUs may
evaluate floating-point numbers differently.
If columns d1
and d2
had
been defined as DECIMAL
rather
than DOUBLE
, the result of the
SELECT
query would have
contained only one row—the last one shown above.
The correct way to do floating-point number comparison is to
first decide on an acceptable tolerance for differences
between the numbers and then do the comparison against the
tolerance value. For example, if we agree that floating-point
numbers should be regarded the same if they are same within a
precision of one in ten thousand (0.0001), the comparison
should be written to find differences larger than the
tolerance value:
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
->GROUP BY i HAVING ABS(a - b) > 0.0001;
+------+-------+------+ | i | a | b | +------+-------+------+ | 6 | -51.4 | 0 | +------+-------+------+ 1 row in set (0.00 sec)
Conversely, to get rows where the numbers are the same, the
test should find differences within the tolerance value:
mysql>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1
->GROUP BY i HAVING ABS(a - b) <= 0.0001;
+------+------+------+ | i | a | b | +------+------+------+ | 1 | 21.4 | 21.4 | | 2 | 76.8 | 76.8 | | 3 | 7.4 | 7.4 | | 4 | 15.4 | 15.4 | | 5 | 7.2 | 7.2 | +------+------+------+ 5 rows in set (0.03 sec)
Floating-point values are subject to platform or
implementation dependencies. Suppose that you execute the
following statements:
CREATE TABLE t1(c1 FLOAT(53,0), c2 FLOAT(53,0)); INSERT INTO t1 VALUES('1e+52','-1e+52'); SELECT * FROM t1;
On some platforms, the SELECT
statement
returns inf
and -inf
. On
others, it returns 0
and
-0
.
An implication of the preceding issues is that if you attempt
to create a replica by dumping table contents with
mysqldump on the source and reloading the
dump file into the replica, tables containing floating-point
columns might differ between the two hosts.
B.3.5 Optimizer-Related Issues
MySQL uses a cost-based optimizer to determine the best way to
resolve a query. In many cases, MySQL can calculate the best
possible query plan, but sometimes MySQL does not have enough
information about the data at hand and has to make
“educated” guesses about the data.
For the cases when MySQL does not do the «right» thing, tools
that you have available to help MySQL are:
-
Use the
EXPLAIN
statement to
get information about how MySQL processes a query. To use
it, just add the keyword
EXPLAIN
to the front of your
SELECT
statement:mysql>
EXPLAIN SELECT * FROM t1, t2 WHERE t1.i = t2.i;
EXPLAIN
is discussed in more
detail in Section 13.8.2, “EXPLAIN Statement”. -
Use
ANALYZE TABLE
to update the
tbl_name
key distributions for the scanned table. See
Section 13.7.3.1, “ANALYZE TABLE Statement”. -
Use
FORCE INDEX
for the scanned table to
tell MySQL that table scans are very expensive compared to
using the given index:SELECT * FROM t1, t2 FORCE INDEX (index_for_column) WHERE t1.col_name=t2.col_name;
USE INDEX
andIGNORE
may also be useful. See
INDEX
Section 8.9.4, “Index Hints”. -
Global and table-level
STRAIGHT_JOIN
. See
Section 13.2.10, “SELECT Statement”. -
You can tune global or thread-specific system variables. For
example, start mysqld with the
--max-seeks-for-key=1000
option or useSET max_seeks_for_key=1000
to tell the optimizer to assume that no key scan causes more
than 1,000 key seeks. See
Section 5.1.8, “Server System Variables”.
B.3.6 Table Definition-Related Issues
B.3.6.1 Problems with ALTER TABLE
If you get a duplicate-key error when using
ALTER TABLE
to change the
character set or collation of a character column, the cause is
either that the new column collation maps two keys to the same
value or that the table is corrupted. In the latter case, you
should run REPAIR TABLE
on the
table. REPAIR TABLE
works for
MyISAM
, ARCHIVE
, and
CSV
tables.
If you use ALTER TABLE
on a
transactional table or if you are using Windows,
ALTER TABLE
unlocks the table
if you had done a
LOCK
on it. This is done because
TABLE
InnoDB
and these operating systems cannot
drop a table that is in use.
B.3.6.2 TEMPORARY Table Problems
Temporary tables created with
CREATE TEMPORARY
have the following limitations:
TABLE
-
TEMPORARY
tables are supported only by
theInnoDB
,MEMORY
,
MyISAM
, andMERGE
storage engines. -
Temporary tables are not supported for NDB Cluster.
-
The
SHOW TABLES
statement
does not listTEMPORARY
tables. -
To rename
TEMPORARY
tables,
RENAME TABLE
does not work. Use
ALTER TABLE
instead:ALTER TABLE old_name RENAME new_name;
-
You cannot refer to a
TEMPORARY
table
more than once in the same query. For example, the
following does not work:SELECT * FROM temp_table JOIN temp_table AS t2;
The statement produces this error:
ERROR 1137: Can't reopen table: 'temp_table'
You can work around this issue if your query permits use
of a common table expression (CTE) rather than a
TEMPORARY
table. For example, this
fails with the Can’t reopen table
error:CREATE TEMPORARY TABLE t SELECT 1 AS col_a, 2 AS col_b; SELECT * FROM t AS t1 JOIN t AS t2;
To avoid the error, use a
WITH
clause that defines a
CTE, rather than theTEMPORARY
table:WITH cte AS (SELECT 1 AS col_a, 2 AS col_b) SELECT * FROM cte AS t1 JOIN cte AS t2;
-
The Can’t reopen table error also
occurs if you refer to a temporary table multiple times in
a stored function under different aliases, even if the
references occur in different statements within the
function. It may occur for temporary tables created
outside stored functions and referred to across multiple
calling and callee functions. -
If a
TEMPORARY
is created with the same
name as an existing non-TEMPORARY
table, the non-TEMPORARY
table is
hidden until theTEMPORARY
table is
dropped, even if the tables use different storage engines. -
There are known issues in using temporary tables with
replication. See
Section 17.5.1.31, “Replication and Temporary Tables”, for
more information.
B.3.7 Known Issues in MySQL
This section lists known issues in recent versions of MySQL.
For information about platform-specific issues, see the
installation and debugging instructions in
Section 2.1, “General Installation Guidance”, and
Section 5.9, “Debugging MySQL”.
The following problems are known:
-
Subquery optimization for
IN
is not as
effective as for=
. -
Even if you use
lower_case_table_names=2
(which enables MySQL to remember the case used for databases
and table names), MySQL does not remember the case used for
database names for the function
DATABASE()
or within the
various logs (on case-insensitive systems). -
Dropping a
FOREIGN KEY
constraint does
not work in replication because the constraint may have
another name on the replica. -
REPLACE
(and
LOAD DATA
with the
REPLACE
option) does not
triggerON DELETE CASCADE
. -
DISTINCT
withORDER BY
does not work inside
GROUP_CONCAT()
if you do not
use all and only those columns that are in the
DISTINCT
list. -
When inserting a big integer value (between
263 and
264−1) into a decimal or
string column, it is inserted as a negative value because
the number is evaluated in signed integer context. -
With statement-based binary logging, the source server
writes the executed queries to the binary log. This is a
very fast, compact, and efficient logging method that works
perfectly in most cases. However, it is possible for the
data on the source and replica to become different if a
query is designed in such a way that the data modification
is nondeterministic (generally not a recommended practice,
even outside of replication).For example:
-
CREATE
or
TABLE ... SELECT
INSERT
statements that insert zero or
... SELECT
NULL
values into an
AUTO_INCREMENT
column. -
DELETE
if you are
deleting rows from a table that has foreign keys with
ON DELETE CASCADE
properties. -
REPLACE ...
,
SELECTINSERT IGNORE ...
if you have duplicate key values in the
SELECT
inserted data.
If and only if the preceding queries
have noORDER BY
clause guaranteeing a
deterministic order.For example, for
INSERT ...
with no
SELECTORDER BY
, the
SELECT
may return rows in a
different order (which results in a row having different
ranks, hence getting a different number in the
AUTO_INCREMENT
column), depending on the
choices made by the optimizers on the source and replica.A query is optimized differently on the source and replica
only if:-
The table is stored using a different storage engine on
the source than on the replica. (It is possible to use
different storage engines on the source and replica. For
example, you can useInnoDB
on the
source, butMyISAM
on the replica if
the replica has less available disk space.) -
MySQL buffer sizes
(key_buffer_size
, and
so on) are different on the source and replica. -
The source and replica run different MySQL versions, and
the optimizer code differs between these versions.
This problem may also affect database restoration using
mysqlbinlog|mysql.The easiest way to avoid this problem is to add an
ORDER BY
clause to the aforementioned
nondeterministic queries to ensure that the rows are always
stored or modified in the same order. Using row-based or
mixed logging format also avoids the problem. -
-
Log file names are based on the server host name if you do
not specify a file name with the startup option. To retain
the same log file names if you change your host name to
something else, you must explicitly use options such as
--log-bin=
.old_host_name
-bin
See Section 5.1.7, “Server Command Options”. Alternatively, rename
the old files to reflect your host name change. If these are
binary logs, you must edit the binary log index file and fix
the binary log file names there as well. (The same is true
for the relay logs on a replica.) -
mysqlbinlog does not delete temporary
files left after aLOAD DATA
statement. See Section 4.6.8, “mysqlbinlog — Utility for Processing Binary Log Files”. -
RENAME
does not work with
TEMPORARY
tables or tables used in a
MERGE
table. -
When using
SET CHARACTER SET
, you cannot
use translated characters in database, table, and column
names. -
Prior to MySQL 8.0.17, you cannot use
_
or%
withESCAPE
in
LIKE ...
.
ESCAPE -
The server uses only the first
max_sort_length
bytes when
comparing data values. This means that values cannot
reliably be used inGROUP BY
,
ORDER BY
, orDISTINCT
if they differ only after the first
max_sort_length
bytes. To
work around this, increase the variable value. The default
value ofmax_sort_length
is
1024 and can be changed at server startup time or at
runtime. -
Numeric calculations are done with
BIGINT
or
DOUBLE
(both are normally 64
bits long). Which precision you get depends on the function.
The general rule is that bit functions are performed with
BIGINT
precision,
IF()
and
ELT()
with
BIGINT
or
DOUBLE
precision, and the
rest withDOUBLE
precision.
You should try to avoid using unsigned long long values if
they resolve to be larger than 63 bits (9223372036854775807)
for anything other than bit fields. -
You can have up to 255
ENUM
andSET
columns in one table. -
In
MIN()
,
MAX()
, and other aggregate
functions, MySQL currently compares
ENUM
and
SET
columns by their string
value rather than by the string’s relative position in the
set. -
In an
UPDATE
statement,
columns are updated from left to right. If you refer to an
updated column, you get the updated value instead of the
original value. For example, the following statement
incrementsKEY
by2
,
not1
:mysql>
UPDATE
tbl_name
SET KEY=KEY+1,KEY=KEY+1; -
You can refer to multiple temporary tables in the same
query, but you cannot refer to any given temporary table
more than once. For example, the following does not work:mysql>
SELECT * FROM temp_table, temp_table AS t2;
ERROR 1137: Can't reopen table: 'temp_table' -
The optimizer may handle
DISTINCT
differently when you are using “hidden” columns
in a join than when you are not. In a join, hidden columns
are counted as part of the result (even if they are not
shown), whereas in normal queries, hidden columns do not
participate in theDISTINCT
comparison.An example of this is:
SELECT DISTINCT mp3id FROM band_downloads WHERE userid = 9 ORDER BY id DESC;
and
SELECT DISTINCT band_downloads.mp3id FROM band_downloads,band_mp3 WHERE band_downloads.userid = 9 AND band_mp3.id = band_downloads.mp3id ORDER BY band_downloads.id DESC;
In the second case, you may get two identical rows in the
result set (because the values in the hidden
id
column may differ).Note that this happens only for queries that do not have the
ORDER BY
columns in the result. -
If you execute a
PROCEDURE
on a query
that returns an empty set, in some cases the
PROCEDURE
does not transform the columns. -
Creation of a table of type
MERGE
does
not check whether the underlying tables are compatible
types. -
If you use
ALTER TABLE
to add
aUNIQUE
index to a table used in a
MERGE
table and then add a normal index
on theMERGE
table, the key order is
different for the tables if there was an old,
non-UNIQUE
key in the table. This is
becauseALTER TABLE
puts
UNIQUE
indexes before normal indexes to
be able to detect duplicate keys as early as possible.
115 мин Просмотров 13.2к.
Описание 768 кодов ошибок при работа с базой данных MySQL. Диапазон допустимых кодов от 1001 до 2059. Методы устранения неполадок.
Коды ошибок MySQL разделяются на два типа:
- Ошибки на стороне сервера.
- Ошибки у клиента, клиентской программы.
Поиск ошибок желательно осуществлять по их коду, так как описания и названия могут меняться от релиза к релизу MySQL. Диапазон допустимых кодов от 1001 и до 2059.
В настоящий момент в базе хранятся только имя ошибки, описание на английском и описание на ломанном русском, в дальнейшем планируется улучшение русского перевода и добавления путей решений и устранения ошибок с различных форумов на просторах интернета. Читайте так же: Расшифровка кодов ошибок PostgreSQL.
Error MySQL: 1001
ER_NISAMCHK
isamchk
isamchk
Error MySQL: 1004
ER_CANT_CREATE_FILE
Can’t create file ‘%s’ (errno: %d)
Не удается создать файл%s ‘(ошибка : %d)
Error MySQL: 1005
ER_CANT_CREATE_TABLE
Can’t create table ‘%s’ (errno: %d)
Не удается создать таблицу «%s ‘(ошибка : %d)
Error MySQL: 1006
ER_CANT_CREATE_DB
Can’t create database ‘%s’ (errno: %d)
He удается создать базу данных ‘%s’ (errno: %d)
Error MySQL: 1007
ER_DB_CREATE_EXISTS
Can’t create database ‘%s’; database exists
He удается создать базу данных ‘%s’; база данных уже существует
Error MySQL: 1008
ER_DB_DROP_EXISTS
Can’t drop database ‘%s’; database doesn’t exist
He удается удалить базу данных; база данных не существует
Error MySQL: 1009
ER_DB_DROP_DELETE
Error dropping database (can’t delete ‘%s’, errno: %d)
Ошибка при удалении базы данных (не удается удалить ‘%s’, errno: %d)
Error MySQL: 1010
ER_DB_DROP_RMDIR
Error dropping database (can’t rmdir ‘%s’, errno: %d)
Ошибка при удалении базы данных (не удается выполнить rmdir ‘%s’)
Error MySQL: 1011
ER_CANT_DELETE_FILE
Error on delete of ‘%s’ (errno: %d)
Ошибка при удалении ‘%s’ (errno: %d)
Error MySQL: 1012
ER_CANT_FIND_SYSTEM_REC
Can’t read record in system table
He удается прочитать запись в системной таблице
Error MySQL: 1013
ER_CANT_GET_STAT
Can’t get status of ‘%s’ (errno: %d)
He удается получить состояние ‘%s’ (errno: %d)
Error MySQL: 1014
ER_CANT_GET_WD
Can’t get working directory (errno: %d)
He удается получить рабочий каталог (errno: %d)
Error MySQL: 1015
ER_CANT_LOCK
Can’t lock file (errno: %d)
He удается заблокировать файл (errno: %d)
Error MySQL: 1016
ER_CANT_OPEN_FILE
Can’t open file: ‘%s’ (errno: %d)
He удается открыть файл ‘%s’ (errno: %d)
Error MySQL: 1017
ER_FILE_NOT_FOUND
Can’t find file: ‘%s’ (errno: %d)
He удается найти файл ‘%s’ (errno: %d)
Error MySQL: 1018
ER_CANT_READ_DIR
Can’t read dir of ‘%s’ (errno: %d)
He удается прочитать каталог «%s» (errno: %d)
Error MySQL: 1019
ER_CANT_SET_WD
Can’t change dir to ‘%s’ (errno: %d)
He удается заменить каталог на «%s»
Error MySQL: 1020
ER_CHECKREAD
Record has changed since last read in table ‘%s’
Запись изменилась с момента последнего считывания таблицы «%s»
Error MySQL: 1021
ER_DISK_FULL
Disk full (%s); waiting for someone to free some space…
Диск переполнен; необходимо освободить некоторое пространство
Error MySQL: 1022
ER_DUP_KEY
Can’t write; duplicate key in table ‘%s’
He удается выполнить запись; дублированный ключ в таблице «%s»
Error MySQL: 1023
ER_ERROR_ON_CLOSE
Error on close of ‘%s’ (errno: %d)
Ошибка при закрытии «%s» (errno: %d)
Error MySQL: 1024
ER_ERROR_ON_READ
Error reading file ‘%s’ (errno: %d)
Ошибка при чтении файла «%s» (errno: %d)
Error MySQL: 1025
ER_ERROR_ON_RENAME
Error on rename of ‘%s’ to ‘%s’ (errno: %d)
Ошибка при переименовании «%s» в «%s» (errno: %d)
Error MySQL: 1026
ER_ERROR_ON_WRITE
Error writing file ‘%s’ (errno: %d)
Ошибка при записи файла «%s» (errno: %d)
Error MySQL: 1027
ER_FILE_USED
%s’ is locked against change
«%s» заблокирован от изменений
Error MySQL: 1028
ER_FILSORT_ABORT
Sort aborted
Сортировка прервана
Error MySQL: 1029
ER_FORM_NOT_FOUND
View ‘%s’ doesn’t exist for ‘%s’
Представление «%sf не существует для «%s»
Error MySQL: 1030
ER_GET_ERRNO
Got error %d from storage engine
Получена ошибка %d от механизма хранения
Error MySQL: 1031
ER_ILLEGAL_HA
Table storage engine for ‘%s’ doesn’t have this option
Механизм хранения таблиц для «%s» эту опцию не поддерживает
Error MySQL: 1032
ER_KEY_NOT_FOUND
Can’t find record in ‘%s’
He удается найти запись в «%s»
Error MySQL: 1033
ER_NOT_FORM_FILE
Incorrect information in file: ‘%s’
Некорректная информация в файле «%s»
Error MySQL: 1034
ER_NOT_KEYFILE
Incorrect key file for table ‘%s’; try to repair it
Некорректный файл ключей для таблицы «%s»
Error MySQL: 1035
ER_OLD_KEYFILE
Old key file for table ‘%s’; repair it!
Старый файл ключей для таблицы «%s»; восстановите его!
Error MySQL: 1036
ER_OPEN_AS_READONLY
Table ‘%s’ is read only
Таблица «%s» является таблицей только для чтения
Error MySQL: 1037
ER_OUTOFMEMORY
Out of memory; restart server and try again (needed %d bytes)
Недостаточно памяти; перезапустите сервер и повторите попытку (требуется %d байт)
Error MySQL: 1038
ER_OUT_OF_SORTMEMORY
Out of sort memory, consider increasing server sort buffer size
Недостаточно памяти для сортировки; увеличьте размер буфера сортировки на сервере
Error MySQL: 1039
ER_UNEXPECTED_EOF
Unexpected EOF found when reading file ‘%s’ (errno: %d)
Обнаружен неожиданный конец файла при чтении файла «%s» (errno: %d)
Error MySQL: 1040
ER_CON_COUNT_ERROR
Too many connections
Слишком много соединений
Error MySQL: 1041
ER_OUT_OF_RESOURCES
Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use ‘ulimit’ to allow mysqld to use more memory or you can add more swap space
Недостаточно памяти; проверьте, использует ли mysqld или какой-то другой процесс всю доступную память; если нет, возможно, понадобится применить «ulimit», чтобы разрешить mysqld использовать больше памяти, или же потребуется добавить дополнительное пространство для свопинга
Error MySQL: 1042
ER_BAD_HOST_ERROR
Can’t get hostname for your address
He удается получить имя хоста для указанного адреса
Error MySQL: 1043
ER_HANDSHAKE_ERROR
Bad handshake
Ошибочное подтверждение
Error MySQL: 1044
ER_DBACCESS_DENIED_ERROR
Access denied for user ‘%s’@’%s’ to database ‘%s’
Пользователю «%sf@»%s» в доступе к базе данных «%s» отказано
Error MySQL: 1045
ER_ACCESS_DENIED_ERROR
Access denied for user ‘%s’@’%s’ (using password: %s)
Пользователю «%s»@»%s» в доступе отказано (используемый пароль: %s)
Error MySQL: 1046
ER_NO_DB_ERROR
No database selected
He выбрана база данных
Error MySQL: 1047
ER_UNKNOWN_COM_ERROR
Unknown command
Неизвестная команда
Error MySQL: 1048
ER_BAD_NULL_ERROR
Column ‘%s’ cannot be null
Столбцы «%s» не могут быть NULL
Error MySQL: 1049
ER_BAD_DB_ERROR
Unknown database ‘%s’
Неизвестная база данных «%s»
Error MySQL: 1050
ER_TABLE_EXISTS_ERROR
Table ‘%s’ already exists
Таблица «%s» уже существует
Error MySQL: 1051
ER_BAD_TABLE_ERROR
Unknown table ‘%s’
Неизвестная таблица «%s»
Error MySQL: 1052
ER_NON_UNIQ_ERROR
Column ‘%s’ in %s is ambiguous
Столбец «%s» в таблице %s неоднозначен
Error MySQL: 1053
ER_SERVER_SHUTDOWN
Server shutdown in progress
Сервер находится в процессе завершения работы
Error MySQL: 1054
ER_BAD_FIELD_ERROR
Unknown column ‘%s’ in ‘%s’
Неизвестный столбец «%s» в таблице «%s!
Error MySQL: 1055
ER_WRONG_FIELD_WITH_GROUP
%s’ isn’t in GROUP BY
«%s» не указано в GROUP BY
Error MySQL: 1056
ER_WRONG_GROUP_FIELD
Can’t group on ‘%s’
He удается выполнить группировку на «%s»
Error MySQL: 1057
ER_WRONG_SUM_SELECT
Statement has sum functions and columns in same statement
Оператор содержит суммарные функции и столбцы в одном и том же выражении
Error MySQL: 1058
ER_WRONG_VALUE_COUNT
Column count doesn’t match value count
Количество столбцов не совпадает с количеством значений
Error MySQL: 1059
ER_TOO_LONG_IDENT
Identifier name ‘%s’ is too long
Имя идентификатора «%s» слишком длинное
Error MySQL: 1060
ER_DUP_FIELDNAME
Duplicate column name ‘%s’
Дублированное имя столбца «%s»
Error MySQL: 1061
ER_DUP_KEYNAME
Duplicate key name ‘%s’
Дублированное имя ключа «%s»
Error MySQL: 1062
ER_DUP_ENTRY
Duplicate entry ‘%s’ for key %d
Дублированная запись «%s» для ключа %d
Error MySQL: 1063
ER_WRONG_FIELD_SPEC
Incorrect column specifier for column ‘%s’
Некорректный спецификатор для столбца «%s»
Error MySQL: 1064
ER_PARSE_ERROR
%s near ‘%s’ at line %d
%s рядом с «%s» в строке %d
Error MySQL: 1065
ER_EMPTY_QUERY
Query was empty
Запрос был пустой
Error MySQL: 1066
ER_NONUNIQ_TABLE
Not unique table/alias: ‘%s’
Неуникальное имя/псевдоним таблицы: «%s»
Error MySQL: 1067
ER_INVALID_DEFAULT
Invalid default value for ‘%s’
Недействительное значение по умолчанию для «%s»
Error MySQL: 1068
ER_MULTIPLE_PRI_KEY
Multiple primary key defined
Определено несколько первичных ключей
Error MySQL: 1069
ER_TOO_MANY_KEYS
Too many keys specified; max %d keys allowed
Указано слишком много ключей; максимально допустимое число ключей равно %d
Error MySQL: 1070
ER_TOO_MANY_KEY_PARTS
Too many key parts specified; max %d parts allowed
Указано слишком много ключевых частей; максимально допускается %d частей
Error MySQL: 1071
ER_TOO_LONG_KEY
Specified key was too long; max key length is %d bytes
Указанный ключ был слишком длинным, максимальная длина ключа равняется %d байтам
Error MySQL: 1072
ER_KEY_COLUMN_DOES_NOT_EXITS
Key column ‘%s’ doesn’t exist in table
Столбец ключей «%s» в таблице не существует
Error MySQL: 1073
ER_BLOB_USED_AS_KEY
BLOB column ‘%s’ can’t be used in key specification with the used table type
BLOB-столбец «%s» не может быть указан в спецификации ключа с используемым типом таблицы
Error MySQL: 1074
ER_TOO_BIG_FIELDLENGTH
Column length too big for column ‘%s’ (max = %lu); use BLOB or TEXT instead
Размер для столбца «%s» слишком большой (максимально допустимый размер равен %d); вместо этого используйте BLOB
Error MySQL: 1075
ER_WRONG_AUTO_KEY
Incorrect table definition; there can be only one auto column and it must be defined as a key
Некорректное определение таблицы; возможен только один столбец auto_increment и определять его следует как ключ
Error MySQL: 1076
ER_READY
%s: ready for connections. Version: ‘%s’ socket: ‘%s’ port: %d
%s: готов для соединений. Версия: «%s», сокет: «%s», порт: %d
Error MySQL: 1077
ER_NORMAL_SHUTDOWN
%s: Normal shutdown
%s: нормальное завершение работы
Error MySQL: 1078
ER_GOT_SIGNAL
%s: Got signal %d. Aborting!
%s: получен сигнал %d — принудительное завершение работы!
Error MySQL: 1079
ER_SHUTDOWN_COMPLETE
%s: Shutdown complete
%s: работа завершена
Error MySQL: 1080
ER_FORCING_CLOSE
%s: Forcing close of thread %ld user: ‘%s’
%s: принудительное закрытие потока %ld пользователь:!%sf.
Error MySQL: 1081
ER_IPSOCK_ERROR
Can’t create IP socket
He удается создать сокет IP
Error MySQL: 1082
ER_NO_SUCH_INDEX
Table ‘%s’ has no index like the one used in CREATE INDEX; recreate the table
Таблица «%s» не содержит индекса, подобного использованному в CREATE INDEX; создайте таблицу заново
Error MySQL: 1083
ER_WRONG_FIELD_TERMINATORS
Field separator argument is not what is expected; check the manual
Аргумент разделителя полей не соответствует ожидаемому; сверьтесь с руководством
Error MySQL: 1084
ER_BLOBS_AND_NO_TERMINATED
You can’t use fixed rowlength with BLOBs; please use ‘fields terminated by’
Нельзя использовать строки фиксированной длины в таблицах BLOB; используйте «поля, оканчивающиеся на»
Error MySQL: 1085
ER_TEXTFILE_NOT_READABLE
The file ‘%s’ must be in the database directory or be readable by all
Файл «%s» должен находиться в каталоге базы данных или быть доступным для чтения всем
Error MySQL: 1086
ER_FILE_EXISTS_ERROR
File ‘%s’ already exists
Файл f%s» уже существует
Error MySQL: 1087
ER_LOAD_INFO
Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
Записи: %ld Удаленные: %ld Пропущенные: %ld Предупреждения: %ld
Error MySQL: 1088
ER_ALTER_INFO
Records: %ld Duplicates: %ld
Записи: %ld Дубликаты:%ld
Error MySQL: 1089
ER_WRONG_SUB_KEY
Incorrect prefix key; the used key part isn’t a string, the used length is longer than the key part, or the storage engine doesn’t support unique prefix keys
Некорректная часть подключа; используемая часть ключа не является строкой, примененная длина больше части ключа или механизм хранения не поддерживает уникальные подключи
Error MySQL: 1090
ER_CANT_REMOVE_ALL_FIELDS
You can’t delete all columns with ALTER TABLE; use DROP TABLE instead
С помощью ALTER TABLE удалить все столбцы нельзя; вместо ALTER TABLE используйте DROP TABLE
Error MySQL: 1091
ER_CANT_DROP_FIELD_OR_KEY
Can’t DROP ‘%s’; check that column/key exists
He удается удалить «%s» с помощью DROP; проверьте существование столбцов/ключей
Error MySQL: 1092
ER_INSERT_INFO
Records: %ld Duplicates: %ld Warnings: %ld
Записи: %ld Дубликаты: %ld Предупреждения: %ld
Error MySQL: 1093
ER_UPDATE_TABLE_USED
You can’t specify target table ‘%s’ for update in FROM clause
Нельзя указать целевую таблицу «%s» для обновления в конструкции FROM
Error MySQL: 1094
ER_NO_SUCH_THREAD
Unknown thread id: %lu
Неизвестный идентификатор потока: %lu
Error MySQL: 1095
ER_KILL_DENIED_ERROR
You are not owner of thread %lu
Вы не являетесь владельцем данного потока
Error MySQL: 1096
ER_NO_TABLES_USED
No tables used
Никакие таблицы не используются
Error MySQL: 1097
ER_TOO_BIG_SET
Too many strings for column %s and SET
Слишком много строк для столбца %s и SET
Error MySQL: 1098
ER_NO_UNIQUE_LOGFILE
Can’t generate a unique log-filename %s.(1-999)
He удается создать уникальное имя системного файла %s (1-999)
Error MySQL: 1099
ER_TABLE_NOT_LOCKED_FOR_WRITE
Table ‘%s’ was locked with a READ lock and can’t be updated
Таблица «%s» была заблокирована с помощью блокировки READ и обновить ее нельзя
Error MySQL: 1100
ER_TABLE_NOT_LOCKED
Table ‘%s’ was not locked with LOCK TABLES
Таблица «%s» не была заблокирована с помощью LOCK TABLES
Error MySQL: 1101
ER_BLOB_CANT_HAVE_DEFAULT
BLOB/TEXT column ‘%s’ can’t have a default value
Столбец BLOB/TEXT с именем «%s» не может содержать значения по умолчанию
Error MySQL: 1102
ER_WRONG_DB_NAME
Incorrect database name ‘%s’
Некорректное имя базы данных «%s»
Error MySQL: 1103
ER_WRONG_TABLE_NAME
Incorrect table name ‘%s’
Некорректное имя таблицы «%s»
Error MySQL: 1104
ER_TOO_BIG_SELECT
The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay
SELECT обработает больше, чем указано в MAX_JOIN_SIZE строк; проверьте условие WHERE и используйте SET SQL__BIG_SELECTS=1 или SET SQL_MAX_JOIN_SIZE=#, если SELECT задан корректно
Error MySQL: 1105
ER_UNKNOWN_ERROR
Unknown error
Неизвестная ошибка
Error MySQL: 1106
ER_UNKNOWN_PROCEDURE
Unknown procedure ‘%s’
Неизвестная процедура «%s»
Error MySQL: 1107
ER_WRONG_PARAMCOUNT_TO_PROCEDURE
Incorrect parameter count to procedure ‘%s’
Некорректное число параметров в процедуре «%s»
Error MySQL: 1108
ER_WRONG_PARAMETERS_TO_PROCEDURE
Incorrect parameters to procedure ‘%s’
Некорректные параметры в процедуре «%s»
Error MySQL: 1109
ER_UNKNOWN_TABLE
Unknown table ‘%s’ in %s
Неизвестная таблица «%s» в %s
Error MySQL: 1110
ER_FIELD_SPECIFIED_TWICE
Column ‘%s’ specified twice
Столбец «%s» указан дважды
Error MySQL: 1111
ER_INVALID_GROUP_FUNC_USE
Invalid use of group function
Недопустимое применение групповой функции
Error MySQL: 1112
ER_UNSUPPORTED_EXTENSION
Table ‘%s’ uses an extension that doesn’t exist in this MySQL version
Таблица «%s» использует расширение, которое не существует в этой версии MySQL
Error MySQL: 1113
ER_TABLE_MUST_HAVE_COLUMNS
A table must have at least 1 column
Таблица должна содержать, по крайней мере, один столбец
Error MySQL: 1114
ER_RECORD_FILE_FULL
The table ‘%s’ is full
Таблица «%s» заполнена
Error MySQL: 1115
ER_UNKNOWN_CHARACTER_SET
Unknown character set: ‘%s’
Неизвестный набор символов «%s»
Error MySQL: 1116
ER_TOO_MANY_TABLES
Too many tables; MySQL can only use %d tables in a join
Слишком много таблиц; MySQL может использовать не больше %d таблиц за одно соединение
Error MySQL: 1117
ER_TOO_MANY_FIELDS
Too many columns
Слишком много столбцов
Error MySQL: 1118
ER_TOO_BIG_ROWSIZE
Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. You have to change some columns to TEXT or BLOBs
Размер строк слишком большой. Максимальный размер строк для используемого типа таблиц, без учета BLOB, равен %ld. Некоторые столбцы необходимо заменить на TEXT или BLOB
Error MySQL: 1119
ER_STACK_OVERRUN
Thread stack overrun: Used: %ld of a %ld stack. Use ‘mysqld —thread_stack=#’ to specify a bigger stack if needed
Переполнение стека потока: Использовано %ld из %ld процентов стека. Используйте mysqld-0 thread_stack=#», чтобы при необходимости указать больший размер стека
Error MySQL: 1120
ER_WRONG_OUTER_JOIN
Cross dependency found in OUTER JOIN; examine your ON conditions
В OUTER JOIN обнаружена перекрестная зависимость; проверьте условия ON
Error MySQL: 1121
ER_NULL_COLUMN_IN_INDEX
Table handler doesn’t support NULL in given index. Please change column ‘%s’ to be NOT NULL or use another handler
Столбец «%s» используется с UNIQUE или INDEX и не определен как NOT NULL
Error MySQL: 1122
ER_CANT_FIND_UDF
Can’t load function ‘%s’
He удается загрузить функцию «%s»
Error MySQL: 1123
ER_CANT_INITIALIZE_UDF
Can’t initialize function ‘%s’; %s
He удается запустить функцию «%s»; %s
Error MySQL: 1124
ER_UDF_NO_PATHS
No paths allowed for shared library
He разрешены никакие пути к совместно используемой библиотеке
Error MySQL: 1125
ER_UDF_EXISTS
Function ‘%s’ already exists
Функция «%s» уже существует
Error MySQL: 1126
ER_CANT_OPEN_LIBRARY
Can’t open shared library ‘%s’ (errno: %d %s)
He удается открыть совместно используемую библиотеку «%sf (errno: %d %s)
Error MySQL: 1127
ER_CANT_FIND_DL_ENTRY
Can’t find symbol ‘%s’ in library
He удается найти функцию «%s» в библиотеке
Error MySQL: 1128
ER_FUNCTION_NOT_DEFINED
Function ‘%s’ is not defined
Функция «%s» не определена
Error MySQL: 1129
ER_HOST_IS_BLOCKED
Host ‘%s’ is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’
Хост «%s» заблокирован по причине многочисленных ошибок соединения; разблокируйте с помощью «mysqladmin flush-hosts»
Error MySQL: 1130
ER_HOST_NOT_PRIVILEGED
Host ‘%s’ is not allowed to connect to this MySQL server
Хосту «%s» запрещено подключение к данному серверу MySQL
Error MySQL: 1131
ER_PASSWORD_ANONYMOUS_USER
You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords
Вы подключились к MySQL как анонимный пользователь, а анонимным пользователям запрещено изменять пароли
Error MySQL: 1132
ER_PASSWORD_NOT_ALLOWED
You must have privileges to update tables in the mysql database to be able to change passwords for others
Недостаточно привилегий для обновления таблиц в базе данных mysql и изменения паролей других пользователей
Error MySQL: 1133
ER_PASSWORD_NO_MATCH
Can’t find any matching row in the user table
He удается найти совпадающую строку в таблице user
Error MySQL: 1134
ER_UPDATE_INFO
Rows matched: %ld Changed: %ld Warnings: %ld
Совпавшие строки: %ld Измененные: %ld Предупреждения: %ld
Error MySQL: 1135
ER_CANT_CREATE_THREAD
Can’t create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
He удается создать новый поток (errno %d); если причина не в недостаточном количестве доступной памяти, сверьтесь с руководством: не исключена ошибка, связанная с ОС
Error MySQL: 1136
ER_WRONG_VALUE_COUNT_ON_ROW
Column count doesn’t match value count at row %ld
Количество столбцов не соответствует количеству значений в строке %ld
Error MySQL: 1137
ER_CANT_REOPEN_TABLE
Can’t reopen table: ‘%s’
He удается повторно открыть таблицу:»%s»
Error MySQL: 1138
ER_INVALID_USE_OF_NULL
Invalid use of NULL value
Недопустимое использование NULL
Error MySQL: 1139
ER_REGEXP_ERROR
Got error ‘%s’ from regexp
Получена ошибка с regexp
Error MySQL: 1140
ER_MIX_OF_GROUP_FUNC_AND_FIELDS
Mixing of GROUP columns (MIN(),MAX(),COUNT(),…) with no GROUP columns is illegal if there is no GROUP BY clause
Смешивание столбцов GROUP (MIN(),MAX(),COUNT О,…) со столбцами не-GROUP недопустимо при отсутствии конструкции GROUP BY
Error MySQL: 1141
ER_NONEXISTING_GRANT
There is no such grant defined for user ‘%s’ on host ‘%s’
Такая привилегия не была определена для пользователя «%s» на хосте «%sf
Error MySQL: 1142
ER_TABLEACCESS_DENIED_ERROR
%s command denied to user ‘%s’@’%s’ for table ‘%s’
В использовании команды %s для таблицы «%s» пользователю •%s•@»%s» отказано
Error MySQL: 1143
ER_COLUMNACCESS_DENIED_ERROR
%s command denied to user ‘%s’@’%s’ for column ‘%s’ in table ‘%s’
Пользователю «Is»G»ls» отказано в KOMaHflt %s для столбца «%s» в таблице «%sf
Error MySQL: 1144
ER_ILLEGAL_GRANT_FOR_TABLE
Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used
Недопустимая команда GRANT/REVOKE; проконсультируйтесь с руководством на предмет используемых привилегий
Error MySQL: 1145
ER_GRANT_WRONG_HOST_OR_USER
The host or user argument to GRANT is too long
Аргумент хоста или пользователя для GRANT слишком длинный
Error MySQL: 1146
ER_NO_SUCH_TABLE
Table ‘%s.%s’ doesn’t exist
Таблица «%s %s» не существует
Error MySQL: 1147
ER_NONEXISTING_TABLE_GRANT
There is no such grant defined for user ‘%s’ on host ‘%s’ on table ‘%s’
Такая привилегия не была определена для пользователя «%s» на хосте «%s» для таблицы «%s»
Error MySQL: 1148
ER_NOT_ALLOWED_COMMAND
The used command is not allowed with this MySQL version
Используемая команда не разрешена в этой версии MySQL
Error MySQL: 1149
ER_SYNTAX_ERROR
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use
Ошибка в синтаксисе SQL; проверьте в руководстве по используемой вами версии MySQL-сервера, какой синтаксис будет корректным
Error MySQL: 1150
ER_DELAYED_CANT_CHANGE_LOCK
Delayed insert thread couldn’t get requested lock for table %s
Потоку задержанных вставок не удалось получить запрашиваемую блокировку для таблицы %s
Error MySQL: 1151
ER_TOO_MANY_DELAYED_THREADS
Too many delayed threads in use
Используется слишком много задержанных потоков
Error MySQL: 1152
ER_ABORTING_CONNECTION
Aborted connection %ld to db: ‘%s’ user: ‘%s’ (%s)
Прервано подключение %ld к базе данных: «%s» пользователь: «%s»
Error MySQL: 1153
ER_NET_PACKET_TOO_LARGE
Got a packet bigger than ‘max_allowed_packet’ bytes
Полученный пакет больше «max_allowedjpacket» байт
Error MySQL: 1154
ER_NET_READ_ERROR_FROM_PIPE
Got a read error from the connection pipe
Получена ошибка при чтении с канала соединения
Error MySQL: 1155
ER_NET_FCNTL_ERROR
Got an error from fcntl()
Получена ошибка от fcntl()
Error MySQL: 1156
ER_NET_PACKETS_OUT_OF_ORDER
Got packets out of order
Получены поврежденные пакеты
Error MySQL: 1157
ER_NET_UNCOMPRESS_ERROR
Couldn’t uncompress communication packet
He удается извлечь коммуникационный пакет
Error MySQL: 1158
ER_NET_READ_ERROR
Got an error reading communication packets
Получена ошибка при чтении коммуникационных пакетов
Error MySQL: 1159
ER_NET_READ_INTERRUPTED
Got timeout reading communication packets
Получен тайм-аут при чтении коммуникационных пакетов
Error MySQL: 1160
ER_NET_ERROR_ON_WRITE
Got an error writing communication packets
Получена ошибка при записи коммуникационных пакетов
Error MySQL: 1161
ER_NET_WRITE_INTERRUPTED
Got timeout writing communication packets
Получен тайм-аут при записи коммуникационных пакетов
Error MySQL: 1162
ER_TOO_LONG_STRING
Result string is longer than ‘max_allowed_packet’ bytes
Строка результата длиннее «max_allowed_packet» байт
Error MySQL: 1163
ER_TABLE_CANT_HANDLE_BLOB
The used table type doesn’t support BLOB/TEXT columns
Используемый тип таблицы не поддерживает столбцы BLOB/TEXT
Error MySQL: 1164
ER_TABLE_CANT_HANDLE_AUTO_INCREMENT
The used table type doesn’t support AUTO_INCREMENT columns
Используемый тип таблицы не поддерживает столбцы AUTO_INCREMENT
Error MySQL: 1165
ER_DELAYED_INSERT_TABLE_LOCKED
INSERT DELAYED can’t be used with table ‘%s’ because it is locked with LOCK TABLES
Команда INSERT DELAYED не может быть использована с таблицей «%s», поскольку она заблокирована через LOCK TABLES
Error MySQL: 1166
ER_WRONG_COLUMN_NAME
Incorrect column name ‘%s’
Некорректное имя столбца «%s»
Error MySQL: 1167
ER_WRONG_KEY_COLUMN
The used storage engine can’t index column ‘%s’
Используемый механизм хранения не может проиндексировать столбец «%s»
Error MySQL: 1168
ER_WRONG_MRG_TABLE
Unable to open underlying table which is differently defined or of non-MyISAM type or doesn’t exist
Все таблицы в таблице MERGE не являются одинаково определенными
Error MySQL: 1169
ER_DUP_UNIQUE
Can’t write, because of unique constraint, to table ‘%s’
He удается выполнить запись в таблицу «%s» по причине ограничения уникальности
Error MySQL: 1170
ER_BLOB_KEY_WITHOUT_LENGTH
BLOB/TEXT column ‘%s’ used in key specification without a key length
BLOB/TEXT-столбец «%s» использовался в спецификации ключа без указания длины ключа
Error MySQL: 1171
ER_PRIMARY_CANT_HAVE_NULL
All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead
Все части PRIMARY KEY должны быть NOT NULL; при необходимости в наличии значения NULL в ключе используйте UNIQUE
Error MySQL: 1172
ER_TOO_MANY_ROWS
Result consisted of more than one row
Результат состоял из более чем одной строки
Error MySQL: 1173
ER_REQUIRES_PRIMARY_KEY
This table type requires a primary key
Для данной таблицы требуется первичный ключ
Error MySQL: 1174
ER_NO_RAID_COMPILED
This version of MySQL is not compiled with RAID support
Данная версия MySQL не компилировалась с поддержкой RAID
Error MySQL: 1175
ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE
You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
Вы используете безопасный режим обновления и попытались обновить таблицу без условия WHERE, использующего столбец KEY
Error MySQL: 1176
ER_KEY_DOES_NOT_EXITS
Key ‘%s’ doesn’t exist in table ‘%s’
Ключ f%sf не существует в таблице !%s»
Error MySQL: 1177
ER_CHECK_NO_SUCH_TABLE
Can’t open table
He удается открыть таблицу
Error MySQL: 1178
ER_CHECK_NOT_IMPLEMENTED
The storage engine for the table doesn’t support %s
Механизм хранения для таблицы не поддерживает %s
Error MySQL: 1179
ER_CANT_DO_THIS_DURING_AN_TRANSACTION
You are not allowed to execute this command in a transaction
Вам запрещено выполнение данной команды в транзакции
Error MySQL: 1180
ER_ERROR_DURING_COMMIT
Got error %d during COMMIT
Получена ошибка %d во время выполнения COMMIT
Error MySQL: 1181
ER_ERROR_DURING_ROLLBACK
Got error %d during ROLLBACK
Получена ошибка %d во время выполнения ROLLBACK
Error MySQL: 1182
ER_ERROR_DURING_FLUSH_LOGS
Got error %d during FLUSH_LOGS
Получена ошибка %d во время выполнения FLUSH_LOGS
Error MySQL: 1183
ER_ERROR_DURING_CHECKPOINT
Got error %d during CHECKPOINT
Получена ошибка %d во время выполнения CHECKPOINT
Error MySQL: 1184
ER_NEW_ABORTING_CONNECTION
Aborted connection %ld to db: ‘%s’ user: ‘%s’ host: ‘%s’ (%s)
Прервано подключение %ld к базе данных «%s» пользователь: «%s» хост 4%s» (%s)
Error MySQL: 1185
ER_DUMP_NOT_IMPLEMENTED
The storage engine for the table does not support binary table dump
Механизм хранения таблицы не поддерживает бинарный дамп таблиц
Error MySQL: 1186
ER_FLUSH_MASTER_BINLOG_CLOSED
Binlog closed, cannot RESET MASTER
Бинарный журнал закрыт, не удается выполнить RESET MASTER
Error MySQL: 1187
ER_INDEX_REBUILD
Failed rebuilding the index of dumped table ‘%s’
Неудачная попытка восстановления индекса из дампа таблицы «%s»
Error MySQL: 1188
ER_MASTER
Error from master: ‘%s’
Ошибка главного сервера:»%s»
Error MySQL: 1189
ER_MASTER_NET_READ
Net error reading from master
Сетевая ошибка при чтении с главного сервера
Error MySQL: 1190
ER_MASTER_NET_WRITE
Net error writing to master
Сетевая ошибка при выполнении записи на главный сервер
Error MySQL: 1191
ER_FT_MATCHING_KEY_NOT_FOUND
Can’t find FULLTEXT index matching the column list
He удается найти индекс FULLTEXT, соответствующий списку столбца
Error MySQL: 1192
ER_LOCK_OR_ACTIVE_TRANSACTION
Can’t execute the given command because you have active locked tables or an active transaction
He удается выполнить данную команду по причине наличия активных заблокированных таблиц или активной транзакции
Error MySQL: 1193
ER_UNKNOWN_SYSTEM_VARIABLE
Unknown system variable ‘%s’
Неизвестная системная переменная «%s»
Error MySQL: 1194
ER_CRASHED_ON_USAGE
Table ‘%s’ is marked as crashed and should be repaired
Таблица «%s» помечена как поврежденная и должна быть исправлена
Error MySQL: 1195
ER_CRASHED_ON_REPAIR
Table ‘%s’ is marked as crashed and last (automatic?) repair failed
failed/Таблица «%s» помечена как поврежденная и последняя попытка(автоматического?) исправления была неудачной
Error MySQL: 1196
ER_WARNING_NOT_COMPLETE_ROLLBACK
Some non-transactional changed tables couldn’t be rolled back
Некоторые нетранзакционные измененные таблицы возврату в первоначальное состояние не подлежат
Error MySQL: 1197
ER_TRANS_CACHE_FULL
Multi-statement transaction required more than ‘max_binlog_cache_size’ bytes of storage; increase this mysqld variable and try again
Для транзакции с множественными операторами потребовалось больше, чем указано в «max_binlog_cache_size» байтов в кэше; увеличьте значение данной переменной и повторите попытку
Error MySQL: 1198
ER_SLAVE_MUST_STOP
This operation cannot be performed with a running slave; run STOP SLAVE first
Данная операция не может быть выполнена при работающем ведомом сервере, сначала выполните STOP SLAVE
Error MySQL: 1199
ER_SLAVE_NOT_RUNNING
This operation requires a running slave; configure slave and do START SLAVE
Для данной операции требуется запустить подчиненный сервер; сконфигурируйте подчиненный сервер и выполните START SLAVE
Error MySQL: 1200
ER_BAD_SLAVE
The server is not configured as slave; fix in config file or with CHANGE MASTER TO
Сервер не сконфигурирован как подчиненный; устраните ошибку в файле конфигурации или воспользуйтесь CHANGE MASTER TO
Error MySQL: 1201
ER_MASTER_INFO
Could not initialize master info structure; more error messages can be found in the MySQL error log
He удалось инициализировать информационную структуру на главном сервере; дополнительные сообщения об ошибках можно найти в журнале ошибок MySQL
Error MySQL: 1202
ER_SLAVE_THREAD
Could not create slave thread; check system resources
He удалось создать поток для подчиненного сервера; проверьте ресурсы системы
Error MySQL: 1203
ER_TOO_MANY_USER_CONNECTIONS
User %s already has more than ‘max_user_connections’ active connections
Количество активных соединений пользователя %s уже превышает «max_user_connections»
Error MySQL: 1204
ER_SET_CONSTANTS_ONLY
You may only use constant expressions with SET
С SET можно использовать только константные выражения
Error MySQL: 1205
ER_LOCK_WAIT_TIMEOUT
Lock wait timeout exceeded; try restarting transaction
Превышено время ожидания блокировки; попробуйте перезапустить транзакцию
Error MySQL: 1206
ER_LOCK_TABLE_FULL
The total number of locks exceeds the lock table size
Общее количество блокировок превышает размер таблицы блокировки
Error MySQL: 1207
ER_READ_ONLY_TRANSACTION
Update locks cannot be acquired during a READ UNCOMMITTED transaction
Получение блокировки обновления невозможно во время выполнения транзакции READ UNCOMMITTED
Error MySQL: 1208
ER_DROP_DB_WITH_READ_LOCK
DROP DATABASE not allowed while thread is holding global read lock
Выполнение DROP DATABASE невозможно, пока в потоке используется глобальная блокировка чтения
Error MySQL: 1209
ER_CREATE_DB_WITH_READ_LOCK
CREATE DATABASE not allowed while thread is holding global read lock
Выполнение CREATE DATABASE невозможно, пока в потоке используется глобальная блокировка чтения
Error MySQL: 1210
ER_WRONG_ARGUMENTS
Incorrect arguments to %s
Некорректные аргументы для %s
Error MySQL: 1211
ER_NO_PERMISSION_TO_CREATE_USER
%s’@’%s’ is not allowed to create new users
Пользователю «%s!@»%s» запрещено создавать новых пользователей
Error MySQL: 1212
ER_UNION_TABLES_IN_DIFFERENT_DIR
Incorrect table definition; all MERGE tables must be in the same database
Таблица определена некорректно; все таблицы MERGE должны находиться в одной и той же базе данных
Error MySQL: 1213
ER_LOCK_DEADLOCK
Deadlock found when trying to get lock; try restarting transaction
Обнаружена ошибка взаимной блокировки при попытке получить блокировку; попробуйте перезапустить транзакцию
Error MySQL: 1214
ER_TABLE_CANT_HANDLE_FT
The used table type doesn’t support FULLTEXT indexes
Используемый тип таблицы не поддерживает индексы FULLTEXT
Error MySQL: 1215
ER_CANNOT_ADD_FOREIGN
Cannot add foreign key constraint
He удается добавить ограничение внешнего ключа
Error MySQL: 1216
ER_NO_REFERENCED_ROW
Cannot add or update a child row: a foreign key constraint fails
He удается добавить или обновить дочернюю строку: ограничение внешнего ключа дает сбой
Error MySQL: 1217
ER_ROW_IS_REFERENCED
Cannot delete or update a parent row: a foreign key constraint fails
He удается удалить или обновить родительскую строку: ограничение внешнего ключа дает сбой
Error MySQL: 1218
ER_CONNECT_TO_MASTER
Error connecting to master: %s
Ошибка при подключении к главному серверу: %s
Error MySQL: 1219
ER_QUERY_ON_MASTER
Error running query on master: %s
Ошибка при выполнении запроса на главном сервере: %s
Error MySQL: 1220
ER_ERROR_WHEN_EXECUTING_COMMAND
Error when executing command %s: %s
Ошибка при выполнении команды %s: %s
Error MySQL: 1221
ER_WRONG_USAGE
Incorrect usage of %s and %s
Некорректное использование %s и %s
Error MySQL: 1222
ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT
The used SELECT statements have a different number of columns
Используемые операторы SELECT имеют разное количество столбцов
Error MySQL: 1223
ER_CANT_UPDATE_WITH_READLOCK
Can’t execute the query because you have a conflicting read lock
He удается выполнить запрос из-за конфликта блокировок чтения
Error MySQL: 1224
ER_MIXING_NOT_ALLOWED
Mixing of transactional and non-transactional tables is disabled
Опция смешивания транзакционных и нетранзакционных таблиц отключена
Error MySQL: 1225
ER_DUP_ARGUMENT
Option ‘%s’ used twice in statement
Опция «%s» используется в операторе дважды
Error MySQL: 1226
ER_USER_LIMIT_REACHED
User ‘%s’ has exceeded the ‘%s’ resource (current value: %ld)
Пользователь «%s» превысил лимит по использованию ресурса «%s»
Error MySQL: 1227
ER_SPECIFIC_ACCESS_DENIED_ERROR
Access denied; you need (at least one of) the %s privilege(s) for this operation
В доступе отказано; для выполнения данной операции требуется привилегия %s
Error MySQL: 1228
ER_LOCAL_VARIABLE
Variable ‘%s’ is a SESSION variable and can’t be used with SET GLOBAL
Переменная «%s» является сеансовой переменной и не может использоваться в SET GLOBAL
Error MySQL: 1229
ER_GLOBAL_VARIABLE
Variable ‘%s’ is a GLOBAL variable and should be set with SET GLOBAL
Переменная «%s» является глобальной переменной и должна устанавливаться с помощью SET GLOBAL
Error MySQL: 1230
ER_NO_DEFAULT
Variable ‘%s’ doesn’t have a default value
Переменная «%s» не имеет значения по умолчанию
Error MySQL: 1231
ER_WRONG_VALUE_FOR_VAR
Variable ‘%s’ can’t be set to the value of ‘%s’
Переменной «%s» не может быть присвоено значение «%s»
Error MySQL: 1232
ER_WRONG_TYPE_FOR_VAR
Incorrect argument type to variable ‘%s’
Некорректный тип аргумента в переменной «%s»
Error MySQL: 1233
ER_VAR_CANT_BE_READ
Variable ‘%s’ can only be set, not read
Переменную «%s» можно только устанавливать, но не считывать
Error MySQL: 1234
ER_CANT_USE_OPTION_HERE
Incorrect usage/placement of ‘%s’
Некорректное использование/размещение «%s»
Error MySQL: 1235
ER_NOT_SUPPORTED_YET
This version of MySQL doesn’t yet support ‘%s’
Данная версия MySQL еще не поддерживает «%s»
Error MySQL: 1236
ER_MASTER_FATAL_ERROR_READING_BINLOG
Got fatal error %d from master when reading data from binary log: ‘%s’
Получена неисправимая ошибка %d: «%s» с ведущего сервера при чтении данных из бинарного журнала
Error MySQL: 1237
ER_SLAVE_IGNORED_TABLE
Slave SQL thread ignored the query because of replicate-*-table rules
Запрос был проигнорирован потоком SQL подчиненного сервера из-за правил replicate-*-table
Error MySQL: 1238
ER_INCORRECT_GLOBAL_LOCAL_VAR
Variable ‘%s’ is a %s variable
Переменная «%sf является переменной %s
Error MySQL: 1239
ER_WRONG_FK_DEF
Incorrect foreign key definition for ‘%s’: %s
Некорректное определение внешнего ключа для «%s»: %s
Error MySQL: 1240
ER_KEY_REF_DO_NOT_MATCH_TABLE_REF
Key reference and table reference don’t match
Ссылка на ключ и ссылка на таблицу не совпадают
Error MySQL: 1241
ER_OPERAND_COLUMNS
Operand should contain %d column(s)
Операнд должен содержать %d столбцов
Error MySQL: 1242
ER_SUBQUERY_NO_1_ROW
Subquery returns more than 1 row
Подзапрос возвращает более чем 1 строку
Error MySQL: 1243
ER_UNKNOWN_STMT_HANDLER
Unknown prepared statement handler (%.*s) given to %s
Для %s указан неизвестный обработчик операторов (%*s)
Error MySQL: 1244
ER_CORRUPT_HELP_DB
Help database is corrupt or does not exist
База данных справочника повреждена или не существует
Error MySQL: 1245
ER_CYCLIC_REFERENCE
Cyclic reference on subqueries
Циклическая ссылка в подзапросах
Error MySQL: 1246
ER_AUTO_CONVERT
Converting column ‘%s’ from %s to %s
Преобразование столбца «%s» из %s в %s
Error MySQL: 1247
ER_ILLEGAL_REFERENCE
Reference ‘%s’ not supported (%s)
Ссылка «%s» не поддерживается (%s)
Error MySQL: 1248
ER_DERIVED_MUST_HAVE_ALIAS
Every derived table must have its own alias
У каждой производной таблицы должен быть свой собственный псевдоним
Error MySQL: 1249
ER_SELECT_REDUCED
Select %u was reduced during optimization
Во время оптимизации %u было сокращено
Error MySQL: 1250
ER_TABLENAME_NOT_ALLOWED_HERE
Table ‘%s’ from one of the SELECTs cannot be used in %s
Таблица «%s», указанная в одном из операторов SELECT не может быть использована в %s
Error MySQL: 1251
ER_NOT_SUPPORTED_AUTH_MODE
Client does not support authentication protocol requested by server; consider upgrading MySQL client
Клиент не поддерживает протокол аутентификации, запрашиваемый сервером; требуется обновление версии клиента MySQL
Error MySQL: 1252
ER_SPATIAL_CANT_HAVE_NULL
All parts of a SPATIAL index must be NOT NULL
Все части индекса SPATIAL должны быть NOT NULL
Error MySQL: 1253
ER_COLLATION_CHARSET_MISMATCH
COLLATION ‘%s’ is not valid for CHARACTER SET ‘%s’
Операция COLLATION «%s» недопустима для CHARACTER SET «%s»
Error MySQL: 1254
ER_SLAVE_WAS_RUNNING
Slave is already running
Подчиненный сервер уже выполняется
Error MySQL: 1255
ER_SLAVE_WAS_NOT_RUNNING
Slave already has been stopped
Подчиненный сервер уже остановлен
Error MySQL: 1256
ER_TOO_BIG_FOR_UNCOMPRESS
Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)
Размер несжатых данных слишком велик; максимально допустимый размер равен %d (не исключено повреждение размера несжатых данных)
Error MySQL: 1257
ER_ZLIB_Z_MEM_ERROR
ZLIB: Not enough memory
ZLIB: Недостаточно памяти
Error MySQL: 1258
ER_ZLIB_Z_BUF_ERROR
ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)
ZLIB: Недостаточно места в выходном буфере (не исключено повреждение размера несжатых данный)
Error MySQL: 1259
ER_ZLIB_Z_DATA_ERROR
ZLIB: Input data corrupted
ZLIB: Повреждение входных данных
Error MySQL: 1260
ER_CUT_VALUE_GROUP_CONCAT
Row %u was cut by GROUP_CONCAT()
%d строк усечено GROUP_CONCAT()
Error MySQL: 1261
ER_WARN_TOO_FEW_RECORDS
Row %ld doesn’t contain data for all columns
Строка %ld не содержит данных для всех столбцов
Error MySQL: 1262
ER_WARN_TOO_MANY_RECORDS
Row %ld was truncated; it contained more data than there were input columns
Строка %ld была усечена; она содержала данных больше, чем было входных столбцов
Error MySQL: 1263
ER_WARN_NULL_TO_NOTNULL
Column set to default value; NULL supplied to NOT NULL column ‘%s’ at row %ld
Данные усечены; значение NULL занесено в столбец NOT NULL в строке %ld
Error MySQL: 1264
ER_WARN_DATA_OUT_OF_RANGE
Out of range value for column ‘%s’ at row %ld
Данные усечены; недостаточный диапазон для столбца «%s» в строке %ld
Error MySQL: 1265
WARN_DATA_TRUNCATED
Data truncated for column ‘%s’ at row %ld
Данные усечены для столбца «%s» в строке %ld
Error MySQL: 1266
ER_WARN_USING_OTHER_HANDLER
Using storage engine %s for table ‘%s’
Использование механизма хранения %s для таблицы «%s»
Error MySQL: 1267
ER_CANT_AGGREGATE_2COLLATIONS
Illegal mix of collations (%s,%s) and (%s,%s) for operation ‘%s’
Недопустимое сочетание сопоставлений (%s,%s) и (%s,%s) для операции » %s»
Error MySQL: 1268
ER_DROP_USER
Cannot drop one or more of the requested users
He удается удалить одного или более из запрашиваемых пользователей
Error MySQL: 1269
ER_REVOKE_GRANTS
Can’t revoke all privileges for one or more of the requested users
He удается отменить все привилегии, предоставленные одному или более из запрашиваемых пользователей
Error MySQL: 1270
ER_CANT_AGGREGATE_3COLLATIONS
Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation ‘%s’
Недопустимое сочетание сопоставлений (%s,%s), (%s,%s), (%s,%s) для операции «%s»
Error MySQL: 1271
ER_CANT_AGGREGATE_NCOLLATIONS
Illegal mix of collations for operation ‘%s’
Недопустимое сочетание сопоставлений для операции «%s»
Error MySQL: 1272
ER_VARIABLE_IS_NOT_STRUCT
Variable ‘%s’ is not a variable component (can’t be used as XXXX.variable_name)
Переменная «%s» не является переменной составляющей (не может ис пользоваться как XXXX.variable_name)
Error MySQL: 1273
ER_UNKNOWN_COLLATION
Unknown collation: ‘%s’
Неизвестное сопоставление: «%s»
Error MySQL: 1274
ER_SLAVE_IGNORED_SSL_PARAMS
SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started
SSL-параметры в CHANGE MASTER игнорируются, потому что данный подчиненный сервер скомпилирован без поддержки SSL; их можно будет использовать потом, если подчиненный сервер MySQL будет запущен с опцией SSL
Error MySQL: 1275
ER_SERVER_IS_IN_SECURE_AUTH_MODE
Server is running in —secure-auth mode, but ‘%s’@’%s’ has a password in the old format; please change the password to the new format
Сервер работает в режиме —secure-auth, но использует пароль старого формата; измените формат пароля на новый.
Error MySQL: 1276
ER_WARN_FIELD_RESOLVED
Field or reference ‘%s%s%s%s%s’ of SELECT #%d was resolved in SELECT #%d
Поле или ссылка «%s%s%s%s%s» в SELECT #%d была разрешена в SELECT #%d
Error MySQL: 1277
ER_BAD_SLAVE_UNTIL_COND
Incorrect parameter or combination of parameters for START SLAVE UNTIL
Некорректный параметр или комбинация параметров для START SLAVE UNTIL
Error MySQL: 1278
ER_MISSING_SKIP_SLAVE
It is recommended to use —skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave’s mysqld restart
Рекомендуется использовать —skip-slave-start при выполнении пошаговой репликации с помощью START SLAVE UNTIL; иначе возникнут проблемы в случае неожиданного перезапуска mysqld на подчиненном сервере
Error MySQL: 1279
ER_UNTIL_COND_IGNORED
SQL thread is not to be started so UNTIL options are ignored
Поток SQL пока запускаться не будет, поэтому опции UNTIL игнорируются
Error MySQL: 1280
ER_WRONG_NAME_FOR_INDEX
Incorrect index name ‘%s’
Некорректное имя индекса «%s»
Error MySQL: 1281
ER_WRONG_NAME_FOR_CATALOG
Incorrect catalog name ‘%s’
Некорректное имя каталога «%s» 398 Глава 9. Обработка ошибок в MySQL
Error MySQL: 1282
ER_WARN_QC_RESIZE
Query cache failed to set size %lu; new query cache size is %lu
Попытка установить размер %lu для кэша запросов была неудачной; новый размер кэша запросов равен %lu
Error MySQL: 1283
ER_BAD_FT_COLUMN
Column ‘%s’ cannot be part of FULLTEXT index
Столбец «%s» не может быть частью индекса FULLTEXT
Error MySQL: 1284
ER_UNKNOWN_KEY_CACHE
Unknown key cache ‘%s’
Неизвестный кэш ключей «%s»
Error MySQL: 1285
ER_WARN_HOSTNAME_WONT_WORK
MySQL is started in —skip-name-resolve mode; you must restart it without this switch for this grant to work
MySQL запущен в режиме —skip-name-resolve; необходимо перезапустить его без этой опции, чтобы данная привилегия работала
Error MySQL: 1286
ER_UNKNOWN_STORAGE_ENGINE
Unknown storage engine ‘%s’
Неизвестный тип таблиц «%s»
Error MySQL: 1287
ER_WARN_DEPRECATED_SYNTAX
%s’ is deprecated and will be removed in a future release. Please use %s instead
«%s» устарела; вместо нее используйте «%s»
Error MySQL: 1288
ER_NON_UPDATABLE_TABLE
The target table %s of the %s is not updatable
Целевая таблица %s из %s не обновляется
Error MySQL: 1289
ER_FEATURE_DISABLED
The ‘%s’ feature is disabled; you need MySQL built with ‘%s’ to have it working
Функция «%s» отключена; чтобы она работала, потребуется выполнить сборку MySQL с «%sf
Error MySQL: 1290
ER_OPTION_PREVENTS_STATEMENT
The MySQL server is running with the %s option so it cannot execute this statement
Сервер MySQL запущен с опцией %s, поэтому не может выполнить данный оператор
Error MySQL: 1291
ER_DUPLICATED_VALUE_IN_TYPE
Column ‘%s’ has duplicated value ‘%s’ in %s
Столбец f%sf содержит дублированное значение «%s» в %s
Error MySQL: 1292
ER_TRUNCATED_WRONG_VALUE
Truncated incorrect %s value: ‘%s’
Усеченное некорректное значение %s: «%sf
Error MySQL: 1293
ER_TOO_MUCH_AUTO_TIMESTAMP_COLS
Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause
Таблица определена некорректно; только один столбец может быть указан с CURRENTJTIMESTAMP в конструкции DEFAULT или ON UPDATE
Error MySQL: 1294
ER_INVALID_ON_UPDATE
Invalid ON UPDATE clause for ‘%s’ column
Недопустимая конструкция ON UPDATE для столбца «%sf
Error MySQL: 1295
ER_UNSUPPORTED_PS
This command is not supported in the prepared statement protocol yet
Данная команда еще не поддерживается в протоколе подготовленных операторов
Error MySQL: 1296
ER_GET_ERRMSG
Got error %d ‘%s’ from %s
He удается создать %s через другую хранимую процедуру
Error MySQL: 1297
ER_GET_TEMPORARY_ERRMSG
Got temporary error %d ‘%s’ from %s
%s %s уже существует
Error MySQL: 1298
ER_UNKNOWN_TIME_ZONE
Unknown or incorrect time zone: ‘%s’
%s %s не существует
Error MySQL: 1299
ER_WARN_INVALID_TIMESTAMP
Invalid TIMESTAMP value in column ‘%s’ at row %ld
He удалось удалить %s %s с помощью DROP
Error MySQL: 1300
ER_INVALID_CHARACTER_STRING
Invalid %s character string: ‘%s’
He удалось создать %s %s с помощью CREATE
Error MySQL: 1301
ER_WARN_ALLOWED_PACKET_OVERFLOWED
Result of %s() was larger than max_allowed_packet (%ld) — truncated
%s без подходящей метки: %s
Error MySQL: 1302
ER_CONFLICTING_DECLARATIONS
Conflicting declarations: ‘%s%s’ and ‘%s%s’
Повторное определение метки %s
Error MySQL: 1303
ER_SP_NO_RECURSIVE_CREATE
Can’t create a %s from within another stored routine
%s с конечной меткой без совпадений
Error MySQL: 1304
ER_SP_ALREADY_EXISTS
%s %s already exists
Обращение к неинициализированной переменной %s
Error MySQL: 1305
ER_SP_DOES_NOT_EXIST
%s %s does not exist
Оператор SELECT в хранимой процедуре должен содержать INTO
Error MySQL: 1306
ER_SP_DROP_FAILED
Failed to DROP %s %s
RETURN разрешено использовать только в FUNCTION
Error MySQL: 1307
ER_SP_STORE_FAILED
Failed to CREATE %s %s
В FUNCTION запрещено использование операторов, подобных SELECT,INSERT, UPDATE (и других)
Error MySQL: 1308
ER_SP_LILABEL_MISMATCH
%s with no matching label: %s
Журнал регистрации обновлений устарел и был заменен бинарным журналом регистрации; команда SET SQL_LOG_UPDATE игнорируется
Error MySQL: 1309
ER_SP_LABEL_REDEFINE
Redefining label %s
Журнал регистрации обновлений устарел и был заменен бинарным журналом регистрации; команда SET SQL_LOG_UPDATE переведена как SET SQL_LOG__BIN
Error MySQL: 1310
ER_SP_LABEL_MISMATCH
End-label %s without match
Выполнение запроса было прервано
Error MySQL: 1311
ER_SP_UNINIT_VAR
Referring to uninitialized variable %s
Неправильное число аргументов для %s %s; ожидалось %u, получено %u
Error MySQL: 1312
ER_SP_BADSELECT
PROCEDURE %s can’t return a result set in the given context
Неопределенная команда CONDITION: %s
Error MySQL: 1313
ER_SP_BADRETURN
RETURN is only allowed in a FUNCTION
RETURN в FUNCTION %s не обнаружен.
Error MySQL: 1314
ER_SP_BADSTATEMENT
%s is not allowed in stored procedures
FUNCTION %s завершилась без RETURN
Error MySQL: 1315
ER_UPDATE_LOG_DEPRECATED_IGNORED
The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. This option will be removed in MySQL 5.6.
Оператором курсора должен быть SELECT
Error MySQL: 1316
ER_UPDATE_LOG_DEPRECATED_TRANSLATED
The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. This option will be removed in MySQL 5.6.
Оператор курсора SELECT не должен содержать INTO
Error MySQL: 1317
ER_QUERY_INTERRUPTED
Query execution was interrupted
Неопределенный курсор CURSOR: %s
Error MySQL: 1318
ER_SP_WRONG_NO_OF_ARGS
Incorrect number of arguments for %s %s; expected %u, got %u
Курсор уже открыт
Error MySQL: 1319
ER_SP_COND_MISMATCH
Undefined CONDITION: %s
Курсор не открыт
Error MySQL: 1320
ER_SP_NORETURN
No RETURN found in FUNCTION %s
Необъявленная переменная: %s
Error MySQL: 1321
ER_SP_NORETURNEND
FUNCTION %s ended without RETURN
Неправильное число переменных FETCH
Error MySQL: 1322
ER_SP_BAD_CURSOR_QUERY
Cursor statement must be a SELECT
Данных для выборки (FETCH) нет
Error MySQL: 1323
ER_SP_BAD_CURSOR_SELECT
Cursor SELECT must not have INTO
Дублированный параметр: %s
Error MySQL: 1324
ER_SP_CURSOR_MISMATCH
Undefined CURSOR: %s
Дублированная переменная: %s
Error MySQL: 1325
ER_SP_CURSOR_ALREADY_OPEN
Cursor is already open
Дублированное условие: %s
Error MySQL: 1326
ER_SP_CURSOR_NOT_OPEN
Cursor is not open
Дублированный курсор: %s
Error MySQL: 1327
ER_SP_UNDECLARED_VAR
Undeclared variable: %s
He удалось изменить %s %s с помощью ALTER
Error MySQL: 1328
ER_SP_WRONG_NO_OF_FETCH_ARGS
Incorrect number of FETCH variables
Значение подвыборки не поддерживается
Error MySQL: 1329
ER_SP_FETCH_NO_DATA
No data — zero rows fetched, selected, or processed
Использование USE в хранимой процедуре запрещено
Error MySQL: 1330
ER_SP_DUP_PARAM
Duplicate parameter: %s
Объявление переменной или условия после объявления курсора или обработчика
Error MySQL: 1331
ER_SP_DUP_VAR
Duplicate variable: %s
Объявление курсора после объявления обработчика
Error MySQL: 1332
ER_SP_DUP_COND
Duplicate condition: %s
He найдена конструкция Case для оператора CASE
Error MySQL: 1333
ER_SP_DUP_CURS
Duplicate cursor: %s
Размер файла конфигурации слишком большой
Error MySQL: 1334
ER_SP_CANT_ALTER
Failed to ALTER %s %s
Некорректно заданный заголовок типа файла в файле «%s»
Error MySQL: 1335
ER_SP_SUBSELECT_NYI
Subquery value not supported
Неожиданный конец файла при анализе комментария «%s»
Error MySQL: 1336
ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG
%s is not allowed in stored function or trigger
Ошибка при анализе параметра «%s»
Error MySQL: 1337
ER_SP_VARCOND_AFTER_CURSHNDLR
Variable or condition declaration after cursor or handler declaration
Неожиданный конец файла при пропуске неизвестного параметра «%s»
Error MySQL: 1338
ER_SP_CURSOR_AFTER_HANDLER
Cursor declaration after handler declaration
Курсор заявление после декларации обработчик
Error MySQL: 1339
ER_SP_CASE_NOT_FOUND
Case not found for CASE statement
Дело не найдено для сазе
Error MySQL: 1340
ER_FPARSER_TOO_BIG_FILE
Configuration file ‘%s’ is too big
Конфигурация файл%s ‘ слишком большой
Error MySQL: 1341
ER_FPARSER_BAD_HEADER
Malformed file type header in file ‘%s’
Заголовок в файле с искаженной тип файл%s ‘
Error MySQL: 1342
ER_FPARSER_EOF_IN_COMMENT
Unexpected end of file while parsing comment ‘%s’
Неожиданный конец файла во время разбора комментарий ‘%s’
Error MySQL: 1343
ER_FPARSER_ERROR_IN_PARAMETER
Error while parsing parameter ‘%s’ (line: ‘%s’)
Ошибка при разборе параметра ‘%s’ (линия : ‘%s’)
Error MySQL: 1344
ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER
Unexpected end of file while skipping unknown parameter ‘%s’
Неожиданный конец файла, пропуская неизвестный параметр ‘%s’
Error MySQL: 1345
ER_VIEW_NO_EXPLAIN
EXPLAIN/SHOW can not be issued; lacking privileges for underlying table
EXPLAIN / ШОУ не может быть выдан;
Error MySQL: 1346
ER_FRM_UNKNOWN_TYPE
File ‘%s’ has unknown type ‘%s’ in its header
Файл ‘ %s’ имеет неизвестный тип «%s ‘ в его заголовке
Error MySQL: 1347
ER_WRONG_OBJECT
%s.%s’ is not %s
% с. % с ‘не % с
Error MySQL: 1348
ER_NONUPDATEABLE_COLUMN
Column ‘%s’ is not updatable
Колонка «%s ‘ не является обновляемым
Error MySQL: 1349
ER_VIEW_SELECT_DERIVED
View’s SELECT contains a subquery in the FROM clause
Посмотреть профиль ВЫБОР содержит вложенный запрос в предложении FROM
Error MySQL: 1350
ER_VIEW_SELECT_CLAUSE
View’s SELECT contains a ‘%s’ clause
Посмотреть профиль ВЫБОР содержит ‘%s’ пункт
Error MySQL: 1351
ER_VIEW_SELECT_VARIABLE
View’s SELECT contains a variable or parameter
Посмотреть профиль ВЫБОР содержит переменную или параметр
Error MySQL: 1352
ER_VIEW_SELECT_TMPTABLE
View’s SELECT refers to a temporary table ‘%s’
Посмотреть профиль ВЫБОР относится к временной таблицы ‘%s’
Error MySQL: 1353
ER_VIEW_WRONG_LIST
View’s SELECT and view’s field list have different column counts
ВЫБОР и Посмотреть профиль Просмотреть список на местах имеют разные счетчики столбцов
Error MySQL: 1354
ER_WARN_VIEW_MERGE
View merge algorithm can’t be used here for now (assumed undefined algorithm)
Вид алгоритм слияния не могут быть использованы здесь на данный момент (предположительно определено алгоритм)
Error MySQL: 1355
ER_WARN_VIEW_WITHOUT_KEY
View being updated does not have complete key of underlying table in it
Посмотреть обновляется не имеет полной ключ базовой таблицы в нем
Error MySQL: 1356
ER_VIEW_INVALID
View ‘%s.%s’ references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
Посмотреть «%s. %s ‘ указывает на недопустимый стол (ы ) или колонки (ы) или функция (ы) или Определитель / Вызывающий вид прав отсутствия их использовать
Error MySQL: 1357
ER_SP_NO_DROP_SP
Can’t drop or alter a %s from within another stored routine
Невозможно удалить или изменить %s из другой хранимой процедуре
Error MySQL: 1358
ER_SP_GOTO_IN_HNDLR
GOTO is not allowed in a stored procedure handler
GOTO не допускается в обработчике хранимой процедуры
Error MySQL: 1359
ER_TRG_ALREADY_EXISTS
Trigger already exists
Запуск уже существует
Error MySQL: 1360
ER_TRG_DOES_NOT_EXIST
Trigger does not exist
Триггера не существует
Error MySQL: 1361
ER_TRG_ON_VIEW_OR_TEMP_TABLE
Trigger’s ‘%s’ is view or temporary table
Триггера ‘%s’ представляет собой вид или временная таблица
Error MySQL: 1362
ER_TRG_CANT_CHANGE_ROW
Updating of %s row is not allowed in %strigger
Обновление подряд %s не допускается в % strigger
Error MySQL: 1363
ER_TRG_NO_SUCH_ROW_IN_TRG
There is no %s row in %s trigger
Существует ряд Нет% с в триггер %s
Error MySQL: 1364
ER_NO_DEFAULT_FOR_FIELD
Field ‘%s’ doesn’t have a default value
Поле ‘ %s’ не имеет значения по умолчанию
Error MySQL: 1365
ER_DIVISION_BY_ZERO
Division by 0
Деление на 0
Error MySQL: 1366
ER_TRUNCATED_WRONG_VALUE_FOR_FIELD
Incorrect %s value: ‘%s’ for column ‘%s’ at row %ld
Неправильные %s значение : «%s на столбец»%s ‘в строке %ld
Error MySQL: 1367
ER_ILLEGAL_VALUE_FOR_TYPE
Illegal %s ‘%s’ value found during parsing
Незаконное % с ‘%s’ найденное значение в процессе синтаксического
Error MySQL: 1368
ER_VIEW_NONUPD_CHECK
CHECK OPTION on non-updatable view ‘%s.%s’
CHECK OPTION на не обновляемого представления «%s. % С ‘
Error MySQL: 1369
ER_VIEW_CHECK_FAILED
CHECK OPTION failed ‘%s.%s’
ПРОВЕРКА ВАРИАНТ удалось ‘ %s. % С ‘
Error MySQL: 1370
ER_PROCACCESS_DENIED_ERROR
%s command denied to user ‘%s’@’%s’ for routine ‘%s’
Команда %s запрещена пользователю ‘ %s ‘ @ ’ %s на обычной ‘%s ‘
Error MySQL: 1371
ER_RELAY_LOG_FAIL
Failed purging old relay logs: %s
Не удалось продувки старые журналы реле : % с
Error MySQL: 1372
ER_PASSWD_LENGTH
Password hash should be a %d-digit hexadecimal number
Пароль хэш должен быть %d — значное шестнадцатеричное число
Error MySQL: 1373
ER_UNKNOWN_TARGET_BINLOG
Target log not found in binlog index
Целевая журнала не найден в Двоичный индекс
Error MySQL: 1374
ER_IO_ERR_LOG_INDEX_READ
I/O error reading log index file
Ошибка ввода / вывода индекс журнала чтение файла
Error MySQL: 1375
ER_BINLOG_PURGE_PROHIBITED
Server configuration does not permit binlog purge
Конфигурация сервера не позволяет Двоичный чистку
Error MySQL: 1376
ER_FSEEK_FAIL
Failed on fseek()
Не удалось на FSEEK ( )
Error MySQL: 1377
ER_BINLOG_PURGE_FATAL_ERR
Fatal error during log purge
Фатальная ошибка во время журнала продувки
Error MySQL: 1378
ER_LOG_IN_USE
A purgeable log is in use, will not purge
Промываемый журнал находится в использовании, не очистит
Error MySQL: 1379
ER_LOG_PURGE_UNKNOWN_ERR
Unknown error during log purge
Неизвестная ошибка при журнала продувки
Error MySQL: 1380
ER_RELAY_LOG_INIT
Failed initializing relay log position: %s
Не удалось инициализации реле позиция журнала : % с
Error MySQL: 1381
ER_NO_BINARY_LOGGING
You are not using binary logging
Вы не используете двоичную регистрацию
Error MySQL: 1382
ER_RESERVED_SYNTAX
The ‘%s’ syntax is reserved for purposes internal to the MySQL server
Синтаксис «%s ‘ зарезервирован для целей внутреннего к серверу MySQL
Error MySQL: 1383
ER_WSAS_FAILED
WSAStartup Failed
WSAStartup удалось
Error MySQL: 1384
ER_DIFF_GROUPS_PROC
Can’t handle procedures with different groups yet
Не можете справиться процедур с различными группами еще
Error MySQL: 1385
ER_NO_GROUP_FOR_PROC
Select must have a group with this procedure
Выберите должны иметь группу с этой процедурой
Error MySQL: 1386
ER_ORDER_WITH_PROC
Can’t use ORDER clause with this procedure
Нельзя использовать пункт заказ с этой процедурой
Error MySQL: 1387
ER_LOGGING_PROHIBIT_CHANGING_OF
Binary logging and replication forbid changing the global server %s
Двоичной лесозаготовки и репликация не дай изменения сервер глобального %s
Error MySQL: 1388
ER_NO_FILE_MAPPING
Can’t map file: %s, errno: %d
Не удается отобразить файл :%s, ошибка:%d
Error MySQL: 1389
ER_WRONG_MAGIC
Wrong magic in %s
Неправильный магия в % с
Error MySQL: 1390
ER_PS_MANY_PARAM
Prepared statement contains too many placeholders
Подготовлено заявление содержит слишком много заполнители
Error MySQL: 1391
ER_KEY_PART_0
Key part ‘%s’ length cannot be 0
Основные части ‘%s’ длина не может быть 0
Error MySQL: 1392
ER_VIEW_CHECKSUM
View text checksum failed
Просмотр текстовых Контрольная удалось
Error MySQL: 1393
ER_VIEW_MULTIUPDATE
Can not modify more than one base table through a join view ‘%s.%s’
Невозможно изменить более одной базовой таблицы через присоединиться вид ‘% с. % С ‘
Error MySQL: 1394
ER_VIEW_NO_INSERT_FIELD_LIST
Can not insert into join view ‘%s.%s’ without fields list
Не удается вставить в присоединиться вид ‘% с. % С ‘ без списка полей
Error MySQL: 1395
ER_VIEW_DELETE_MERGE_VIEW
Can not delete from join view ‘%s.%s’
Не удается удалить из присоединиться вид ‘% с. % С ‘
Error MySQL: 1396
ER_CANNOT_USER
Operation %s failed for %s
Операция % с Сбой % с
Error MySQL: 1397
ER_XAER_NOTA
XAER_NOTA: Unknown XID
XAER_NOTA : неизвестно XID
Error MySQL: 1398
ER_XAER_INVAL
XAER_INVAL: Invalid arguments (or unsupported command)
XAER_INVAL : инвалидные параметры (или не поддерживается команда)
Error MySQL: 1399
ER_XAER_RMFAIL
XAER_RMFAIL: The command cannot be executed when global transaction is in the %s state
XAER_RMFAIL : Команда не может быть выполнена, когда глобальная транзакция находится в состоянии в %s
Error MySQL: 1400
ER_XAER_OUTSIDE
XAER_OUTSIDE: Some work is done outside global transaction
XAER_OUTSIDE : Некоторые работы выполняются вне глобальной транзакции
Error MySQL: 1401
ER_XAER_RMERR
XAER_RMERR: Fatal error occurred in the transaction branch — check your data for consistency
XAER_RMERR : Фатальная ошибка в ветви транзакции — проверить данные на соответствие
Error MySQL: 1402
ER_XA_RBROLLBACK
XA_RBROLLBACK: Transaction branch was rolled back
XA_RBROLLBACK : филиал сделка откат
Error MySQL: 1403
ER_NONEXISTING_PROC_GRANT
There is no such grant defined for user ‘%s’ on host ‘%s’ on routine ‘%s’
Там нет такой грант определены для пользователя ‘%s’ на хосте ‘%s’ на обычной ‘%s’
Error MySQL: 1404
ER_PROC_AUTO_GRANT_FAIL
Failed to grant EXECUTE and ALTER ROUTINE privileges
Не удалось предоставить EXECUTE и ALTER рутины привилегии
Error MySQL: 1405
ER_PROC_AUTO_REVOKE_FAIL
Failed to revoke all privileges to dropped routine
Не удалось отменить все привилегии упал рутины
Error MySQL: 1406
ER_DATA_TOO_LONG
Data too long for column ‘%s’ at row %ld
Данные слишком долго для столбца ‘%s’ в строке%ld
Error MySQL: 1407
ER_SP_BAD_SQLSTATE
Bad SQLSTATE: ‘%s’
Плохой SQLSTATE : ‘%s’
Error MySQL: 1408
ER_STARTUP
%s: ready for connections. Version: ‘%s’ socket: ‘%s’ port: %d %s
% с : Готов принимать соединения.
Error MySQL: 1409
ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR
Can’t load value from file with fixed size rows to variable
Не удается загрузить значение из файла с фиксированного размера строк в переменной
Error MySQL: 1410
ER_CANT_CREATE_USER_WITH_GRANT
You are not allowed to create a user with GRANT
Вы не можете создать пользователя с Грантом
Error MySQL: 1411
ER_WRONG_VALUE_FOR_TYPE
Incorrect %s value: ‘%s’ for function %s
Неправильные %s значение : «%s на функции %s
Error MySQL: 1412
ER_TABLE_DEF_CHANGED
Table definition has changed, please retry transaction
Определение таблицы изменилось, повторите попытку сделки
Error MySQL: 1413
ER_SP_DUP_HANDLER
Duplicate handler declared in the same block
Дубликат обработчик заявил в том же блоке
Error MySQL: 1414
ER_SP_NOT_VAR_ARG
OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger
OUT или INOUT аргумент%d для рутинной % с не является переменной или НОВЫЙ псевдопеременная в перед срабатыванием
Error MySQL: 1415
ER_SP_NO_RETSET
Not allowed to return a result set from a %s
Не разрешается возвращать результирующий набор из %s
Error MySQL: 1416
ER_CANT_CREATE_GEOMETRY_OBJECT
Cannot get geometry object from data you send to the GEOMETRY field
Не удается получить геометрии объекта из данных отправке на поле ГЕОМЕТРИИ
Error MySQL: 1417
ER_FAILED_ROUTINE_BREAK_BINLOG
A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes
Процедура не удалось, и не имеет ни Нет SQL, ни ЧИТАЕТ SQL DATA в его декларации и двоичный включено ведение журнала;
Error MySQL: 1418
ER_BINLOG_UNSAFE_ROUTINE
This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Эта функция не имеет ни одного из детерминированных, NO SQL или ЧИТАЕТ SQL DATA в своем заявлении и двоичный ведение журнала включено (вы * возможно * хотите использовать менее безопасные log_bin_trust_function_creators переменных )
Error MySQL: 1419
ER_BINLOG_CREATE_ROUTINE_NEED_SUPER
You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)
Вы не имеете SUPER привилегии и двоичный ведение журнала включено (вы * может * хотите использовать менее безопасные log_bin_trust_function_creators переменных )
Error MySQL: 1420
ER_EXEC_STMT_WITH_OPEN_CURSOR
You can’t execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.
Вы не можете выполнить подготовленное заявление, которое имеет открытый курсор, связанный с ним.
Error MySQL: 1421
ER_STMT_HAS_NO_OPEN_CURSOR
The statement (%lu) has no open cursor.
В заявлении ( % лу ) не имеет открытого курсора.
Error MySQL: 1422
ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG
Explicit or implicit commit is not allowed in stored function or trigger.
Явное или неявное обязательство не допускается в сохраненной функции или триггера.
Error MySQL: 1423
ER_NO_DEFAULT_FOR_VIEW_FIELD
Field of view ‘%s.%s’ underlying table doesn’t have a default value
Поле зрения «%s. % С ‘ базовая таблица не имеет значения по умолчанию
Error MySQL: 1424
ER_SP_NO_RECURSION
Recursive stored functions and triggers are not allowed.
Рекурсивные хранимые функции и триггеры не допускаются.
Error MySQL: 1425
ER_TOO_BIG_SCALE
Too big scale %d specified for column ‘%s’. Maximum is %lu.
Слишком большой масштаб %d указано для столбец «%s ‘.
Error MySQL: 1426
ER_TOO_BIG_PRECISION
Too big precision %d specified for column ‘%s’. Maximum is %lu.
Слишком большой точности %d указано для столбец «%s ‘.
Error MySQL: 1427
ER_M_BIGGER_THAN_D
For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column ‘%s’).
Для поплавка ( M, D), дважды ( M, D ) или десятичной ( M, D ), М должны бытьu003e = D ( столбец «%s ‘).
Error MySQL: 1428
ER_WRONG_LOCK_OF_SYSTEM_TABLE
You can’t combine write-locking of system tables with other tables or lock types
Вы не можете комбинировать рецензию блокировку системных таблиц с другими таблицами или заблокировать типы
Error MySQL: 1429
ER_CONNECT_TO_FOREIGN_DATA_SOURCE
Unable to connect to foreign data source: %s
Не удается подключиться к внешней источника данных : % с
Error MySQL: 1430
ER_QUERY_ON_FOREIGN_DATA_SOURCE
There was a problem processing the query on the foreign data source. Data source Error MySQL: %s
Существовал проблема обработки запроса на внешнем источнике данных.
Error MySQL: 1431
ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST
The foreign data source you are trying to reference does not exist. Data source Error MySQL: %s
Иностранный источник данных вы пытаетесь ссылкой не существует.
Error MySQL: 1432
ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE
Can’t create federated table. The data source connection string ‘%s’ is not in the correct format
Не удается создать таблицу федеративного.
Error MySQL: 1433
ER_FOREIGN_DATA_STRING_INVALID
The data source connection string ‘%s’ is not in the correct format
Строка подключения источника данных «%s ‘не в правильном формате
Error MySQL: 1434
ER_CANT_CREATE_FEDERATED_TABLE
Can’t create federated table. Foreign data src Error MySQL: %s
Не удается создать таблицу федеративного.
Error MySQL: 1435
ER_TRG_IN_WRONG_SCHEMA
Trigger in wrong schema
Запуск в неправильном схеме
Error MySQL: 1436
ER_STACK_OVERRUN_NEED_MORE
Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use ‘mysqld —thread_stack=#’ to specify a bigger stack.
Стек потоков переполнен : байт LD% используемых стека байт LD%, и нуждался % байт LD.
Error MySQL: 1437
ER_TOO_LONG_BODY
Routine body for ‘%s’ is too long
Регулярное тело для ‘%s’ слишком длинный
Error MySQL: 1438
ER_WARN_CANT_DROP_DEFAULT_KEYCACHE
Cannot drop default keycache
Невозможно удалить умолчанию keycache
Error MySQL: 1439
ER_TOO_BIG_DISPLAYWIDTH
Display width out of range for column ‘%s’ (max = %lu)
Ширина дисплея вне диапазона для столбец «%s » (макс. = % лу )
Error MySQL: 1440
ER_XAER_DUPID
XAER_DUPID: The XID already exists
XAER_DUPID :XID уже существует
Error MySQL: 1441
ER_DATETIME_FUNCTION_OVERFLOW
Datetime function: %s field overflow
Функция даты и времени : % с Переполнение поля
Error MySQL: 1442
ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
Can’t update table ‘%s’ in stored function/trigger because it is already used by statement which invoked this stored function/trigger.
Невозможно обновить таблицу ‘%s’ в хранимой функции / триггера, так как он уже используется заявлении, которое вызывается эту хранимую функцию / курок.
Error MySQL: 1443
ER_VIEW_PREVENT_UPDATE
The definition of table ‘%s’ prevents operation %s on table ‘%s’.
Определение таблица «%s ‘ предотвращает операция %s таблицы»%s ‘.
Error MySQL: 1444
ER_PS_NO_RECURSION
The prepared statement contains a stored routine call that refers to that same statement. It’s not allowed to execute a prepared statement in such a recursive manner
Подготовленный оператор содержит хранимую стандартного вызова, который ссылается на тот же заявлении.
Error MySQL: 1445
ER_SP_CANT_SET_AUTOCOMMIT
Not allowed to set autocommit from a stored function or trigger
Не допускается устанавливать автоматической фиксации из хранимой функции или триггера
Error MySQL: 1446
ER_MALFORMED_DEFINER
Definer is not fully qualified
Definer не полное
Error MySQL: 1447
ER_VIEW_FRM_NO_USER
View ‘%s’.’%s’ has no definer information (old table format). Current user is used as definer. Please recreate the view!
Посмотреть «%s ‘.’ %s ‘ не имеет никакой информации Definer (старый в виде таблицы).
Error MySQL: 1448
ER_VIEW_OTHER_USER
You need the SUPER privilege for creation view with ‘%s’@’%s’ definer
Вам нужен SUPER привилегии для зрения создания с ‘%s’ @ ‘ %s’ Definer
Error MySQL: 1449
ER_NO_SUCH_USER
The user specified as a definer (‘%s’@’%s’) does not exist
Указанный в качестве определителя (‘%s’ @ ‘ %s’) пользователь не существует
Error MySQL: 1450
ER_FORBID_SCHEMA_CHANGE
Changing schema from ‘%s’ to ‘%s’ is not allowed.
Изменение схемы из ‘%s’ в ‘%s’ не допускается.
Error MySQL: 1451
ER_ROW_IS_REFERENCED_2
Cannot delete or update a parent row: a foreign key constraint fails (%s)
Не можете удалить или обновить родительскую строку : ограничение внешнего ключа не удается ( %s)
Error MySQL: 1452
ER_NO_REFERENCED_ROW_2
Cannot add or update a child row: a foreign key constraint fails (%s)
Невозможно добавить или обновить дочернюю строку : ограничение внешнего ключа не удается ( %s)
Error MySQL: 1453
ER_SP_BAD_VAR_SHADOW
Variable ‘%s’ must be quoted with `…`, or renamed
Переменная ‘ %s’ должна быть указана с `…`, или переименованы
Error MySQL: 1454
ER_TRG_NO_DEFINER
No definer attribute for trigger ‘%s’.’%s’. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.
Нет Определитель атрибут для запуска ‘%s’ ‘%s’..
Error MySQL: 1455
ER_OLD_FILE_FORMAT
%s’ has an old format, you should re-create the ‘%s’ object(s)
%s ‘ имеет старый формат, вы должны заново создать ‘ ‘ объект % с (ы)
Error MySQL: 1456
ER_SP_RECURSION_LIMIT
Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %s
Рекурсивные предел %d (как указано в переменной max_sp_recursion_depth ) был превышен на рутинной % с
Error MySQL: 1457
ER_SP_PROC_TABLE_CORRUPT
Failed to load routine %s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)
Не удалось загрузить рутинной %s.
Error MySQL: 1458
ER_SP_WRONG_NAME
Incorrect routine name ‘%s’
Неправильное имя процедуры ‘%s’
Error MySQL: 1459
ER_TABLE_NEEDS_UPGRADE
Table upgrade required. Please do «REPAIR TABLE `%s`» or dump/reload to fix it!
Требуется обновление Таблица.
Error MySQL: 1460
ER_SP_NO_AGGREGATE
AGGREGATE is not supported for stored functions
СОВОКУПНАЯ не поддерживается для хранимых функций
Error MySQL: 1461
ER_MAX_PREPARED_STMT_COUNT_REACHED
Can’t create more than max_prepared_stmt_count statements (current value: %lu)
Не удается создать более max_prepared_stmt_count отчетности ( текущее значение : % лу )
Error MySQL: 1462
ER_VIEW_RECURSIVE
`%s`.`%s` contains view recursion
`% с `. `% с ` содержит вид рекурсии
Error MySQL: 1463
ER_NON_GROUPING_FIELD_USED
Non-grouping field ‘%s’ is used in %s clause
Номера для группировки поле «%s » используется в пункте %s
Error MySQL: 1464
ER_TABLE_CANT_HANDLE_SPKEYS
The used table type doesn’t support SPATIAL indexes
Используемая таблица браузер не поддерживает пространственных индексов
Error MySQL: 1465
ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA
Triggers can not be created on system tables
Триггеры не могут быть созданы для системных таблиц
Error MySQL: 1466
ER_REMOVED_SPACES
Leading spaces are removed from name ‘%s’
Ведущие пробелы удаляются из имени «%s ‘
Error MySQL: 1467
ER_AUTOINC_READ_FAILED
Failed to read auto-increment value from storage engine
Не удалось прочитать значение автоприращения от механизма хранения
Error MySQL: 1468
ER_USERNAME
user name
имя пользователя
Error MySQL: 1469
ER_HOSTNAME
host name
имя хоста
Error MySQL: 1470
ER_WRONG_STRING_LENGTH
String ‘%s’ is too long for %s (should be no longer than %d)
Строка «%s ‘ слишком длинный для % с ( должна быть не более %d)
Error MySQL: 1471
ER_NON_INSERTABLE_TABLE
The target table %s of the %s is not insertable-into
Целевая таблица % х годов % с не вставляться — в
Error MySQL: 1472
ER_ADMIN_WRONG_MRG_TABLE
Table ‘%s’ is differently defined or of non-MyISAM type or doesn’t exist
Таблица ‘%s’ по-разному определяется или типа не- MyISAM или не существует
Error MySQL: 1473
ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT
Too high level of nesting for select
Слишком высокий уровень вложенности для выбора
Error MySQL: 1474
ER_NAME_BECOMES_EMPTY
Name ‘%s’ has become »
Имя «%s » стал »
Error MySQL: 1475
ER_AMBIGUOUS_FIELD_TERM
First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY
Первый символ из полей завершенная строка неоднозначно;
Error MySQL: 1476
ER_FOREIGN_SERVER_EXISTS
The foreign server, %s, you are trying to create already exists.
Иностранный сервера,% с, вы пытаетесь создать, уже существует.
Error MySQL: 1477
ER_FOREIGN_SERVER_DOESNT_EXIST
The foreign server name you are trying to reference does not exist. Data source Error MySQL: %s
Название иностранной сервер вы пытаетесь ссылкой не существует.
Error MySQL: 1478
ER_ILLEGAL_HA_CREATE_OPTION
Table storage engine ‘%s’ does not support the create option ‘%s’
Хранения Таблица двигатель «%s ‘не поддерживаетсоздание опция’ %s ‘
Error MySQL: 1479
ER_PARTITION_REQUIRES_VALUES_ERROR
Syntax Error MySQL: %s PARTITIONING requires definition of VALUES %s for each partition
Синтаксическая ошибка: %s PARTITIONING требуется определение ЗНАЧЕНИЯ % с для каждого раздела
Error MySQL: 1480
ER_PARTITION_WRONG_VALUES_ERROR
Only %s PARTITIONING can use VALUES %s in partition definition
Только %s PARTITIONING можете использовать значения %s в определении разделов
Error MySQL: 1481
ER_PARTITION_MAXVALUE_ERROR
MAXVALUE can only be used in last partition definition
MAXVALUE может использоваться только в последнем определении разделов
Error MySQL: 1482
ER_PARTITION_SUBPARTITION_ERROR
Subpartitions can only be hash partitions and by key
Подразделы может быть только хеш- разделов и ключ
Error MySQL: 1483
ER_PARTITION_SUBPART_MIX_ERROR
Must define subpartitions on all partitions if on one partition
Необходимо определить подразделы на всех разделах, если на одном разделе
Error MySQL: 1484
ER_PARTITION_WRONG_NO_PART_ERROR
Wrong number of partitions defined, mismatch with previous setting
Неверное количество разделов, определенных, несоответствие с предыдущей настройке
Error MySQL: 1485
ER_PARTITION_WRONG_NO_SUBPART_ERROR
Wrong number of subpartitions defined, mismatch with previous setting
Неверное количество подразделов определенных, несоответствие с предыдущей настройке
Error MySQL: 1486
ER_CONST_EXPR_IN_PARTITION_FUNC_ERROR
Constant/Random expression in (sub)partitioning function is not allowed
Постоянное / Random выражение в (под) функции секционирования не допускается
Error MySQL: 1486
ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR
Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed
Постоянные, случайные или часовой пояс в зависимости от выражения в (под) функции секционирования не допускаются
Error MySQL: 1487
ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR
Expression in RANGE/LIST VALUES must be constant
Выражение в диапазоне / Список значений должен быть постоянным
Error MySQL: 1488
ER_FIELD_NOT_FOUND_PART_ERROR
Field in list of fields for partition function not found in table
Поле в списке полей для функции распределения не найден в таблице
Error MySQL: 1489
ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR
List of fields is only allowed in KEY partitions
Список полей допускается только в ключевых разделов
Error MySQL: 1490
ER_INCONSISTENT_PARTITION_INFO_ERROR
The partition info in the frm file is not consistent with what can be written into the frm file
Информация раздела в файле FRM не согласуется с тем, что можно записать в файл FRM
Error MySQL: 1491
ER_PARTITION_FUNC_NOT_ALLOWED_ERROR
The %s function returns the wrong type
Функция% с возвращает неправильный тип
Error MySQL: 1492
ER_PARTITIONS_MUST_BE_DEFINED_ERROR
For %s partitions each partition must be defined
Для %s разделов каждый раздел должен быть определен
Error MySQL: 1493
ER_RANGE_NOT_INCREASING_ERROR
VALUES LESS THAN value must be strictly increasing for each partition
Значения меньше стоимости должны быть строго возрастает для каждого раздела
Error MySQL: 1494
ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR
VALUES value must be of same type as partition function
ЗНАЧЕНИЯ значение должно быть одного типа, как функции распределения
Error MySQL: 1495
ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR
Multiple definition of same constant in list partitioning
Несколько определение же константой в список разделов
Error MySQL: 1496
ER_PARTITION_ENTRY_ERROR
Partitioning can not be used stand-alone in query
Разметка не может использоваться автономно в запросе
Error MySQL: 1497
ER_MIX_HANDLER_ERROR
The mix of handlers in the partitions is not allowed in this version of MySQL
Сочетание обработчиков в разделах не допускается в данной версии MySQL
Error MySQL: 1498
ER_PARTITION_NOT_DEFINED_ERROR
For the partitioned engine it is necessary to define all %s
Для многораздельной двигателя необходимо определить все % с
Error MySQL: 1499
ER_TOO_MANY_PARTITIONS_ERROR
Too many partitions (including subpartitions) were defined
Слишком много разделов (в том числе подразделов ) были определены
Error MySQL: 1500
ER_SUBPARTITION_ERROR
It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning
Это возможно только смешивать RANGE / разделов списка с хэш / ключ разделения для subpartitioning
Error MySQL: 1501
ER_CANT_CREATE_HANDLER_FILE
Failed to create specific handler file
Не удалось создать определенный файл обработчика
Error MySQL: 1502
ER_BLOB_FIELD_IN_PART_FUNC_ERROR
A BLOB field is not allowed in partition function
Поле BLOB не допускается в функции секционирования
Error MySQL: 1503
ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF
A %s must include all columns in the table’s partitioning function
% С должны включить все столбцы в функции секционирования таблицы
Error MySQL: 1504
ER_NO_PARTS_ERROR
Number of %s = 0 is not an allowed value
Количество % с = 0 не является допустимое значение
Error MySQL: 1505
ER_PARTITION_MGMT_ON_NONPARTITIONED
Partition management on a not partitioned table is not possible
Управление разделов на не секционированной таблицы не возможно
Error MySQL: 1506
ER_FOREIGN_KEY_ON_PARTITIONED
Foreign key clause is not yet supported in conjunction with partitioning
Предложение Внешний ключ пока не поддерживается в сочетании с разбиением
Error MySQL: 1507
ER_DROP_PARTITION_NON_EXISTENT
Error in list of partitions to %s
Ошибка в списке разделов, %s
Error MySQL: 1508
ER_DROP_LAST_PARTITION
Cannot remove all partitions, use DROP TABLE instead
Не можете удалить все разделы, используйте DROP TABLE вместо
Error MySQL: 1509
ER_COALESCE_ONLY_ON_HASH_PARTITION
COALESCE PARTITION can only be used on HASH/KEY partitions
COALESCE раздел может быть использован только на ХЭШ / KEY разделов
Error MySQL: 1510
ER_REORG_HASH_ONLY_ON_SAME_NO
REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers
REORGANIZE раздел может быть использован только реорганизовать разделы не менять свои номера
Error MySQL: 1511
ER_REORG_NO_PARAM_ERROR
REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs
REORGANIZE PARTITION без параметров может быть использован только на авто — распределяли таблиц с использованием хэш- перегородки
Error MySQL: 1512
ER_ONLY_ON_RANGE_LIST_PARTITION
%s PARTITION can only be used on RANGE/LIST partitions
%s раздел может быть использован только на RANGE / LIST разделов
Error MySQL: 1513
ER_ADD_PARTITION_SUBPART_ERROR
Trying to Add partition(s) with wrong number of subpartitions
Попытка Добавить раздел (ы) с неправильным числом подразделов
Error MySQL: 1514
ER_ADD_PARTITION_NO_NEW_PARTITION
At least one partition must be added
По крайней мере один раздел должен быть добавлен
Error MySQL: 1515
ER_COALESCE_PARTITION_NO_PARTITION
At least one partition must be coalesced
По крайней мере один раздел должен быть объединились
Error MySQL: 1516
ER_REORG_PARTITION_NOT_EXIST
More partitions to reorganize than there are partitions
Еще разделы по реорганизации, чем Есть разделы
Error MySQL: 1517
ER_SAME_NAME_PARTITION
Duplicate partition name %s
Дубликат имя раздела % с
Error MySQL: 1518
ER_NO_BINLOG_ERROR
It is not allowed to shut off binlog on this command
Не допускается, чтобы отключить Двоичный по этой команде
Error MySQL: 1519
ER_CONSECUTIVE_REORG_PARTITIONS
When reorganizing a set of partitions they must be in consecutive order
При реорганизации набор разделов они должны быть в последовательном порядке
Error MySQL: 1520
ER_REORG_OUTSIDE_RANGE
Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range
Реорганизовать разделов дальности не может изменить общий диапазоны для последнего раздела, где она может расширить диапазон за исключением
Error MySQL: 1521
ER_PARTITION_FUNCTION_FAILURE
Partition function not supported in this version for this handler
Статистическая не поддерживается в этой версии для этого обработчика
Error MySQL: 1522
ER_PART_STATE_ERROR
Partition state cannot be defined from CREATE/ALTER TABLE
Состояние раздела не может быть определена с CREATE / ALTER TABLE
Error MySQL: 1523
ER_LIMITED_PART_RANGE
The %s handler only supports 32 bit integers in VALUES
Обработчик в %s поддерживает только 32-битные целые числа в ЦЕННОСТЕЙ
Error MySQL: 1524
ER_PLUGIN_IS_NOT_LOADED
Plugin ‘%s’ is not loaded
Плагин ‘%s’ не загружен
Error MySQL: 1525
ER_WRONG_VALUE
Incorrect %s value: ‘%s’
Неправильные %s значение : «%s ‘
Error MySQL: 1526
ER_NO_PARTITION_FOR_GIVEN_VALUE
Table has no partition for value %s
Таблица не имеет раздел для значение % с
Error MySQL: 1527
ER_FILEGROUP_OPTION_ONLY_ONCE
It is not allowed to specify %s more than once
Не допускается указывать % с более чем один раз
Error MySQL: 1528
ER_CREATE_FILEGROUP_FAILED
Failed to create %s
Не удалось создать % с
Error MySQL: 1529
ER_DROP_FILEGROUP_FAILED
Failed to drop %s
Не удалось удалить % с
Error MySQL: 1530
ER_TABLESPACE_AUTO_EXTEND_ERROR
The handler doesn’t support autoextend of tablespaces
Обработчик браузер не поддерживает AUTOEXTEND табличных
Error MySQL: 1531
ER_WRONG_SIZE_NUMBER
A size parameter was incorrectly specified, either number or on the form 10M
Параметр размера был неправильно определен, либо номер или на форме 10M
Error MySQL: 1532
ER_SIZE_OVERFLOW_ERROR
The size number was correct but we don’t allow the digit part to be more than 2 billion
Размер телефона был правилен, но мы не позволяем цифра часть не может быть более 2 млрд.
Error MySQL: 1533
ER_ALTER_FILEGROUP_FAILED
Failed to alter: %s
Не удалось изменить : % с
Error MySQL: 1534
ER_BINLOG_ROW_LOGGING_FAILED
Writing one row to the row-based binary log failed
Написание одну строку в рядной бинарного журнала не удалось
Error MySQL: 1535
ER_BINLOG_ROW_WRONG_TABLE_DEF
Table definition on master and slave does not match: %s
Определение таблицы на ведущего и ведомого не соответствует : % с
Error MySQL: 1536
ER_BINLOG_ROW_RBR_TO_SBR
Slave running with —log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events
Ведомый работает с — войти — рабовладельцы обновления должны использовать строки на основе двоичную регистрацию, чтобы иметь возможность повторить двоичных событий журнала строк на основе
Error MySQL: 1537
ER_EVENT_ALREADY_EXISTS
Event ‘%s’ already exists
Событие «%s ‘уже существует
Error MySQL: 1538
ER_EVENT_STORE_FAILED
Failed to store event %s. Error code %d from storage engine.
Не удалось сохранить событие %s.
Error MySQL: 1539
ER_EVENT_DOES_NOT_EXIST
Unknown event ‘%s’
Неизвестный событие ‘%s’
Error MySQL: 1540
ER_EVENT_CANT_ALTER
Failed to alter event ‘%s’
Не удалось изменить событие ‘%s’
Error MySQL: 1541
ER_EVENT_DROP_FAILED
Failed to drop %s
Не удалось удалить % с
Error MySQL: 1542
ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG
INTERVAL is either not positive or too big
ИНТЕРВАЛ либо не положительный или слишком большой
Error MySQL: 1543
ER_EVENT_ENDS_BEFORE_STARTS
ENDS is either invalid or before STARTS
Концами либо недействительным или до начала
Error MySQL: 1544
ER_EVENT_EXEC_TIME_IN_THE_PAST
Event execution time is in the past. Event has been disabled
Время выполнения событие в прошлом.
Error MySQL: 1545
ER_EVENT_OPEN_TABLE_FAILED
Failed to open mysql.event
Не удалось открыть mysql.event
Error MySQL: 1546
ER_EVENT_NEITHER_M_EXPR_NOR_M_AT
No datetime expression provided
Нет выражение даты и времени при условии,
Error MySQL: 1547
ER_COL_COUNT_DOESNT_MATCH_CORRUPTED
Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted
Колонка кол MySQL. % С неправильно.
Error MySQL: 1548
ER_CANNOT_LOAD_FROM_TABLE
Cannot load from mysql.%s. The table is probably corrupted
Не удается загрузить из MySQL. % С.
Error MySQL: 1549
ER_EVENT_CANNOT_DELETE
Failed to delete the event from mysql.event
Не удалось удалить событие из mysql.event
Error MySQL: 1550
ER_EVENT_COMPILE_ERROR
Error during compilation of event’s body
Ошибка при компиляции тела мероприятия
Error MySQL: 1551
ER_EVENT_SAME_NAME
Same old and new event name
То же самое старое и новое название события
Error MySQL: 1552
ER_EVENT_DATA_TOO_LONG
Data for column ‘%s’ too long
Данные за столбец «%s ‘ слишком долго
Error MySQL: 1553
ER_DROP_INDEX_FK
Cannot drop index ‘%s’: needed in a foreign key constraint
Невозможно удалить индекс «%s ‘ : необходимо в ограничении внешнего ключа
Error MySQL: 1554
ER_WARN_DEPRECATED_SYNTAX_WITH_VER
The syntax ‘%s’ is deprecated and will be removed in MySQL %s. Please use %s instead
Синтаксис «%s ‘ устарела и будет удалена в MySQL % с.
Error MySQL: 1555
ER_CANT_WRITE_LOCK_LOG_TABLE
You can’t write-lock a log table. Only read access is possible
Вы не можете написать — блокировки таблицы журнала.
Error MySQL: 1556
ER_CANT_LOCK_LOG_TABLE
You can’t use locks with log tables.
Вы не можете использовать замки с таблицами журнала.
Error MySQL: 1557
ER_FOREIGN_DUPLICATE_KEY
Upholding foreign key constraints for table ‘%s’, entry ‘%s’, key %d would lead to a duplicate entry
Поддержание внешнего ключа для таблицы «%s ‘, вход ‘%s ‘, ключ%d приведет к дублирования ввода
Error MySQL: 1558
ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE
Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.
Колонка кол MySQL. % С неправильно.
Error MySQL: 1559
ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR
Cannot switch out of the row-based binary log format when the session has open temporary tables
Невозможно переключить из двоичном формате журнала рядной когда сессия есть открытые временные таблицы
Error MySQL: 1560
ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT
Cannot change the binary logging format inside a stored function or trigger
Невозможно изменить двоичный формат ведения журнала внутри хранимой функции или триггера
Error MySQL: 1561
ER_NDB_CANT_SWITCH_BINLOG_FORMAT
The NDB cluster engine does not support changing the binlog format on the fly yet
Кластер двигатель NDB браузер не поддерживает изменения Двоичный формат на лету еще
Error MySQL: 1562
ER_PARTITION_NO_TEMPORARY
Cannot create temporary table with partitions
Невозможно создать временную таблицу с разделами
Error MySQL: 1563
ER_PARTITION_CONST_DOMAIN_ERROR
Partition constant is out of partition function domain
Постоянная разделов находится вне функции секционирования области
Error MySQL: 1564
ER_PARTITION_FUNCTION_IS_NOT_ALLOWED
This partition function is not allowed
Эта функция раздел не допускается
Error MySQL: 1565
ER_DDL_LOG_ERROR
Error in DDL log
Ошибка в журнале DDL
Error MySQL: 1566
ER_NULL_IN_VALUES_LESS_THAN
Not allowed to use NULL value in VALUES LESS THAN
Не разрешается использовать NULL значение в величине меньше, чем
Error MySQL: 1567
ER_WRONG_PARTITION_NAME
Incorrect partition name
Неправильное имя раздела
Error MySQL: 1568
ER_CANT_CHANGE_TX_ISOLATION
Transaction isolation level can’t be changed while a transaction is in progress
Уровень изоляции транзакций не может быть изменен в то время как транзакция выполняется
Error MySQL: 1569
ER_DUP_ENTRY_AUTOINCREMENT_CASE
ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘%s’ for key ‘%s’
ALTER TABLE вызывает auto_increment Resequencing, в результате дублирования ввода ‘ %s на ключевой ‘%s ‘
Error MySQL: 1570
ER_EVENT_MODIFY_QUEUE_ERROR
Internal scheduler error %d
Внутренняя ошибка планировщик %d
Error MySQL: 1571
ER_EVENT_SET_VAR_ERROR
Error during starting/stopping of the scheduler. Error code %u
Ошибка при Запуск / остановка планировщика.
Error MySQL: 1572
ER_PARTITION_MERGE_ERROR
Engine cannot be used in partitioned tables
Двигатель не может быть использован в секционированных таблиц
Error MySQL: 1573
ER_CANT_ACTIVATE_LOG
Cannot activate ‘%s’ log
Невозможно активировать ‘%s’ журнал
Error MySQL: 1574
ER_RBR_NOT_AVAILABLE
The server was not built with row-based replication
Сервер не был построен с рядной репликации
Error MySQL: 1575
ER_BASE64_DECODE_ERROR
Decoding of base64 string failed
Расшифровка base64 строки не удалось
Error MySQL: 1576
ER_EVENT_RECURSION_FORBIDDEN
Recursion of EVENT DDL statements is forbidden when body is present
Рекурсия события DDL заявления запрещено, когда тело присутствует
Error MySQL: 1577
ER_EVENTS_DB_ERROR
Cannot proceed because system tables used by Event Scheduler were found damaged at server start
Не удается выполнить, потому что системные таблицы, используемые Event Scheduler были найдены повреждения при запуске сервера
Error MySQL: 1578
ER_ONLY_INTEGERS_ALLOWED
Only integers allowed as number here
Только целые допускается в качестве числа здесь
Error MySQL: 1579
ER_UNSUPORTED_LOG_ENGINE
This storage engine cannot be used for log tables»
Этот двигатель хранения не могут быть использованы для таблиц журнала «
Error MySQL: 1580
ER_BAD_LOG_STATEMENT
You cannot ‘%s’ a log table if logging is enabled
Вы не можете ‘%s’ таблица журнала, если включено ведение журнала
Error MySQL: 1581
ER_CANT_RENAME_LOG_TABLE
Cannot rename ‘%s’. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to ‘%s’
Невозможно переименовать ‘%s’.
Error MySQL: 1582
ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT
Incorrect parameter count in the call to native function ‘%s’
Неправильное количество параметров в вызове собственной функции ‘%s’
Error MySQL: 1583
ER_WRONG_PARAMETERS_TO_NATIVE_FCT
Incorrect parameters in the call to native function ‘%s’
Неверные параметры в вызове собственной функции ‘%s’
Error MySQL: 1584
ER_WRONG_PARAMETERS_TO_STORED_FCT
Incorrect parameters in the call to stored function ‘%s’
Неверные параметры в вызове хранимой функции ‘%s’
Error MySQL: 1585
ER_NATIVE_FCT_NAME_COLLISION
This function ‘%s’ has the same name as a native function
Эта функция ‘%s’ имеет то же имя, родной функции
Error MySQL: 1586
ER_DUP_ENTRY_WITH_KEY_NAME
Duplicate entry ‘%s’ for key ‘%s’
Дублировать запись ‘%s’ для ключа «%s ‘
Error MySQL: 1587
ER_BINLOG_PURGE_EMFILE
Too many files opened, please execute the command again
Слишком много файлов открыто, пожалуйста, выполните команду снова
Error MySQL: 1588
ER_EVENT_CANNOT_CREATE_IN_THE_PAST
Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
Время выполнения событие в прошлом и по окончании не сохраняют установлен.
Error MySQL: 1589
ER_EVENT_CANNOT_ALTER_IN_THE_PAST
Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.
Время выполнения событие в прошлом и по окончании не сохраняют установлен.
Error MySQL: 1590
ER_SLAVE_INCIDENT
The incident %s occured on the master. %s
Инцидент % с произошло на главном.
Error MySQL: 1591
ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT
Table has no partition for some existing values
Таблица не имеет раздел для некоторых существующих значений
Error MySQL: 1592
ER_BINLOG_UNSAFE_STATEMENT
Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s
Небезопасная заявление записываются в двоичном журнале с использованием формата отчетности с BINLOG_FORMAT = ЗАЯВЛЕНИЕ.
Error MySQL: 1593
ER_SLAVE_FATAL_ERROR
Fatal Error MySQL: %s
Фатальная ошибка: % с
Error MySQL: 1594
ER_SLAVE_RELAY_LOG_READ_FAILURE
Relay log read failure: %s
Журнал Реле читать провал : % с
Error MySQL: 1595
ER_SLAVE_RELAY_LOG_WRITE_FAILURE
Relay log write failure: %s
Реле журнала ошибка записи : % с
Error MySQL: 1596
ER_SLAVE_CREATE_EVENT_FAILURE
Failed to create %s
Не удалось создать % с
Error MySQL: 1597
ER_SLAVE_MASTER_COM_FAILURE
Master command %s failed: %s
Мастер команда% с не удалось: % с
Error MySQL: 1598
ER_BINLOG_LOGGING_IMPOSSIBLE
Binary logging not possible. %s
Двоичной регистрации невозможно.
Error MySQL: 1599
ER_VIEW_NO_CREATION_CTX
View `%s`.`%s` has no creation context
Зайти % с `. `% С ` не имеет контекст создания
Error MySQL: 1600
ER_VIEW_INVALID_CREATION_CTX
Creation context of view `%s`.`%s’ is invalid
Контекст Создание зрения `% ов `. `% С » недопустим
Error MySQL: 1601
ER_SR_INVALID_CREATION_CTX
Creation context of stored routine `%s`.`%s` is invalid
Контекст Создание хранимой рутинной `% с `. `% С ` является недействительным
Error MySQL: 1602
ER_TRG_CORRUPTED_FILE
Corrupted TRG file for table `%s`.`%s`
Поврежденный TRG файл для таблицы ‘% с `. `% С `
Error MySQL: 1603
ER_TRG_NO_CREATION_CTX
Triggers for table `%s`.`%s` have no creation context
Не Триггеры для таблицы ` % с `. « Имеют никакого контекста слова %s
Error MySQL: 1604
ER_TRG_INVALID_CREATION_CTX
Trigger creation context of table `%s`.`%s` is invalid
Создание триггера контекст таблицы ` % с `. `% С ` является недействительным
Error MySQL: 1605
ER_EVENT_INVALID_CREATION_CTX
Creation context of event `%s`.`%s` is invalid
Контекст Создание событий `% с `. `% С ` является недействительным
Error MySQL: 1606
ER_TRG_CANT_OPEN_TABLE
Cannot open table for trigger `%s`.`%s`
Не могу открыть стол для запуска `% ов `. `% С `
Error MySQL: 1607
ER_CANT_CREATE_SROUTINE
Cannot create stored routine `%s`. Check warnings
Невозможно создать хранимую рутинной ` %s `.
Error MySQL: 1608
ER_SLAVE_AMBIGOUS_EXEC_MODE
Ambiguous slave modes combination. %s
Неоднозначное ведомом режимах комбинации.
Error MySQL: 1608
ER_NEVER_USED
Ambiguous slave modes combination. %s
Неоднозначное ведомом режимах комбинации.
Error MySQL: 1609
ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT
The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.
Двоичный утверждение типа `% ов ` не предшествовала Описание формата Двоичный заявлении.
Error MySQL: 1610
ER_SLAVE_CORRUPT_EVENT
Corrupted replication event was detected
Поврежденный событие репликации был обнаружен
Error MySQL: 1611
ER_LOAD_DATA_INVALID_COLUMN
Invalid column reference (%s) in LOAD DATA
Ссылка Неверный колонка ( %s) в LOAD DATA
Error MySQL: 1612
ER_LOG_PURGE_NO_FILE
Being purged log %s was not found
Будучи очищены журнал %s не найден
Error MySQL: 1613
ER_XA_RBTIMEOUT
XA_RBTIMEOUT: Transaction branch was rolled back: took too long
XA_RBTIMEOUT : филиал сделка откат : занимает слишком много времени
Error MySQL: 1614
ER_XA_RBDEADLOCK
XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
XA_RBDEADLOCK : филиал сделка откат : тупик был обнаружен
Error MySQL: 1615
ER_NEED_REPREPARE
Prepared statement needs to be re-prepared
Подготовлено заявление должно быть повторно подготовлен
Error MySQL: 1616
ER_DELAYED_NOT_SUPPORTED
DELAYED option not supported for table ‘%s’
ЗАДЕРЖАН вариант не поддерживается для таблицы «%s ‘
Error MySQL: 1617
WARN_NO_MASTER_INFO
The master info structure does not exist
Мастер информационная структура не существует
Error MySQL: 1618
WARN_OPTION_IGNORED
<%s> option ignored
u003c с % u003e опция игнорируется
Error MySQL: 1619
WARN_PLUGIN_DELETE_BUILTIN
Built-in plugins cannot be deleted
Встроенные плагины не могут быть удалены
Error MySQL: 1620
WARN_PLUGIN_BUSY
Plugin is busy and will be uninstalled on shutdown
Плагин занят и будет удалена при завершении работы
Error MySQL: 1621
ER_VARIABLE_IS_READONLY
%s variable ‘%s’ is read-only. Use SET %s to assign the value
%s переменная ‘ %s’ только для чтения.
Error MySQL: 1622
ER_WARN_ENGINE_TRANSACTION_ROLLBACK
Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted
Хранение двигателя % с браузер не поддерживает откат для этого заявления.
Error MySQL: 1623
ER_SLAVE_HEARTBEAT_FAILURE
Unexpected master’s heartbeat data: %s
Данные сердцебиение Нечаянная мастера : % с
Error MySQL: 1624
ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE
The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).
Запрашиваемая значение для периода сердечных сокращений либо отрицательный или превышает максимально допустимое ( %s секунды ).
Error MySQL: 1625
ER_NDB_REPLICATION_SCHEMA_ERROR
Bad schema for mysql.ndb_replication table. %s
Плохой схемы для mysql.ndb_replication таблице.
Error MySQL: 1626
ER_CONFLICT_FN_PARSE_ERROR
Error in parsing conflict function. %s
Ошибка при разборе функцию конфликта.
Error MySQL: 1627
ER_EXCEPTIONS_WRITE_ERROR
Write to exceptions table failed. %s»
Пишите исключений таблице не удалось.
Error MySQL: 1628
ER_TOO_LONG_TABLE_COMMENT
Comment for table ‘%s’ is too long (max = %lu)
Комментарий для таблицы «%s ‘ слишком длинный (макс. = % лу )
Error MySQL: 1629
ER_TOO_LONG_FIELD_COMMENT
Comment for field ‘%s’ is too long (max = %lu)
Комментарий для поля ‘%s’ слишком длинный (макс. = % лу )
Error MySQL: 1630
ER_FUNC_INEXISTENT_NAME_COLLISION
FUNCTION %s does not exist. Check the ‘Function Name Parsing and Resolution’ section in the Reference Manual
ФУНКЦИИ % с не существует.
Error MySQL: 1631
ER_DATABASE_NAME
Database
база данных
Error MySQL: 1632
ER_TABLE_NAME
Table
стол
Error MySQL: 1633
ER_PARTITION_NAME
Partition
раздел
Error MySQL: 1634
ER_SUBPARTITION_NAME
Subpartition
подразделу
Error MySQL: 1635
ER_TEMPORARY_NAME
Temporary
временный
Error MySQL: 1636
ER_RENAMED_NAME
Renamed
переименованный
Error MySQL: 1637
ER_TOO_MANY_CONCURRENT_TRXS
Too many active concurrent transactions
Слишком много активных параллельные транзакции
Error MySQL: 1638
WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED
Non-ASCII separator arguments are not fully supported
Аргументы сепаратор не-ASCII поддерживаются не полностью
Error MySQL: 1639
ER_DEBUG_SYNC_TIMEOUT
debug sync point wait timed out
точка отладки синхронизации ожидание истекло
Error MySQL: 1640
ER_DEBUG_SYNC_HIT_LIMIT
debug sync point hit limit reached
точка отладки синхронизации хит Достигнут предел
Error MySQL: 1641
ER_DUP_SIGNAL_SET
Duplicate condition information item ‘%s’
Дублировать состояние информационного элемента ‘%s’
Error MySQL: 1642
ER_SIGNAL_WARN
Unhandled user-defined warning condition
Неизвестное определяемые пользователем условие предупреждение
Error MySQL: 1643
ER_SIGNAL_NOT_FOUND
Unhandled user-defined not found condition
Неизвестное определяемые пользователем не найден состояние
Error MySQL: 1644
ER_SIGNAL_EXCEPTION
Unhandled user-defined exception condition
Неизвестное определяемые пользователем состояние исключение
Error MySQL: 1645
ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER
RESIGNAL when handler not active
RESIGNAL когда обработчик не активен
Error MySQL: 1646
ER_SIGNAL_BAD_CONDITION_TYPE
SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE
СИГНАЛ / RESIGNAL можно использовать только состояние, определяемое с SQLSTATE
Error MySQL: 1647
WARN_COND_ITEM_TRUNCATED
Data truncated for condition item ‘%s’
Данные усечены для Состояние ‘%s’
Error MySQL: 1648
ER_COND_ITEM_TOO_LONG
Data too long for condition item ‘%s’
Данные слишком долго для Состояние ‘%s’
Error MySQL: 1649
ER_UNKNOWN_LOCALE
Unknown locale: ‘%s’
Неизвестно Язык: ‘%s’
Error MySQL: 1650
ER_SLAVE_IGNORE_SERVER_IDS
The requested server id %d clashes with the slave startup option —replicate-same-server-id
Запрашиваемая идентификатор сервера %d столкновения с параметром запуска раб — повторить — же — сервера идентификатор
Error MySQL: 1651
ER_QUERY_CACHE_DISABLED
Query cache is disabled; restart the server with query_cache_type=1 to enable it
Кэш запросов отключена;
Error MySQL: 1652
ER_SAME_NAME_PARTITION_FIELD
Duplicate partition field name ‘%s’
Дублирование разделов имя поля ‘%s’
Error MySQL: 1653
ER_PARTITION_COLUMN_LIST_ERROR
Inconsistency in usage of column lists for partitioning
Непоследовательность в использовании списков столбцов для разделения
Error MySQL: 1654
ER_WRONG_TYPE_COLUMN_VALUE_ERROR
Partition column values of incorrect type
Перегородки значения столбцов из неправильного типа
Error MySQL: 1655
ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR
Too many fields in ‘%s’
Слишком много полей в ‘%s’
Error MySQL: 1656
ER_MAXVALUE_IN_VALUES_IN
Cannot use MAXVALUE as value in VALUES IN
Нельзя использовать MAXVALUE как значение значений в
Error MySQL: 1657
ER_TOO_MANY_VALUES_ERROR
Cannot have more than one value for this type of %s partitioning
Не может иметь более одного значения для этого типа секционирования %s
Error MySQL: 1658
ER_ROW_SINGLE_PARTITION_FIELD_ERROR
Row expressions in VALUES IN only allowed for multi-field column partitioning
Выражения Row значений в только разрешенных для разделения столбца многопрофильной
Error MySQL: 1659
ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD
Field ‘%s’ is of a not allowed type for this type of partitioning
Поле ‘ %s’ имеет не допускается типа для этого типа разделов
Error MySQL: 1660
ER_PARTITION_FIELDS_TOO_LONG
The total length of the partitioning fields is too large
Общая длина полей разделения слишком велик
Error MySQL: 1661
ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.
Невозможно выполнить заявление: нельзя писать в двоичный журнал, поскольку обе строки — не в состоянии двигатели и заявление — неспособным двигатели участвуют.
Error MySQL: 1662
ER_BINLOG_ROW_MODE_AND_STMT_ENGINE
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.
Невозможно выполнить заявление: нельзя писать в двоичный журнал с BINLOG_FORMAT = СТРОКА и по крайней мере одна таблица использует механизм хранения ограничивается заявление на основе регистрации.
Error MySQL: 1663
ER_BINLOG_UNSAFE_AND_STMT_ENGINE
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. %s
Невозможно выполнить заявление: нельзя писать в двоичный журнал с заявлением небезопасно, механизм хранения ограничивается заявление на основе регистрации, и BINLOG_FORMAT = MIXED.
Error MySQL: 1664
ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE
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 MySQL: 1665
ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
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.%s
Невозможно выполнить заявление: нельзя писать в двоичный журнал с BINLOG_FORMAT = ЗАЯВЛЕНИЕ и по крайней мере одна таблица использует механизм хранения ограничен грести на основе рубок % с.
Error MySQL: 1666
ER_BINLOG_ROW_INJECTION_AND_STMT_MODE
Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.
Невозможно выполнить заявление: нельзя писать в двоичный журнал с заявлением в формате строк и BINLOG_FORMAT = ЗАЯВЛЕНИЕ.
Error MySQL: 1667
ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
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 MySQL: 1668
ER_BINLOG_UNSAFE_LIMIT
The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.
В заявлении небезопасно, поскольку он использует оговорку предел.
Error MySQL: 1669
ER_BINLOG_UNSAFE_INSERT_DELAYED
The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.
В заявлении небезопасно, поскольку он использует INSERT DELAYED.
Error MySQL: 1670
ER_BINLOG_UNSAFE_SYSTEM_TABLE
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.
В заявлении небезопасно, поскольку он использует общий журнал, журнал медленных запросов или performance_schema таблицу (ы).
Error MySQL: 1671
ER_BINLOG_UNSAFE_AUTOINC_COLUMNS
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.
О себе небезопасно, потому что это вызывает триггер или хранимую функцию, которая вставляет в столбец AUTO_INCREMENT.
Error MySQL: 1672
ER_BINLOG_UNSAFE_UDF
Statement is unsafe because it uses a UDF which may not return the same value on the slave.
О себе небезопасно, поскольку он использует UDF, которые не могут вернуться и то же значение на раб.
Error MySQL: 1673
ER_BINLOG_UNSAFE_SYSTEM_VARIABLE
Statement is unsafe because it uses a system variable that may have a different value on the slave.
О себе небезопасно, поскольку он использует системную переменную, которая может иметь различное значение на раба.
Error MySQL: 1674
ER_BINLOG_UNSAFE_SYSTEM_FUNCTION
Statement is unsafe because it uses a system function that may return a different value on the slave.
О себе небезопасно, поскольку он использует системную функцию, которая может вернуть другое значение на раб.
Error MySQL: 1675
ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS
Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.
О себе небезопасно, потому что обращается к таблице нетранзакционных после доступа к таблице транзакций в рамках одной транзакции.
Error MySQL: 1676
ER_MESSAGE_AND_STATEMENT
%s Statement: %s
% с себе : % с
Error MySQL: 1677
ER_SLAVE_CONVERSION_FAILED
Column %d of table ‘%s.%s’ cannot be converted from type ‘%s’ to type ‘%s’
Колонка %d из таблицы «%s. % С ‘не может быть преобразован из типа»%s ‘ ввести ‘%s’
Error MySQL: 1678
ER_SLAVE_CANT_CREATE_CONVERSION
Can’t create conversion table for table ‘%s.%s’
Невозможно создать таблицу преобразования для таблицы «% с. % С ‘
Error MySQL: 1679
ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT
Cannot modify @@session.binlog_format inside a transaction
Невозможно изменить @ @ session.binlog_format внутри транзакции
Error MySQL: 1680
ER_PATH_LENGTH
The path specified for %s is too long.
Путь, указанный для % с слишком длинный.
Error MySQL: 1681
ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
%s’ is deprecated and will be removed in a future release.
% с ‘ устарела и будет удалена в будущих версиях.
Error MySQL: 1682
ER_WRONG_NATIVE_TABLE_STRUCTURE
Native table ‘%s’.’%s’ has the wrong structure
Родной таблица «%s ‘.’ %s ‘ имеет неправильную структуру
Error MySQL: 1683
ER_WRONG_PERFSCHEMA_USAGE
Invalid performance_schema usage.
Недопустимое использование performance_schema.
Error MySQL: 1684
ER_WARN_I_S_SKIPPED_TABLE
Table ‘%s’.’%s’ was skipped since its definition is being modified by concurrent DDL statement
Таблица «%s ‘.’ %s ‘ был пропущен, поскольку ее определение вносятся изменения одновременным заявлением DDL
Error MySQL: 1685
ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT
Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction
Невозможно изменить @ @ session.binlog_direct_non_transactional_updates внутри транзакции
Error MySQL: 1686
ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT
Cannot change the binlog direct flag inside a stored function or trigger
Невозможно изменить Двоичный прямой флаг внутри хранимой функции или триггера
Error MySQL: 1687
ER_SPATIAL_MUST_HAVE_GEOM_COL
A SPATIAL index may only contain a geometrical type column
Пространственный индекс может содержать только столбец геометрическая типа
Error MySQL: 1688
ER_TOO_LONG_INDEX_COMMENT
Comment for index ‘%s’ is too long (max = %lu)
Комментарий для индекса » %s ‘ слишком длинный (макс. = % лу )
Error MySQL: 1689
ER_LOCK_ABORTED
Wait on a lock was aborted due to a pending exclusive lock
Ожидание блокировки была прервана из-за отложенного исключительной блокировки
Error MySQL: 1690
ER_DATA_OUT_OF_RANGE
%s value is out of range in ‘%s’
Значение %s находится вне диапазона в ‘%s’
Error MySQL: 1691
ER_WRONG_SPVAR_TYPE_IN_LIMIT
A variable of a non-integer based type in LIMIT clause
Переменная типа не целое, основанной в пункте LIMIT
Error MySQL: 1692
ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
Mixing self-logging and non-self-logging engines in a statement is unsafe.
Смешивание собственного рубками и несамоходных протоколирования двигатели в заявлении небезопасно.
Error MySQL: 1693
ER_BINLOG_UNSAFE_MIXED_STATEMENT
Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
О себе доступ нетранзактных стол, а также транзакций или временную таблицу, и записывает в любой из них.
Error MySQL: 1694
ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN
Cannot modify @@session.sql_log_bin inside a transaction
Невозможно изменить @ @ session.sql_log_bin внутри транзакции
Error MySQL: 1695
ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN
Cannot change the sql_log_bin inside a stored function or trigger
Невозможно изменить SQL_LOG_BIN внутри хранимой функции или триггера
Error MySQL: 1696
ER_FAILED_READ_FROM_PAR_FILE
Failed to read from the .par file
Не удалось прочитать из номинальной файле.
Error MySQL: 1697
ER_VALUES_IS_NOT_INT_TYPE_ERROR
VALUES value for partition ‘%s’ must have type INT
Значение значения для раздела ‘%s’ должно иметь тип INT
Error MySQL: 1698
ER_ACCESS_DENIED_NO_PASSWORD_ERROR
Access denied for user ‘%s’@’%s’
Доступ закрыт для пользователя ‘ %s ‘ @ ’ %s ‘
Error MySQL: 1699
ER_SET_PASSWORD_AUTH_PLUGIN
SET PASSWORD has no significance for users authenticating via plugins
Установить пароль не имеет никакого значения для пользователей аутентификации через плагины
Error MySQL: 1700
ER_GRANT_PLUGIN_USER_EXISTS
GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists
ГРАНТ с отождествляется с незаконно, так как пользователь % -. * Ы уже существует
Error MySQL: 1701
ER_TRUNCATE_ILLEGAL_FK
Cannot truncate a table referenced in a foreign key constraint (%s)
Невозможно усечь таблицу ссылается ключевого ограничения ( %s) иностранной
Error MySQL: 1702
ER_PLUGIN_IS_PERMANENT
Plugin ‘%s’ is force_plus_permanent and can not be unloaded
Плагин ‘%s’ является force_plus_permanent и не может быть выгружен
Error MySQL: 1703
ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN
The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.
Запрашиваемая значение для периода сердечных сокращений меньше 1 миллисекунды.
Error MySQL: 1704
ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX
The requested value for the heartbeat period exceeds the value of `slave_net_timeout’ seconds. A sensible value for the period should be less than the timeout.
Запрашиваемая значение для периода сердечных сокращений превышает стоимость ` slave_net_timeout » секунд.
Error MySQL: 1705
ER_STMT_CACHE_FULL
Multi-row statements required more than ‘max_binlog_stmt_cache_size’ bytes of storage; increase this mysqld variable and try again
Заявления Многорядные требуется больше, чем » max_binlog_stmt_cache_size ‘ байт хранения;
Error MySQL: 1706
ER_MULTI_UPDATE_KEY_CONFLICT
Primary key/partition key update is not allowed since the table is updated both as ‘%s’ and ‘%s’.
Первичный ключ / раздел обновления ключа не допускается, так как таблица обновляется и как «%s ‘и’%s ‘.
Error MySQL: 1707
ER_TABLE_NEEDS_REBUILD
Table rebuild required. Please do «ALTER TABLE `%s` FORCE» or dump/reload to fix it!
Таблица восстановить требуется.
Error MySQL: 1708
WARN_OPTION_BELOW_LIMIT
The value of ‘%s’ should be no less than the value of ‘%s’
Значение ‘%s’ не должно быть меньше, чем значение ‘%s’
Error MySQL: 1709
ER_INDEX_COLUMN_TOO_LONG
Index column size too large. The maximum column size is %lu bytes.
Размер индекса столбец слишком велик.
Error MySQL: 1710
ER_ERROR_IN_TRIGGER_BODY
Trigger ‘%s’ has an error in its body: ‘%s’
Триггер «%s ‘ имеет ошибку в своем теле : ‘%s ‘
Error MySQL: 1711
ER_ERROR_IN_UNKNOWN_TRIGGER_BODY
Unknown trigger has an error in its body: ‘%s’
Неизвестный триггер имеет ошибку в своем теле : ‘%s’
Error MySQL: 1712
ER_INDEX_CORRUPT
Index %s is corrupted
Индекс % с поврежден
Error MySQL: 1713
ER_UNDO_RECORD_TOO_BIG
Undo log record is too big.
Отменить запись журнала является слишком большой.
Error MySQL: 1714
ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT
INSERT IGNORE… SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
INSERT IGNORE… SELECT небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строки игнорируются.
Error MySQL: 1715
ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE
INSERT… SELECT… ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.
INSERT… SELECT… НА дубликат ключа UPDATE небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строки обновляются.
Error MySQL: 1716
ER_BINLOG_UNSAFE_REPLACE_SELECT
REPLACE… SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
ЗАМЕНА… ВЫБОР небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строк будут заменены.
Error MySQL: 1717
ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT
CREATE… IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
СОЗДАТЬ… IGNORE ВЫБОР небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строки игнорируются.
Error MySQL: 1718
ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT
CREATE… REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.
СОЗДАТЬ… Replace Select небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строк будут заменены.
Error MySQL: 1719
ER_BINLOG_UNSAFE_UPDATE_IGNORE
UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.
UPDATE IGNORE небезопасно, потому что порядок, в котором строки обновляются определяет, какие ( если таковые имеются) строки игнорируются.
Error MySQL: 1720
ER_PLUGIN_NO_UNINSTALL
Plugin ‘%s’ is marked as not dynamically uninstallable. You have to stop the server to uninstall it.
Плагин ‘%s’ помечен как не динамически невозможно установить.
Error MySQL: 1721
ER_PLUGIN_NO_INSTALL
Plugin ‘%s’ is marked as not dynamically installable. You have to stop the server to install it.
Плагин ‘%s’ помечен как не динамически устанавливаемый.
Error MySQL: 1722
ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT
Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.
Заявления писать в таблицу со столбцом автоинкрементного после выбора из другой таблицы являются небезопасными, потому что порядок, в котором строки извлекаются определяет, какие ( если таковые имеются) строки будут написаны.
Error MySQL: 1723
ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC
CREATE TABLE… SELECT… on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.
CREATE TABLE… SELECT… на столе с колонки автоинкрементного небезопасно, потому что порядок, в котором строки извлекаются в зависимости от выбранного ( если таковые имеются) строки вставляются.
Error MySQL: 1724
ER_BINLOG_UNSAFE_INSERT_TWO_KEYS
INSERT… ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe
INSERT… ON дубликат ключа UPDATE в таблице с более чем одной уникальный ключ небезопасно
Error MySQL: 1725
ER_TABLE_IN_FK_CHECK
Table is being used in foreign key check.
Таблица используется в проверке внешнего ключа.
Error MySQL: 1726
ER_UNSUPPORTED_ENGINE
Storage engine ‘%s’ does not support system tables. [%s.%s]
Двигатель хранения «%s ‘не поддерживает системные таблицы.
Error MySQL: 1727
ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST
INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.
Вставьте в автоинкремент области, которая не является первая часть в первичный ключ состоит небезопасно.
Error MySQL: 2000
CR_UNKNOWN_ERROR
Unknown MySQL error
Неизвестная ошибка MySQL
Error MySQL: 2001
CR_SOCKET_CREATE_ERROR
Can’t create UNIX socket (%d)
Невозможно создать сокет UNIX ( %d)
Error MySQL: 2002
CR_CONNECTION_ERROR
Can’t connect to local MySQL server through socket ‘%s’ (%d)
Не удается подключиться к локальному серверу MySQL через сокет ‘%s’ ( %d)
Error MySQL: 2003
CR_CONN_HOST_ERROR
Can’t connect to MySQL server on ‘%s’ (%d)
Не удается подключиться к серверу MySQL на ‘%s’ ( %d)
Error MySQL: 2004
CR_IPSOCK_ERROR
Can’t create TCP/IP socket (%d)
Не удается создать TCP / IP сокет ( %d)
Error MySQL: 2005
CR_UNKNOWN_HOST
Unknown MySQL server host ‘%s’ (%d)
Сервер Неизвестный MySQL хост ‘%s’ ( %d)
Error MySQL: 2006
CR_SERVER_GONE_ERROR
MySQL server has gone away
Сервер MySQL ушел
Error MySQL: 2007
CR_VERSION_ERROR
Protocol mismatch; server version = %d, client version = %d
Протокол несоответствие;
Error MySQL: 2008
CR_OUT_OF_MEMORY
MySQL client ran out of memory
Клиент MySQL не хватило памяти
Error MySQL: 2009
CR_WRONG_HOST_INFO
Wrong host info
Неправильный Информация хозяин
Error MySQL: 2010
CR_LOCALHOST_CONNECTION
Localhost via UNIX socket
LocalHost через гнездо UNIX
Error MySQL: 2011
CR_TCP_CONNECTION
%s via TCP/IP
% с помощью TCP / IP
Error MySQL: 2012
CR_SERVER_HANDSHAKE_ERR
Error in server handshake
Ошибка в серверной рукопожатия
Error MySQL: 2013
CR_SERVER_LOST
Lost connection to MySQL server during query
Потеряно соединение с сервером MySQL во время запроса
Error MySQL: 2014
CR_COMMANDS_OUT_OF_SYNC
Commands out of sync; you can’t run this command now
Команды из синхронизации;
Error MySQL: 2015
CR_NAMEDPIPE_CONNECTION
Named pipe: %s
Названный трубы: % с
Error MySQL: 2016
CR_NAMEDPIPEWAIT_ERROR
Can’t wait for named pipe to host: %s pipe: %s (%lu)
Не могу дождаться именованного канала для размещения : % с трубы: % с ( % лу )
Error MySQL: 2017
CR_NAMEDPIPEOPEN_ERROR
Can’t open named pipe to host: %s pipe: %s (%lu)
Не могу открыть назвал трубу для размещения :%s трубу :%s ( % LU)
Error MySQL: 2018
CR_NAMEDPIPESETSTATE_ERROR
Can’t set state of named pipe to host: %s pipe: %s (%lu)
Невозможно установить состояние именованного канала для размещения : % с трубы: % с ( % лу )
Error MySQL: 2019
CR_CANT_READ_CHARSET
Can’t initialize character set %s (path: %s)
Невозможно инициализировать набор символов %s (путь : %s)
Error MySQL: 2020
CR_NET_PACKET_TOO_LARGE
Got packet bigger than ‘max_allowed_packet’ bytes
Получил пакет больше, чем ‘ max_allowed_packet ‘ байт
Error MySQL: 2021
CR_EMBEDDED_CONNECTION
Embedded server
Встроенный сервер
Error MySQL: 2022
CR_PROBE_SLAVE_STATUS
Error on SHOW SLAVE STATUS:
Ошибка на SHOW SLAVE STATUS :
Error MySQL: 2023
CR_PROBE_SLAVE_HOSTS
Error on SHOW SLAVE HOSTS:
Ошибка на SHOW SLAVE HOSTS :
Error MySQL: 2024
CR_PROBE_SLAVE_CONNECT
Error connecting to slave:
Ошибка соединения с раба :
Error MySQL: 2025
CR_PROBE_MASTER_CONNECT
Error connecting to master:
Ошибка соединения с мастером :
Error MySQL: 2026
CR_SSL_CONNECTION_ERROR
SSL connection Error MySQL: %s
Ошибка подключения SSL : % с
Error MySQL: 2027
CR_MALFORMED_PACKET
Malformed packet
сформированный пакет
Error MySQL: 2028
CR_WRONG_LICENSE
This client library is licensed only for use with MySQL servers having ‘%s’ license
Этот клиент библиотека предоставляется только для работы с серверами MySQL, имеющих ‘%s’ лицензию
Error MySQL: 2029
CR_NULL_POINTER
Invalid use of null pointer
Неправильное использование нулевого указателя
Error MySQL: 2030
CR_NO_PREPARE_STMT
Statement not prepared
О себе не готовы
Error MySQL: 2031
CR_PARAMS_NOT_BOUND
No data supplied for parameters in prepared statement
Нет данных, поставляемые для параметров в подготовленном заявлении
Error MySQL: 2032
CR_DATA_TRUNCATED
Data truncated
данные усеченной
Error MySQL: 2033
CR_NO_PARAMETERS_EXISTS
No parameters exist in the statement
Параметры не существуют в заявлении
Error MySQL: 2034
CR_INVALID_PARAMETER_NO
Invalid parameter number
Неверный номер параметра
Error MySQL: 2035
CR_INVALID_BUFFER_USE
Can’t send long data for non-string/non-binary data types (parameter: %d)
Не удается отправить длинные данные для non-string/non-binary типов данных (параметр : %d)
Error MySQL: 2036
CR_UNSUPPORTED_PARAM_TYPE
Using unsupported buffer type: %d (parameter: %d)
Использование неподдерживаемый тип буфера : %d (параметр : %d)
Error MySQL: 2037
CR_SHARED_MEMORY_CONNECTION
Shared memory: %s
Общая память : % с
Error MySQL: 2038
CR_SHARED_MEMORY_CONNECT_REQUEST_ERROR
Can’t open shared memory; client could not create request event (%lu)
Не удается открыть общую память;
Error MySQL: 2039
CR_SHARED_MEMORY_CONNECT_ANSWER_ERROR
Can’t open shared memory; no answer event received from server (%lu)
Не удается открыть общую память;
Error MySQL: 2040
CR_SHARED_MEMORY_CONNECT_FILE_MAP_ERROR
Can’t open shared memory; server could not allocate file mapping (%lu)
Не удается открыть общую память;
Error MySQL: 2041
CR_SHARED_MEMORY_CONNECT_MAP_ERROR
Can’t open shared memory; server could not get pointer to file mapping (%lu)
Не удается открыть общую память;
Error MySQL: 2042
CR_SHARED_MEMORY_FILE_MAP_ERROR
Can’t open shared memory; client could not allocate file mapping (%lu)
Не удается открыть общую память;
Error MySQL: 2043
CR_SHARED_MEMORY_MAP_ERROR
Can’t open shared memory; client could not get pointer to file mapping (%lu)
Не удается открыть общую память;
Error MySQL: 2044
CR_SHARED_MEMORY_EVENT_ERROR
Can’t open shared memory; client could not create %s event (%lu)
Не удается открыть общую память;
Error MySQL: 2045
CR_SHARED_MEMORY_CONNECT_ABANDONED_ERROR
Can’t open shared memory; no answer from server (%lu)
Не удается открыть общую память;
Error MySQL: 2046
CR_SHARED_MEMORY_CONNECT_SET_ERROR
Can’t open shared memory; cannot send request event to server (%lu)
Не удается открыть общую память;
Error MySQL: 2047
CR_CONN_UNKNOW_PROTOCOL
Wrong or unknown protocol
Неверный или неизвестный протокол
Error MySQL: 2048
CR_INVALID_CONN_HANDLE
Invalid connection handle
Неверный дескриптор соединения
Error MySQL: 2049
CR_SECURE_AUTH
Connection using old (pre-4.1.1) authentication protocol refused (client option ‘secure_auth’ enabled)
Соединения, используя старые (до 4.1.1 ) протокол аутентификации отказался (опция клиент ‘ secure_auth ‘ включен )
Error MySQL: 2050
CR_FETCH_CANCELED
Row retrieval was canceled by mysql_stmt_close() call
Поиск строк был отменен призыв mysql_stmt_close ( )
Error MySQL: 2051
CR_NO_DATA
Attempt to read column without prior row fetch
Попытка прочитать колонку без предварительного подряд выборки
Error MySQL: 2052
CR_NO_STMT_METADATA
Prepared statement contains no metadata
Подготовлено заявление не содержит метаданные
Error MySQL: 2053
CR_NO_RESULT_SET
Attempt to read a row while there is no result set associated with the statement
Попытка прочитать строку в то время как нет результирующий набор, связанный с инструкцией
Error MySQL: 2054
CR_NOT_IMPLEMENTED
This feature is not implemented yet
Эта функция пока не реализована
Error MySQL: 2055
CR_SERVER_LOST_EXTENDED
Lost connection to MySQL server at ‘%s’, system Error MySQL: %d
Потеряно соединение с сервером MySQL на ‘%s’, системной ошибки : %d
Error MySQL: 2056
CR_STMT_CLOSED
Statement closed indirectly because of a preceeding %s() call
Заявление закрыт косвенно из-за звонка предшествующих % с ( )
Error MySQL: 2057
CR_NEW_STMT_METADATA
The number of columns in the result set differs from the number of bound buffers. You must reset the statement, rebind the result set columns, and execute the statement again
Столбцов в результирующем наборе отличается от числа связанных буферов.
Error MySQL: 2058
CR_ALREADY_CONNECTED
This handle is already connected. Use a separate handle for each connection.
Эта ручка уже подключен.
Error MySQL: 2059
CR_AUTH_PLUGIN_CANNOT_LOAD
Authentication plugin ‘%s’ cannot be loaded: %s
Плагин аутентификации ‘%s’ не может быть загружен : % с