config root man

Current Path : /usr/local/share/mysql/norwegian-ny/

FreeBSD hs32.drive.ne.jp 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Wed Jan 14 12:18:08 JST 2015 root@hs32.drive.ne.jp:/sys/amd64/compile/hs32 amd64
Upload File :
Current File : //usr/local/share/mysql/norwegian-ny/errmsg.sys

þþeáH}²î+vÃðMx›Éø)^˜Ô8d¡Ô÷	5Y•·ÚMg±
OtŽºÕ&n‚’·Ð÷	C	^	ƒ	¬	Ë	
2
V
}
¦
Ê
ù
+Nq‘Æÿ8k¯ú,
l
ƒ
¦
¿
ö
r±Pu°Ç8„Áé+?]sžÐBw—µWc{£Çç.w›¶Ö®#d°Íø=t¾ ]¾(V…A]w–Jã?n’æ@ƒ£â@ZsœÇñF~´ïG g š Ô !U!°!Ö!ý!5"›"È"Ù"#C#^#{#š#¹#$K$n$¤$À$Þ$ú$-%Œ%­%è%0&n&ó&A''à'D(z(Æ(õ(,)b)¨)ë)0*J**É*+A+c+š+ß+,*,S,p,®,ï,0-T-–-×-!.j.™.Ñ.þ.*/L/{/Ç/
000b00´0Õ0161U1z1 1Ì1ö162›2É2ü2343£3»3474]4Š4Ö465m5—5¾5ÿ5.6q6¸6å697U7ö7|8Ñ89Ñ9:-:N:Ž:¿:Û:H;b;‡;»;<^<“<¿<8=e=ª=Ê=ô=>O>t>¸>ä>?.?C?X?o??¡?¼?ã?@D@k@Ì@CAcA A¸A×AøAB;BPBgBzB’B¶BêBCC1CFC\CzCªCðCD?DfD’DÉDEBEŠEÀEÚEûE0FUF„F·FøFFGŽGHJH|H“HªHØHI(ITIbI¢IÑIJ(JmJJÅJêJK=KOKlK–KµKàKLKL]LL¼LçL+MNMdM–M»MÕM!NcN‘N²NÉNO[O–OóO%P{P°PãPQQdQ QÐQR=RjRÍRúR>SüSÁTTUÎUöU@VŒVÅVWJW™WëWXzXÙX?Y‡YÅYÝYiZZ­ZèZ[4[¿[\²\ò\]’]à]	^C^‘^Û^_Ò_`x`å`aJazaÉaóa(b\b‰b³bëbõbÿb@czcÇcìcdd®dÐdeYehashchkisamchkNEIJAKan ikkje opprette fila '%-.200s' (Feilkode: %d)Kan ikkje opprette tabellen '%-.200s' (Feilkode: %d)Kan ikkje opprette databasen '%-.64s' (Feilkode: %d)Kan ikkje opprette databasen '%-.64s'; databasen eksistererKan ikkje fjerne (drop) '%-.64s'; databasen eksisterer ikkjeFeil ved fjerning (drop) av databasen (kan ikkje slette '%-.64s', feil %d)Feil ved sletting av database (kan ikkje slette katalogen '%-.64s', feil %d)Feil ved sletting av '%-.64s' (Feilkode: %d)Kan ikkje lese posten i systemkatalogenKan ikkje lese statusen til '%-.200s' (Feilkode: %d)Kan ikkje lese aktiv katalog(Feilkode: %d)Kan ikkje låse fila (Feilkode: %d)Kan ikkje åpne fila: '%-.200s' (Feilkode: %d)Kan ikkje finne fila: '%-.200s' (Feilkode: %d)Kan ikkje lese katalogen '%-.64s' (Feilkode: %d)Kan ikkje skifte katalog til '%-.64s' (Feilkode: %d)Posten har vorte endra sidan den sist vart lesen '%-.64s'Ikkje meir diskplass (%s). Ventar på å få frigjort plass...Kan ikkje skrive, flere like nyklar i tabellen '%-.64s'Feil ved lukking av '%-.64s' (Feilkode: %d)Feil ved lesing av '%-.200s' (Feilkode: %d)Feil ved omdøyping av '%-.150s' til '%-.150s' (Feilkode: %d)Feil ved skriving av fila '%-.200s' (Feilkode: %d)'%-.64s' er låst mot oppdateringarSortering avbroteView '%-.64s' eksisterar ikkje for '%-.64s'Mottok feil %d fra tabell handterarTabell håndteraren for '%-.64s' har ikkje denne moglegheitaKan ikkje finne posten i '%-.64s'Feil informasjon i fila: '%-.200s'Tabellen '%-.200s' har feil i nykkelfila; prøv å reparere denGammel nykkelfil for tabellen '%-.64s'; reparer den!'%-.64s' er skrivetryggjaIkkje meir minne. Start på nytt tenesten og prøv igjen (trengte %d bytar)Ikkje meir sorteringsminne. Auk sorteringsminnet (sorteringsbffer storleik) for tenestenUventa slutt på fil (eof) ved lesing av fila '%-.64s' (Feilkode: %d)For mange tilkoplingar (connections)Tomt for tråd plass/minneKan ikkje få tak i vertsnavn for di adresseFeil handtrykk (handshake)Tilgang ikkje tillate for brukar: '%-.32s'@'%-.64s' til databasen '%-.64s' nektaTilgang ikke tillate for brukar: '%-.32s'@'%-.64s' (Brukar passord: %s)Ingen database valdUkjent kommandoKolonne '%-.64s' kan ikkje vere nullUkjent database '%-.64s'Tabellen '%-.64s' eksisterar allereideUkjent tabell '%-.100s'Kolonne: '%-.64s' i tabell %-.64s er ikkje eintydigTenar nedkopling er i gangUkjent felt '%-.64s' i tabell %-.64sBrukte '%-.64s' som ikkje var i group byKan ikkje gruppere på '%-.64s'Uttrykket har summer (sum) funksjoner og kolonner i same uttrykkKolonne telling stemmer verdi tellingIdentifikator '%-.100s' er for langFeltnamnet '%-.64s' eksisterte frå førNøkkelnamnet '%-.64s' eksisterte frå førLike verdiar '%-.64s' for nykkel %dFeil kolonne spesifikator for kolonne '%-.64s'%s attmed '%-.80s' på line %dFørespurnad var tomIkkje unikt tabell/alias: '%-.64s'Ugyldig standardverdi for '%-.64s'Fleire primærnyklar spesifisertFor mange nykler spesifisert. Maks %d nyklar tillattFor mange nykkeldelar spesifisert. Maks %d delar tillattSpesifisert nykkel var for lang. Maks nykkellengde er %dNykkel kolonne '%-.64s' eksiterar ikkje i tabellenBlob kolonne '%-.64s' kan ikkje brukast ved spesifikasjon av nyklarFor stor nykkellengde for felt '%-.64s' (maks = %lu). Bruk BLOB istadenforBare eitt auto felt kan være definert som nøkkel.%s: klar for tilkoblingar
Version: '%s'  socket: '%s'  port: %d%s: Normal nedkopling
%s: Oppdaga signal %d. Avsluttar!
%s: Nedkopling komplett
%s: Påtvinga avslutning av tråd %ld  brukar: '%-.32s'
Kan ikkje opprette IP socketTabellen '%-.64s' har ingen index som den som er brukt i CREATE INDEX. Oprett tabellen på nyttFelt skiljer argumenta er ikkje som venta, sjå dokumentasjonenEin kan ikkje bruke faste feltlengder med BLOB. Vennlisgt bruk 'fields terminated by'.Filen '%-.128s' må være i database-katalogen for å være lesbar for alleFilen '%-.200s' eksisterte allereidePoster: %ld  Fjerna: %ld  Hoppa over: %ld  Åtvaringar: %ldPoster: %ld  Like: %ldFeil delnykkel. Den brukte delnykkelen er ikkje ein streng eller den oppgitte lengda er lengre enn nykkellengdenEin kan ikkje slette alle felt med ALTER TABLE. Bruk DROP TABLE istadenfor.Kan ikkje DROP '%-.64s'. Undersøk om felt/nøkkel eksisterar.Postar: %ld  Like: %ld  Åtvaringar: %ldYou can't specify target table '%-.64s' for update in FROM clauseUkjent tråd id: %luDu er ikkje eigar av tråd %luIngen tabellar i brukFor mange tekststrengar felt %-.64s og SETKan ikkje lage unikt loggfilnavn %-.200s.(1-999)
Tabellen '%-.64s' var låst med READ lås og kan ikkje oppdaterastTabellen '%-.64s' var ikkje låst med LOCK TABLESBlob feltet '%-.64s' kan ikkje ha ein standard verdiUgyldig database namn '%-.100s'Ugyldig tabell namn '%-.100s'SELECT ville undersøkje for mange postar og ville sannsynligvis ta veldig lang tid. Undersøk WHERE klausulen og bruk SET SQL_BIG_SELECTS=1 om SELECTen er korrektUkjend feilUkjend prosedyre %-.64sFeil parameter tal til prosedyra %-.64sFeil parameter til prosedyra %-.64sUkjend tabell '%-.64s' i %-.32sFeltet '%-.64s' er spesifisert to gangarInvalid use of group functionTable '%-.64s' uses a extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.64s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow 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 BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld -O thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsColumn '%-.64s' is used with UNIQUE or INDEX but is not defined as NOT NULLCan't load function '%-.64s'Can't initialize function '%-.64s'; %-.80sNo paths allowed for shared libraryFunction '%-.64s' already existsCan't open shared library '%-.64s' (errno: %d %-.128s)Can't find function '%-.128s' in libraryFunction '%-.64s' is not definedHost '%-.64s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.64s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.64sInvalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.64s' on host '%-.64s'%-.16s command denied to user '%-.32s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.32s'@'%-.64s' for column '%-.64s' in table '%-.64s'Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used.The host or user argument to GRANT is too longTable '%-.64s.%-.64s' doesn't existThere is no such grant defined for user '%-.32s' on host '%-.64s' on table '%-.64s'The used command is not allowed with this MySQL versionSomething is wrong in your syntaxDelayed insert thread couldn't get requested lock for table %-.64sToo many delayed threads in useAborted connection %ld to db: '%-.64s' user: '%-.32s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.64s', because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.64s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.64s'BLOB column '%-.64s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY columnKey '%-.64s' doesn't exist in table '%-.64s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d during COMMITGot error %d during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %ld to db: '%-.64s' user: '%-.32s' host: '%-.64s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET MASTERFailed rebuilding the index of  dumped table '%-.64s'Error from master: '%-.64s'Net error reading from masterNet error writing to masterCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.64s' is marked as crashed and should be repairedTable '%-.64s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running slave; run STOP SLAVE firstThis operation requires a running slave; configure slave and do START SLAVEThe server is not configured as slave; fix in config file or with CHANGE MASTER TOCould not initialize master info structure; more error messages can be found in the MySQL error logCould not create slave thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.32s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to master: %-.128sError running query on master: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need the %-.128s privilege for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.64s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d: '%-.128s' from master when reading data from binary logSlave SQL thread ignored the query because of replicate-*-table rulesVariable '%-.64s' is a %s variableIncorrect foreign key definition for '%-.64s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.64s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Slave is already runningSlave already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corrupted%d line(s) were cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn was set to data type implicit default; NULL supplied for NOT NULL column '%s' at row %ldOut of range value adjusted for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'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 startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.64s%s%-.64s%s%-.64s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START SLAVE UNTILIt 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 restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.64s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown table engine '%s''%s' is deprecated; use '%s' insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.32s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.64s' columnThis command is not supported in the prepared statement protocol yetMottok feil %d '%-.100s' fra %sMottok temporary feil %d '%-.100s' fra %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignoredThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BINQuery execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubselect value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.64s' is too bigMalformed file type header in file '%-.64s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.64s' (line: '%-.64s')Unexpected end of file while skipping unknown parameter '%-.64s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.64s' has unknown type '%-.64s' in its header'%-.64s.%-.64s' is not %sColumn '%-.64s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.64s'View's SELECT and view's field list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.64s.%-.64s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.64s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.64s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.64s' at row %ldIllegal %s '%-.64s' value found during parsingCHECK OPTION on non-updatable view '%-.64s.%-.64s'CHECK OPTION failed '%-.64s.%-.64s'%-.16s command denied to user '%-.32s'@'%-.64s' for routine '%-.64s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.64s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.64s.%-.64s'Can not insert into join view '%-.64s.%-.64s' without fields listCan not delete from join view '%-.64s.%-.64s'Operation %s failed for '%.256s'XAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.32s' on host '%-.64s' on routine '%-.64s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections.
Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA 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 changesThis 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)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)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.64s.%-.64s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %lu specified for column '%-.64s'. Maximum is %d.Too big precision %lu specified for column '%-.64s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.64s').You can't combine write-locking of system '%-.64s.%-.64s' table with other tablesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld -O thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.64s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.64s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.64s' prevents operation %.64s on table '%-.64s'.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 mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.64s'.'%-.64s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.64s'@'%-.64s' definerThere is no '%-.64s'@'%-.64s' registeredChanging schema from '%-.64s' to '%-.64s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.64s'.'%-.64s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.'%-.64s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.64sFailed to load routine %s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.64s'Table upgrade required. Please do "REPAIR TABLE `%-.32s`" to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.64s`.`%-.64s` contains view recursionnon-grouping field '%-.64s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedToo many active concurrent transactions

Man Man