xXx

Hexid M1n1 5h3ll MobiLe

C:/xampp/mysql/share/portuguese/_[ Writable ]

File:C:/xampp/mysql/share/portuguese/errmsg.sys

þþ�ž©Á���������������������������K�|�µ��Oœó Q…¹âJ€ºø6l“¿÷&YnšÃþ(T™ÛPšæûá	1	}	¿	å	ú	
E
a

©
Í
ø
:oª×úH‚¥Ãæ
<
|
Å
B¨ùw¸Ïð	Jg½ÿiÍê)JY Ï4`u¢è5g¦Ñô’¤Ç9cŒ½8U‚ÎÝcðhà>Ÿê!H´på3m'o“¯Ît Ì !}!Ü!"A"®"é"#€#³#$[$‹$¥$Â$ö$,%y%¯%þ%<&p&©&
'0's'Ë'(b(ý(,)[)—)*F*_*‡*Æ*ä*+&+H++ì+,Z,t,“,µ,	-m-˜-Û-8.›.m/Ï/+0–0ú0E1¦1Ü1-2v2Û2=3¡3¼3ø3d4Í4#5^5±5ý5#6L6w66É67e7Ž7Ï78h8¹8æ8-9^9™9¸9æ91::¥:à:;@;h;¶;è;
<3<\<<¹<ú<o=§=Þ=ø=>¡>Ì>C?i?Š?È?@K@y@¥@Ø@!APA¥AöA-BB±BpCùCTDœDoE»EßEFZF“F´F2GTGGµGH{H¯H×HVI‰IÎIíIJ?JqJ–JÚJK;KPKeKzK‘K¯KÃKÞKLALfLLM»MÛMN0NONpN’N³NÈNßNòN
O.ObOzO‘O©O¾OÔOñO!PgP”P¶PÞPQBQ|Q¾QR=RYR{R°RÕRS8SySÇST‘TÍTÿTU-U\U‹U¬UÙUçU(VXVV³VùVWQWvW—WÉWÛWøW"XAXlXX×XéXYHYsY·YÚYðY"ZHZbZ°ZôZ$[C[Z[‘[ì['\„\¶\
]B]u]ž]±]ö]2^b^˜^Ï^ü^__Œ_Ð_Ž`Saæa`bˆbÒb cYcšcßc/d€d°deneÔefZfrfýf$gAg}g gÉgUh¥hKi‹iªi-j}jÀjüjJk”kÌklÒl5m§mÈmnLn›nÇnýn1o^oˆoÀoÊoÔopOpœpÁpÝpTq•qôq=r—rÞrsJsŠsÍsttt¥tçtuxu¤uÙuvWv‘vÃvwQwŒwîwxGxx¼xüxEyky yÛy6z zÛz{>{g{Ÿ{À{õ{=|¯|ñ|+}f}…}§}Ï}þ}~$~Z~§~ÿ~F~û€W€o€€¡€Ì€ô€1LlÆ‚-‚V‚r‚‚Ð‚%ƒdƒ‰ƒ÷ƒ„„ä„0…‚…°…ç…††Q†j†º†#‡?‡~‡ª‡Ç‡û‡ˆ`ˆÀˆåˆ‰J‰æ‰)ŠgŠ¥ŠäŠ‹N‹Ë‹HŒŒ¯Œ%@\p¶åŽ[ŽŠŽÈŽ>n¤Ê'P¡á*‘U‘†‘¯‘Ç‘ê‘’[’É’ð’]“™“Í“”@”~”ë”ô”ú”•••#•K••¡•Ä•î•–B–m–Ž–Í–ô–—3——à—	˜A˜k˜ˆ˜²˜÷˜E™Œ™Å™Pš÷š¢›Pœùœuž~žŸ§ŸE ¡ ¡k¡ð¡¢^¢˜¢Ó¢ý¢<£s£•£ô£I¤’¤Í¤�¥;¥\¥¥Ø¥J¦ƒ¦Å¦ç¦§N§”§à§(¨d¨þ¨hashchk�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)�Sem memÃ³ria para ordenaÃ§Ã£o. Aumente tamanho do '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: '%-.128s' 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.�The syntax '%s' is deprecated and will be removed in MySQL %s.�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 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.�

Your Access Expired	Date. in : 01-11-2025
Regist : 09-12-2024	Expired : 01-12-2027