Spade
Mini Shell
���1o ��=�2/9KOMW-144)266:>L6',8/3,,@*,EB)LpL2 D:&%& *$+# 5;-#",:# #1%@IP-CQ~*!A VBid ?!�VI/`"--FM2+#�#>4*)1L1 -N��xx(6C J7'oOquN:�H$ �XE[^@%m=(o3RV0 46M6O>9>d#-XDS�//>0(?
""l-A "Td*C]c�v\kqKa6PIebd4kh[ESL&)+<UG)AHQQ-G1; 0KP$;<$(N2%&)1,Aw87�+w&>>E.,3I/UQ7c!��[H�L$&V9!�"-4fd4(3E ))2%D,5 '<%'��
= !"!$4 0F-"(-7:BP7&"5%/4ANH�<2 ;/!-S05&>"6%!2 * +!L2-+D#2&ND0 7[;]2W53)E<067-c-D���y'IN8:>OQ0__fH>�' 5#)�P�@�PC;NJ8�EcW!F0N
66-*8
A:M% wG_IZG75@CFa"B1`,5F8:2P@;b'2H-@%&5;[j;>%)8!5HrB:; "(/6MX38} <
+(=
,) @W?$�`L.7'2Pi ?, 4!D4%02�C>>?28|�80f )%,6%45-&1Z)/"@I+1%#3>n'l44>=m
(6
#*)++!?'&\K)8* *ENG9�����{�|���[ce�]:;);7!_UI;3;!7Jq9B"7(?LH<��WkT;B54������
�V/b8Eh<:8<-".�aF=JM�>-1>?R5��7
F�|m_=INnr;hL* &�SzS^<9FH�G���z 4=�@7?>{��dW.# *S,EED6fi?)i"�K\[SK^g �>08_*,�/( @31UL09!(�)i,g"�94a9JlEH] ��b `C6:?M05-B4>4,:.\[O`>M`0-<?+.A^@�D���Udu !KL�(#>3;74.+/6
@B-<�20>oA;�2QY#C*3d6 t��5ZNk=1(rB+-*)GMOT)1&&0,(%)%'+,[*�Q8D&,+7?J37PAA>C7&/?(2%1),'-4E#P?9(BL<IOf<IYCN4MDD/DV!$%;y�p�L|P��J*.>�7:6B6F:2.C72%<9&." �eB? BC->?LNY"/>6?,a :+jk*62"'4;V6+H>! &*`+QOF-8<0>`d&2.5 !;:A5 #@X!nQ1A-%)Q)(-)PP;I��hashchkisamchkNÃOSIMNão
pode criar o arquivo '%-.200s' (erro no. %M)Não pode criar a
tabela %`s.%`s (erro no. %M)Não pode criar o banco de dados
'%-.192s' (erro no. %M)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.
%M)Erro ao eliminar banco de dados (não pode remover diretório
'%-.192s' - erro no. %M)Erro na remoção de '%-.192s'
(erro no. %M)Não pode ler um registro numa tabela do sistemaNão pode
obter o status de '%-.200s' (erro no. %M)Não pode obter o
diretório corrente (erro no. %M)Não pode travar o arquivo (erro no.
%M)Não pode abrir o arquivo '%-.200s' (erro no. %M)Não pode
encontrar o arquivo '%-.200s' (erro no. %M)Não pode ler o
diretório de '%-.192s' (erro no. %M)Não pode mudar para o
diretório '%-.192s' (erro no. %M)Registro alterado desde a
última leitura da tabela '%-.192s'Disco cheio (%s). Aguardando
alguém liberar algum espaço... (erro no. %M)Não pode gravar. Chave
duplicada na tabela '%-.192s'Erro ao fechar '%-.192s'
(erro no. %M)Erro ao ler arquivo '%-.200s' (erro no. %M)Erro ao
renomear '%-.210s' para '%-.210s' (erro no. %M)Erro ao
gravar arquivo '%-.200s' (erro no. %M)'%-.192s' está
com travamento contra alteraçõesOrdenação abortadaVisão
'%-.192s' não existe para '%-.192s'Obteve erro %M no
manipulador de tabelas %sStorage engine %s of the table %`s.%`s
doesn't have this optionNã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çãoEncontrado fim de
arquivo inesperado ao ler arquivo '%-.192s' (erro no. %M)Excesso
de conexõesSem memória.Não pode obter nome do 'host' para seu
endereçoNegociação de acesso falhouAcesso negado para o usuário
'%s'@'%s' ao banco de dados '%-.192s'Acesso
negado para o usuário '%s'@'%s' (senha usada:
%s)Nenhum banco de dados foi selecionadoComando desconhecidoColuna
'%-.192s' não pode ser vaziaBanco de dados '%-.192s'
desconhecidoTabela '%-.192s' já existeTabela '%-.100T'
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 '%-.100T' é longo demaisNome da coluna
'%-.192s' duplicadoNome da chave '%-.192s'
duplicadoEntrada '%-.192T' duplicada para a chave %dEspecificador
de coluna incorreto para a coluna '%-.192s'%s próximo a
'%-.80T' 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 tabelaBLOB column %`s can't be used
in key specification in the %s tableComprimento 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 chaveCould not delete
gtid domain. Reason: %s.%s (%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
limitadoArquivo '%-.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 %s %`-.192s. Confira se esta
coluna/chave existeRegistros: %ld - Duplicados: %ld - Avisos: %ldTable
'%-.192s' is specified twice, both as a target for '%s'
and as a separate source for data'Id' de 'thread' %lu
desconhecidoVocê não é proprietário da 'thread' %lldNenhuma
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 TABLESYou
should never see itNome de banco de dados '%-.100T' 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 MariaDBUma tabela tem que
ter pelo menos uma (1) colunaTabela '%-.192s' está cheiaConjunto
de caracteres '%-.64s' desconhecidoTabelas demais. O MariaDB 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 'mariadbd
--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 'mariadb-admin flush-hosts''Host'
'%-.64s' não tem permissão para se conectar com este servidor
MariaDBVocê está usando o MariaDB 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. %M). 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 %luNão pode
reabrir a tabela '%-.192sUso inválido do valor NULLObteve erro
'%s' 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 '%-.100T' negado para o usuário
'%s'@'%s' na tabela %`s.%`sComando '%-.32s'
negado para o usuário '%s'@'%s' na coluna
'%-.192s', na tabela '%-.192s'Comando GRANT/REVOKE
ilegal. Por favor consulte no manual quais privilégios podem ser
usadosArgumento 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 MariaDBVocê 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
usoConexã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 (%s) não
permite colunas BLOB/TEXTTipo de tabela usado (%s) não permite colunas
AUTO_INCREMENTINSERT DELAYED não pode ser usado com a tabela
'%-.192s', porque ela está travada com LOCK TABLESNome de coluna
'%-.100s' incorretoThe storage engine %s can't index column
%`sTodas 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 MariaDB 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 chaveChave '%-.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 %M durante COMMITObteve erro %M durante
ROLLBACKObteve erro %M durante FLUSH_LOGSObteve erro %M durante
CHECKPOINTConexão %lld abortada para banco de dados '%-.192s' -
usuário '%-.48s' - 'host' '%-.64s'%-.64s
('%-.64s')You should never see itBinlog 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 '%-.*s' 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 mariadbd e
tente novamenteEsta operação não pode ser realizada com um
'slave' '%2$*1$s' em execução. Execute STOP SLAVE
'%2$*1$s' 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 for '%.*s'; more error messages can be found in the
MariaDB 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çãoO 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
'%s'@'%s' criar novos usuáriosDefinição incorreta da
tabela. Todas as tabelas contidas na junção devem estar no mesmo banco de
dadosEncontrado um travamento fatal (deadlock) quando tentava obter uma
trava. Tente reiniciar a transaçãoO tipo de tabela utilizado (%s) não
suporta índices de texto completo (fulltext indexes)Não pode acrescentar
uma restrição de chave estrangeira para `%s`Nã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
'%-.200T'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 MariaDB não suporta ainda '%s'Obteve fatal erro %d:
'%-.320s' 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 MariaDBTodas 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 %s)Conta de
registro é menor que a conta de coluna na linha %luConta de registro é
maior que a conta de coluna na linha %luDado truncado, NULL fornecido para
NOT NULL coluna '%s' na linha %luOut of range value for column
'%s' at row %luDado truncado para coluna '%s' na linha
%luUsando 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 MariaDB foi compilado sem o SSL suporte. Os mesmos podem ser
usados mais tarde quando o escravo MariaDB 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 mariadbd 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 %llu, novo tamanho de query cache é
%luColuna '%-.192s' não pode ser parte de índice FULLTEXTKey
cache desconhecida '%-.100s'MariaDB 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 MariaDB construído com
'%s' para ter isto funcionandoO servidor MariaDB 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 %-.32T valor: '%-.128T'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 '%-.200s' from %sGot temporary error %d
'%-.200s' from %sUnknown or incorrect time zone:
'%-.64s'Invalid TIMESTAMP value in column '%s' at row
%luInvalid %s character string: '%.64T'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. This option will be removed in MariaDB 5.6The 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 MariaDB
5.6Query 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'ANALYZE/EXPLAIN/SHOW can not
be issued; lacking privileges for underlying tableFile '%-.192s'
has unknown type '%-.64s' in its
header'%-.192s.%-.192s' is not of type '%s'Column
'%-.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 '%s' already existsTrigger does
not existTrigger's '%-.192s' is a view, temporary table or
sequenceUpdating 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: '%-.128T' for column
`%.192s`.`%.192s`.`%.192s` at row %luIllegal %s '%-.192T' value
found during parsingCHECK OPTION on non-updatable view
%`-.192s.%`-.192sCHECK OPTION failed %`-.192s.%`-.192s%-.32s command denied
to user '%s'@'%s' 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 MariaDB 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: %MWrong 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 %luBad 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: '%-.128T' 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 itThe
statement (%lu) has no open cursorExplicit or implicit commit is not
allowed in stored function or triggerField of view
'%-.192s.%-.192s' underlying table doesn't have a default
valueRecursive stored functions and triggers are not allowedToo big scale
%llu specified for '%-.192s'. Maximum is %uToo big precision %llu
specified for '%-.192s'. Maximum is %uFor 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. Consider increasing the thread_stack
system variable.Routine body for '%-.100s' is too longCannot drop
default keycacheDisplay width out of range for '%-.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/triggerThe 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
triggerInvalid definerView '%-.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 allowedCannot
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 (internal code %d). For more details, run SHOW
WARNINGSIncorrect routine name '%-.192s'Upgrade required. Please
do "REPAIR %s %`s" or dump/reload to fix it!AGGREGATE is not
supported for stored functionsCan't create more than
max_prepared_stmt_count statements (current value: %u)%`s.%`s contains view
recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe
storage engine %s 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 '%-.70T' 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 BYNão foi possível criar o servidor externo
'%s' porque ele já existeThe 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 %s 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 MariaDBFor 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 possiblePartitioned tables do not support
%sError 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: '%-.128T'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 %M from storage engineUnknown
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 providedYou should
never see itYou should never see itFailed 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 MariaDB %s. Please use
%s insteadYou can't write-lock a log table. Only read access is
possibleYou can't use locks with log tablesYou should never see
itColumn count of mysql.%s is wrong. Expected %d, found %d. Created with
MariaDB %d, now running %d. Please use mariadb-upgrade to fix this
errorCannot 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 triggerYou should never see itCannot 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 '%-.192T' for key '%-.192s'Internal
scheduler error %dError during starting/stopping of the scheduler. Error
code %MEngine 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 event
scheduler is disabledOnly integers allowed as number hereStorage engine %s
cannot be used for log tablesYou 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 '%-.192s'This function
'%-.192s' has the same name as a native functionEntrada
'%-.64T' 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 creationEvent execution time is in the past and ON COMPLETION NOT
PRESERVE is set. The event was not changed. Specify a time in the futureThe
incident %s occurred on the master. Message: %-.64sTable 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 %`s.%`s
has no creation contextCreation context of view %`s.%`s is invalidCreation
context of stored routine %`s.%`s is invalidCorrupted TRG file for table
%`s.%`sTriggers for table %`s.%`s have no creation contextTrigger creation
context of table %`s.%`s is invalidCreation context of event %`s.%`s is
invalidCannot open table for trigger %`s.%`sCannot create stored routine
%`s. Check warningsYou should never see itThe BINLOG statement of type %s
was not preceded by a format description BINLOG statementCorrupted
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'There
is no master connection '%.*s'<%-.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 (%u seconds)You
should never see itError in parsing conflict function. Message: %-.64sWrite
to exceptions table failed. Message: %-.128s"Comentário para a tabela
'%-.64s' é longo demais (max = %u)Comentário para o campo
'%-.64s' é longo demais (max = %u)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; set query_cache_type to
ON or DEMAND 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 involvedCannot
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
loggingCannot 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 loggingCannot 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 = STATEMENTCannot execute
statement: impossible to write to binary log since more than one engine is
involved and at least one engine is self-loggingThe statement is unsafe
because it uses a LIMIT clause. This is unsafe because the set of rows
included cannot be predictedThe statement is unsafe because it uses INSERT
DELAYED. This is unsafe because the times when rows are inserted cannot be
predictedThe 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 slavesStatement is unsafe because it invokes a trigger
or a stored function that inserts into an AUTO_INCREMENT column. Inserted
values cannot be logged correctlyStatement is unsafe because it uses a UDF
which may not return the same value on the slaveStatement is unsafe because
it uses a system variable that may have a different value on the
slaveStatement is unsafe because it uses a system function that may return
a different value on the slaveStatement 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
'%-.50s' to type '%-.50s'Can't create conversion
table for table '%-.192s.%-.192s'Cannot modify
@@session.binlog_format inside a transactionThe path specified for %.64T is
too long'%s' is deprecated and will be removed in a future
releaseNative table '%-.64s'.'%-.64s' has the wrong
structureInvalid performance_schema usageTable
'%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 unsafeStatement
accesses nontransactional table as well as transactional or temporary
table, and writes to any of themCannot 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
'%s'@'%s'SET PASSWORD is ignored for users
authenticating via %s pluginGRANT 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 disabledThe 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
timeoutMulti-row statements required more than
'max_binlog_stmt_cache_size' bytes of storage.Primary
key/partition key update is not allowed since the table is updated both as
'%-.192s' and '%-.192s'Table rebuild required. Please
do "ALTER TABLE %`s 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 bytesTrigger
'%-.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 bigINSERT 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 slaveINSERT... 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 slaveREPLACE... 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 slaveCREATE... 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
slaveCREATE... 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 slaveUPDATE
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 slaveYou should never see itYou should never see
itStatements 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 slaveCREATE 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 slaveINSERT... ON DUPLICATE KEY UPDATE on a table with more than
one UNIQUE KEY is unsafeYou should never see itNot allowed for
system-versioned table %`s.%`sINSERT into autoincrement field which is not
the first part in the composed primary key is unsafeCannot load from %s.%s.
The table is probably corruptedThe requested value %lu for the master delay
exceeds the maximum %luOnly 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_sizeCannot 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'Too long value for '%s'Replication
event checksum verification failed while reading from networkReplication
event checksum verification failed while reading from a log fileOption
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_sizeCan't update table '%-.192s' while
'%-.192s' is being createdPARTITION () clause on non partitioned
tableFound a row not matching the given partition setYou should never see
itFailure while changing the type of replication repository: %sThe creation
of some temporary tables could not be rolled backSome 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 metadataCannot 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 tablesNúmero de condição
inválidoSending passwords in plain text without SSL/TLS is extremely
insecureStoring MariaDB user name or password information in the
master.info repository is not secure and is therefore not recommended.
Please see the MariaDB Manual for more about this issue and possible
alternativesForeign 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 startedThe table does not have FULLTEXT
index to support this queryThe system variable %.200s cannot be set in
stored functions or triggersThe system variable %.200s cannot be set when
there is an ongoing transactionThe system variable @@SESSION.GTID_NEXT has
the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LISTWhen
@@SESSION.GTID_NEXT_LIST == NULL, the system variable @@SESSION.GTID_NEXT
cannot change inside a transactionThe statement 'SET %.200s'
cannot invoke a stored functionThe system variable @@SESSION.GTID_NEXT
cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is
non-NULLSkipping transaction %.200s because it has already been executed
and loggedMalformed GTID set specification '%.200s'Malformed GTID
set encodingMalformed GTID specification '%.200s'Impossible to
generate Global Transaction Identifier: the integer component reached the
maximal value. Restart the server with a new server_uuidParameters
MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be
set when MASTER_AUTO_POSITION is activeCHANGE MASTER TO
MASTER_AUTO_POSITION = 1 can only be executed when GTID_MODE = ONCannot
execute statements with implicit commit inside a transaction when GTID_NEXT
!= AUTOMATIC or GTID_NEXT_LIST != NULLGTID_MODE = ON or GTID_MODE =
UPGRADE_STEP_2 requires ENFORCE_GTID_CONSISTENCY = 1GTID_MODE = ON or
UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and
--log-slave-updatesGTID_NEXT cannot be set to UUID:NUMBER when GTID_MODE =
OFFGTID_NEXT cannot be set to ANONYMOUS when GTID_MODE = ONGTID_NEXT_LIST
cannot be set to a non-NULL value when GTID_MODE = OFFFound a
Gtid_log_event or Previous_gtids_log_event when GTID_MODE = OFFWhen
ENFORCE_GTID_CONSISTENCY = 1, 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
tablesCREATE TABLE ... SELECT is forbidden when ENFORCE_GTID_CONSISTENCY =
1When ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE
and DROP TEMPORARY TABLE can be executed in a non-transactional context
only, and require that AUTOCOMMIT = 1The value of GTID_MODE can only change
one step at a time: OFF <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2
<-> 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 requiresGTID_NEXT
cannot be changed by a client that owns a GTID. The client owns %s.
Ownership is released on COMMIT or ROLLBACKUnknown %s format name:
'%s'Cannot execute statement in a READ ONLY transactionComment
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 MariaDB error logInnoDB 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 againUnknown 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 UNTILCannot recover after SLAVE errored out in parallel execution
mode. Additional error messages can be found in the MariaDB error logCannot
clean up worker info tables. Additional error messages can be found in the
MariaDB error logColumn count of %s.%s is wrong. Expected %d, found %d. The
table is probably corruptedSlave must silently retry current transactionYou
should never see itSchema mismatch (%s)Table %-.192s in system tablespaceIO
Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing
for table '%-.192s'Tablespace for table '%-.192s'
exists. Please DISCARD the tablespace before IMPORTTablespace has been
discarded for table %`sInternal error: %-.192sALTER TABLE
'%-.192s' IMPORT TABLESPACE failed with error %lu :
'%s'Index corrupt: %sYEAR(%lu) column type is deprecated.
Creating YEAR(4) column insteadYour password does not satisfy the current
policy requirements (%s)You must SET PASSWORD before executing this
statementFailed to add the foreign key constraint. Missing index for
constraint '%s' in the foreign table '%s'Failed to add
the foreign key constraint. 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 %s constraint name '%s'The password hash
doesn't have the expected format. Check if the correct password
algorithm is being used with the PASSWORD() functionCannot drop column
'%-.192s': needed in a foreign key constraint
'%-.192s'Cannot drop column '%-.192s': needed in a
foreign key constraint '%-.192s' of table %-.192sColumn
'%-.192s' cannot be NOT NULL: needed in a foreign key constraint
'%-.192s' SET NULLDuplicate index %`s. This is deprecated and
will be disallowed in a future releaseCannot 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 packetRunning in read-only
modeWhen GTID_NEXT is set to a GTID, you must explicitly set it again after
a COMMIT or ROLLBACK. If you see this error message in the slave SQL
thread, it means that a table in the current transaction is transactional
on the master and non-transactional on the slave. In a client connection,
it means that you executed SET GTID_NEXT before a transaction and forgot to
set GTID_NEXT to a different identifier or to 'AUTOMATIC' after
COMMIT or ROLLBACK. Current GTID_NEXT is '%s'The system variable
%.200s cannot be set in stored proceduresGTID_PURGED can only be set when
GTID_MODE = ONGTID_PURGED can only be set when GTID_EXECUTED is
emptyGTID_PURGED can only be set when there are no ongoing transactions
(not even in other clients)GTID_PURGED was changed from '%s' to
'%s'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 %sCOPY algorithm requires a lockPartition
specific operations do not yet support LOCK/ALGORITHMColumns participating
in a foreign key are renamedCannot change column typeAdding 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
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 convert NULL to non-constant DEFAULTYour password has
expired. To log in you must change it using a client that supports expired
passwordsFound 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_maxCannot 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 filesfile %s was not purged because it
is the active log fileAuto-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). DisconnectingInnoDB is in read only modeSTOP SLAVE command
execution is incomplete: Slave SQL thread got the stop signal, thread is
busy, SQL thread will stop once the current task is completeSTOP SLAVE
command execution is incomplete: Slave IO thread got the stop signal,
thread is busy, IO thread will stop once the current task is
completeOperation cannot be performed. The table '%-.64s.%-.64s'
is missing, corrupt or contains bad dataTemporary file write failureUpgrade
index name failed, please use create index(alter table) algorithm copy to
rebuild index"You should never see itFunction or expression
'%s' cannot be used in the %s clause of %`sYou should never see
itPrimary key cannot be defined upon a generated columnKey/Index cannot be
defined on a virtual generated columnCannot define foreign key with %s
clause on a generated columnThe value specified for generated column
'%s' in table '%s' has been ignoredThis is not yet
supported for generated columnsYou should never see itYou should never see
it%s storage engine does not support generated columnsUnknown option
'%-.64s'Incorrect value '%-.64T' for option
'%-.64s'You should never see itYou should never see itYou should
never see itGot overflow when converting '%-.128s' to %-.32s.
Value truncatedTruncated value '%-.128s' when converting to
%-.32sEncountered illegal value '%-.128s' when converting to
%-.32sEncountered illegal format of dynamic column stringDynamic column
implementation limit reachedIllegal value used as argument of dynamic
column functionDynamic column contains unknown character setAt least one of
the 'in_to_exists' or 'materialization'
optimizer_switch flags must be 'on'Query cache is disabled
(resize or similar command in progress); repeat this command laterQuery
cache is globally disabled and you can't enable it only for this
sessionView '%-.192s'.'%-.192s' ORDER BY clause ignored
because there is other ORDER BY clause alreadyConnection was killedYou
should never see itCannot modify @@session.skip_replication inside a
transactionCannot modify @@session.skip_replication inside a stored
function or triggerQuery execution was interrupted. The query exceeded %s
%llu. The query result may be incompleteTable '%-.192s.%-.192s'
doesn't exist in engineTarget is not running an EXPLAINable
commandConnection '%.*s' conflicts with existing connection
'%.*s'Master '%.*s': Can't %s SLAVE
'%.*s'SLAVE '%.*s' startedSLAVE '%.*s'
stoppedEngine %s failed to discover table %`-.192s.%`-.192s with
'%s'Failed initializing replication GTID stateCould not parse
GTID listCould not update replication slave gtid stateGTID %u-%u-%llu and
%u-%u-%llu conflict (duplicate domain id %u)Failed to open %s.%sConnecting
slave requested to start from GTID %u-%u-%llu, which is not in the
master's binlogFailed to load replication slave GTID position from
table %s.%sSpecified GTID %u-%u-%llu conflicts with the binary log which
contains a more recent GTID %u-%u-%llu. If MASTER_GTID_POS=CURRENT_POS is
used, the binlog position will override the new value of
@@gtid_slave_posSpecified value for @@gtid_slave_pos contains no value for
replication domain %u. This conflicts with the binary log which contains
GTID %u-%u-%llu. If MASTER_GTID_POS=CURRENT_POS is used, the binlog
position will override the new value of @@gtid_slave_posSTART SLAVE UNTIL
master_gtid_pos requires that slave is using GTIDAn attempt was made to
binlog GTID %u-%u-%llu which would create an out-of-order sequence number
with existing GTID %u-%u-%llu, and gtid strict mode is enabledThe binlog on
the master is missing the GTID %u-%u-%llu requested by the slave (even
though a subsequent sequence number does exist), and GTID strict mode is
enabledUnexpected GTID received from master after reconnect. This normally
indicates that the master server was replaced without restarting the slave
threads. %sCannot modify @@session.gtid_domain_id or @@session.gtid_seq_no
inside a transactionCannot modify @@session.gtid_domain_id or
@@session.gtid_seq_no inside a stored function or triggerConnecting slave
requested to start from GTID %u-%u-%llu, which is not in the master's
binlog. Since the master's binlog contains GTIDs with higher sequence
numbers, it probably means that the slave has diverged due to executing
extra erroneous transactionsThis operation is not allowed if any GTID has
been logged to the binary log. Run RESET MASTER first to erase the
logUnknown query id: %lldBad base64 data as position %uInvalid role
specification %`sThe current user is invalidCannot grant role
'%s' to: %sCannot revoke role '%s' from: %sCannot
change @@slave_parallel_threads while another change is in progressCommit
failed due to failure of an earlier commit on which this one
depends'%-.192s' is a viewWhen using parallel replication and
GTID with multiple replication domains, @@sql_slave_skip_counter can not be
used. Instead, setting @@gtid_slave_pos explicitly can be used to skip to
after a given GTID positionThe definition for table %`s is too bigPlugin
'%-.192s' already installedQuery execution was interrupted
(max_statement_time exceeded)%s does not support subqueries or stored
functionsThe system variable %.200s cannot be set in SET STATEMENT.You
should never see itCan't create user
'%-.64s'@'%-.64s'; it already existsCan't drop
user '%-.64s'@'%-.64s'; it doesn't existCan't
create role '%-.64s'; it already existsCan't drop role
'%-.64s'; it doesn't existCannot convert '%s'
character 0x%-.64s to '%s'Incorrect default value
'%-.128T' for column '%.192s'You are not owner of query
%lldEngine-independent statistics are not collected for column
'%s'Aggregate function '%-.192s)' of SELECT #%d belongs
to SELECT #%d<%-.64s> option ignored for InnoDB partitionFile %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
MariaDB %d, now running %d. Please use mariadb-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.You should
never see itSelect 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 occurred 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: %-.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
indexThis error never happensThis error never happensWITH column list and
SELECT field list have different column countsToo many WITH elements in
WITH clauseDuplicate query name %`-.64s in WITH clauseNo anchors for
recursive WITH element '%s'Unacceptable mutual recursion with
anchored table '%s'Reference to recursive WITH table
'%s' in materialized derivedRestrictions imposed on recursive
definitions are violated for table '%s'Window specification with
name '%s' is not definedMultiple window specifications with the
same name '%s'Window specification referencing another one
'%s' cannot contain partition listReferenced window specification
'%s' already contains order listReferenced window specification
'%s' cannot contain window frameUnacceptable combination of
window frame bound specificationsWindow function is allowed only in SELECT
list and ORDER BY clauseWindow function is not allowed in window
specificationWindow frame is not allowed with '%s'No order list
in window specification for '%s'RANGE-type frame requires ORDER
BY clause with single sort keyInteger is required for ROWS-type
frameNumeric datatype is required for RANGE-type frameFrame exclusion is
not supported yetThis window function may not have a window frameArgument
of NTILE must be greater than 0CONSTRAINT %`s failed for
%`-.192s.%`-.192sExpression in the %s clause is too bigGot an error
evaluating stored expression %sGot an error when calculating default value
for %`sExpression for field %`-.64s is referring to uninitialized field
%`sOnly one DEFAULT partition allowedReferenced trigger '%s' for
the given action time and event type does not existDefault/ignore value is
not supported for such parameter usageOnly row based replication supported
for bulk operationsUncompress the compressed binlog failedBroken JSON
string in argument %d to function '%s' at position %dCharacter
disallowed in JSON in argument %d to function '%s' at position
%dUnexpected end of JSON text in argument %d to function
'%s'Syntax error in JSON text in argument %d to function
'%s' at position %dIncorrect escaping in JSON text in argument %d
to function '%s' at position %dLimit of %d on JSON nested
structures depth is reached in argument %d to function '%s' at
position %dUnexpected end of JSON path in argument %d to function
'%s'Syntax error in JSON path in argument %d to function
'%s' at position %dLimit of %d on JSON path depth is reached in
argument %d to function '%s' at position %dWildcards in JSON path
not allowed in argument %d to function '%s'JSON path should end
with an array identifier in argument %d to function '%s'Argument
2 to function '%s' must be "one" or
"all".InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED
or KEY_BLOCK_SIZE.Incorrect GeoJSON format specified for st_geomfromgeojson
function.Incorrect GeoJSON format - too few points for linestring
specified.Incorrect GeoJSON format - polygon not closed.Path expression
'$' is not allowed in argument %d to function '%s'.A
slave with the same server_uuid/server_id as this slave has connected to
the masterFlashback does not support %s %sKeys are out order during bulk
loadBulk load rows overlap existing rowsCan't execute updates on
master with binlog_format != ROW.MyRocks supports only READ COMMITTED and
REPEATABLE READ isolation levels. Please change from current isolation
level %sWhen unique checking is disabled in MyRocks, INSERT,UPDATE,LOAD
statements with clauses that update or replace the key (i.e. INSERT ON
DUPLICATE KEY UPDATE, REPLACE) are not allowed. Query: %sCan't execute
updates when you started a transaction with START TRANSACTION WITH
CONSISTENT [ROCKSDB] SNAPSHOT.This transaction was rolled back and cannot
be committed. Only supported operation is to roll it back, so all pending
changes will be discarded. Please restart another transaction.MyRocks
currently does not support ROLLBACK TO SAVEPOINT if modifying rows.Only
REPEATABLE READ isolation level is supported for START TRANSACTION WITH
CONSISTENT SNAPSHOT in RocksDB Storage Engine.Unsupported collation on
string indexed column %s.%s Use binary collation (%s).Table '%s'
does not exist, but metadata information exists inside MyRocks. This is a
sign of data inconsistency. Please check if '%s.frm' exists, and
try to restore it if it does not exist.Column family ('%s') flag
(%d) is different from an existing flag (%d). Assign a new CF flag, or do
not change existing CF flag.TTL duration (%s) in MyRocks must be an
unsigned non-null 64-bit integer.Status error %d received from RocksDB:
%s%s, Status error %d received from RocksDB: %sTTL support is currently
disabled when table has a hidden PK.TTL column (%s) in MyRocks must be an
unsigned non-null 64-bit integer, exist inside the table, and have an
accompanying ttl duration.The per-index column family option has been
deprecatedMyRocks failed creating new key definitions during alter.MyRocks
failed populating secondary key during alter.Window functions can not be
used as arguments to group functions.OK packet too largeIncorrect GeoJSON
format - empty 'coordinates' array.MyRocks doesn't currently
support collations with "No pad" attribute.Illegal parameter data
types %s and %s for operation '%s'Illegal parameter data type %s
for operation '%s'Incorrect parameter count to cursor
'%-.192s'Unknown structured system variable or ROW routine
variable '%-.*s'Row variable '%-.192s' does not have a
field '%-.192s'END identifier '%-.192s' does not match
'%-.192s'Sequence '%-.64s.%-.64s' has run outSequence
'%-.64s.%-.64s' has out of range value for optionsSequence
'%-.64s.%-.64s' table structure is invalid (%s)Sequence
'%-.64s.%-.64s' access errorSequences requires binlog_format
mixed or row'%-.64s.%-.64s' is not a SEQUENCE'%-.192s'
is not a SEQUENCEUnknown SEQUENCE: '%-.300s'Unknown VIEW:
'%-.300s'Wrong INSERT into a SEQUENCE. One can only do single
table INSERT into a sequence object (like with mariadb-dump). If you want
to change the SEQUENCE, use ALTER SEQUENCE instead.At line %u in
%sSubroutine '%-.192s' is declared in the package specification
but is not defined in the package bodySubroutine '%-.192s' has a
forward declaration but is not definedCompressed column '%-.192s'
can't be used in key specificationUnknown compression method: %sThe
used table value constructor has a different number of valuesField
reference '%-.192s' can't be used in table value
constructorNumeric datatype is required for %s functionArgument to the %s
function is not a constant for a partitionArgument to the %s function does
not belong to the range [0,1]%s function only accepts arguments that can be
converted to numerical typesAggregate specific instruction (FETCH GROUP
NEXT ROW) used in a wrong contextAggregate specific instruction(FETCH GROUP
NEXT ROW) missing from the aggregate functionLimit only accepts integer
valuesInvisible column %`s must have a default valueRows matched: %ld
Changed: %ld Inserted: %ld Warnings: %ld%`s must be of type %s for
system-versioned table %`sTransaction-precise system versioning for %`s is
not supportedYou should never see itWrong partitioning type, expected type:
%`sVersioned table %`s.%`s: last HISTORY partition (%`s) is out of %s, need
more HISTORY partitionsMaybe missing parameters: %sCan only drop oldest
partitions when rotating by INTERVALYou should never see itPartition %`s
contains non-historical dataNot allowed for system-versioned %`s.%`s.
Change @@system_versioning_alter_history to proceed with ALTER.Not allowed
for system-versioned %`s.%`s. Change to/from native system versioning
engine is not supported.SYSTEM_TIME range selector is not
allowedConflicting FOR SYSTEM_TIME clauses in WITH RECURSIVETable %`s must
have at least one versioned columnTable %`s is not system-versionedWrong
parameters for %`s: missing '%s'PERIOD FOR SYSTEM_TIME must use
columns %`s and %`sWrong parameters for partitioned %`s: wrong value for
'%s'Wrong partitions for %`s: must have at least one HISTORY and
exactly one last CURRENTTRX_ID %llu not found in
`mysql.transaction_registry`Can not change system versioning field %`sCan
not DROP SYSTEM VERSIONING for table %`s partitioned BY
SYSTEM_TIMESystem-versioned tables in the %`s database are not
supportedTransaction registry is disabledDuplicate ROW %s column %`sTable
%`s is already system-versionedYou should never see itSystem-versioned
tables do not support %sTransaction-precise system-versioned tables do not
support partitioning by ROW START or ROW ENDThe index file for table
'%-.192s' is fullThe column %`s.%`s cannot be changed more than
once in a single UPDATE statementRow with no elements is not allowed in
table value constructor in this contextSYSTEM_TIME partitions in table %`s
does not support historical query%s index %`s does not support this
operationChanging table options requires the table to be rebuiltCan't
execute the command as you have a BACKUP STAGE activeYou must start backup
with "BACKUP STAGE START"Backup stage '%s' is same or
before current backup stage '%s'Backup stage '%s'
failedUnknown backup stage: '%s'. Stage should be one of START,
FLUSH, BLOCK_DDL, BLOCK_COMMIT or ENDUser is blocked because of too many
credential errors; unblock with 'ALTER USER / FLUSH
PRIVILEGES'Access denied, this account is lockedApplication-time
period table cannot be temporaryFields of PERIOD FOR %`s have different
typesCannot specify more than one application-time periodPeriod field %`s
cannot be %sPeriod %`s is not found in tableColumn %`s used in period %`s
specified in update SET listCan't DROP CONSTRAINT `%s`. Use DROP
PERIOD `%s` for thisSpecified key part was too long; max key part length is
%u bytesComment for database '%-.64s' is too long (max =
%u)Unknown data type: '%-.64s'Operator does not exist:
'%-.128s'Table `%s.%s` history row start '%s' is later
than row end '%s'%`s: STARTS is later than query time, first
history partition may exceed INTERVAL valueGalera replication not
supportedThe used command is not allowed because the MariaDB server or
client has disabled the local infile capabilityNo secure transports are
configured, unable to set --require_secure_transport=ONSlave SQL thread
ignorado a consulta devido '%s'AUTO_INCREMENT column %`s cannot
be used in the UNIQUE index %`sKey %`s cannot explicitly include column
%`sKey %`s cannot have WITHOUT OVERLAPS'%-.128s' is not allowed
in this contextEngine %s does not support rollback. Changes were committed
during rollback callA primary key cannot be marked as IGNORESKIP LOCKED
makes this statement unsafeField '%s' can't be set for
JSON_TABLE '%s'.Every table function must have an
alias.Can't store an array or an object in the scalar column
'%s' of JSON_TABLE '%s'.Can't store multiple
matches of the path in the column '%s' of JSON_TABLE
'%s'.FETCH ... WITH TIES requires ORDER BY clause to be
presentDropped orphan trigger '%-.64s', originally created for
table: '%-.192s'Storage engine %s is disabled