Edit D:\chineseall_products\software\win-32bit\Mysql\share\portuguese\errmsg.sys
? ?? K | ? O?? Q???J???6l???&Yn???(T??P? " : X ? ? ! F l ? ? ? ? B a ? ? ? ! C o ? ? ? > c ? ? <i? ???0q??&??Pq*???9[???\??????,`???._|????/e?? H o ? ( ? Z ? N ? ? ? ? ? ? A!?!"C"h"?"#8#?#?#,$?$?$?$?$ %S%?%?%%&c&?&?&4'W'?'?'6(?($)S)?)?)=*m*?*?*?* +++M+o+?+,@,?,?,?,?,0-?-?-._.?.?/?/R0?0!1l1?12T2?23d3?3?3 4?4?4J5?5?5$6J6s6?6?6?6E7?7?7?7>8?8?8 9T9?9?9?9 :X:?:?:;C;g;?;?;<4<Z<?<?<?<!=?=?=> >8>?>?>j???????-@r@???@HAwA? BTB??? D{D???F,F???YG{G??@H???}I??J=JfJ??K-KbKwK?????L,LhL??@M?N?NWNvN????OO1OUO??????PHP???Q2QiQ??-RdR?R???+S_S??6T??&U=UTU??? VVOVV?? WBWxW???X XIXhX???YBYoY??ZZIZoZ??[K[j[??\N\??4]i]??? ^Y^???#_????za b???Gc?c?dVd??6e??Cf??$gKghg???|h?ri??Tj??#kqk????\m??Cnsn??$oXo?????<pvp??q{q?rdr?s<sqs??:t??u?u?? vFv~v??8wxw?x<xnx??#yly??z]z?{@{e{??? |d|?}R}????%~9~K~??&:m?"?A?~??????????(????????? ?? ?????5??????????"???? ???? ???? ?=??????<??????? ?????.???????????????????????(?????!?+?8????????>??????????0????? ????? ??? ??(??*????,???(????$????????$???????????? ???(????????? ?)???????????.???ashchk isamchk N?O SIM N?o pode criar o arquivo '%-.200s' (erro no. %d) N?o pode criar a tabela '%-.200s' (erro no. %d) N?o pode criar o banco de dados '%-.192s' (erro no. %d) N?o pode criar o banco de dados '%-.192s'; este banco de dados j? existe N?o pode eliminar o banco de dados '%-.192s'; este banco de dados n?o existe Erro ao eliminar banco de dados (n?o pode eliminar '%-.192s' - erro no. %d) Erro ao eliminar banco de dados (n?o pode remover diret?rio '%-.192s' - erro no. %d) Erro na remo??o de '%-.192s' (erro no. %d) N?o pode ler um registro numa tabela do sistema N?o pode obter o status de '%-.200s' (erro no. %d) N?o pode obter o diret?rio corrente (erro no. %d) N?o pode travar o arquivo (erro no. %d) N?o pode abrir o arquivo '%-.200s' (erro no. %d) N?o pode encontrar o arquivo '%-.200s' (erro no. %d) N?o pode ler o diret?rio de '%-.192s' (erro no. %d) N?o pode mudar para o diret?rio '%-.192s' (erro no. %d) Registro alterado desde a ?ltima leitura da tabela '%-.192s' Disco cheio (%s). Aguardando algu?m liberar algum espa?o... N?o pode gravar. Chave duplicada na tabela '%-.192s' Erro ao fechar '%-.192s' (erro no. %d) Erro ao ler arquivo '%-.200s' (erro no. %d) Erro ao renomear '%-.210s' para '%-.210s' (erro no. %d) Erro ao gravar arquivo '%-.200s' (erro no. %d) '%-.192s' est? com travamento contra altera??es Ordena??o abortada Vis?o '%-.192s' n?o existe para '%-.192s' Obteve erro %d no manipulador de tabelas Manipulador de tabela para '%-.192s' n?o tem esta op??o N?o pode encontrar registro em '%-.192s' Informa??o incorreta no arquivo '%-.200s' Arquivo de ?ndice incorreto para tabela '%-.200s'; tente repar?-lo Arquivo de ?ndice desatualizado para tabela '%-.192s'; repare-o! Tabela '%-.192s' ? somente para leitura Sem mem?ria. Reinicie o programa e tente novamente (necessita de %d bytes) N?o h? mem?ria suficiente para ordena??o. Considere aumentar o tamanho do retentor (buffer) de ordena??o. Encontrado fim de arquivo inesperado ao ler arquivo '%-.192s' (erro no. %d) Excesso de conex?es Sem mem?ria. Verifique se o mysqld ou algum outro processo est? usando toda mem?ria dispon?vel. Se n?o, voc? pode ter que usar 'ulimit' para permitir ao mysqld usar mais mem?ria ou voc? pode adicionar mais ?rea de 'swap' N?o pode obter nome do 'host' para seu endere?o Negocia??o de acesso falhou Acesso negado para o usu?rio '%-.48s'@'%-.64s' ao banco de dados '%-.192s' Acesso negado para o usu?rio '%-.48s'@'%-.64s' (senha usada: %s) Nenhum banco de dados foi selecionado Comando desconhecido Coluna '%-.192s' n?o pode ser vazia Banco de dados '%-.192s' desconhecido Tabela '%-.192s' j? existe Tabela '%-.100s' desconhecida Coluna '%-.192s' em '%-.192s' ? amb?gua 'Shutdown' do servidor em andamento Coluna '%-.192s' desconhecida em '%-.192s' '%-.192s' n?o est? em 'GROUP BY' N?o pode agrupar em '%-.192s' Cl?usula cont?m fun??es de soma e colunas juntas Contagem de colunas n?o confere com a contagem de valores Nome identificador '%-.100s' ? longo demais Nome da coluna '%-.192s' duplicado Nome da chave '%-.192s' duplicado Entrada '%-.192s' duplicada para a chave %d Especificador de coluna incorreto para a coluna '%-.192s' %s pr?ximo a '%-.80s' na linha %d Consulta (query) estava vazia Tabela/alias '%-.192s' n?o ?nica Valor padr?o (default) inv?lido para '%-.192s' Definida mais de uma chave prim?ria Especificadas chaves demais. O m?ximo permitido s?o %d chaves Especificadas partes de chave demais. O m?ximo permitido s?o %d partes Chave especificada longa demais. O comprimento de chave m?ximo permitido ? %d Coluna chave '%-.192s' n?o existe na tabela Coluna BLOB '%-.192s' n?o pode ser utilizada na especifica??o de chave para o tipo de tabela usado Comprimento da coluna '%-.192s' grande demais (max = %lu); use BLOB em seu lugar Defini??o incorreta de tabela. Somente ? permitido um ?nico campo auto-incrementado e ele tem que ser definido como chave %s: Pronto para conex?es Version: '%s' socket: '%s' port: %d" %s: 'Shutdown' normal %s: Obteve sinal %d. Abortando! %s: 'Shutdown' completo %s: For?ando finaliza??o da 'thread' %ld - usu?rio '%-.48s' N?o pode criar o soquete IP Tabela '%-.192s' n?o possui um ?ndice como o usado em CREATE INDEX. Recrie a tabela Argumento separador de campos n?o ? o esperado. Cheque o manual Voc? n?o pode usar comprimento de linha fixo com BLOBs. Por favor, use campos com comprimento limitado. Arquivo '%-.128s' tem que estar no diret?rio do banco de dados ou ter leitura poss?vel para todos Arquivo '%-.200s' j? existe Registros: %ld - Deletados: %ld - Ignorados: %ld - Avisos: %ld Registros: %ld - Duplicados: %ld Sub parte da chave incorreta. A parte da chave usada n?o ? uma 'string' ou o comprimento usado ? maior que parte da chave ou o manipulador de tabelas n?o suporta sub chaves ?nicas Voc? n?o pode deletar todas as colunas com ALTER TABLE; use DROP TABLE em seu lugar N?o se pode fazer DROP '%-.192s'. Confira se esta coluna/chave existe Registros: %ld - Duplicados: %ld - Avisos: %ld You can't specify target table '%-.192s' for update in FROM clause 'Id' de 'thread' %lu desconhecido Voc? n?o ? propriet?rio da 'thread' %lu Nenhuma tabela usada 'Strings' demais para coluna '%-.192s' e SET N?o pode gerar um nome de arquivo de 'log' ?nico '%-.200s'.(1-999) Tabela '%-.192s' foi travada com trava de leitura e n?o pode ser atualizada Tabela '%-.192s' n?o foi travada com LOCK TABLES Coluna BLOB '%-.192s' n?o pode ter um valor padr?o (default) Nome de banco de dados '%-.100s' incorreto Nome de tabela '%-.100s' incorreto O SELECT examinaria registros demais e provavelmente levaria muito tempo. Cheque sua cl?usula WHERE e use SET SQL_BIG_SELECTS=1, se o SELECT estiver correto Erro desconhecido 'Procedure' '%-.192s' desconhecida N?mero de par?metros incorreto para a 'procedure' '%-.192s' Par?metros incorretos para a 'procedure' '%-.192s' Tabela '%-.192s' desconhecida em '%-.32s' Coluna '%-.192s' especificada duas vezes Uso inv?lido de fun??o de agrupamento (GROUP) Tabela '%-.192s' usa uma extens?o que n?o existe nesta vers?o do MySQL Uma tabela tem que ter pelo menos uma (1) coluna Tabela '%-.192s' est? cheia Conjunto de caracteres '%-.64s' desconhecido Tabelas demais. O MySQL pode usar somente %d tabelas em uma jun??o (JOIN) Colunas demais Tamanho de linha grande demais. O m?ximo tamanho de linha, n?o contando BLOBs, ? %ld. Voc? tem que mudar alguns campos para BLOBs Estouro da pilha do 'thread'. Usados %ld de uma pilha de %ld. Use 'mysqld --thread_stack=#' para especificar uma pilha maior, se necess?rio Depend?ncia cruzada encontrada em jun??o externa (OUTER JOIN); examine as condi??es utilizadas nas cl?usulas 'ON' Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler N?o pode carregar a fun??o '%-.192s' N?o pode inicializar a fun??o '%-.192s' - '%-.80s' N?o h? caminhos (paths) permitidos para biblioteca compartilhada Fun??o '%-.192s' j? existe N?o pode abrir biblioteca compartilhada '%-.192s' (erro no. %d '%-.128s') N?o pode encontrar a fun??o '%-.128s' na biblioteca Fun??o '%-.192s' n?o est? definida 'Host' '%-.64s' est? bloqueado devido a muitos erros de conex?o. Desbloqueie com 'mysqladmin flush-hosts' 'Host' '%-.64s' n?o tem permiss?o para se conectar com este servidor MySQL Voc? est? usando o MySQL como usu?rio an?nimo e usu?rios an?nimos n?o t?m permiss?o para mudar senhas Voc? deve ter privil?gios para atualizar tabelas no banco de dados mysql para ser capaz de mudar a senha de outros N?o pode encontrar nenhuma linha que combine na tabela usu?rio (user table) Linhas que combinaram: %ld - Alteradas: %ld - Avisos: %ld N?o pode criar uma nova 'thread' (erro no. %d). Se voc? n?o estiver sem mem?ria dispon?vel, voc? pode consultar o manual sobre um poss?vel 'bug' dependente do sistema operacional Contagem de colunas n?o confere com a contagem de valores na linha %ld N?o pode reabrir a tabela '%-.192s Uso inv?lido do valor NULL Obteve erro '%-.64s' em regexp Mistura de colunas agrupadas (com MIN(), MAX(), COUNT(), ...) com colunas n?o agrupadas ? ilegal, se n?o existir uma cl?usula de agrupamento (cl?usula GROUP BY) N?o existe tal permiss?o (grant) definida para o usu?rio '%-.48s' no 'host' '%-.64s' Comando '%-.16s' negado para o usu?rio '%-.48s'@'%-.64s' na tabela '%-.192s' Comando '%-.16s' negado para o usu?rio '%-.48s'@'%-.64s' na coluna '%-.192s', na tabela '%-.192s' Comando GRANT/REVOKE ilegal. Por favor consulte no manual quais privil?gios podem ser usados. Argumento de 'host' ou de usu?rio para o GRANT ? longo demais Tabela '%-.192s.%-.192s' n?o existe N?o existe tal permiss?o (grant) definido para o usu?rio '%-.48s' no 'host' '%-.64s', na tabela '%-.192s' Comando usado n?o ? permitido para esta vers?o do MySQL Voc? tem um erro de sintaxe no seu SQL 'Thread' de inser??o retardada (atrasada) pois n?o conseguiu obter a trava solicitada para tabela '%-.192s' Excesso de 'threads' retardadas (atrasadas) em uso Conex?o %ld abortou para o banco de dados '%-.192s' - usu?rio '%-.48s' (%-.64s) Obteve um pacote maior do que a taxa m?xima de pacotes definida (max_allowed_packet) Obteve um erro de leitura no 'pipe' da conex?o Obteve um erro em fcntl() Obteve pacotes fora de ordem N?o conseguiu descomprimir pacote de comunica??o Obteve um erro na leitura de pacotes de comunica??o Obteve expira??o de tempo (timeout) na leitura de pacotes de comunica??o Obteve um erro na escrita de pacotes de comunica??o Obteve expira??o de tempo ('timeout') na escrita de pacotes de comunica??o 'String' resultante ? mais longa do que 'max_allowed_packet' Tipo de tabela usado n?o permite colunas BLOB/TEXT Tipo de tabela usado n?o permite colunas AUTO_INCREMENT INSERT DELAYED n?o pode ser usado com a tabela '%-.192s', porque ela est? travada com LOCK TABLES Nome de coluna '%-.100s' incorreto O manipulador de tabela usado n?o pode indexar a coluna '%-.192s' Todas as tabelas contidas na tabela fundida (MERGE) n?o est?o definidas identicamente N?o pode gravar, devido ? restri??o UNIQUE, na tabela '%-.192s' Coluna BLOB '%-.192s' usada na especifica??o de chave sem o comprimento da chave Todas as partes de uma chave prim?ria devem ser n?o-nulas. Se voc? precisou usar um valor nulo (NULL) em uma chave, use a cl?usula UNIQUE em seu lugar O resultado consistiu em mais do que uma linha Este tipo de tabela requer uma chave prim?ria Esta vers?o do MySQL n?o foi compilada com suporte a RAID Voc? est? usando modo de atualiza??o seguro e tentou atualizar uma tabela sem uma cl?usula WHERE que use uma coluna chave Chave '%-.192s' n?o existe na tabela '%-.192s' N?o pode abrir a tabela O manipulador de tabela n?o suporta %s N?o lhe ? permitido executar este comando em uma transa??o Obteve erro %d durante COMMIT Obteve erro %d durante ROLLBACK Obteve erro %d durante FLUSH_LOGS Obteve erro %d durante CHECKPOINT Conex?o %ld abortada para banco de dados '%-.192s' - usu?rio '%-.48s' - 'host' '%-.64s' ('%-.64s') O manipulador de tabela n?o suporta 'dump' bin?rio de tabela Binlog fechado. N?o pode fazer RESET MASTER Falhou na reconstru??o do ?ndice da tabela 'dumped' '%-.192s' Erro no 'master' '%-.64s' Erro de rede lendo do 'master' Erro de rede gravando no 'master' N?o pode encontrar um ?ndice para o texto todo que combine com a lista de colunas N?o pode executar o comando dado porque voc? tem tabelas ativas travadas ou uma transa??o ativa Vari?vel de sistema '%-.64s' desconhecida Tabela '%-.192s' est? marcada como danificada e deve ser reparada Tabela '%-.192s' est? marcada como danificada e a ?ltima repara??o (autom?tica?) falhou Aviso: Algumas tabelas n?o-transacionais alteradas n?o puderam ser reconstitu?das (rolled back) Transa??es multi-declaradas (multi-statement transactions) requeriram mais do que o valor limite (max_binlog_cache_size) de bytes para armazenagem. Aumente o valor desta vari?vel do mysqld e tente novamente Esta opera??o n?o pode ser realizada com um 'slave' em execu??o. Execute STOP SLAVE primeiro Esta opera??o requer um 'slave' em execu??o. Configure o 'slave' e execute START SLAVE O servidor n?o est? configurado como 'slave'. Acerte o arquivo de configura??o ou use CHANGE MASTER TO Could not initialize master info structure; more error messages can be found in the MySQL error log N?o conseguiu criar 'thread' de 'slave'. Verifique os recursos do sistema Usu?rio '%-.64s' j? possui mais que o valor m?ximo de conex?es (max_user_connections) ativas Voc? pode usar apenas express?es constantes com SET Tempo de espera (timeout) de travamento excedido. Tente reiniciar a transa??o. O n?mero total de travamentos excede o tamanho da tabela de travamentos Travamentos de atualiza??o n?o podem ser obtidos durante uma transa??o de tipo READ UNCOMMITTED DROP DATABASE n?o permitido enquanto uma 'thread' est? mantendo um travamento global de leitura CREATE DATABASE n?o permitido enquanto uma 'thread' est? mantendo um travamento global de leitura Argumentos errados para %s N?o ? permitido a '%-.48s'@'%-.64s' criar novos usu?rios Defini??o incorreta da tabela. Todas as tabelas contidas na jun??o devem estar no mesmo banco de dados. Encontrado um travamento fatal (deadlock) quando tentava obter uma trava. Tente reiniciar a transa??o. O tipo de tabela utilizado n?o suporta ?ndices de texto completo (fulltext indexes) N?o pode acrescentar uma restri??o de chave estrangeira N?o pode acrescentar uma linha filha: uma restri??o de chave estrangeira falhou N?o pode apagar uma linha pai: uma restri??o de chave estrangeira falhou Erro conectando com o master: %-.128s Erro rodando consulta no master: %-.128s Erro quando executando comando %s: %-.128s Uso errado de %s e %s Os comandos SELECT usados t?m diferente n?mero de colunas N?o posso executar a consulta porque voc? tem um conflito de travamento de leitura Mistura de tabelas transacional e n?o-transacional est? desabilitada Op??o '%s' usada duas vezes no comando Usu?rio '%-.64s' tem excedido o '%s' recurso (atual valor: %ld) Acesso negado. Voc? precisa o privil?gio %-.128s para essa opera??o Vari?vel '%-.64s' ? uma SESSION vari?vel e n?o pode ser usada com SET GLOBAL Vari?vel '%-.64s' ? uma GLOBAL vari?vel e deve ser configurada com SET GLOBAL Vari?vel '%-.64s' n?o tem um valor padr?o Vari?vel '%-.64s' n?o pode ser configurada para o valor de '%-.200s' Tipo errado de argumento para vari?vel '%-.64s' Vari?vel '%-.64s' somente pode ser configurada, n?o lida Errado uso/coloca??o de '%s' Esta vers?o de MySQL n?o suporta ainda '%s' Obteve fatal erro %d: '%-.320s' do master quando lendo dados do binary log Slave SQL thread ignorado a consulta devido ?s normas de replica??o-*-tabela Variable '%-.192s' is a %s variable Defini??o errada da chave estrangeira para '%-.192s': %s Refer?ncia da chave e refer?ncia da tabela n?o coincidem Operand should contain %d column(s) Subconsulta retorna mais que 1 registro Desconhecido manipulador de declara??o preparado (%.*s) determinado para %s Banco de dado de ajuda corrupto ou n?o existente Refer?ncia c?clica em subconsultas Convertendo coluna '%s' de %s para %s Refer?ncia '%-.64s' n?o suportada (%s) Cada tabela derivada deve ter seu pr?prio alias Select %u foi reduzido durante otimiza??o Tabela '%-.192s' de um dos SELECTs n?o pode ser usada em %-.32s Cliente n?o suporta o protocolo de autentica??o exigido pelo servidor; considere a atualiza??o do cliente MySQL Todas as partes de uma SPATIAL index devem ser NOT NULL COLLATION '%s' n?o ? v?lida para CHARACTER SET '%s' O slave j? est? rodando O slave j? est? parado Tamanho muito grande dos dados des comprimidos. O m?ximo tamanho ? %d. (provavelmente, o comprimento dos dados descomprimidos est? corrupto) ZLIB: N?o suficiente mem?ria dispon?vel ZLIB: N?o suficiente espa?o no buffer emissor (provavelmente, o comprimento dos dados descomprimidos est? corrupto) ZLIB: Dados de entrada est? corrupto Row %u was cut by GROUP_CONCAT() Conta de registro ? menor que a conta de coluna na linha %ld Conta de registro ? maior que a conta de coluna na linha %ld Dado truncado, NULL fornecido para NOT NULL coluna '%s' na linha %ld Out of range value for column '%s' at row %ld Dado truncado para coluna '%s' na linha %ld Usando engine de armazenamento %s para tabela '%s' Combina??o ilegal de collations (%s,%s) e (%s,%s) para opera??o '%s' Cannot drop one or more of the requested users N?o pode revocar todos os privil?gios, grant para um ou mais dos usu?rios pedidos Ilegal combina??o de collations (%s,%s), (%s,%s), (%s,%s) para opera??o '%s' Ilegal combina??o de collations para opera??o '%s' Vari?vel '%-.64s' n?o ? uma vari?vel componente (N?o pode ser usada como XXXX.vari?vel_nome) Collation desconhecida: '%-.64s' SSL par?metros em CHANGE MASTER s?o ignorados porque este escravo MySQL foi compilado sem o SSL suporte. Os mesmos podem ser usados mais tarde quando o escravo MySQL com SSL seja iniciado. Servidor est? rodando em --secure-auth modo, por?m '%s'@'%s' tem senha no formato antigo; por favor troque a senha para o novo formato Campo ou refer?ncia '%-.192s%s%-.192s%s%-.192s' de SELECT #%d foi resolvido em SELECT #%d Par?metro ou combina??o de par?metros errado para START SLAVE UNTIL ? recomendado para rodar com --skip-slave-start quando fazendo replica??o passo-por-passo com START SLAVE UNTIL, de outra forma voc? n?o est? seguro em caso de inesperada reiniciali??o do mysqld escravo Thread SQL n?o pode ser inicializado tal que op??es UNTIL s?o ignoradas Incorreto nome de ?ndice '%-.100s' Incorreto nome de cat?logo '%-.100s' Falha em Query cache para configurar tamanho %lu, novo tamanho de query cache ? %lu Coluna '%-.192s' n?o pode ser parte de ?ndice FULLTEXT Key cache desconhecida '%-.100s' MySQL foi inicializado em modo --skip-name-resolve. Voc? necesita reincializ?-lo sem esta op??o para este grant funcionar Motor de tabela desconhecido '%s' '%s' ? desatualizado. Use '%s' em seu lugar A tabela destino %-.100s do %s n?o ? atualiz?vel O recurso '%s' foi desativado; voc? necessita MySQL constru?do com '%s' para ter isto funcionando O servidor MySQL est? rodando com a op??o %s raz?o pela qual n?o pode executar esse commando Coluna '%-.100s' tem valor duplicado '%-.64s' em %s Truncado errado %-.32s valor: '%-.128s' Incorreta defini??o de tabela; Pode ter somente uma coluna TIMESTAMP com CURRENT_TIMESTAMP em DEFAULT ou ON UPDATE cl?usula Inv?lida cl?usula ON UPDATE para campo '%-.192s' 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 Entrada '%-.64s' duplicada para a chave '%-.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" Coment?rio para a tabela '%-.64s' ? longo demais (max = %lu) Coment?rio para o campo '%-.64s' ? longo demais (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 Acesso negado para o usu?rio '%-.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