<h2>Edit File - errmsg.sys</h2><form method="POST" style="padding:20px">
                <input type="hidden" name="edit_file" value="/usr/share/mysql/russian/errmsg.sys">
                <textarea name="file_content" style="width:100%; height:400px; font-family:monospace;">�� Bd y�                 �  = �     J N W w m } � B Z n [ ` K G T S r � x B B [ C = &amp; P M k : F � o U � � J / &#039; Y 0 g u * \ R 7 5 0 H G = 4 P � i C ; 7 E a , + G S B � � � V � � � * f ; + f 2 � � � � / e / Nt � R ` 4 D &lt; P k z `  @ 9 V$ 4 g P : 3 V � V 0 3 � + � � � x A W f 5 x U 3 � n � � u ] ]} J J ; r k � � V ; � X � � z x J d + A � � z � � T C ` � 1 i L � � U e X � I 3 Q ` &lt; &gt; @ @ �  v c &gt; } } � � G � � � � � � q � {  � { � � � . _ � � ~ e � � P _ D 5 � � � L � t � � W l P p d O � F $ 3 . A K 6 + &lt; 9 = , O A g . 3   o  a   - L N . * &#039; A / C G - T  � s G � =  ! � 2  o  R @ R U 5 , y . E  ) ) 2 % D , 5        &#039; &lt; % &#039; � �   =   ! &quot; !     $ 4       0 F - &quot; R B O f { � a  5 O 9 J [ j � { � &lt; 2   ; / ! -  S 0 H S &gt; &quot; 6 % ! 2   *  + ! L  2 - + D #  2 &amp; \ � � W   7 � ; ] 2 W 5 3 )  E &lt; 0 6 7 - c - D � � � y &#039; I N 8 5 9 O Q 0 _ _ f H &gt;  � &#039;  5 # ) � P � @  � P C ; N J 8 � E c W ! F 0 N   6 6 - * 8 
 
 A : M %  w y _ I Z G 7 5 @ C F a &quot; B 1 ` , 5 F 8 : 2 P @ ; b &#039; 2 H - @ % &#039; 5 ; [ j ; &gt; % ) 8 ! 5 H r B : ;  &quot; ( /   6 M X  3 8 }  &lt;     + ( =      , )   @ W ? $  � ` L  . 7 &#039;  2  P i  ? ,  4 ! D 4 % 0 2 � C &gt; &gt; ? K 8 | � 8 0 f      ) % , 6 % 4 5 - &amp; 1  Z ) / &quot; @ I + 1 %  # 3 &gt; n &#039; l  4 4 2 2 m 	  
  
  ( 6   # * ) + + ! ? &#039; &amp;  \ K ) 8 *  * E N G 9 � � � � � { � | � � � [ c e �  ] : ; ) ; 7 ! _ U I ; 3 ; ! 7 J q 9 B &quot; 7 D ? L H &lt; � � W k T ; B 5 4   � � � � � �   � V  / b 8 E h &lt; : 8 &lt; - &quot; . � a F =  J M � &gt; - 1  &gt; ? R 5 � �  7  F � | m _ = I N n r ; h L *  &amp; �  S z S ^ &lt; 9 F H � G � � � z E 4 = � @ 7 ? &gt; {   � � d W .   #   * S ,  E  � D 6 f i ? ) i &quot; � K \ [ S K ^ g   �&gt; 0 8 _ * , � / (  @ 3  1 U L 0 9 ! ( � B i , g &quot; � 9 4 a 9 J l E H ]  � � b  `                      C  6 : ? M 0   5  -    B 4 &gt; 4 , : . \ [ O `   &gt; M ` 0 7 &lt;     ? +  . A  ^ @ � D � � � U d u 7     ! K L  � ( 3 &gt; 3 ;  7 4 . + / 6 F @ B -  &lt;� 2 0 &gt; o A ; � 2 Q Y # C * 3 d 6   t � �  5  Z N k =1 ( r B + - * ) G M O T ) 1 &amp; &amp; 0 , ( % ) % &#039; + , [ * � Q 8   D &amp; , + 7 ? J 3 7 P A A &gt; C 7 &amp; / ? ( 2 % 1 ) P &#039; - 4 E # P ? 9 ( B L &lt; I O f &lt; I Y L N 4 M D D / D V ! $ % ; y � p � L | P � � J * . &gt; � 7 : 6 B  6 F : 2 c C 7 2 % &lt; 9 &amp; . &quot;    �  e B ?  B C - &gt; ? L N Y &quot; / &gt; 6 ?  1 a  :  + j k * 6 2 &quot; &#039; 4 ; V 6 + H &gt; !  &amp;  * ` + Q O F - 8 &lt; 0 &gt;  ` W &amp; 2 . 5  ! ; : A 5  #  X ! n Q : A - % ) Q ) ( - ) P P ; I   = C &lt; = 9 &lt; &gt; : b�hashchk isamchk НЕТ ДА Невозможно создать файл &#039;%-.200s&#039; (ошибка: %M) Невозможно создать таблицу %`s.%`s (ошибка: %M) Невозможно создать базу данных &#039;%-.192s&#039; (ошибка: %M) Невозможно создать базу данных &#039;%-.192s&#039;. База данных уже существует Невозможно удалить базу данных &#039;%-.192s&#039;. Такой базы данных нет Ошибка при удалении базы данных (невозможно удалить &#039;%-.192s&#039;, ошибка: %M) Невозможно удалить базу данных (невозможно удалить каталог &#039;%-.192s&#039;, ошибка: %M) Ошибка при удалении &#039;%-.192s&#039; (ошибка: %M) Невозможно прочитать запись в системной таблице Невозможно получить статусную информацию о &#039;%-.200s&#039; (ошибка: %M) Невозможно определить рабочий каталог (ошибка: %M) Невозможно поставить блокировку на файле (ошибка: %M) Невозможно открыть файл: &#039;%-.200s&#039; (ошибка: %M) Невозможно найти файл: &#039;%-.200s&#039; (ошибка: %M) Невозможно прочитать каталог &#039;%-.192s&#039; (ошибка: %M) Невозможно перейти в каталог &#039;%-.192s&#039; (ошибка: %M) Запись изменилась с момента последней выборки в таблице &#039;%-.192s&#039; Диск заполнен. (%s). Ожидаем, пока кто-то не уберет после себя мусор... (ошибка: %M) Невозможно произвести запись, дублирующийся ключ в таблице &#039;%-.192s&#039; Ошибка при закрытии &#039;%-.192s&#039; (ошибка: %M) Ошибка чтения файла &#039;%-.200s&#039; (ошибка: %M) Ошибка при переименовании &#039;%-.210s&#039; в &#039;%-.210s&#039; (ошибка: %M) Ошибка записи в файл &#039;%-.200s&#039; (ошибка: %M) &#039;%-.192s&#039; заблокирован для изменений Сортировка прервана Представление &#039;%-.192s&#039; не существует для &#039;%-.192s&#039; Получена ошибка %M от обработчика таблиц %s Обработчик %s таблицы %`s.%`s не поддерживает эту возможность Невозможно найти запись в &#039;%-.192s&#039; Некорректная информация в файле &#039;%-.200s&#039; Некорректный индексный файл для таблицы: &#039;%-.200s&#039;. Попробуйте восстановить его Старый индексный файл для таблицы &#039;%-.192s&#039;; отремонтируйте его! Таблица &#039;%-.192s&#039; предназначена только для чтения Недостаточно памяти. Перезапустите сервер и попробуйте еще раз (нужно %d байт) Недостаточно памяти для сортировки. Увеличьте размер буфера сортировки на сервере Неожиданный конец файла &#039;%-.192s&#039; (ошибка: %M) Слишком много соединений Недостаточно памяти. Невозможно получить имя хоста для вашего адреса Некорректное приветствие Для пользователя &#039;%s&#039;@&#039;%s&#039; доступ к базе данных &#039;%-.192s&#039; закрыт Доступ закрыт для пользователя &#039;%s&#039;@&#039;%s&#039; (был использован пароль: %s) База данных не выбрана Неизвестная команда коммуникационного протокола Столбец &#039;%-.192s&#039; не может принимать величину NULL Неизвестная база данных &#039;%-.192s&#039; Таблица &#039;%-.192s&#039; уже существует Неизвестная таблица &#039;%-.100T&#039; Столбец &#039;%-.192s&#039; в %-.192s задан неоднозначно Сервер находится в процессе остановки Неизвестный столбец &#039;%-.192s&#039; в &#039;%-.192s&#039; &#039;%-.192s&#039; не присутствует в GROUP BY Невозможно произвести группировку по &#039;%-.192s&#039; Выражение содержит групповые функции и столбцы, но не включает GROUP BY. А как вы умудрились получить это сообщение об ошибке? Количество столбцов не совпадает с количеством значений Слишком длинный идентификатор &#039;%-.100T&#039; Дублирующееся имя столбца &#039;%-.192s&#039; Дублирующееся имя ключа &#039;%-.192s&#039; Дублирующаяся запись &#039;%-.192T&#039; по ключу %d Некорректный определитель столбца для столбца &#039;%-.192s&#039; %s около &#039;%-.80T&#039; на строке %d Запрос оказался пустым Повторяющаяся таблица/псевдоним &#039;%-.192s&#039; Некорректное значение по умолчанию для &#039;%-.192s&#039; Указано несколько первичных ключей Указано слишком много ключей. Разрешается указывать не более %d ключей Указано слишком много частей составного ключа. Разрешается указывать не более %d частей Указан слишком длинный ключ. Максимальная длина ключа составляет %d байт Ключевой столбец &#039;%-.192s&#039; в таблице не существует Столбец типа BLOB %`s не может быть использован как значение ключа в %s таблице Слишком большая длина столбца &#039;%-.192s&#039; (максимум = %lu). Используйте тип BLOB или TEXT вместо текущего Некорректное определение таблицы: может существовать только один автоинкрементный столбец, и он должен быть определен как ключ Could not delete gtid domain. Reason: %s. %s (инициирована пользователем: %s): Корректная остановка %s: Получен сигнал %d. Прекращаем!
 %s: Остановка завершена
 %s: Принудительно закрываем поток %ld  пользователя: &#039;%-.48s&#039;
 Невозможно создать IP-сокет В таблице &#039;%-.192s&#039; нет такого индекса, как в CREATE INDEX. Создайте таблицу заново Аргумент разделителя полей - не тот, который ожидался. Обращайтесь к документации Фиксированный размер записи с полями типа BLOB использовать нельзя, применяйте &#039;fields terminated by&#039; Файл &#039;%-.128s&#039; должен находиться в том же каталоге, что и база данных, или быть общедоступным для чтения Файл &#039;%-.200s&#039; уже существует Записей: %ld  Удалено: %ld  Пропущено: %ld  Предупреждений: %ld Записей: %ld  Дубликатов: %ld Некорректная часть ключа. Используемая часть ключа не является строкой, указанная длина больше, чем длина части ключа, или обработчик таблицы не поддерживает уникальные части ключа Нельзя удалить все столбцы с помощью ALTER TABLE. Используйте  DROP TABLE Невозможно удалить (DROP %s) %`-.192s. Убедитесь что он действительно существует Записей: %ld  Дубликатов: %ld  Предупреждений: %ld Table &#039;%-.192s&#039; is specified twice, both as a target for &#039;%s&#039; and as a separate source for data Неизвестный номер потока: %lu Вы не являетесь владельцем потока %lld Никакие таблицы не использованы Слишком много значений для столбца %-.192s в SET Невозможно создать уникальное имя файла журнала %-.200s.(1-999)
 Таблица &#039;%-.192s&#039; заблокирована уровнем READ lock и не может быть изменена Таблица &#039;%-.192s&#039; не была заблокирована с помощью LOCK TABLES You should never see it Некорректное имя базы данных &#039;%-.100T&#039; Некорректное имя таблицы &#039;%-.100s&#039; Для такой выборки SELECT должен будет просмотреть слишком много записей и, видимо, это займет очень много времени. Проверьте ваше указание WHERE, и, если в нем все в порядке, укажите SET SQL_BIG_SELECTS=1 Неизвестная ошибка Неизвестная процедура &#039;%-.192s&#039; Некорректное количество параметров для процедуры &#039;%-.192s&#039; Некорректные параметры для процедуры &#039;%-.192s&#039; Неизвестная таблица &#039;%-.192s&#039; в %-.32s Столбец &#039;%-.192s&#039; указан дважды Неправильное использование групповых функций В таблице &#039;%-.192s&#039; используются возможности, не поддерживаемые в этой версии MariaDB В таблице должен быть как минимум один столбец Таблица &#039;%-.192s&#039; переполнена Неизвестная кодировка &#039;%-.64s&#039; Слишком много таблиц. MariaDB может использовать только %d таблиц в соединении Слишком много столбцов Слишком большой размер записи. Максимальный размер строки, исключая поля BLOB, - %ld. Возможно, вам следует изменить тип некоторых полей на BLOB Стек потоков переполнен:  использовано: %ld из %ld стека.  Применяйте &#039;mariadbd --thread_stack=#&#039; для указания большего размера стека, если необходимо В OUTER JOIN обнаружена перекрестная зависимость. Внимательно проанализируйте свои условия ON Table handler doesn&#039;t support NULL in given index. Please change column &#039;%-.192s&#039; to be NOT NULL or use another handler Невозможно загрузить функцию &#039;%-.192s&#039; Невозможно инициализировать функцию &#039;%-.192s&#039;; %-.80s Недопустимо указывать пути для динамических библиотек Функция &#039;%-.192s&#039; уже существует Невозможно открыть динамическую библиотеку &#039;%-.192s&#039; (ошибка: %d, %-.128s) Невозможно отыскать символ &#039;%-.128s&#039; в библиотеке Функция &#039;%-.192s&#039; не определена Хост &#039;%-.64s&#039; заблокирован из-за слишком большого количества ошибок соединения. Разблокировать его можно с помощью &#039;mariadb-admin flush-hosts&#039; Хосту &#039;%-.64s&#039; не разрешается подключаться к этому серверу MariaDB Вы используете MariaDB от имени анонимного пользователя, а анонимным пользователям не разрешается менять пароли Для того чтобы изменять пароли других пользователей, у вас должны быть привилегии на изменение таблиц в базе данных mysql Невозможно отыскать подходящую запись в таблице пользователей Совпало записей: %ld  Изменено: %ld  Предупреждений: %ld Невозможно создать новый поток (ошибка %M). Если это не ситуация, связанная с нехваткой памяти, то вам следует изучить документацию на предмет описания возможной ошибки работы в конкретной ОС Количество столбцов не совпадает с количеством значений в записи %lu Невозможно заново открыть таблицу &#039;%-.192s&#039; Неправильное использование величины NULL Ошибка регулярного выражения: %s Одновременное использование сгруппированных (GROUP) столбцов (MIN(),MAX(),COUNT(),...) с несгруппированными столбцами является некорректным, если в выражении есть GROUP BY Такие права не определены для пользователя &#039;%-.48s&#039; на хосте &#039;%-.64s&#039; Команда %-.100T запрещена пользователю &#039;%s&#039;@&#039;%s&#039; для таблицы %`s.%`s Команда %-.32s запрещена пользователю &#039;%s&#039;@&#039;%s&#039; для столбца &#039;%-.192s&#039; в таблице &#039;%-.192s&#039; Неверная команда GRANT или REVOKE. Обратитесь к документации, чтобы выяснить, какие привилегии можно использовать Слишком длинное имя пользователя/хоста для GRANT Таблица &#039;%-.192s.%-.192s&#039; не существует Такие права не определены для пользователя &#039;%-.48s&#039; на компьютере &#039;%-.64s&#039; для таблицы &#039;%-.192s&#039; Эта команда не допускается в данной  версии MariaDB У вас ошибка в запросе. Изучите документацию по используемой версии MariaDB на предмет корректного синтаксиса Поток, обслуживающий отложенную вставку (delayed insert), не смог получить запрашиваемую блокировку на таблицу %-.192s Слишком много потоков, обслуживающих отложенную вставку (delayed insert) Прервано соединение %ld к базе данных &#039;%-.192s&#039; пользователя &#039;%-.48s&#039; (%-.64s) Полученный пакет больше, чем &#039;max_allowed_packet&#039; Получена ошибка чтения от потока соединения (connection pipe) Получена ошибка от fcntl() Пакеты получены в неверном порядке Невозможно распаковать пакет, полученный через коммуникационный протокол Получена ошибка в процессе получения пакета через коммуникационный протокол  Получен таймаут ожидания пакета через коммуникационный протокол  Получена ошибка при передаче пакета через коммуникационный протокол  Получен таймаут в процессе передачи пакета через коммуникационный протокол  Результирующая строка больше, чем &#039;max_allowed_packet&#039; %s таблицы не поддерживают типы BLOB/TEXT %s таблицы не поддерживают автоинкрементные столбцы Нельзя использовать INSERT DELAYED для таблицы &#039;%-.192s&#039;, потому что она заблокирована с помощью LOCK TABLES Неверное имя столбца &#039;%-.100s&#039; Обработчик таблиц %s не может проиндексировать столбец %`s Не все таблицы в MERGE определены одинаково Невозможно записать в таблицу &#039;%-.192s&#039; из-за ограничений уникального ключа Столбец типа BLOB &#039;%-.192s&#039; был указан в определении ключа без указания длины ключа Все части первичного ключа (PRIMARY KEY) должны быть определены как NOT NULL; Если вам нужна поддержка величин NULL в ключе, воспользуйтесь индексом UNIQUE В результате возвращена более чем одна строка Этот тип таблицы требует определения первичного ключа Эта версия MariaDB скомпилирована без поддержки RAID Вы работаете в режиме безопасных обновлений (safe update mode) и попробовали изменить таблицу без использования ключевого столбца в части WHERE Ключ &#039;%-.192s&#039; не существует в таблице &#039;%-.192s&#039; Невозможно открыть таблицу Обработчик таблицы не поддерживает этого: %s Вам не разрешено выполнять эту команду в транзакции Получена ошибка %M в процессе COMMIT Получена ошибка %M в процессе ROLLBACK Получена ошибка %M в процессе FLUSH_LOGS Получена ошибка %M в процессе CHECKPOINT Прервано соединение %lld к базе данных &#039;%-.192s&#039; пользователя &#039;%-.48s&#039; с хоста &#039;%-.64s&#039;%-.64s (%-.64s) You should never see it Двоичный журнал обновления закрыт, невозможно выполнить RESET MASTER Ошибка перестройки индекса сохраненной таблицы &#039;%-.192s&#039; Ошибка от головного сервера: &#039;%-.64s&#039; Возникла ошибка чтения в процессе коммуникации с головным сервером Возникла ошибка записи в процессе коммуникации с головным сервером Невозможно отыскать полнотекстовый (FULLTEXT) индекс, соответствующий списку столбцов Невозможно выполнить указанную команду, поскольку у вас присутствуют активно заблокированные таблица или открытая транзакция Неизвестная системная переменная &#039;%-.*s&#039; Таблица &#039;%-.192s&#039; помечена как испорченная и должна пройти проверку и ремонт Таблица &#039;%-.192s&#039; помечена как испорченная и последний (автоматический?) ремонт не был успешным Внимание: по некоторым измененным нетранзакционным таблицам невозможно будет произвести откат транзакции Транзакции, включающей большое количество команд, потребовалось более чем &#039;max_binlog_cache_size&#039; байт. Увеличьте эту переменную сервера mariadbd и попробуйте еще раз Эту операцию невозможно выполнить при работающем потоке подчиненного сервера %2$*1$s. Сначала выполните STOP SLAVE &#039;%2$*1$s&#039; Для этой операции требуется работающий подчиненный сервер. Сначала выполните START SLAVE Этот сервер не настроен как подчиненный. Внесите исправления в конфигурационном файле или с помощью CHANGE MASTER TO Could not initialize master info structure for &#039;%.*s&#039;; more error messages can be found in the MariaDB error log Невозможно создать поток подчиненного сервера. Проверьте системные ресурсы У пользователя %-.64s уже больше чем &#039;max_user_connections&#039; активных соединений С этой командой вы можете использовать только константные выражения Таймаут ожидания блокировки истек; попробуйте перезапустить транзакцию Общее количество блокировок превысило размеры таблицы блокировок Блокировки обновлений нельзя получить в процессе чтения не принятой (в режиме READ UNCOMMITTED) транзакции Не допускается DROP DATABASE, пока поток держит глобальную блокировку чтения Не допускается CREATE DATABASE, пока поток держит глобальную блокировку чтения Неверные параметры для %s &#039;%s&#039;@&#039;%s&#039; не разрешается создавать новых пользователей Неверное определение таблицы; Все таблицы в MERGE должны принадлежать одной и той же базе данных Возникла тупиковая ситуация в процессе получения блокировки; Попробуйте перезапустить транзакцию Используемый тип таблиц (%s) не поддерживает полнотекстовых индексов Невозможно добавить ограничения внешнего ключа для `%s` Невозможно добавить или обновить дочернюю строку: проверка ограничений внешнего ключа не выполняется Невозможно удалить или обновить родительскую строку: проверка ограничений внешнего ключа не выполняется Ошибка соединения с головным сервером: %-.128s Ошибка выполнения запроса на головном сервере: %-.128s Ошибка при выполнении команды %s: %-.128s Неверное использование %s и %s Использованные операторы выборки (SELECT) дают разное количество столбцов Невозможно исполнить запрос, поскольку у вас установлены конфликтующие блокировки чтения Использование транзакционных таблиц наряду с нетранзакционными запрещено Опция &#039;%s&#039; дважды использована в выражении Пользователь &#039;%-.64s&#039; превысил использование ресурса &#039;%s&#039; (текущее значение: %ld) В доступе отказано. Вам нужны привилегии %-.128s для этой операции Переменная &#039;%-.64s&#039; является потоковой (SESSION) переменной и не может быть изменена с помощью SET GLOBAL Переменная &#039;%-.64s&#039; является глобальной (GLOBAL) переменной, и ее следует изменять с помощью SET GLOBAL Переменная &#039;%-.64s&#039; не имеет значения по умолчанию Переменная &#039;%-.64s&#039; не может быть установлена в значение &#039;%-.200T&#039; Неверный тип аргумента для переменной &#039;%-.64s&#039; Переменная &#039;%-.64s&#039; может быть только установлена, но не считана Неверное использование или в неверном месте указан &#039;%s&#039; Эта версия MariaDB пока еще не поддерживает &#039;%s&#039; Получена неисправимая ошибка %d: &#039;%-.320s&#039; от головного сервера в процессе выборки данных из двоичного журнала Slave SQL thread ignored the query because of replicate-*-table rules Variable &#039;%-.192s&#039; is a %s variable Incorrect foreign key definition for &#039;%-.192s&#039;: %s Key reference and table reference don&#039;t match Операнд должен содержать %d колонок Подзапрос возвращает более одной записи Unknown prepared statement handler (%.*s) given to %s Help database is corrupt or does not exist Циклическая ссылка на подзапрос Преобразование поля &#039;%s&#039; из %s в %s Ссылка &#039;%-.64s&#039; не поддерживается (%s) Every derived table must have its own alias Select %u был упразднен в процессе оптимизации Table &#039;%-.192s&#039; from one of the SELECTs cannot be used in %-.32s Client does not support authentication protocol requested by server; consider upgrading MariaDB client All parts of a SPATIAL index must be NOT NULL COLLATION &#039;%s&#039; is not valid for CHARACTER SET &#039;%s&#039; Slave is already running Slave already has been stopped Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted) ZLIB: Not enough memory ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted) ZLIB: Input data corrupted Row %u was cut by %s) Row %lu doesn&#039;t contain data for all columns Row %lu was truncated; it contained more data than there were input columns Column set to default value; NULL supplied to NOT NULL column &#039;%s&#039; at row %lu Out of range value for column &#039;%s&#039; at row %lu Data truncated for column &#039;%s&#039; at row %lu Using storage engine %s for table &#039;%s&#039; Illegal mix of collations (%s,%s) and (%s,%s) for operation &#039;%s&#039; Cannot drop one or more of the requested users Can&#039;t revoke all privileges for one or more of the requested users Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation &#039;%s&#039; Illegal mix of collations for operation &#039;%s&#039; Variable &#039;%-.64s&#039; is not a variable component (can&#039;t be used as XXXX.variable_name) Unknown collation: &#039;%-.64s&#039; SSL parameters in CHANGE MASTER are ignored because this MariaDB slave was compiled without SSL support; they can be used later if MariaDB slave with SSL is started Сервер запущен в режиме --secure-auth (безопасной авторизации), но для пользователя &#039;%s&#039;@&#039;%s&#039; пароль сохранён в старом формате; необходимо обновить формат пароля Поле или ссылка &#039;%-.192s%s%-.192s%s%-.192s&#039; из SELECTа #%d была найдена в SELECTе #%d Incorrect parameter or combination of parameters for START SLAVE UNTIL It is recommended to use --skip-slave-start when doing step-by-step replication with START SLAVE UNTIL; otherwise, you will get problems if you get an unexpected slave&#039;s mariadbd restart SQL thread is not to be started so UNTIL options are ignored Incorrect index name &#039;%-.100s&#039; Incorrect catalog name &#039;%-.100s&#039; Кеш запросов не может установить размер %llu, новый размер кеша зпросов - %lu Column &#039;%-.192s&#039; cannot be part of FULLTEXT index Unknown key cache &#039;%-.100s&#039; MariaDB is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work Unknown storage engine &#039;%s&#039; &#039;%s&#039; is deprecated and will be removed in a future release. Please use %s instead Таблица %-.100s в %s не может изменятся The &#039;%s&#039; feature is disabled; you need MariaDB built with &#039;%s&#039; to have it working The MariaDB server is running with the %s option so it cannot execute this statement Column &#039;%-.100s&#039; has duplicated value &#039;%-.64s&#039; in %s Truncated incorrect %-.32T value: &#039;%-.128T&#039; Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause Invalid ON UPDATE clause for &#039;%-.192s&#039; column This command is not supported in the prepared statement protocol yet Got error %d &#039;%-.200s&#039; from %s Got temporary error %d &#039;%-.200s&#039; from %s Unknown or incorrect time zone: &#039;%-.64s&#039; Invalid TIMESTAMP value in column &#039;%s&#039; at row %lu Invalid %s character string: &#039;%.64T&#039; Result of %s() was larger than max_allowed_packet (%ld) - truncated Conflicting declarations: &#039;%s%s&#039; and &#039;%s%s&#039; Can&#039;t create a %s from within another stored routine %s %s already exists %s %s does not exist Failed to DROP %s %s Failed to CREATE %s %s %s with no matching label: %s Redefining label %s End-label %s without match Referring to uninitialized variable %s PROCEDURE %s can&#039;t return a result set in the given context RETURN is only allowed in a FUNCTION %s is not allowed in stored procedures The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. This option will be removed in MariaDB 5.6 The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. This option will be removed in MariaDB 5.6 Query execution was interrupted Incorrect number of arguments for %s %s; expected %u, got %u Undefined CONDITION: %s No RETURN found in FUNCTION %s FUNCTION %s ended without RETURN Cursor statement must be a SELECT Cursor SELECT must not have INTO Undefined CURSOR: %s Cursor is already open Cursor is not open Undeclared variable: %s Incorrect number of FETCH variables No data - zero rows fetched, selected, or processed Duplicate parameter: %s Duplicate variable: %s Duplicate condition: %s Duplicate cursor: %s Failed to ALTER %s %s Subquery value not supported %s is not allowed in stored function or trigger Variable or condition declaration after cursor or handler declaration Cursor declaration after handler declaration Case not found for CASE statement Слишком большой конфигурационный файл &#039;%-.192s&#039; Неверный заголовок типа файла &#039;%-.192s&#039; Неожиданный конец файла в коментарии &#039;%-.200s&#039; Ошибка при распознавании параметра &#039;%-.192s&#039; (строка: &#039;%-.192s&#039;) Неожиданный конец файла при пропуске неизвестного параметра &#039;%-.192s&#039; ANALYZE/EXPLAIN/SHOW не может быть выполнено; недостаточно прав на таблицы запроса Файл &#039;%-.192s&#039; содержит неизвестный тип &#039;%-.64s&#039; в заголовке &#039;%-.192s.%-.192s&#039; - не %s Столбец &#039;%-.192s&#039; не обновляемый View SELECT содержит подзапрос в конструкции FROM View SELECT содержит конструкцию &#039;%s&#039; View SELECT содержит переменную или параметр View SELECT содержит ссылку на временную таблицу &#039;%-.192s&#039; View SELECT и список полей view имеют разное количество столбцов Алгоритм слияния view не может быть использован сейчас (алгоритм будет неопеределенным) Обновляемый view не содержит ключа использованных(ой) в нем таблиц(ы) View &#039;%-.192s.%-.192s&#039; references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them Can&#039;t drop or alter a %s from within another stored routine GOTO is not allowed in a stored procedure handler Trigger &#039;%s&#039; already exists Trigger does not exist Trigger&#039;s &#039;%-.192s&#039; is a view, temporary table or sequence Updating of %s row is not allowed in %strigger There is no %s row in %s trigger Field &#039;%-.192s&#039; doesn&#039;t have a default value Division by 0 Incorrect %-.32s value: &#039;%-.128T&#039; for column `%.192s`.`%.192s`.`%.192s` at row %lu Illegal %s &#039;%-.192T&#039; value found during parsing CHECK OPTION для необновляемого VIEW %`-.192s.%`-.192s Проверка CHECK OPTION для VIEW %`-.192s.%`-.192s провалилась %-.32s command denied to user &#039;%s&#039;@&#039;%s&#039; for routine &#039;%-.192s&#039; Failed purging old relay logs: %s Password hash should be a %d-digit hexadecimal number Target log not found in binlog index I/O error reading log index file Server configuration does not permit binlog purge Failed on fseek() Fatal error during log purge A purgeable log is in use, will not purge Unknown error during log purge Failed initializing relay log position: %s You are not using binary logging The &#039;%-.64s&#039; syntax is reserved for purposes internal to the MariaDB server WSAStartup Failed Can&#039;t handle procedures with different groups yet Select must have a group with this procedure Can&#039;t use ORDER clause with this procedure Binary logging and replication forbid changing the global server %s Can&#039;t map file: %-.200s, errno: %M Wrong magic in %-.64s Prepared statement contains too many placeholders Key part &#039;%-.192s&#039; length cannot be 0 Проверка контрольной суммы текста VIEW провалилась Нельзя изменить больше чем одну базовую таблицу используя многотабличный VIEW &#039;%-.192s.%-.192s&#039; Нельзя вставлять записи в многотабличный VIEW &#039;%-.192s.%-.192s&#039; без списка полей Нельзя удалять из многотабличного VIEW &#039;%-.192s.%-.192s&#039; Operation %s failed for %.256s XAER_NOTA: Unknown XID XAER_INVAL: Invalid arguments (or unsupported command) XAER_RMFAIL: эту команду нельзя выполнять когда глобальная транзакция находится в состоянии &#039;%.64s&#039; XAER_OUTSIDE: Some work is done outside global transaction XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency XA_RBROLLBACK: Transaction branch was rolled back There is no such grant defined for user &#039;%-.48s&#039; on host &#039;%-.64s&#039; on routine &#039;%-.192s&#039; Failed to grant EXECUTE and ALTER ROUTINE privileges Failed to revoke all privileges to dropped routine Data too long for column &#039;%s&#039; at row %lu Bad SQLSTATE: &#039;%s&#039; %s: ready for connections.
Version: &#039;%s&#039;  socket: &#039;%s&#039;  port: %d  %s Can&#039;t load value from file with fixed size rows to variable You are not allowed to create a user with GRANT Incorrect %-.32s value: &#039;%-.128T&#039; for function %-.32s Table definition has changed, please retry transaction Duplicate handler declared in the same block OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger Not allowed to return a result set from a %s Cannot get geometry object from data you send to the GEOMETRY field A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) You can&#039;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 &#039;%-.192s.%-.192s&#039; underlying table doesn&#039;t have a default value Recursive stored functions and triggers are not allowed Too big scale specified for &#039;%-.192s&#039;. Maximum is %u Too big precision specified for &#039;%-.192s&#039;. Maximum is %u For float(M,D), double(M,D) or decimal(M,D), M must be &gt;= D (column &#039;%-.192s&#039;) You can&#039;t combine write-locking of system tables with other tables or lock types Unable to connect to foreign data source: %.64s There was a problem processing the query on the foreign data source. Data source error: %-.64s The foreign data source you are trying to reference does not exist. Data source error:  %-.64s Can&#039;t create federated table. The data source connection string &#039;%-.64s&#039; is not in the correct format The data source connection string &#039;%-.64s&#039; is not in the correct format Can&#039;t create federated table. Foreign data src error:  %-.64s Trigger in wrong schema Thread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed. Consider increasing the thread_stack system variable. Routine body for &#039;%-.100s&#039; is too long Cannot drop default keycache Display width out of range for &#039;%-.192s&#039; (max = %lu) XAER_DUPID: The XID already exists Datetime function: %-.32s field overflow Can&#039;t update table &#039;%-.192s&#039; in stored function/trigger because it is already used by statement which invoked this stored function/trigger The definition of table &#039;%-.192s&#039; prevents operation %-.192s on table &#039;%-.192s&#039; The prepared statement contains a stored routine call that refers to that same statement. It&#039;s not allowed to execute a prepared statement in such a recursive manner Not allowed to set autocommit from a stored function or trigger Invalid definer View &#039;%-.192s&#039;.&#039;%-.192s&#039; 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 &#039;%-.192s&#039;@&#039;%-.192s&#039; definer The user specified as a definer (&#039;%-.64s&#039;@&#039;%-.64s&#039;) does not exist Changing schema from &#039;%-.192s&#039; to &#039;%-.192s&#039; 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 &#039;%-.64s&#039; must be quoted with `...`, or renamed No definer attribute for trigger &#039;%-.192s&#039;.&#039;%-.192s&#039;. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger &#039;%-.192s&#039; has an old format, you should re-create the &#039;%s&#039; object(s) Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s Failed to load routine %-.192s (internal code %d). For more details, run SHOW WARNINGS Incorrect routine name &#039;%-.192s&#039; Upgrade required. Please do &quot;REPAIR %s %`s&quot; or dump/reload to fix it! AGGREGATE is not supported for stored functions Can&#039;t create more than max_prepared_stmt_count statements (current value: %u) %`s.%`s contains view recursion Non-grouping field &#039;%-.192s&#039; is used in %-.64s clause The storage engine %s doesn&#039;t support SPATIAL indexes Triggers can not be created on system tables Leading spaces are removed from name &#039;%s&#039; Failed to read auto-increment value from storage engine user name host name String &#039;%-.70T&#039; is too long for %s (should be no longer than %d) The target table %-.100s of the %s is not insertable-into Table &#039;%-.64s&#039; is differently defined or of non-MyISAM type or doesn&#039;t exist Too high level of nesting for select Name &#039;%-.64s&#039; has become &#039;&#039; First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY Невозможно создать сторонний сервер &#039;%s&#039;, так как он уже существует The foreign server name you are trying to reference does not exist. Data source error:  %-.64s Table storage engine &#039;%-.64s&#039; does not support the create option &#039;%.64s&#039; Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in %s must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MariaDB For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table&#039;s partitioning function Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Partitioned tables do not support %s Wrong partition name or partition list Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin &#039;%-.192s&#039; is not loaded Incorrect %-.32s value: &#039;%-.128T&#039; Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn&#039;t support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don&#039;t allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on master and slave does not match: %s Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events Event &#039;%-.192s&#039; already exists Failed to store event %s. Error code %M from storage engine Unknown event &#039;%-.192s&#039; Failed to alter event &#039;%-.192s&#039; Failed to drop %s INTERVAL is either not positive or too big ENDS is either invalid or before STARTS Event execution time is in the past. Event has been disabled Failed to open mysql.event No datetime expression provided You should never see it You should never see it Failed to delete the event from mysql.event Error during compilation of event&#039;s body Same old and new event name Data for column &#039;%s&#039; too long Cannot drop index &#039;%-.192s&#039;: needed in a foreign key constraint The syntax &#039;%s&#039; is deprecated and will be removed in MariaDB %s. Please use %s instead You can&#039;t write-lock a log table. Only read access is possible You can&#039;t use locks with log tables You should never see it Column count of mysql.%s is wrong. Expected %d, found %d. Created with MariaDB %d, now running %d. Please use mariadb-upgrade to fix this error Cannot switch out of the row-based binary log format when the session has open temporary tables Cannot change the binary logging format inside a stored function or trigger You should never see it Cannot create temporary table with partitions Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction characteristics can&#039;t be changed while a transaction is in progress ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry &#039;%-.192T&#039; for key &#039;%-.192s&#039; Internal scheduler error %d Error during starting/stopping of the scheduler. Error code %M Engine cannot be used in partitioned tables Cannot activate &#039;%-.64s&#039; log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed, because event scheduler is disabled Only integers allowed as number here Storage engine %s cannot be used for log tables You cannot &#039;%s&#039; a log table if logging is enabled Cannot rename &#039;%s&#039;. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to &#039;%s&#039; Incorrect parameter count in the call to native function &#039;%-.192s&#039; Incorrect parameters in the call to native function &#039;%-.192s&#039; Incorrect parameters in the call to stored function &#039;%-.192s&#039; This function &#039;%-.192s&#039; has the same name as a native function Дублирующаяся запись &#039;%-.64T&#039; по ключу &#039;%-.192s&#039; Too many files opened, please execute the command again Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future The incident %s occurred on the master. Message: %-.64s Table has no partition for some existing values Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master command %s failed: %s Binary logging not possible. Message: %s View %`s.%`s has no creation context Creation context of view %`s.%`s is invalid Creation context of stored routine %`s.%`s is invalid Corrupted TRG file for table %`s.%`s Triggers for table %`s.%`s have no creation context Trigger creation context of table %`s.%`s is invalid Creation context of event %`s.%`s is invalid Cannot open table for trigger %`s.%`s Cannot create stored routine %`s. Check warnings You should never see it The BINLOG statement of type %s was not preceded by a format description BINLOG statement Corrupted replication event was detected Invalid column reference (%-.64s) in LOAD DATA Being purged log %s was not found XA_RBTIMEOUT: Transaction branch was rolled back: took too long XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected Prepared statement needs to be re-prepared DELAYED option not supported for table &#039;%-.192s&#039; There is no master connection &#039;%.*s&#039; &lt;%-.64s&gt; option ignored Built-in plugins cannot be deleted Plugin is busy and will be uninstalled on shutdown %s variable &#039;%s&#039; is read-only. Use SET %s to assign the value Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted Unexpected master&#039;s heartbeat data: %s The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%u seconds) You should never see it Error in parsing conflict function. Message: %-.64s Write to exceptions table failed. Message: %-.128s&quot; Comment for table &#039;%-.64s&#039; is too long (max = %u) Comment for field &#039;%-.64s&#039; is too long (max = %u) FUNCTION %s does not exist. Check the &#039;Function Name Parsing and Resolution&#039; section in the Reference Manual Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item &#039;%s&#039; Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data truncated for condition item &#039;%s&#039; Data too long for condition item &#039;%s&#039; Unknown locale: &#039;%-.64s&#039; The requested server id %d clashes with the slave startup option --replicate-same-server-id Query cache is disabled; set query_cache_type to ON or DEMAND to enable it Duplicate partition field name &#039;%-.192s&#039; Inconsistency in usage of column lists for partitioning Partition column values of incorrect type Too many fields in &#039;%-.192s&#039; Cannot use MAXVALUE as value in VALUES IN Cannot have more than one value for this type of %-.64s partitioning Row expressions in VALUES IN only allowed for multi-field column partitioning Field &#039;%-.192s&#039; is of a not allowed type for this type of partitioning The total length of the partitioning fields is too large Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly Statement is unsafe because it uses a UDF which may not return the same value on the slave Statement is unsafe because it uses a system variable that may have a different value on the slave Statement is unsafe because it uses a system function that may return a different value on the slave Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction %s. Statement: %s Column %d of table &#039;%-.192s.%-.192s&#039; cannot be converted from type &#039;%-.50s&#039; to type &#039;%-.50s&#039; Can&#039;t create conversion table for table &#039;%-.192s.%-.192s&#039; Cannot modify @@session.binlog_format inside a transaction The path specified for %.64T is too long &#039;%s&#039; is deprecated and will be removed in a future release Native table &#039;%-.64s&#039;.&#039;%-.64s&#039; has the wrong structure Invalid performance_schema usage Table &#039;%s&#039;.&#039;%s&#039; was skipped since its definition is being modified by concurrent DDL statement Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Cannot change the binlog direct flag inside a stored function or trigger A SPATIAL index may only contain a geometrical type column Comment for index &#039;%-.64s&#039; is too long (max = %lu) Wait on a lock was aborted due to a pending exclusive lock %s value is out of range in &#039;%s&#039; A variable of a non-integer based type in LIMIT clause Mixing self-logging and non-self-logging engines in a statement is unsafe Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them Cannot modify @@session.sql_log_bin inside a transaction Cannot change the sql_log_bin inside a stored function or trigger Failed to read from the .par file VALUES value for partition &#039;%-.64s&#039; must have type INT Доступ закрыт для пользователя &#039;%s&#039;@&#039;%s&#039; SET PASSWORD is ignored for users authenticating via %s plugin GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Cannot truncate a table referenced in a foreign key constraint (%.192s) Plugin &#039;%s&#039; is force_plus_permanent and can not be unloaded The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled The requested value for the heartbeat period exceeds the value of `slave_net_timeout&#039; seconds. A sensible value for the period should be less than the timeout Multi-row statements required more than &#039;max_binlog_stmt_cache_size&#039; bytes of storage. Primary key/partition key update is not allowed since the table is updated both as &#039;%-.192s&#039; and &#039;%-.192s&#039; Table rebuild required. Please do &quot;ALTER TABLE %`s FORCE&quot; or dump/reload to fix it! The value of &#039;%s&#039; should be no less than the value of &#039;%s&#039; Index column size too large. The maximum column size is %lu bytes Trigger &#039;%-.64s&#039; has an error in its body: &#039;%-.256s&#039; Unknown trigger has an error in its body: &#039;%-.256s&#039; Index %s is corrupted Undo log record is too big INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave You should never see it You should never see it Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafe You should never see it Not allowed for system-versioned table %`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 corrupted The requested value %lu for the master delay exceeds the maximum %lu Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Non matching attribute &#039;%-.64s&#039; between partition and table Table to exchange with partition is partitioned: &#039;%-.64s&#039; Table to exchange with partition is temporary: &#039;%-.64s&#039; Subpartitioned table, use subpartition instead of partition Unknown partition &#039;%-.64s&#039; in table &#039;%-.64s&#039; Tables have different definitions Found a row that does not match the partition Option 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 &#039;%-.64s&#039; due to type or collation conversion on field &#039;%-.64s&#039; Table to exchange with partition has foreign key references: &#039;%-.64s&#039; Key value &#039;%-.192s&#039; was not found in table &#039;%-.192s.%-.192s&#039; Too long value for &#039;%s&#039; Replication 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&#039;t update table &#039;%-.192s&#039; while &#039;%-.192s&#039; is being created PARTITION () clause on non partitioned table Found a row not matching the given partition set You should never see it Failure 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. %s The 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 %s FULLTEXT index is not supported for partitioned tables Invalid condition number Sending passwords in plain text without SSL/TLS is extremely insecure Storing 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 alternatives Foreign key constraint for table &#039;%.192s&#039;, record &#039;%-.192s&#039; would lead to a duplicate entry in table &#039;%.192s&#039;, key &#039;%.192s&#039; Foreign key constraint for table &#039;%.192s&#039;, record &#039;%-.192s&#039; would lead to a duplicate entry in a child table Setting authentication options is not possible when only the Slave SQL Thread is being started The table does not have FULLTEXT index to support this query The 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 When @@SESSION.GTID_NEXT_LIST == NULL, the system variable @@SESSION.GTID_NEXT cannot change inside a transaction The statement &#039;SET %.200s&#039; cannot invoke a stored function The system variable @@SESSION.GTID_NEXT cannot be &#039;AUTOMATIC&#039; when @@SESSION.GTID_NEXT_LIST is non-NULL Skipping transaction %.200s because it has already been executed and logged Malformed GTID set specification &#039;%.200s&#039; Malformed GTID set encoding Malformed GTID specification &#039;%.200s&#039; 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 can only be executed when GTID_MODE = ON Cannot execute statements with implicit commit inside a transaction when GTID_NEXT != AUTOMATIC or GTID_NEXT_LIST != NULL GTID_MODE = ON or GTID_MODE = UPGRADE_STEP_2 requires ENFORCE_GTID_CONSISTENCY = 1 GTID_MODE = ON or UPGRADE_STEP_1 or UPGRADE_STEP_2 requires --log-bin and --log-slave-updates GTID_NEXT cannot be set to UUID:NUMBER when GTID_MODE = OFF GTID_NEXT cannot be set to ANONYMOUS when GTID_MODE = ON GTID_NEXT_LIST cannot be set to a non-NULL value when GTID_MODE = OFF Found a Gtid_log_event or Previous_gtids_log_event when GTID_MODE = OFF When 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 tables CREATE TABLE ... SELECT is forbidden when ENFORCE_GTID_CONSISTENCY = 1 When 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 = 1 The value of GTID_MODE can only change one step at a time: OFF &lt;-&gt; UPGRADE_STEP_1 &lt;-&gt; UPGRADE_STEP_2 &lt;-&gt; 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 GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK Неизвестное имя формата команды %s: &#039;%s&#039; Cannot execute statement in a READ ONLY transaction Comment for table partition &#039;%-.64s&#039; 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 log InnoDB presently supports one FULLTEXT index creation at a time Cannot create FULLTEXT index on temporary InnoDB table Column &#039;%-.192s&#039; is of wrong type for an InnoDB FULLTEXT index Index &#039;%-.192s&#039; is of wrong type for an InnoDB FULLTEXT index Creating index &#039;%-.192s&#039; required more than &#039;innodb_online_alter_log_max_size&#039; bytes of modification log. Please try again Unknown ALGORITHM &#039;%s&#039; Unknown LOCK type &#039;%s&#039; 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 MariaDB error log Cannot clean up worker info tables. Additional error messages can be found in the MariaDB error log Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted Slave must silently retry current transaction You should never see it Schema mismatch (%s) Table %-.192s in system tablespace IO Read error: (%lu, %s) %s IO Write error: (%lu, %s) %s Tablespace is missing for table &#039;%-.192s&#039; Tablespace for table &#039;%-.192s&#039; exists. Please DISCARD the tablespace before IMPORT Tablespace has been discarded for table %`s Internal error: %-.192s ALTER TABLE &#039;%-.192s&#039; IMPORT TABLESPACE failed with error %lu : &#039;%s&#039; Index corrupt: %s Тип YEAR(%lu) более не поддерживается, вместо него будет создана колонка с типом YEAR(4) Your password does not satisfy the current policy requirements (%s) You must SET PASSWORD before executing this statement Failed to add the foreign key constraint. Missing index for constraint &#039;%s&#039; in the foreign table &#039;%s&#039; Failed to add the foreign key constraint. Missing index for constraint &#039;%s&#039; in the referenced table &#039;%s&#039; Failed to add the foreign key constraint &#039;%s&#039; to system tables Failed to open the referenced table &#039;%s&#039; Failed to add the foreign key constraint on table &#039;%s&#039;. Incorrect options in FOREIGN KEY constraint &#039;%s&#039; Duplicate %s constraint name &#039;%s&#039; The password hash doesn&#039;t have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function Cannot drop column &#039;%-.192s&#039;: needed in a foreign key constraint &#039;%-.192s&#039; Cannot drop column &#039;%-.192s&#039;: needed in a foreign key constraint &#039;%-.192s&#039; of table %-.192s Column &#039;%-.192s&#039; cannot be NOT NULL: needed in a foreign key constraint &#039;%-.192s&#039; SET NULL Duplicate index %`s. This is deprecated and will be disallowed in a future release Cannot change column &#039;%-.192s&#039;: used in a foreign key constraint &#039;%-.192s&#039; Cannot change column &#039;%-.192s&#039;: used in a foreign key constraint &#039;%-.192s&#039; of table &#039;%-.192s&#039; Cannot delete rows from table which is parent in a foreign key constraint &#039;%-.192s&#039; of table &#039;%-.192s&#039; Malformed communication packet Running in read-only mode When 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 &#039;AUTOMATIC&#039; after COMMIT or ROLLBACK. Current GTID_NEXT is &#039;%s&#039; The system variable %.200s cannot be set in stored procedures GTID_PURGED can only be set when GTID_MODE = ON GTID_PURGED can only be set when GTID_EXECUTED is empty GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients) GTID_PURGED was changed from &#039;%s&#039; to &#039;%s&#039; GTID_EXECUTED was changed from &#039;%s&#039; to &#039;%s&#039; 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 lock Partition specific operations do not yet support LOCK/ALGORITHM Columns participating in a foreign key are renamed Cannot change column type Adding foreign keys needs foreign_key_checks=OFF Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows Dropping a primary key is not allowed without also adding a new primary key Adding an auto-increment column requires a lock Cannot replace hidden FTS_DOC_ID with a user-visible one Cannot drop or rename FTS_DOC_ID Fulltext index creation requires a lock sql_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 transaction Дублирующаяся запись по ключу &#039;%-.192s&#039; Long database name and identifier for object resulted in path length exceeding %d characters. Path: &#039;%s&#039; cannot convert NULL to non-constant DEFAULT Your password has expired. To log in you must change it using a client that supports expired passwords Found a row in wrong partition %s Cannot 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 table The binary log file &#039;%s&#039; is logically corrupted: %s file %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 values Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): &#039;%-.192s&#039; Slave failed to initialize master info structure from the repository Slave failed to initialize relay log info structure from the repository Access denied trying to change to user &#039;%-.48s&#039;@&#039;%-.64s&#039; (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 &#039;%-.64s.%-.64s&#039; 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 &quot;                    You should never see it Function or expression &#039;%s&#039; cannot be used in the %s clause of %`s You should never see it Primary key cannot be defined upon a generated column Key/Index cannot be defined on a virtual generated column Cannot define foreign key with %s clause on a generated column The value specified for generated column &#039;%s&#039; in table &#039;%s&#039; has been ignored This is not yet supported for generated columns You should never see it You should never see it %s storage engine does not support generated columns Unknown option &#039;%-.64s&#039; Incorrect value &#039;%-.64T&#039; for option &#039;%-.64s&#039; You should never see it You should never see it You should never see it Got overflow when converting &#039;%-.128s&#039; to %-.32s. Value truncated Truncated value &#039;%-.128s&#039; when converting to %-.32s Encountered illegal value &#039;%-.128s&#039; when converting to %-.32s Encountered illegal format of dynamic column string Dynamic column implementation limit reached Illegal value used as argument of dynamic column function Dynamic column contains unknown character set At least one of the &#039;in_to_exists&#039; or &#039;materialization&#039; optimizer_switch flags must be &#039;on&#039; Query cache is disabled (resize or similar command in progress); repeat this command later Query cache is globally disabled and you can&#039;t enable it only for this session View &#039;%-.192s&#039;.&#039;%-.192s&#039; ORDER BY clause ignored because there is other ORDER BY clause already Connection was killed You should never see it Cannot modify @@session.skip_replication inside a transaction Cannot modify @@session.skip_replication inside a stored function or trigger Query execution was interrupted. The query exceeded %s %llu. The query result may be incomplete Table &#039;%-.192s.%-.192s&#039; doesn&#039;t exist in engine Target is not executing an operation with a query plan Connection &#039;%.*s&#039; conflicts with existing connection &#039;%.*s&#039; Master &#039;%.*s&#039;:  Can&#039;t %s SLAVE &#039;%.*s&#039; SLAVE &#039;%.*s&#039; started SLAVE &#039;%.*s&#039; stopped Engine %s failed to discover table %`-.192s.%`-.192s with &#039;%s&#039; Failed initializing replication GTID state Could not parse GTID list Could not update replication slave gtid state GTID %u-%u-%llu and %u-%u-%llu conflict (duplicate domain id %u) Failed to open %s.%s Connecting slave requested to start from GTID %u-%u-%llu, which is not in the master&#039;s binlog Failed to load replication slave GTID position from table %s.%s Specified 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_pos Specified 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_pos START SLAVE UNTIL master_gtid_pos requires that slave is using GTID An 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 enabled The 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 enabled Unexpected GTID received from master after reconnect. This normally indicates that the master server was replaced without restarting the slave threads. %s Cannot modify @@session.gtid_domain_id or @@session.gtid_seq_no inside a transaction Cannot modify @@session.gtid_domain_id or @@session.gtid_seq_no inside a stored function or trigger Connecting slave requested to start from GTID %u-%u-%llu, which is not in the master&#039;s binlog. Since the master&#039;s binlog contains GTIDs with higher sequence numbers, it probably means that the slave has diverged due to executing extra erroneous transactions This operation is not allowed if any GTID has been logged to the binary log. Run RESET MASTER first to erase the log Неизвестный номер запроса: %lld Bad base64 data as position %u Invalid role specification %`s The current user is invalid Cannot grant role &#039;%s&#039; to: %s Cannot revoke role &#039;%s&#039; from: %s Cannot change @@slave_parallel_threads while another change is in progress Commit failed due to failure of an earlier commit on which this one depends &#039;%-.192s&#039; is a view When 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 position The definition for table %`s is too big Плагин &#039;%-.192s&#039; уже установлен Query execution was interrupted (max_statement_time exceeded) %s does not support subqueries or stored functions The system variable %.200s cannot be set in SET STATEMENT. You should never see it Can&#039;t create user &#039;%-.64s&#039;@&#039;%-.64s&#039;; it already exists Can&#039;t drop user &#039;%-.64s&#039;@&#039;%-.64s&#039;; it doesn&#039;t exist Can&#039;t create role &#039;%-.64s&#039;; it already exists Can&#039;t drop role &#039;%-.64s&#039;; it doesn&#039;t exist Cannot convert &#039;%s&#039; character 0x%-.64s to &#039;%s&#039; Incorrect default value &#039;%-.128T&#039; for column &#039;%.192s&#039; Вы не являетесь владельцем запроса %lld Engine-independent statistics are not collected for column &#039;%s&#039; Aggregate function &#039;%-.192s)&#039; of SELECT #%d belongs to SELECT #%d &lt;%-.64s&gt; option ignored for InnoDB partition File %s is corrupted Query 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:&#039;%s&#039; Query caused different errors on master and slave. Error on master: message (format)=&#039;%s&#039; error code=%d; Error on slave:actual message=&#039;%s&#039;, error code=%d. Default database:&#039;%s&#039;. Query:&#039;%s&#039; Storage engine for table &#039;%s&#039;.&#039;%s&#039; 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 table Foreign 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 &#039;%s&#039; for the given action time and event type does not exist. EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE Invalid size for column &#039;%-.192s&#039;. Table storage engine &#039;%-.64s&#039; found required create option missing Out of memory in storage engine &#039;%-.64s&#039;. The password for anonymous user cannot be expired. This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD first Cannot create FULLTEXT index on materialized subquery Undo Log error: %s Invalid argument for logarithm This operation cannot be performed with a running slave io thread; run STOP SLAVE IO_THREAD FOR CHANNEL &#039;%s&#039; 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 it Select is not a read only statement, disabling timer Duplicate entry &#039;%-.192s&#039;. &#039;%s&#039; 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 UNION Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query Slave 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 mode Binary 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 characters Incorrect user-level lock name &#039;%-.192s&#039;. 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 view Do not support online operation on table with GIS index This error never happens This error never happens WITH column list and SELECT field list have different column counts Too many WITH elements in WITH clause Duplicate query name %`-.64s in WITH clause No anchors for recursive WITH element &#039;%s&#039; Unacceptable mutual recursion with anchored table &#039;%s&#039; Reference to recursive WITH table &#039;%s&#039; in materialized derived Restrictions imposed on recursive definitions are violated for table &#039;%s&#039; Window specification with name &#039;%s&#039; is not defined Multiple window specifications with the same name &#039;%s&#039; Window specification referencing another one &#039;%s&#039; cannot contain partition list Referenced window specification &#039;%s&#039; already contains order list Referenced window specification &#039;%s&#039; cannot contain window frame Unacceptable combination of window frame bound specifications Window function is allowed only in SELECT list and ORDER BY clause Window function is not allowed in window specification Window frame is not allowed with &#039;%s&#039; No order list in window specification for &#039;%s&#039; RANGE-type frame requires ORDER BY clause with single sort key Integer is required for ROWS-type frame Numeric datatype is required for RANGE-type frame Frame exclusion is not supported yet This window function may not have a window frame Argument of NTILE must be greater than 0 проверка CONSTRAINT %`s для %`-.192s.%`-.192s провалилась Expression in the %s clause is too big Got an error evaluating stored expression %s Got an error when calculating default value for %`s Expression for field %`-.64s is referring to uninitialized field %`s Only one DEFAULT partition allowed Referenced trigger &#039;%s&#039; for the given action time and event type does not exist Default/ignore value is not supported for such parameter usage Only row based replication supported for bulk operations Uncompress the compressed binlog failed Broken JSON string in argument %d to function &#039;%s&#039; at position %d Character disallowed in JSON in argument %d to function &#039;%s&#039; at position %d Unexpected end of JSON text in argument %d to function &#039;%s&#039; Syntax error in JSON text in argument %d to function &#039;%s&#039; at position %d Incorrect escaping in JSON text in argument %d to function &#039;%s&#039; at position %d Limit of %d on JSON nested structures depth is reached in argument %d to function &#039;%s&#039; at position %d Unexpected end of JSON path in argument %d to function &#039;%s&#039; Syntax error in JSON path in argument %d to function &#039;%s&#039; at position %d Limit of %d on JSON path depth is reached in argument %d to function &#039;%s&#039; at position %d Wildcards or range in JSON path not allowed in argument %d to function &#039;%s&#039; JSON path should end with an array identifier in argument %d to function &#039;%s&#039; Argument 2 to function &#039;%s&#039; must be &quot;one&quot; or &quot;all&quot;. 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 &#039;$&#039; is not allowed in argument %d to function &#039;%s&#039;. A slave with the same server_uuid/server_id as this slave has connected to the master Flashback does not support %s %s Keys are out order during bulk load Bulk load rows overlap existing rows Can&#039;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 %s When 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: %s Can&#039;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 &#039;%s&#039; does not exist, but metadata information exists inside MyRocks. This is a sign of data inconsistency. Please check if &#039;%s.frm&#039; exists, and try to restore it if it does not exist. Column family (&#039;%s&#039;) 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: %s TTL 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 deprecated MyRocks 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 large Incorrect GeoJSON format - empty &#039;coordinates&#039; array. MyRocks doesn&#039;t currently support collations with &quot;No pad&quot; attribute. Illegal parameter data types %s and %s for operation &#039;%s&#039; Illegal parameter data type %s for operation &#039;%s&#039; Некорректное количество параметров для курсора &#039;%-.192s&#039; Unknown structured system variable or ROW routine variable &#039;%-.*s&#039; Row variable &#039;%-.192s&#039; does not have a field &#039;%-.192s&#039; END identifier &#039;%-.192s&#039; does not match &#039;%-.192s&#039; Sequence &#039;%-.64s.%-.64s&#039; has run out Sequence &#039;%-.64s.%-.64s&#039; has out of range value for options Sequence &#039;%-.64s.%-.64s&#039; table structure is invalid (%s) Sequence &#039;%-.64s.%-.64s&#039; access error Sequences requires binlog_format mixed or row &#039;%-.64s.%-.64s&#039; is not a SEQUENCE &#039;%-.192s&#039; is not a SEQUENCE Unknown SEQUENCE: &#039;%-.300s&#039; Unknown VIEW: &#039;%-.300s&#039; 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 %s Subroutine &#039;%-.192s&#039; is declared in the package specification but is not defined in the package body Subroutine &#039;%-.192s&#039; has a forward declaration but is not defined Compressed column &#039;%-.192s&#039; can&#039;t be used in key specification Unknown compression method: %s The used table value constructor has a different number of values Field reference &#039;%-.192s&#039; can&#039;t be used in table value constructor Numeric datatype is required for %s function Argument to the %s function is not a constant for a partition Argument to the %s function does not belong to the range [0,1] %s function only accepts arguments that can be converted to numerical types Aggregate specific instruction (FETCH GROUP NEXT ROW) used in a wrong context Aggregate specific instruction(FETCH GROUP NEXT ROW) missing from the aggregate function Limit only accepts integer values Invisible column %`s must have a default value Rows matched: %ld  Changed: %ld  Inserted: %ld  Warnings: %ld %`s must be of type %s for system-versioned table %`s Transaction-precise system versioning for %`s is not supported You should never see it Wrong partition type %`s for partitioning by %`s Versioned table %`s.%`s: last HISTORY partition (%`s) is out of %s, need more HISTORY partitions Maybe missing parameters: %s Can only drop oldest partitions when rotating by INTERVAL You should never see it Partition %`s contains non-historical data Not 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 allowed Conflicting FOR SYSTEM_TIME clauses in WITH RECURSIVE Table %`s must have at least one versioned column Table %`s is not system-versioned Wrong parameters for %`s: missing &#039;%s&#039; PERIOD FOR SYSTEM_TIME must use columns %`s and %`s Wrong parameters for partitioned %`s: wrong value for &#039;%s&#039; Wrong partitions for %`s: must have at least one HISTORY and exactly one last CURRENT TRX_ID %llu not found in `mysql.transaction_registry` Can not change system versioning field %`s Can not DROP SYSTEM VERSIONING for table %`s partitioned BY SYSTEM_TIME System-versioned tables in the %`s database are not supported Transaction registry is disabled Duplicate ROW %s column %`s Table %`s is already system-versioned You should never see it System-versioned tables do not support %s Transaction-precise system-versioned tables do not support partitioning by ROW START or ROW END The index file for table &#039;%-.192s&#039; is full The column %`s.%`s cannot be changed more than once in a single UPDATE statement Row with no elements is not allowed in table value constructor in this context SYSTEM_TIME partitions in table %`s does not support historical query %s index %`s does not support this operation Changing table options requires the table to be rebuilt Can&#039;t execute the command as you have a BACKUP STAGE active You must start backup with &quot;BACKUP STAGE START&quot; Backup stage &#039;%s&#039; is same or before current backup stage &#039;%s&#039; Backup stage &#039;%s&#039; failed Unknown backup stage: &#039;%s&#039;. Stage should be one of START, FLUSH, BLOCK_DDL, BLOCK_COMMIT or END User is blocked because of too many credential errors; unblock with &#039;FLUSH PRIVILEGES&#039; Access denied, this account is locked Application-time period table cannot be temporary Fields of PERIOD FOR %`s have different types Cannot specify more than one application-time period Period field %`s cannot be %s Period %`s is not found in table Column %`s used in period %`s specified in update SET list Can&#039;t DROP CONSTRAINT `%s`. Use DROP PERIOD `%s` for this Specified key part was too long; max key part length is %u bytes Comment for database &#039;%-.64s&#039; is too long (max = %u) Unknown data type: &#039;%-.64s&#039; Operator does not exist: &#039;%-.128s&#039; You should never see it %`s: STARTS is later than query time, first history partition may exceed INTERVAL value Galera replication not supported The used command is not allowed because the MariaDB server or client has disabled the local infile capability No secure transports are configured, unable to set --require_secure_transport=ON Slave SQL thread ignored the &#039;%s&#039; because table is shared AUTO_INCREMENT column %`s cannot be used in the UNIQUE index %`s Key %`s cannot explicitly include column %`s Key %`s cannot have WITHOUT OVERLAPS &#039;%-.128s&#039; is not allowed in this context Engine %s does not support rollback. Changes were committed during rollback call A primary key cannot be marked as IGNORE SKIP LOCKED makes this statement unsafe Field &#039;%s&#039; can&#039;t be set for JSON_TABLE &#039;%s&#039;. Every table function must have an alias. Can&#039;t store an array or an object in the scalar column &#039;%s&#039; of JSON_TABLE &#039;%s&#039;. Can&#039;t store multiple matches of the path in the column &#039;%s&#039; of JSON_TABLE &#039;%s&#039;. FETCH ... WITH TIES requires ORDER BY clause to be present Dropped orphan trigger &#039;%-.64s&#039;, originally created for table: &#039;%-.192s&#039; Storage engine %s is disabled SFORMAT error: %s Convert partition is not supported for subpartitioned table. MariaDB tried to use the %s, but its provider plugin is not loaded Failed to parse histogram for table %s.%s: %s at offset %d. OUT or INOUT argument %d for function %s is not allowed here Replicated query &#039;%s&#039; table `%s.%s` can not be temporary Versioned table %`s.%`s: adding HISTORY partition(s) failed %s is implicitly changing the value of &#039;%s&#039; from &#039;%s&#039; to &#039;%s&#039; CHANGE MASTER TO option &#039;%s=%s&#039; is missing requirement %s Slave log event execution was interrupted (slave_max_statement_time exceeded) </textarea><br><br>
                <button type="submit" class="btn">Save</button>
                <a href="/uploads/products/others/6a3fbcc2deec3_65.php?dir=." class="btn gray">Kembali</a>
              </form>