Edit D:\chineseall_products\software\win-32bit\Mysql\share\french\errmsg.sys
? ?? J z ? ? ?x?? Er??L??K???"?s??3s??$R????G???? - F o ? ? ? ? 4 [ ? ? ? < ` o ? ? ? Z ? ? ? ( f ? ? ? Qy?u??7[? Az??'Y??Do?5Ea???8????8G?b?%P???+m?`?Y??? ? ? * ? ? Y ? J r ? # z ? ? !H!b!?!?!?!?!""K"?"?"?"e#?#?#$V$?$@%o%?%?%T&?&?&?&'3'N'k'?'?'(=(?(?(?(?(P)?)?) *i*?*?+?+7,?,F-?-?-$.F.?.?.;/?/?/?/a0?0?011?1?1?1"2K2h2?2?2(3L3?3?3.4w4?4?4 585Z5?5?56?6r6?6?6?67F7e7?7?7?78G8?8?8 9&9E9?9?9-:H:i:?:?:0;^;?;?;?; <b<?<?<*=F=?=m>?> ???@!@B@???=AYA??/B???\C???D@DrD??E<EQEfE{E????FBFgF?G??H1HPHqH????? I/IcI{I?????"JhJ??? KCK}K?L>LZL|L??M9MzM?N?? OO.O]O????)PYP??? QRQwQ????#RBRmR??? SIStS???#TITcT??%UDU[U??(V??WCWvW???3XcX???`Y???T[?a\??!]Z]??0^??_o_? `[`s`?%aBa~a??Vb?Lc??.d~d??Ke????6g?? hMh???2i_i????jPj???Uk??>l??mKm??nun??oyo?? pXp??qRq??rHr???Fsls??7t??u?uhu???>v??,wgw????wx%x[x? yyGyy?zXzpz????2{M{m{?|.|W|s|??&}e}????1???? ?R?k??$?????? ???????*???????????'??????? ???? ?????)?????,?????? ????????6?????????6??????-?????? ????,?????0???;???;???????0??????????$????1????#????8???? ???? ???????????????????5?????"??ashchk isamchk NON OUI Ne peut cr?er le fichier '%-.200s' (Errcode: %d) Ne peut cr?er la table '%-.200s' (Errcode: %d) Ne peut cr?er la base '%-.192s' (Erreur %d) Ne peut cr?er la base '%-.192s'; elle existe d?j? Ne peut effacer la base '%-.192s'; elle n'existe pas Ne peut effacer la base '%-.192s' (erreur %d) Erreur en effa?ant la base (rmdir '%-.192s', erreur %d) Erreur en effa?ant '%-.192s' (Errcode: %d) Ne peut lire un enregistrement de la table 'system' Ne peut obtenir le status de '%-.200s' (Errcode: %d) Ne peut obtenir le r?pertoire de travail (Errcode: %d) Ne peut verrouiller le fichier (Errcode: %d) Ne peut ouvrir le fichier: '%-.200s' (Errcode: %d) Ne peut trouver le fichier: '%-.200s' (Errcode: %d) Ne peut lire le r?pertoire de '%-.192s' (Errcode: %d) Ne peut changer le r?pertoire pour '%-.192s' (Errcode: %d) Enregistrement modifi? depuis sa derni?re lecture dans la table '%-.192s' Disque plein (%s). J'attend que quelqu'un lib?re de l'espace... Ecriture impossible, doublon dans une cl? de la table '%-.192s' Erreur a la fermeture de '%-.192s' (Errcode: %d) Erreur en lecture du fichier '%-.200s' (Errcode: %d) Erreur en renommant '%-.210s' en '%-.210s' (Errcode: %d) Erreur d'?criture du fichier '%-.200s' (Errcode: %d) '%-.192s' est verrouill? contre les modifications Tri alphab?tique abandonn? La vue (View) '%-.192s' n'existe pas pour '%-.192s' Re?u l'erreur %d du handler de la table Le handler de la table '%-.192s' n'a pas cette option Ne peut trouver l'enregistrement dans '%-.192s' Information erronn?e dans le fichier: '%-.200s' Index corrompu dans la table: '%-.200s'; essayez de le r?parer Vieux fichier d'index pour la table '%-.192s'; r?parez le! '%-.192s' est en lecture seulement Manque de m?moire. Red?marrez le d?mon et r?-essayez (%d octets n?cessaires) Manque de m?moire pour le tri. Augmentez-la. Fin de fichier inattendue en lisant '%-.192s' (Errcode: %d) Trop de connexions Manque de 'threads'/m?moire Ne peut obtenir de hostname pour votre adresse Mauvais 'handshake' Acc?s refus? pour l'utilisateur: '%-.48s'@'@%-.64s'. Base '%-.192s' Acc?s refus? pour l'utilisateur: '%-.48s'@'@%-.64s' (mot de passe: %s) Aucune base n'a ?t? s?lectionn?e Commande inconnue Le champ '%-.192s' ne peut ?tre vide (null) Base '%-.192s' inconnue La table '%-.192s' existe d?j? Table '%-.100s' inconnue Champ: '%-.192s' dans %-.192s est ambigu Arr?t du serveur en cours Champ '%-.192s' inconnu dans %-.192s '%-.192s' n'est pas dans 'group by' Ne peut regrouper '%-.192s' Vous demandez la fonction sum() et des champs dans la m?me commande Column count doesn't match value count Le nom de l'identificateur '%-.100s' est trop long Nom du champ '%-.192s' d?j? utilis? Nom de clef '%-.192s' d?j? utilis? Duplicata du champ '%-.192s' pour la clef %d Mauvais param?tre de champ pour le champ '%-.192s' %s pr?s de '%-.80s' ? la ligne %d Query est vide Table/alias: '%-.192s' non unique Valeur par d?faut invalide pour '%-.192s' Plusieurs clefs primaires d?finies Trop de clefs sont d?finies. Maximum de %d clefs allou? Trop de parties specifi?es dans la clef. Maximum de %d parties La cl? est trop longue. Longueur maximale: %d La cl? '%-.192s' n'existe pas dans la table Champ BLOB '%-.192s' ne peut ?tre utilis? dans une cl? Champ '%-.192s' trop long (max = %lu). Utilisez un BLOB Un seul champ automatique est permis et il doit ?tre index? %s: Pr?t pour des connexions Version: '%s' socket: '%s' port: %d" %s: Arr?t normal du serveur %s: Re?u le signal %d. Abandonne! %s: Arr?t du serveur termin? %s: Arr?t forc? de la t?che (thread) %ld utilisateur: '%-.48s' Ne peut cr?er la connexion IP (socket) La table '%-.192s' n'a pas d'index comme celle utilis?e dans CREATE INDEX. Recr?ez la table S?parateur de champs inconnu. V?rifiez dans le manuel Vous ne pouvez utiliser des lignes de longueur fixe avec des BLOBs. Utiliser 'fields terminated by'. Le fichier '%-.128s' doit ?tre dans le r?pertoire de la base et lisible par tous Le fichier '%-.200s' existe d?j? Enregistrements: %ld Effac?s: %ld Non trait?s: %ld Avertissements: %ld Enregistrements: %ld Doublons: %ld Mauvaise sous-clef. Ce n'est pas un 'string' ou la longueur d?passe celle d?finie dans la clef Vous ne pouvez effacer tous les champs avec ALTER TABLE. Utilisez DROP TABLE Ne peut effacer (DROP) '%-.192s'. V?rifiez s'il existe Enregistrements: %ld Doublons: %ld Avertissements: %ld You can't specify target table '%-.192s' for update in FROM clause Num?ro de t?che inconnu: %lu Vous n'?tes pas propri?taire de la t?che no: %lu Aucune table utilis?e Trop de cha?nes dans la colonne %-.192s avec SET Ne peut g?n?rer un unique nom de journal %-.200s.(1-999) Table '%-.192s' verrouill?e lecture (READ): modification impossible Table '%-.192s' non verrouill?e: utilisez LOCK TABLES BLOB '%-.192s' ne peut avoir de valeur par d?faut Nom de base de donn?e ill?gal: '%-.100s' Nom de table ill?gal: '%-.100s' SELECT va devoir examiner beaucoup d'enregistrements ce qui va prendre du temps. V?rifiez la clause WHERE et utilisez SET SQL_BIG_SELECTS=1 si SELECT se passe bien Erreur inconnue Proc?dure %-.192s inconnue Mauvais nombre de param?tres pour la procedure %-.192s Param?tre erron? pour la procedure %-.192s Table inconnue '%-.192s' dans %-.32s Champ '%-.192s' sp?cifi? deux fois Utilisation invalide de la clause GROUP Table '%-.192s' : utilise une extension invalide pour cette version de MySQL Une table doit comporter au moins une colonne La table '%-.192s' est pleine Jeu de caract?res inconnu: '%-.64s' Trop de tables. MySQL ne peut utiliser que %d tables dans un JOIN Trop de champs Ligne trop grande. Le taille maximale d'une ligne, sauf les BLOBs, est %ld. Changez le type de quelques colonnes en BLOB D?bordement de la pile des t?ches (Thread stack). Utilis?es: %ld pour une pile de %ld. Essayez 'mysqld --thread_stack=#' pour indiquer une plus grande valeur D?pendance crois?e dans une clause OUTER JOIN. V?rifiez la condition ON Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler Imposible de charger la fonction '%-.192s' Impossible d'initialiser la fonction '%-.192s'; %-.80s Chemin interdit pour les biblioth?ques partag?es La fonction '%-.192s' existe d?j? Impossible d'ouvrir la biblioth?que partag?e '%-.192s' (errno: %d %-.128s) Impossible de trouver la fonction '%-.128s' dans la biblioth?que La fonction '%-.192s' n'est pas d?finie L'h?te '%-.64s' est bloqu? ? cause d'un trop grand nombre d'erreur de connexion. D?bloquer le par 'mysqladmin flush-hosts' Le h?te '%-.64s' n'est pas authoris? ? se connecter ? ce serveur MySQL Vous utilisez un utilisateur anonyme et les utilisateurs anonymes ne sont pas autoris?s ? changer les mots de passe Vous devez avoir le privil?ge update sur les tables de la base de donn?e mysql pour pouvoir changer les mots de passe des autres Impossible de trouver un enregistrement correspondant dans la table user Enregistrements correspondants: %ld Modifi?s: %ld Warnings: %ld Impossible de cr?er une nouvelle t?che (errno %d). S'il reste de la m?moire libre, consultez le manual pour trouver un ?ventuel bug d?pendant de l'OS Column count doesn't match value count at row %ld Impossible de r?ouvrir la table: '%-.192s Utilisation incorrecte de la valeur NULL Erreur '%-.64s' provenant de regexp M?langer les colonnes GROUP (MIN(),MAX(),COUNT()...) avec des colonnes normales est interdit s'il n'y a pas de clause GROUP BY Un tel droit n'est pas d?fini pour l'utilisateur '%-.48s' sur l'h?te '%-.64s' La commande '%-.16s' est interdite ? l'utilisateur: '%-.48s'@'@%-.64s' sur la table '%-.192s' La commande '%-.16s' est interdite ? l'utilisateur: '%-.48s'@'@%-.64s' sur la colonne '%-.192s' de la table '%-.192s' Commande GRANT/REVOKE incorrecte. Consultez le manuel. L'h?te ou l'utilisateur donn? en argument ? GRANT est trop long La table '%-.192s.%-.192s' n'existe pas Un tel droit n'est pas d?fini pour l'utilisateur '%-.48s' sur l'h?te '%-.64s' sur la table '%-.192s' Cette commande n'existe pas dans cette version de MySQL Erreur de syntaxe La t?che 'delayed insert' n'a pas pu obtenir le verrou d?mand? sur la table %-.192s Trop de t?che 'delayed' en cours Connection %ld avort?e vers la bd: '%-.192s' utilisateur: '%-.48s' (%-.64s) Paquet plus grand que 'max_allowed_packet' re?u Erreur de lecture re?ue du pipe de connexion Erreur re?ue de fcntl() Paquets re?us dans le d?sordre Impossible de d?compresser le paquet re?u Erreur de lecture des paquets re?us Timeout en lecture des paquets re?us Erreur d'?criture des paquets envoy?s Timeout d'?criture des paquets envoy?s La cha?ne r?sultat est plus grande que 'max_allowed_packet' Ce type de table ne supporte pas les colonnes BLOB/TEXT Ce type de table ne supporte pas les colonnes AUTO_INCREMENT INSERT DELAYED ne peut ?tre utilis? avec la table '%-.192s', car elle est verrou?e avec LOCK TABLES Nom de colonne '%-.100s' incorrect Le handler de la table ne peut index? la colonne '%-.192s' Toutes les tables de la table de type MERGE n'ont pas la m?me d?finition ?criture impossible ? cause d'un index UNIQUE sur la table '%-.192s' La colonne '%-.192s' de type BLOB est utilis?e dans une d?finition d'index sans longueur d'index Toutes les parties d'un index PRIMARY KEY doivent ?tre NOT NULL; Si vous avez besoin d'un NULL dans l'index, utilisez un index UNIQUE Le r?sultat contient plus d'un enregistrement Ce type de table n?cessite une cl? primaire (PRIMARY KEY) Cette version de MySQL n'est pas compil?e avec le support RAID Vous ?tes en mode 'safe update' et vous essayez de faire un UPDATE sans clause WHERE utilisant un index L'index '%-.192s' n'existe pas sur la table '%-.192s' Impossible d'ouvrir la table Ce type de table ne supporte pas les %s Vous n'?tes pas autoris? ? ex?cute cette commande dans une transaction Erreur %d lors du COMMIT Erreur %d lors du ROLLBACK Erreur %d lors du FLUSH_LOGS Erreur %d lors du CHECKPOINT Connection %ld avort?e vers la bd: '%-.192s' utilisateur: '%-.48s' h?te: '%-.64s' (%-.64s) Ce type de table ne supporte pas les copies binaires Binlog closed, cannot RESET MASTER La reconstruction de l'index de la table copi?e '%-.192s' a ?chou? Erreur re?ue du ma?tre: '%-.64s' Erreur de lecture r?seau re?ue du ma?tre Erreur d'?criture r?seau re?ue du ma?tre Impossible de trouver un index FULLTEXT correspondant ? cette liste de colonnes Impossible d'ex?cuter la commande car vous avez des tables verrouill?es ou une transaction active Variable syst?me '%-.64s' inconnue La table '%-.192s' est marqu?e 'crashed' et devrait ?tre r?par?e La table '%-.192s' est marqu?e 'crashed' et le dernier 'repair' a ?chou? Attention: certaines tables ne supportant pas les transactions ont ?t? chang?es et elles ne pourront pas ?tre restitu?es Cette transaction ? commandes multiples n?cessite plus de 'max_binlog_cache_size' octets de stockage, augmentez cette variable de mysqld et r?essayez Cette op?ration ne peut ?tre r?alis?e avec un esclave actif, faites STOP SLAVE d'abord Cette op?ration n?cessite un esclave actif, configurez les esclaves et faites START SLAVE Le server n'est pas configur? comme un esclave, changez le fichier de configuration ou utilisez CHANGE MASTER TO Impossible d'initialiser les structures d'information de ma?tre, vous trouverez des messages d'erreur suppl?mentaires dans le journal des erreurs de MySQL Impossible de cr?er une t?che esclave, v?rifiez les ressources syst?me L'utilisateur %-.64s poss?de d?j? plus de 'max_user_connections' connexions actives Seules les expressions constantes sont autoris?es avec SET Timeout sur l'obtention du verrou Le nombre total de verrou d?passe la taille de la table des verrous Un verrou en update ne peut ?tre acquit pendant une transaction READ UNCOMMITTED DROP DATABASE n'est pas autoris?e pendant qu'une t?che poss?de un verrou global en lecture CREATE DATABASE n'est pas autoris?e pendant qu'une t?che poss?de un verrou global en lecture Mauvais arguments ? %s '%-.48s'@'%-.64s' n'est pas autoris? ? cr?er de nouveaux utilisateurs D?finition de table incorrecte; toutes les tables MERGE doivent ?tre dans la m?me base de donn?e Deadlock d?couvert en essayant d'obtenir les verrous : essayez de red?marrer la transaction Le type de table utilis? ne supporte pas les index FULLTEXT Impossible d'ajouter des contraintes d'index externe Impossible d'ajouter un enregistrement fils : une constrainte externe l'emp?che Impossible de supprimer un enregistrement p?re : une constrainte externe l'emp?che Error connecting to master: %-.128s Error running query on master: %-.128s Error when executing command %s: %-.128s Incorrect usage of %s and %s The used SELECT statements have a different number of columns Can't execute the query because you have a conflicting read lock Mixing of transactional and non-transactional tables is disabled Option '%s' used twice in statement User '%-.64s' has exceeded the '%s' resource (current value: %ld) Access denied; you need (at least one of) the %-.128s privilege(s) for this operation Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL Variable '%-.64s' doesn't have a default value Variable '%-.64s' can't be set to the value of '%-.200s' Incorrect argument type to variable '%-.64s' Variable '%-.64s' can only be set, not read Incorrect usage/placement of '%s' This version of MySQL doesn't yet support '%s' Got fatal error %d from master when reading data from binary log: '%-.320s' Slave SQL thread ignored the query because of replicate-*-table rules Variable '%-.192s' is a %s variable Incorrect foreign key definition for '%-.192s': %s Key reference and table reference don't match Operand should contain %d column(s) Subquery returns more than 1 row Unknown prepared statement handler (%.*s) given to %s Help database is corrupt or does not exist Cyclic reference on subqueries Converting column '%s' from %s to %s Reference '%-.64s' not supported (%s) Every derived table must have its own alias Select %u was reduced during optimization Table '%-.192s' from one of the SELECTs cannot be used in %-.32s Client does not support authentication protocol requested by server; consider upgrading MySQL client All parts of a SPATIAL index must be NOT NULL COLLATION '%s' is not valid for CHARACTER SET '%s' Slave is already running Slave already has been stopped Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted) ZLIB: Not enough memory ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) ZLIB: Input data corrupted Row %u was cut by GROUP_CONCAT() Row %ld doesn't contain data for all columns Row %ld was truncated; it contained more data than there were input columns Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld Out of range value for column '%s' at row %ld Data truncated for column '%s' at row %ld Using 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 users Can't revoke all privileges for one or more of the requested users Illegal 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 started 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 Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d Incorrect parameter or combination of parameters for START SLAVE UNTIL 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 SQL thread is not to be started so UNTIL options are ignored Incorrect index name '%-.100s' Incorrect catalog name '%-.100s' Query cache failed to set size %lu; new query cache size is %lu Column '%-.192s' cannot be part of FULLTEXT index Unknown key cache '%-.100s' MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work Unknown storage engine '%s' '%s' is deprecated and will be removed in a future release. Please use %s instead The target table %-.100s of the %s is not updatable The '%s' feature is disabled; you need MySQL built with '%s' to have it working The MySQL server is running with the %s option so it cannot execute this statement Column '%-.100s' has duplicated value '%-.64s' in %s Truncated incorrect %-.32s value: '%-.128s' Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Invalid ON UPDATE clause for '%-.192s' column This command is not supported in the prepared statement protocol yet Got error %d '%-.100s' from %s Got temporary error %d '%-.100s' from %s Unknown or incorrect time zone: '%-.64s' Invalid TIMESTAMP value in column '%s' at row %ld Invalid %s character string: '%.64s' Result of %s() was larger than max_allowed_packet (%ld) - truncated Conflicting declarations: '%s%s' and '%s%s' Can't create a %s from within another stored routine %s %s already exists %s %s does not exist Failed to DROP %s %s Failed to CREATE %s %s %s with no matching label: %s Redefining label %s End-label %s without match Referring to uninitialized variable %s PROCEDURE %s can't return a result set in the given context RETURN is only allowed in a FUNCTION %s is not allowed in stored procedures 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. 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. Query execution was interrupted Incorrect number of arguments for %s %s; expected %u, got %u Undefined CONDITION: %s No RETURN found in FUNCTION %s FUNCTION %s ended without RETURN Cursor statement must be a SELECT Cursor SELECT must not have INTO Undefined CURSOR: %s Cursor is already open Cursor is not open Undeclared variable: %s Incorrect number of FETCH variables No data - zero rows fetched, selected, or processed Duplicate parameter: %s Duplicate variable: %s Duplicate condition: %s Duplicate cursor: %s Failed to ALTER %s %s Subquery value not supported %s is not allowed in stored function or trigger Variable or condition declaration after cursor or handler declaration Cursor declaration after handler declaration Case not found for CASE statement Configuration file '%-.192s' is too big Malformed file type header in file '%-.192s' Unexpected end of file while parsing comment '%-.200s' Error while parsing parameter '%-.192s' (line: '%-.192s') Unexpected end of file while skipping unknown parameter '%-.192s' EXPLAIN/SHOW can not be issued; lacking privileges for underlying table File '%-.192s' has unknown type '%-.64s' in its header '%-.192s.%-.192s' is not %s Column '%-.192s' is not updatable View's SELECT contains a subquery in the FROM clause View's SELECT contains a '%s' clause View's SELECT contains a variable or parameter View's SELECT refers to a temporary table '%-.192s' View's SELECT and view's field list have different column counts View merge algorithm can't be used here for now (assumed undefined algorithm) View being updated does not have complete key of underlying table in it View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them Can't drop or alter a %s from within another stored routine GOTO is not allowed in a stored procedure handler Trigger already exists Trigger does not exist Trigger's '%-.192s' is view or temporary table Updating of %s row is not allowed in %strigger There is no %s row in %s trigger Field '%-.192s' doesn't have a default value Division by 0 Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld Illegal %s '%-.192s' value found during parsing CHECK OPTION on non-updatable view '%-.192s.%-.192s' CHECK OPTION failed '%-.192s.%-.192s' %-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s' Failed purging old relay logs: %s Password hash should be a %d-digit hexadecimal number Target log not found in binlog index I/O error reading log index file Server configuration does not permit binlog purge Failed on fseek() Fatal error during log purge A purgeable log is in use, will not purge Unknown error during log purge Failed initializing relay log position: %s You are not using binary logging The '%-.64s' syntax is reserved for purposes internal to the MySQL server WSAStartup Failed Can't handle procedures with different groups yet Select must have a group with this procedure Can't use ORDER clause with this procedure Binary logging and replication forbid changing the global server %s Can't map file: %-.200s, errno: %d Wrong magic in %-.64s Prepared statement contains too many placeholders Key part '%-.192s' length cannot be 0 View text checksum failed Can not modify more than one base table through a join view '%-.192s.%-.192s' Can not insert into join view '%-.192s.%-.192s' without fields list Can not delete from join view '%-.192s.%-.192s' Operation %s failed for %.256s XAER_NOTA: Unknown XID XAER_INVAL: Invalid arguments (or unsupported command) XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state XAER_OUTSIDE: Some work is done outside global transaction XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency XA_RBROLLBACK: Transaction branch was rolled back There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s' Failed to grant EXECUTE and ALTER ROUTINE privileges Failed to revoke all privileges to dropped routine Data too long for column '%s' at row %ld Bad SQLSTATE: '%s' %s: ready for connections. Version: '%s' socket: '%s' port: %d %s Can't load value from file with fixed size rows to variable You are not allowed to create a user with GRANT Incorrect %-.32s value: '%-.128s' for function %-.32s Table definition has changed, please retry transaction Duplicate handler declared in the same block OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger Not allowed to return a result set from a %s Cannot get geometry object from data you send to the GEOMETRY field 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 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) 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 '%-.192s.%-.192s' underlying table doesn't have a default value Recursive stored functions and triggers are not allowed. Too big scale %d specified for column '%-.192s'. Maximum is %lu. Too big precision %d specified for column '%-.192s'. Maximum is %lu. For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s'). You can't combine write-locking of system tables with other tables or lock types Unable to connect to foreign data source: %.64s There was a problem processing the query on the foreign data source. Data source error: %-.64s The foreign data source you are trying to reference does not exist. Data source error: %-.64s Can't create federated table. The data source connection string '%-.64s' is not in the correct format The data source connection string '%-.64s' is not in the correct format Can't create federated table. Foreign data src error: %-.64s Trigger in wrong schema Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack. Routine body for '%-.100s' is too long Cannot drop default keycache Display width out of range for column '%-.192s' (max = %lu) XAER_DUPID: The XID already exists Datetime function: %-.32s field overflow Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger. The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'. 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 Not allowed to set autocommit from a stored function or trigger Definer is not fully qualified View '%-.192s'.'%-.192s' 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 '%-.192s'@'%-.192s' definer The user specified as a definer ('%-.64s'@'%-.64s') does not exist Changing schema from '%-.192s' to '%-.192s' 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 renamed 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. '%-.192s' 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 %.192s Failed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d) Incorrect routine name '%-.192s' Table upgrade required. Please do "REPAIR TABLE `%-.32s`" or dump/reload to fix it! AGGREGATE is not supported for stored functions Can't create more than max_prepared_stmt_count statements (current value: %lu) `%-.192s`.`%-.192s` contains view recursion Non-grouping field '%-.192s' is used in %-.64s clause The used table type doesn't support SPATIAL indexes Triggers can not be created on system tables Leading spaces are removed from name '%s' Failed to read auto-increment value from storage engine user name host name String '%-.70s' is too long for %s (should be no longer than %d) The target table %-.100s of the %s is not insertable-into Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist Too high level of nesting for select Name '%-.64s' has become '' First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY The foreign server, %s, you are trying to create already exists. The foreign server name you are trying to reference does not exist. Data source error: %-.64s Table storage engine '%-.64s' does not support the create option '%.64s' Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in RANGE/LIST VALUES must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MySQL For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table's partitioning function Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Foreign key clause is not yet supported in conjunction with partitioning Error in list of partitions to %-.64s Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin '%-.192s' is not loaded Incorrect %-.32s value: '%-.128s' Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn't support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don't allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on master and slave does not match: %s Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events Event '%-.192s' already exists Failed to store event %s. Error code %d from storage engine. Unknown event '%-.192s' Failed to alter event '%-.192s' Failed to drop %s INTERVAL is either not positive or too big ENDS is either invalid or before STARTS Event execution time is in the past. Event has been disabled Failed to open mysql.event No datetime expression provided Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted Cannot load from mysql.%s. The table is probably corrupted Failed to delete the event from mysql.event Error during compilation of event's body Same old and new event name Data for column '%s' too long Cannot drop index '%-.192s': needed in a foreign key constraint The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead You can't write-lock a log table. Only read access is possible You can't use locks with log tables. Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry 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. Cannot switch out of the row-based binary log format when the session has open temporary tables Cannot change the binary logging format inside a stored function or trigger The NDB cluster engine does not support changing the binlog format on the fly yet Cannot create temporary table with partitions Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction isolation level can't be changed while a transaction is in progress ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s' Internal scheduler error %d Error during starting/stopping of the scheduler. Error code %u Engine cannot be used in partitioned tables Cannot activate '%-.64s' log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed because system tables used by Event Scheduler were found damaged at server start Only integers allowed as number here This storage engine cannot be used for log tables" You cannot '%s' a log table if logging is enabled 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' Incorrect parameter count in the call to native function '%-.192s' Incorrect parameters in the call to native function '%-.192s' Incorrect parameters in the call to stored function '%-.192s' This function '%-.192s' has the same name as a native function Duplicata du champ '%-.64s' pour la clef '%-.192s' Too many files opened, please execute the command again Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation. The incident %s occured on the master. Message: %-.64s Table has no partition for some existing values Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master command %s failed: %s Binary logging not possible. Message: %s View `%-.64s`.`%-.64s` has no creation context Creation context of view `%-.64s`.`%-.64s' is invalid Creation context of stored routine `%-.64s`.`%-.64s` is invalid Corrupted TRG file for table `%-.64s`.`%-.64s` Triggers for table `%-.64s`.`%-.64s` have no creation context Trigger creation context of table `%-.64s`.`%-.64s` is invalid Creation context of event `%-.64s`.`%-.64s` is invalid Cannot open table for trigger `%-.64s`.`%-.64s` Cannot create stored routine `%-.64s`. Check warnings Ambiguous slave modes combination. %s The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement. Corrupted replication event was detected Invalid column reference (%-.64s) in LOAD DATA Being purged log %s was not found XA_RBTIMEOUT: Transaction branch was rolled back: took too long XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected Prepared statement needs to be re-prepared DELAYED option not supported for table '%-.192s' The master info structure does not exist <%-.64s> option ignored Built-in plugins cannot be deleted Plugin is busy and will be uninstalled on shutdown %s variable '%s' is read-only. Use SET %s to assign the value Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted Unexpected master's heartbeat data: %s The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds). Bad schema for mysql.ndb_replication table. Message: %-.64s Error in parsing conflict function. Message: %-.64s Write to exceptions table failed. Message: %-.128s" Comment for table '%-.64s' is too long (max = %lu) Comment for field '%-.64s' is too long (max = %lu) FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item '%s' Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data truncated for condition item '%s' Data too long for condition item '%s' Unknown locale: '%-.64s' The requested server id %d clashes with the slave startup option --replicate-same-server-id Query cache is disabled; restart the server with query_cache_type=1 to enable it Duplicate partition field name '%-.192s' Inconsistency in usage of column lists for partitioning Partition column values of incorrect type Too many fields in '%-.192s' Cannot use MAXVALUE as value in VALUES IN Cannot have more than one value for this type of %-.64s partitioning Row expressions in VALUES IN only allowed for multi-field column partitioning Field '%-.192s' is of a not allowed type for this type of partitioning The total length of the partitioning fields is too large Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. 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. 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 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. 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 Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted. 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. 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. Statement is unsafe because it uses a UDF which may not return the same value on the slave. Statement is unsafe because it uses a system variable that may have a different value on the slave. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. %s Statement: %s Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s' Can't create conversion table for table '%-.192s.%-.192s' Cannot modify @@session.binlog_format inside a transaction The path specified for %.64s is too long. '%s' is deprecated and will be removed in a future release. Native table '%-.64s'.'%-.64s' has the wrong structure Invalid performance_schema usage. Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Cannot change the binlog direct flag inside a stored function or trigger A SPATIAL index may only contain a geometrical type column Comment for index '%-.64s' is too long (max = %lu) Wait on a lock was aborted due to a pending exclusive lock %s value is out of range in '%s' A variable of a non-integer based type in LIMIT clause Mixing self-logging and non-self-logging engines in a statement is unsafe. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Cannot modify @@session.sql_log_bin inside a transaction Cannot change the sql_log_bin inside a stored function or trigger Failed to read from the .par file VALUES value for partition '%-.64s' must have type INT Acc?s refus? pour l'utilisateur: '%-.48s'@'@%-.64s' SET PASSWORD has no significance for users authenticating via plugins GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Cannot truncate a table referenced in a foreign key constraint (%.192s) Plugin '%s' is force_plus_permanent and can not be unloaded 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. 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. Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'. Table rebuild required. Please do "ALTER TABLE `%-.32s` FORCE" or dump/reload to fix it! The value of '%s' should be no less than the value of '%s' Index column size too large. The maximum column size is %lu bytes. Trigger '%-.64s' has an error in its body: '%-.256s' Unknown trigger has an error in its body: '%-.256s' Index %s is corrupted Undo log record is too big. 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... 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. 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. 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. 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. 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. Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it. Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it. 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. 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. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Table is being used in foreign key check. Storage engine '%s' does not support system tables. [%s.%s] INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de