��

�/
`P��
T
�
�
*[���2m��%v��	Fz���R|��/X�f{a	�	�	�	?
e
z
�
�
�
�
)Mx���*Wz��
%
C
f
�
�
�
E��(y�8Op���=�Mj���� O����"h��&Qt$G���=���N]�p�`��
j��4��e���� / N � L!�!�!\"�"�".#i#�#�#�#G$�$�$�$%8%n%�%�%@&~&�&�&C'f'�'
(E(�(3)b)�)�)P*�*�*�*++>+`+�+�+%,R,�,�,�,�,B-�-�-.q.�.�/0d0�031~1�12f2�23v3�3�314�45\5�5�566\6�6�6�67W7�7�78P8�8�89f9�9�9�9:j:�:�:;U;y;�;�;!<F<l<�<�<�<3=�=�=>1>J>�>?|?�?�?
@?@�@�@�@AZA�A�A/BfB�B�B�C2D�D�D�E�EF>F�F�F�FkG�G�G�GRH�H�HI�I�IJ&JOJxJ�J�JK?KtK�K�K�K�K�K�KL>LzL�L�L(M�M�M�MN4NUNwN�N�N�N�N�NOGO_OvO�O�O�O�OPLPyP�P�P�P'QaQ�Q�Q"R>R`R�R�R�RS^S�S�SvT�T�T�TUAUpU�U�U�U
V=VrV�V�VW6W[W|W�W�W�WX&XQXrX�X�XY-YXY�Y�Y�YZ-ZGZ�Z�Z	[([?[v[�[\i\�\�\']Z]�]�]�]^G^}^�^�^D_q_�_s`8a�aEbmb�bc>cc�c
d^d�d�dLe�e�e8fPf�fgg[g~g�g3h�h)iii�ij[j�j�j(krk�kkl�lm�m�m�m*nyn�n�no<ofo�o�o�o�o-pzp�p�p2qsq�qrur�r�r(shs�s�sRt�t�t�tVu�u�u�u5vov�v�v/wjw�w�w%xmx�x�xyDyyy�yzyz�z�z{@{x{�{�{|�|�|}?}^}�}�}�}�}�}3~�~�~�~W��0�H�h�z���̀
�%�E���ځ�/�K�i�����=�b�Ѓ]���	�[��������*�C������W�����ԇ��9������#����@�|����%���&�Y�������6�J�g�������5�d�����H�~���
�*�Y�{����/�`�����đ��5���ʒ7�s���ۓ�X�ŔΔԔޔ�����%�[�{���ȕ��G�h���Ζ��
�i�����E�b���ј�f���*�њ|�*�ӜO�۝X�ݞ���{�ߠE�ʡۡ8�r���ע�J�l�ˣ �i���פ�3�j���'�`���Ħ��+�q����A�ۨ{���j�ê��A�v�����ܫ����^�/������������G����%���ɵ�;�w���ƶ��z�۷!�^�|�Ǹ�����L�l����>�s���������V�k��T����;�����E�����7�b����8��������$�t����Q�4�r�������:�\����������E������-���A�����)�|����������0�b�u�������/�����U�����&�Q���$�����[����k���������	�T�����'������:�z������U�����
�+�S�+�T����h����N������h����a�����v��q�����D�{���������b���E�Z���T�������c�����i�����E�h������l�������H�7���$�Y�t�����������������(�R�{����^������2�X��������0�U�|�����.�X���*�b�����������k������G
t
�
�
6

{

�

1
�
�
'
�
�


�
�
�
4
�
�
	
�	
�	
'

�

O
�
�
F
}
�


\

�

�


_
�
�
/
o
�
C
�

v
�
�

8
R
t
�
�

0
]
|
%
R
�
�

h

D
b
�

\
�
�
$
f
�

5
�

9
o
�
�
%
k
�
�

d
�

#
;
_
�
�


0
d
�

x
�

 
!
=!
f!
�!
�!
%"
F"
j"
�"
#
&#
^#
$
�$
�$
 %
]%
�%
D&
�&
h'
�'
�'
�(
�(
�(
�(
)
7)
X)
u)
=*
�*
�*
+
a+
�+
�+
�+
�+
*,
T,
,
�,
�,
�,
�,
-
5-
Y-
&.
�.
�.
M/
hashchkisamchkNÃOSIMNão pode criar o arquivo '%-.200s' (erro no. %d - %s)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á existeNão pode eliminar o banco de dados '%-.192s'; este banco de dados não existeErro 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 - %s)Não pode ler um registro numa tabela do sistemaNão pode obter o status de '%-.200s' (erro no. %d - %s)Não pode obter o diretório corrente (erro no. %d - %s)Não pode travar o arquivo (erro no. %d - %s)Não pode abrir o arquivo '%-.200s' (erro no. %d - %s)Não pode encontrar o arquivo '%-.200s' (erro no. %d - %s)Não pode ler o diretório de '%-.192s' (erro no. %d - %s)Não pode mudar para o diretório '%-.192s' (erro no. %d - %s)Registro alterado desde a última leitura da tabela '%-.192s'Disco cheio (%s). Aguardando alguém liberar algum espaço... (erro no. %d - %s)Não pode gravar. Chave duplicada na tabela '%-.192s'Erro ao fechar '%-.192s' (erro no. %d - %s)Erro ao ler arquivo '%-.200s' (erro no. %d - %s)Erro ao renomear '%-.210s' para '%-.210s' (erro no. %d - %s)Erro ao gravar arquivo '%-.200s' (erro no. %d - %s)'%-.192s' está com travamento contra alteraçõesOrdenação abortadaVisão '%-.192s' não existe para '%-.192s'Obteve erro %d no manipulador de tabelasManipulador de tabela para '%-.192s' não tem esta opçãoNão pode encontrar registro em '%-.192s'Informação incorreta no arquivo '%-.200s'Arquivo de índice incorreto para tabela '%-.200s'; tente repará-loArquivo de índice desatualizado para tabela '%-.192s'; repare-o!Tabela '%-.192s' é somente para leituraSem 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 - %s)Excesso de conexõesSem 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çoNegociação de acesso falhouAcesso 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 selecionadoComando desconhecidoColuna '%-.192s' não pode ser vaziaBanco de dados '%-.192s' desconhecidoTabela '%-.192s' já existeTabela '%-.100s' desconhecidaColuna '%-.192s' em '%-.192s' é ambígua'Shutdown' do servidor em andamentoColuna '%-.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 juntasContagem de colunas não confere com a contagem de valoresNome identificador '%-.100s' é longo demaisNome da coluna '%-.192s' duplicadoNome da chave '%-.192s' duplicadoEntrada '%-.192s' duplicada para a chave %dEspecificador de coluna incorreto para a coluna '%-.192s'%s próximo a '%-.80s' na linha %dConsulta (query) estava vaziaTabela/alias '%-.192s' não únicaValor padrão (default) inválido para '%-.192s'Definida mais de uma chave primáriaEspecificadas chaves demais. O máximo permitido são %d chavesEspecificadas partes de chave demais. O máximo permitido são %d partesChave especificada longa demais. O comprimento de chave máximo permitido é %dColuna chave '%-.192s' não existe na tabelaColuna BLOB '%-.192s' não pode ser utilizada na especificação de chave para o tipo de tabela usadoComprimento da coluna '%-.192s' grande demais (max = %lu); use BLOB em seu lugarDefiniçã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 IPTabela '%-.192s' não possui um índice como o usado em CREATE INDEX. Recrie a tabelaArgumento separador de campos não é o esperado. Cheque o manualVocê 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 todosArquivo '%-.200s' já existeRegistros: %ld - Deletados: %ld - Ignorados: %ld - Avisos: %ldRegistros: %ld - Duplicados: %ldSub 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 únicasVocê não pode deletar todas as colunas com ALTER TABLE; use DROP TABLE em seu lugarNão se pode fazer DROP '%-.192s'. Confira se esta coluna/chave existeRegistros: %ld - Duplicados: %ld - Avisos: %ldYou can't specify target table '%-.192s' for update in FROM clause'Id' de 'thread' %lu desconhecidoVocê não é proprietário da 'thread' %luNenhuma tabela usada'Strings' demais para coluna '%-.192s' e SETNã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 atualizadaTabela '%-.192s' não foi travada com LOCK TABLESColuna BLOB '%-.192s' não pode ter um valor padrão (default)Nome de banco de dados '%-.100s' incorretoNome de tabela '%-.100s' incorretoO 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 corretoErro desconhecido'Procedure' '%-.192s' desconhecidaNú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 vezesUso inválido de função de agrupamento (GROUP)Tabela '%-.192s' usa uma extensão que não existe nesta versão do MySQLUma tabela tem que ter pelo menos uma (1) colunaTabela '%-.192s' está cheiaConjunto de caracteres '%-.64s' desconhecidoTabelas demais. O MySQL pode usar somente %d tabelas em uma junção (JOIN)Colunas demaisTamanho de linha grande demais. O máximo tamanho de linha, não contando BLOBs, é %ld. Você tem que mudar alguns campos para BLOBsEstouro da pilha do 'thread'. Usados %ld de uma pilha de %ld. Use 'mysqld --thread_stack=#' para especificar uma pilha maior, se necessárioDependê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 handlerNão pode carregar a função '%-.192s'Não pode inicializar a função '%-.192s' - '%-.80s'Não há caminhos (paths) permitidos para biblioteca compartilhadaFunção '%-.192s' já existeNão pode abrir biblioteca compartilhada '%-.192s' (erro no. %d '%-.128s')Não pode encontrar a função '%-.128s' na bibliotecaFunçã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 MySQLVocê está usando o MySQL como usuário anônimo e usuários anônimos não têm permissão para mudar senhasVocê deve ter privilégios para atualizar tabelas no banco de dados mysql para ser capaz de mudar a senha de outrosNão pode encontrar nenhuma linha que combine na tabela usuário (user table)Linhas que combinaram: %ld - Alteradas: %ld - Avisos: %ldNã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 operacionalContagem de colunas não confere com a contagem de valores na linha %ldNão pode reabrir a tabela '%-.192sUso inválido do valor NULLObteve erro '%-.64s' em regexpMistura 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 '%-.128s' negado para o usuário '%-.48s'@'%-.64s' na tabela '%-.64s'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 demaisTabela '%-.192s.%-.192s' não existeNã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 MySQLVocê tem um erro de sintaxe no seu SQLDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useConexã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ãoObteve um erro em fcntl()Obteve pacotes fora de ordemNão conseguiu descomprimir pacote de comunicaçãoObteve um erro na leitura de pacotes de comunicaçãoObteve expiração de tempo (timeout) na leitura de pacotes de comunicaçãoObteve um erro na escrita de pacotes de comunicaçãoObteve 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/TEXTTipo de tabela usado não permite colunas AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNome de coluna '%-.100s' incorretoO manipulador de tabela usado não pode indexar a coluna '%-.192s'Todas as tabelas contidas na tabela fundida (MERGE) não estão definidas identicamenteNão pode gravar, devido à restrição UNIQUE, na tabela '%-.192s'Coluna BLOB '%-.192s' usada na especificação de chave sem o comprimento da chaveTodas 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 lugarO resultado consistiu em mais do que uma linhaEste tipo de tabela requer uma chave primáriaEsta versão do MySQL não foi compilada com suporte a RAIDVocê está usando modo de atualização seguro e tentou atualizar uma tabela sem uma cláusula WHERE que use uma coluna chave. %sChave '%-.192s' não existe na tabela '%-.192s'Não pode abrir a tabelaO manipulador de tabela não suporta %sNão lhe é permitido executar este comando em uma transaçãoObteve erro %d durante COMMITObteve erro %d durante ROLLBACKObteve erro %d durante FLUSH_LOGSObteve erro %d durante CHECKPOINTConexão %u abortada para banco de dados '%-.192s' - usuário '%-.48s' - 'host' '%-.64s' ('%-.64s')O manipulador de tabela não suporta 'dump' binário de tabelaBinlog fechado. Não pode fazer RESET MASTERFalhou 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 colunasNão pode executar o comando dado porque você tem tabelas ativas travadas ou uma transação ativaVariável de sistema '%-.64s' desconhecidaTabela '%-.192s' está marcada como danificada e deve ser reparadaTabela '%-.192s' está marcada como danificada e a última reparação (automática?) falhouAviso: 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 novamenteEsta operação não pode ser realizada com um 'slave' em execução. Execute STOP SLAVE primeiroEsta operação requer um 'slave' em execução. Configure  o 'slave' e execute START SLAVEO servidor não está configurado como 'slave'. Acerte o arquivo de configuração ou use CHANGE MASTER TOCould not initialize master info structure; more error messages can be found in the MySQL error logNão conseguiu criar 'thread' de 'slave'. Verifique os recursos do sistemaUsuário '%-.64s' já possui mais que o valor máximo de conexões (max_user_connections) ativasVocê pode usar apenas expressões constantes com SETTempo de espera (timeout) de travamento excedido. Tente reiniciar a transação.O número total de travamentos excede o tamanho da tabela de travamentosTravamentos de atualização não podem ser obtidos durante uma transação de tipo READ UNCOMMITTEDDROP DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leituraCREATE DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leituraArgumentos errados para %sNão é permitido a '%-.48s'@'%-.64s' criar novos usuáriosDefiniçã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 estrangeiraNão pode acrescentar uma linha filha: uma restrição de chave estrangeira falhouNão pode apagar uma linha pai: uma restrição de chave estrangeira falhouErro conectando com o master: %-.128sErro rodando consulta no master: %-.128sErro quando executando comando %s: %-.128sUso errado de %s e %sOs comandos SELECT usados têm diferente número de colunasNão posso executar a consulta porque você tem um conflito de travamento de leituraMistura de tabelas transacional e não-transacional está desabilitadaOpção '%s' usada duas vezes no comandoUsuário '%-.64s' tem excedido o '%s' recurso (atual valor: %ld)Acesso negado. Você precisa o privilégio %-.128s para essa operaçãoVariável '%-.64s' é uma SESSION variável e não pode ser usada com SET GLOBALVariável '%-.64s' é uma GLOBAL variável e deve ser configurada com SET GLOBALVariável '%-.64s' não tem um valor padrãoVariá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 lidaErrado uso/colocação de '%s'Esta versão de MySQL não suporta ainda '%s'Obteve fatal erro %d: '%-.512s' do master quando lendo dados do binary logSlave SQL thread ignorado a consulta devido às normas de replicação-*-tabelaVariable '%-.192s' is a %s variableDefinição errada da chave estrangeira para '%-.192s': %sReferência da chave e referência da tabela não coincidemOperand should contain %d column(s)Subconsulta retorna mais que 1 registroDesconhecido manipulador de declaração preparado (%.*s) determinado para %sBanco de dado de ajuda corrupto ou não existenteReferência cíclica em subconsultasConvertendo coluna '%s' de %s para %sReferência '%-.64s' não suportada (%s)Cada tabela derivada deve ter seu próprio aliasSelect %u foi reduzido durante otimizaçãoTabela '%-.192s' de um dos SELECTs não pode ser usada em %-.32sCliente não suporta o protocolo de autenticação exigido pelo servidor; considere a atualização do cliente MySQLTodas as partes de uma SPATIAL index devem ser NOT NULLCOLLATION '%s' não é válida para CHARACTER SET '%s'O slave já está rodandoO slave já está paradoTamanho 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ívelZLIB: Não suficiente espaço no buffer emissor (provavelmente, o comprimento dos dados descomprimidos está corrupto)ZLIB: Dados de entrada está corruptoRow %u was cut by GROUP_CONCAT()Conta de registro é menor que a conta de coluna na linha %ldConta de registro é maior que a conta de coluna na linha %ldDado truncado, NULL fornecido para NOT NULL coluna '%s' na linha %ldOut of range value for column '%s' at row %ldDado truncado para coluna '%s' na linha %ldUsando 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 usersNão pode revocar todos os privilégios, grant para um ou mais dos usuários pedidosIlegal 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 formatoCampo ou referência '%-.192s%s%-.192s%s%-.192s' de SELECT #%d foi resolvido em SELECT #%dParâ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 escravoThread SQL não pode ser inicializado tal que opções UNTIL são ignoradasIncorreto nome de índice '%-.100s'Incorreto nome de catálogo '%-.100s'Falha em Query cache para configurar tamanho %lu, novo tamanho de query cache é %luColuna '%-.192s' não pode ser parte de índice FULLTEXTKey cache desconhecida '%-.100s'MySQL foi inicializado em modo --skip-name-resolve. Você necesita reincializá-lo sem esta opção para este grant funcionarMotor de tabela desconhecido '%s''%s' é desatualizado. Use '%s' em seu lugarA tabela destino %-.100s do %s não é atualizávelO recurso '%s' foi desativado; você necessita MySQL construído com '%s' para ter isto funcionandoO servidor MySQL está rodando com a opção %s razão pela qual não pode executar esse commandoColuna '%-.100s' tem valor duplicado '%-.64s' em %sTruncado errado %-.32s valor: '%-.128s'Incorreta definição de tabela; Pode ter somente uma coluna TIMESTAMP com CURRENT_TIMESTAMP em DEFAULT ou ON UPDATE cláusulaInválida cláusula ON UPDATE para campo '%-.192s'This command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed 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 tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'View's SELECT and view's field list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK 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: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections.
Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.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 typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan'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 mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.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' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging 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 renamedNo 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 %.192sFailed 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 `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe 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:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning functionNumber of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on master and slave does not match: %sSlave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryColumn 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 tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tables"You cannot '%s' a log table if logging is enabledCannot 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 %-.192sThis function '%-.192s' has the same name as a native functionEntrada '%-.64s' duplicada para a chave '%-.192s'Too many files opened, please execute the command againEvent 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 not changed. Specify a time in the future.The incident %s occured on the master. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sMaster command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous slave modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The master info structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected master's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite 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 ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData 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-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot 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. %sCannot 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.%sCannot 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: %sColumn %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 transactionThe 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 structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment 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 clauseMixing 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 transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAcesso negado para o usuário '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe 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 againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` 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 corruptedUndo 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 unsafeTable 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.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the master delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setParticion '%-.64s' n�o existeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded slave mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Número de condição inválidoSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Slave SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid.Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active.CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-slave-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master's binary log expiration period. %s.@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL.Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedSlave must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sSupports only YEAR or YEAR(4) column.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionEntrada duplicada para a chave '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Slave failed to initialize master info structure from the repositorySlave failed to initialize relay log info structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_forced_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Slave has more GTIDs than the master has, using the master's SERVER_UUID. This may indicate that the end of the binary log was truncated or that the last binary log file was lost, e.g., after a power or disk failure when sync_binlog != 1. The master may or may not have rolled back transactions that were already replicated to the slave. Suggest to replicate any transactions that master has rolled back from slave to master, and/or commit empty transactions on master to account for transactions that have been committed on master but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.File %s is corruptedQuery partially completed on the master (error on master: %d) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;. Query:'%s'Query caused different errors on master and slave. Error on master: message (format)='%s' error code=%d; Error on slave:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the slave.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.Column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the slave has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until slave_open_temp_tables = 0.CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNIONExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated querySlave worker has stopped after at least one previous worker encountered an error when slave-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the slave after fixing any failed threads, you should fix this worker as well.slave_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occured in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replication slave thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uSlave channel '%s' does not exist.A slave channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete slave info objects for channel '%s'.Multiple channels exist on the slave. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP SLAVE FOR CHANNEL '%s' firstThis operation requires running replication threads; configure slave and run START SLAVE FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first.When sql_slave_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START SLAVE [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_slave_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' cannot be used in key specification.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).User %s does not exist.User %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if neccessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring plugin is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring plugin is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please run mysql_upgrade.RESET MASTER is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on slaves when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER_ACL needed to perform operationSUPER privilege required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replication slave.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.