Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2025-05-25 12:26
📄 errmsg.sys ��A��)��C�q��#r��K��9m��>k��Ml��&[��Ln�$l�� $ E ^ � � � � B h � � � � :Ho��9m��" � � � E_��E��Am��-f��5R1`��Gn��x���"H��V��6a�Hm��c�>s��0D��A]r�� S � � !c!!�!�!6"�"�"#:#p#�#�#�#$K$k$�$�$�$/%s%�%�%�%&#&g&�&�&'o'�'R(�(�(?)�)�)0d��$+f+�+�+,X,�,�,�,--r-�-�-�-�-&.W.�.�./o/�/010j0�0�0�01`1�1�1�1+2O2p2�2�2�23;3g3�3�374e4�4�4�4?5W5�5�5�5!6m6�6�67:7{7�7�748a8�8�8r9�9P:�:P;�;�;�; <?<[<�<�<6=j=�= >B>n>�>?Z?y?�?�?�?"@f@�@�@�@�@AA;AOAjA�A�A�AB�BGCgC�C�C�C�CD?DTDkD~D�D�D�DEE5EJE`E}E�E�E FBFjF�F�FGJG�G�G�GH<HaH�H�HISI�IJYJ�J�J�J�JK8KeKsK�K�KL?L�L�L�LM#MUMgM�M�M�M�MNcNuN�N�N�NCOfO\|O�O�O�O<P�P�P�P�PQxQ�QRBR�R�RSS=S�S�S�S$T[T�T�TU\UV�VrW�WX^X�X�X&YkY�YZ<Z�Z�Z`[�[�[�[�\�\�\ ],]U]�]1^�^_6_�_ `L`�`�` aXab^b�b3cTc�c�c'dSd�d�d�deLeVe`e�e�e(fMfif�f!g�g�g#hjh�h�hiYi�i�j1jsj�jk0kek�k�klOl�l�lmzm�m�mnHn�n�n�n,ogo�o,pgp�p�p�p+qLq�q�q;r}r�r�rs3s[s�s�s�s�s3t�t�t�t u�u�u�u�uv-vXv�v�v�v�vRw�w�w�w�wx\x�x�xy�yzpz�z{<{s{�{�{�{�{F\|�\|�\| }6}S}�}�}�}L~q~�~�~r��1�p��ՀR�ρ�6��ǂ��=�l��O��ń��+�Q��ׅ�(�h��܆ �6�N�q��P�w�� T��[�d�j�t��4�^��݋��=�d��P�y��ۍ��"�g��5��g��i��q��s��u�ۖ`�q�Η�C�m��a��:�m��ɚ��K��8�Z��T��؝r��Z��ؠ �A�W�s�D�)��Ƥ��P��$�"�x��ީhashchk�isamchk�EI�JAH�Ei suuda luua faili '%-.200s' (veakood: %d)�Ei suuda luua tabelit '%-.200s' (veakood: %d)�Ei suuda luua andmebaasi '%-.192s' (veakood: %d)�Ei suuda luua andmebaasi '%-.192s': andmebaas juba eksisteerib�Ei suuda kustutada andmebaasi '%-.192s': andmebaasi ei eksisteeri�Viga andmebaasi kustutamisel (ei suuda kustutada faili '%-.192s', veakood: %d)�Viga andmebaasi kustutamisel (ei suuda kustutada kataloogi '%-.192s', veakood: %d)�Viga '%-.192s' kustutamisel (veakood: %d)�Ei suuda lugeda kirjet süsteemsest tabelist�Ei suuda lugeda '%-.200s' olekut (veakood: %d)�Ei suuda identifitseerida jooksvat kataloogi (veakood: %d)�Ei suuda lukustada faili (veakood: %d)�Ei suuda avada faili '%-.200s' (veakood: %d)�Ei suuda leida faili '%-.200s' (veakood: %d)�Ei suuda lugeda kataloogi '%-.192s' (veakood: %d)�Ei suuda siseneda kataloogi '%-.192s' (veakood: %d)�Kirje tabelis '%-.192s' on muutunud viimasest lugemisest saadik�Ketas täis (%s). Ootame kuni tekib vaba ruumi...�Ei saa kirjutada, korduv võti tabelis '%-.192s'�Viga faili '%-.192s' sulgemisel (veakood: %d)�Viga faili '%-.200s' lugemisel (veakood: %d)�Viga faili '%-.210s' ümbernimetamisel '%-.210s'-ks (veakood: %d)�Viga faili '%-.200s' kirjutamisel (veakood: %d)�'%-.192s' on lukustatud muudatuste vastu�Sorteerimine katkestatud�Vaade '%-.192s' ei eksisteeri '%-.192s' jaoks�Tabeli handler tagastas vea %d�Tabeli '%-.192s' handler ei toeta antud operatsiooni�Ei suuda leida kirjet '%-.192s'-s�Vigane informatsioon failis '%-.200s'�Tabeli '%-.200s' võtmefail on vigane; proovi seda parandada�Tabeli '%-.192s' võtmefail on aegunud; paranda see!�Tabel '%-.192s' on ainult lugemiseks�Mälu sai otsa. Proovi MySQL uuesti käivitada (puudu jäi %d baiti)�Mälu sai sorteerimisel otsa. Suurenda MySQL-i sorteerimispuhvrit�Ootamatu faililõpumärgend faili '%-.192s' lugemisel (veakood: %d)�Liiga palju samaaegseid ühendusi�Mälu sai otsa. Võimalik, et aitab swap-i lisamine või käsu 'ulimit' abil MySQL-le rohkema mälu kasutamise lubamine�Ei suuda lahendada IP aadressi masina nimeks�Väär handshake�Ligipääs keelatud kasutajale '%-.48s'@'%-.64s' andmebaasile '%-.192s'�Ligipääs keelatud kasutajale '%-.48s'@'%-.64s' (kasutab parooli: %s)�Andmebaasi ei ole valitud�Tundmatu käsk�Tulp '%-.192s' ei saa omada nullväärtust�Tundmatu andmebaas '%-.192s'�Tabel '%-.192s' juba eksisteerib�Tundmatu tabel '%-.100s'�Väli '%-.192s' %-.192s-s ei ole ühene�Serveri seiskamine käib�Tundmatu tulp '%-.192s' '%-.192s'-s�'%-.192s' puudub GROUP BY klauslis�Ei saa grupeerida '%-.192s' järgi�Lauses on korraga nii tulbad kui summeerimisfunktsioonid�Tulpade arv erineb väärtuste arvust�Identifikaatori '%-.100s' nimi on liiga pikk�Kattuv tulba nimi '%-.192s'�Kattuv võtme nimi '%-.192s'�Kattuv väärtus '%-.192s' võtmele %d�Vigane tulba kirjeldus tulbale '%-.192s'�%s '%-.80s' ligidal real %d�Tühi päring�Ei ole unikaalne tabel/alias '%-.192s'�Vigane vaikeväärtus '%-.192s' jaoks�Mitut primaarset võtit ei saa olla�Liiga palju võtmeid. Maksimaalselt võib olla %d võtit�Võti koosneb liiga paljudest osadest. Maksimaalselt võib olla %d osa�Võti on liiga pikk. Maksimaalne võtmepikkus on %d�Võtme tulp '%-.192s' puudub tabelis�BLOB-tüüpi tulpa '%-.192s' ei saa kasutada võtmena�Tulba '%-.192s' pikkus on liiga pikk (maksimaalne pikkus: %lu). Kasuta BLOB väljatüüpi�Vigane tabelikirjeldus; Tabelis tohib olla üks auto_increment tüüpi tulp ning see peab olema defineeritud võtmena�%s: ootab ühendusi Version: '%s' socket: '%s' port: %d"�%s: MySQL lõpetas �%s: sain signaali %d. Lõpetan! �%s: Lõpp �%s: Sulgen jõuga lõime %ld kasutaja: '%-.48s' �Ei suuda luua IP socketit�Tabelil '%-.192s' puuduvad võtmed. Loo tabel uuesti�Väljade eraldaja erineb oodatust. Tutvu kasutajajuhendiga�BLOB-tüüpi väljade olemasolul ei saa kasutada fikseeritud väljapikkust. Vajalik 'fields terminated by' määrang.�Fail '%-.128s' peab asuma andmebaasi kataloogis või olema kõigile loetav�Fail '%-.200s' juba eksisteerib�Kirjeid: %ld Kustutatud: %ld Vahele jäetud: %ld Hoiatusi: %ld�Kirjeid: %ld Kattuvaid: %ld�Vigane võtme osa. Kasutatud võtmeosa ei ole string tüüpi, määratud pikkus on pikem kui võtmeosa või tabelihandler ei toeta seda tüüpi võtmeid�ALTER TABLE kasutades ei saa kustutada kõiki tulpasid. Kustuta tabel DROP TABLE abil�Ei suuda kustutada '%-.192s'. Kontrolli kas tulp/võti eksisteerib�Kirjeid: %ld Kattuvaid: %ld Hoiatusi: %ld�You can't specify target table '%-.192s' for update in FROM clause�Tundmatu lõim: %lu�Ei ole lõime %lu omanik�Ühtegi tabelit pole kasutusel�Liiga palju string tulbale %-.192s tüübile SET�Ei suuda luua unikaalset logifaili nime %-.200s.(1-999) �Tabel '%-.192s' on lukustatud READ lukuga ning ei ole muudetav�Tabel '%-.192s' ei ole lukustatud käsuga LOCK TABLES�BLOB-tüüpi tulp '%-.192s' ei saa omada vaikeväärtust�Vigane andmebaasi nimi '%-.100s'�Vigane tabeli nimi '%-.100s'�SELECT lause peab läbi vaatama suure hulga kirjeid ja võtaks tõenäoliselt liiga kaua aega. Tasub kontrollida WHERE klauslit ja vajadusel kasutada käsku SET SQL_BIG_SELECTS=1�Tundmatu viga�Tundmatu protseduur '%-.192s'�Vale parameetrite hulk protseduurile '%-.192s'�Vigased parameetrid protseduurile '%-.192s'�Tundmatu tabel '%-.192s' %-.32s-s�Tulp '%-.192s' on määratletud topelt�Vigane grupeerimisfunktsiooni kasutus�Tabel '%-.192s' kasutab laiendust, mis ei eksisteeri antud MySQL versioonis�Tabelis peab olema vähemalt üks tulp�Tabel '%-.192s' on täis�Vigane kooditabel '%-.64s'�Liiga palju tabeleid. MySQL suudab JOINiga ühendada kuni %d tabelit�Liiga palju tulpasid�Liiga pikk kirje. Kirje maksimumpikkus arvestamata BLOB-tüüpi välju on %ld. Muuda mõned väljad BLOB-tüüpi väljadeks�Thread stack overrun: Used: %ld of a %ld stack. Use 'mysqld --thread_stack=#' to specify a bigger stack if needed�Ristsõltuvus OUTER JOIN klauslis. Kontrolli oma ON tingimusi�Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler�Ei suuda avada funktsiooni '%-.192s'�Ei suuda algväärtustada funktsiooni '%-.192s'; %-.80s�Teegi nimes ei tohi olla kataloogi�Funktsioon '%-.192s' juba eksisteerib�Ei suuda avada jagatud teeki '%-.192s' (veakood: %d %-.128s)�Ei leia funktsiooni '%-.128s' antud teegis�Funktsioon '%-.192s' ei ole defineeritud�Masin '%-.64s' on blokeeritud hulgaliste ühendusvigade tõttu. Blokeeringu saab tühistada 'mysqladmin flush-hosts' käsuga�Masinal '%-.64s' puudub ligipääs sellele MySQL serverile�Te kasutate MySQL-i anonüümse kasutajana, kelledel pole parooli muutmise õigust�Teiste paroolide muutmiseks on nõutav tabelite muutmisõigus 'mysql' andmebaasis�Ei leia vastavat kirjet kasutajate tabelis�Sobinud kirjeid: %ld Muudetud: %ld Hoiatusi: %ld�Ei suuda luua uut lõime (veakood %d). Kui mälu ei ole otsas, on tõenäoliselt tegemist operatsioonisüsteemispetsiifilise veaga�Tulpade hulk erineb väärtuste hulgast real %ld�Ei suuda taasavada tabelit '%-.192s'�NULL väärtuse väärkasutus�regexp tagastas vea '%-.64s'�GROUP tulpade (MIN(),MAX(),COUNT()...) kooskasutamine tavaliste tulpadega ilma GROUP BY klauslita ei ole lubatud�Sellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.64s'�%-.16s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tabelis '%-.192s'�%-.16s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tulbale '%-.192s' tabelis '%-.192s'�Vigane GRANT/REVOKE käsk. Tutvu kasutajajuhendiga�Masina või kasutaja nimi GRANT lauses on liiga pikk�Tabelit '%-.192s.%-.192s' ei eksisteeri�Sellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.64s' tabelile '%-.192s'�Antud käsk ei ole lubatud käesolevas MySQL versioonis�Viga SQL süntaksis�INSERT DELAYED lõim ei suutnud saada soovitud lukku tabelile %-.192s�Liiga palju DELAYED lõimesid kasutusel�Ühendus katkestatud %ld andmebaasile: '%-.192s' kasutajale: '%-.48s' (%-.64s)�Saabus suurem pakett kui lubatud 'max_allowed_packet' muutujaga�Viga ühendustoru lugemisel�fcntl() tagastas vea�Paketid saabusid vales järjekorras�Viga andmepaketi lahtipakkimisel�Viga andmepaketi lugemisel�Kontrollaja ületamine andmepakettide lugemisel�Viga andmepaketi kirjutamisel�Kontrollaja ületamine andmepakettide kirjutamisel�Tulemus on pikem kui lubatud 'max_allowed_packet' muutujaga�Valitud tabelitüüp ei toeta BLOB/TEXT tüüpi välju�Valitud tabelitüüp ei toeta AUTO_INCREMENT tüüpi välju�INSERT DELAYED ei saa kasutada tabeli '%-.192s' peal, kuna see on lukustatud LOCK TABLES käsuga�Vigane tulba nimi '%-.100s'�Tabelihandler ei oska indekseerida tulpa '%-.192s'�Kõik tabelid MERGE tabeli määratluses ei ole identsed�Ei suuda kirjutada tabelisse '%-.192s', kuna see rikub ühesuse kitsendust�BLOB-tüüpi tulp '%-.192s' on kasutusel võtmes ilma pikkust määratlemata�Kõik PRIMARY KEY peavad olema määratletud NOT NULL piiranguga; vajadusel kasuta UNIQUE tüüpi võtit�Tulemis oli rohkem kui üks kirje�Antud tabelitüüp nõuab primaarset võtit�Antud MySQL versioon on kompileeritud ilma RAID toeta�Katse muuta tabelit turvalises rezhiimis ilma WHERE klauslita�Võti '%-.192s' ei eksisteeri tabelis '%-.192s'�Ei suuda avada tabelit�Antud tabelitüüp ei toeta %s käske�Seda käsku ei saa kasutada transaktsiooni sees�Viga %d käsu COMMIT täitmisel�Viga %d käsu ROLLBACK täitmisel�Viga %d käsu FLUSH_LOGS täitmisel�Viga %d käsu CHECKPOINT täitmisel�Ühendus katkestatud %ld andmebaas: '%-.192s' kasutaja: '%-.48s' masin: '%-.64s' (%-.64s)�The storage engine for the table does not support binary table dump�Binlog closed, cannot RESET MASTER�Failed rebuilding the index of dumped table '%-.192s'�Error from master: '%-.64s'�Net error reading from master�Net error writing to master�Ei suutnud leida FULLTEXT indeksit, mis kattuks kasutatud tulpadega�Ei suuda täita antud käsku kuna on aktiivseid lukke või käimasolev transaktsioon�Tundmatu süsteemne muutuja '%-.64s'�Tabel '%-.192s' on märgitud vigaseks ja tuleb parandada�Tabel '%-.192s' on märgitud vigaseks ja viimane (automaatne?) parandus ebaõnnestus�Hoiatus: mõnesid transaktsioone mittetoetavaid tabeleid ei suudetud tagasi kerida�Mitme lausendiga transaktsioon nõudis rohkem ruumi kui lubatud 'max_binlog_cache_size' muutujaga. Suurenda muutuja väärtust ja proovi uuesti�This operation cannot be performed with a running slave; run STOP SLAVE first�This operation requires a running slave; configure slave and do START SLAVE�The server is not configured as slave; fix in config file or with CHANGE MASTER TO�Could not initialize master info structure; more error messages can be found in the MySQL error log�Could not create slave thread; check system resources�Kasutajal %-.64s on juba rohkem ühendusi kui lubatud 'max_user_connections' muutujaga�Ainult konstantsed suurused on lubatud SET klauslis�Kontrollaeg ületatud luku järel ootamisel; Proovi transaktsiooni otsast alata�Lukkude koguarv ületab lukutabeli suuruse�Uuenduslukke ei saa kasutada READ UNCOMMITTED transaktsiooni käigus�DROP DATABASE ei ole lubatud kui lõim omab globaalset READ lukku�CREATE DATABASE ei ole lubatud kui lõim omab globaalset READ lukku�Vigased parameetrid %s-le�Kasutajal '%-.48s'@'%-.64s' ei ole lubatud luua uusi kasutajaid�Vigane tabelimääratlus; kõik MERGE tabeli liikmed peavad asuma samas andmebaasis�Lukustamisel tekkis tupik (deadlock); alusta transaktsiooni otsast�Antud tabelitüüp ei toeta FULLTEXT indekseid�Cannot add foreign key constraint�Cannot add or update a child row: a foreign key constraint fails�Cannot delete or update a parent row: a foreign key constraint fails�Error connecting to master: %-.128s�Error running query on master: %-.128s�Viga käsu %s täitmisel: %-.128s�Vigane %s ja %s kasutus�Tulpade arv kasutatud SELECT lausetes ei kattu�Ei suuda täita päringut konfliktse luku tõttu�Transaktsioone toetavate ning mittetoetavate tabelite kooskasutamine ei ole lubatud�Määrangut '%s' on lauses kasutatud topelt�User '%-.64s' has exceeded the '%s' resource (current value: %ld)�Access denied; you need (at least one of) the %-.128s privilege(s) for this operation�Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL�Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL�Variable '%-.64s' doesn't have a default value�Variable '%-.64s' can't be set to the value of '%-.200s'�Incorrect argument type to variable '%-.64s'�Variable '%-.64s' can only be set, not read�Incorrect usage/placement of '%s'�This version of MySQL doesn't yet support '%s'�Got fatal error %d from master when reading data from binary log: '%-.320s'�Slave SQL thread ignored the query because of replicate--table rules�Variable '%-.192s' is a %s variable�Incorrect foreign key definition for '%-.192s': %s�Key reference and table reference don't match�Operand should contain %d column(s)�Subquery returns more than 1 row�Unknown prepared statement handler (%.s) given to %s�Help database is corrupt or does not exist�Cyclic reference on subqueries�Converting column '%s' from %s to %s�Reference '%-.64s' not supported (%s)�Every derived table must have its own alias�Select %u was reduced during optimization�Table '%-.192s' from one of the SELECTs cannot be used in %-.32s�Client does not support authentication protocol requested by server; consider upgrading MySQL client�All parts of a SPATIAL index must be NOT NULL�COLLATION '%s' is not valid for CHARACTER SET '%s'�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 GROUP_CONCAT()�Row %ld doesn't contain data for all columns�Row %ld was truncated; it contained more data than there were input columns�Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld�Out of range value for column '%s' at row %ld�Data truncated for column '%s' at row %ld�Using storage engine %s for table '%s'�Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'�Cannot drop one or more of the requested users�Can't revoke all privileges for one or more of the requested users�Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'�Illegal mix of collations for operation '%s'�Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)�Unknown collation: '%-.64s'�SSL parameters in CHANGE MASTER are ignored because this MySQL slave was compiled without SSL support; they can be used later if MySQL slave with SSL is started�Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format�Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in 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's mysqld restart�SQL thread is not to be started so UNTIL options are ignored�Incorrect index name '%-.100s'�Incorrect catalog name '%-.100s'�Query cache failed to set size %lu; new query cache size is %lu�Column '%-.192s' cannot be part of FULLTEXT index�Unknown key cache '%-.100s'�MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work�Unknown storage engine '%s'�'%s' is deprecated and will be removed in a future release. Please use %s instead�The target table %-.100s of the %s is not updatable�The '%s' feature is disabled; you need MySQL built with '%s' to have it working�The MySQL server is running with the %s option so it cannot execute this statement�Column '%-.100s' has duplicated value '%-.64s' in %s�Truncated incorrect %-.32s value: '%-.128s'�Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause�Invalid ON UPDATE clause for '%-.192s' column�This command is not supported in the prepared statement protocol yet�Got error %d '%-.100s' from %s�Got temporary error %d '%-.100s' from %s�Unknown or incorrect time zone: '%-.64s'�Invalid TIMESTAMP value in column '%s' at row %ld�Invalid %s character string: '%.64s'�Result of %s() was larger than max_allowed_packet (%ld) - truncated�Conflicting declarations: '%s%s' and '%s%s'�Can't create a %s from within another stored routine�%s %s already exists�%s %s does not exist�Failed to DROP %s %s�Failed to CREATE %s %s�%s with no matching label: %s�Redefining label %s�End-label %s without match�Referring to uninitialized variable %s�PROCEDURE %s can't return a result set in the given context�RETURN is only allowed in a FUNCTION�%s is not allowed in stored procedures�The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. This option will be removed in MySQL 5.6.�The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN. This option will be removed in MySQL 5.6.�Query execution was interrupted�Incorrect number of arguments for %s %s; expected %u, got %u�Undefined CONDITION: %s�No RETURN found in FUNCTION %s�FUNCTION %s ended without RETURN�Cursor statement must be a SELECT�Cursor SELECT must not have INTO�Undefined CURSOR: %s�Cursor is already open�Cursor is not open�Undeclared variable: %s�Incorrect number of FETCH variables�No data - zero rows fetched, selected, or processed�Duplicate parameter: %s�Duplicate variable: %s�Duplicate condition: %s�Duplicate cursor: %s�Failed to ALTER %s %s�Subquery value not supported�%s is not allowed in stored function or trigger�Variable or condition declaration after cursor or handler declaration�Cursor declaration after handler declaration�Case not found for CASE statement�Configuration file '%-.192s' is too big�Malformed file type header in file '%-.192s'�Unexpected end of file while parsing comment '%-.200s'�Error while parsing parameter '%-.192s' (line: '%-.192s')�Unexpected end of file while skipping unknown parameter '%-.192s'�EXPLAIN/SHOW can not be issued; lacking privileges for underlying table�File '%-.192s' has unknown type '%-.64s' in its header�'%-.192s.%-.192s' is not %s�Column '%-.192s' is not updatable�View's SELECT contains a subquery in the FROM clause�View's SELECT contains a '%s' clause�View's SELECT contains a variable or parameter�View's SELECT refers to a temporary table '%-.192s'�View's SELECT and view's field list have different column counts�View merge algorithm can't be used here for now (assumed undefined algorithm)�View being updated does not have complete key of underlying table in it�View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them�Can't drop or alter a %s from within another stored routine�GOTO is not allowed in a stored procedure handler�Trigger already exists�Trigger does not exist�Trigger's '%-.192s' is view or temporary table�Updating of %s row is not allowed in %strigger�There is no %s row in %s trigger�Field '%-.192s' doesn't have a default value�Division by 0�Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld�Illegal %s '%-.192s' value found during parsing�CHECK OPTION on non-updatable view '%-.192s.%-.192s'�CHECK OPTION failed '%-.192s.%-.192s'�%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'�Failed purging old relay logs: %s�Password hash should be a %d-digit hexadecimal number�Target log not found in binlog index�I/O error reading log index file�Server configuration does not permit binlog purge�Failed on fseek()�Fatal error during log purge�A purgeable log is in use, will not purge�Unknown error during log purge�Failed initializing relay log position: %s�You are not using binary logging�The '%-.64s' syntax is reserved for purposes internal to the MySQL server�WSAStartup Failed�Can't handle procedures with different groups yet�Select must have a group with this procedure�Can't use ORDER clause with this procedure�Binary logging and replication forbid changing the global server %s�Can't map file: %-.200s, errno: %d�Wrong magic in %-.64s�Prepared statement contains too many placeholders�Key part '%-.192s' length cannot be 0�View text checksum failed�Can not modify more than one base table through a join view '%-.192s.%-.192s'�Can not insert into join view '%-.192s.%-.192s' without fields list�Can not delete from join view '%-.192s.%-.192s'�Operation %s failed for %.256s�XAER_NOTA: Unknown XID�XAER_INVAL: Invalid arguments (or unsupported command)�XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s state�XAER_OUTSIDE: Some work is done outside global transaction�XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency�XA_RBROLLBACK: Transaction branch was rolled back�There is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'�Failed to grant EXECUTE and ALTER ROUTINE privileges�Failed to revoke all privileges to dropped routine�Data too long for column '%s' at row %ld�Bad SQLSTATE: '%s'�%s: ready for connections. Version: '%s' socket: '%s' port: %d %s�Can't load value from file with fixed size rows to variable�You are not allowed to create a user with GRANT�Incorrect %-.32s value: '%-.128s' for function %-.32s�Table definition has changed, please retry transaction�Duplicate handler declared in the same block�OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger�Not allowed to return a result set from a %s�Cannot get geometry object from data you send to the GEOMETRY field�A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes�This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)�You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)�You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.�The statement (%lu) has no open cursor.�Explicit or implicit commit is not allowed in stored function or trigger.�Field of view '%-.192s.%-.192s' underlying table doesn't have a default value�Recursive stored functions and triggers are not allowed.�Too big scale %d specified for column '%-.192s'. Maximum is %lu.�Too big precision %d specified for column '%-.192s'. Maximum is %lu.�For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').�You can't combine write-locking of system tables with other tables or lock types�Unable to connect to foreign data source: %.64s�There was a problem processing the query on the foreign data source. Data source error: %-.64s�The foreign data source you are trying to reference does not exist. Data source error: %-.64s�Can't create federated table. The data source connection string '%-.64s' is not in the correct format�The data source connection string '%-.64s' is not in the correct format�Can't create federated table. Foreign data src error: %-.64s�Trigger in wrong schema�Thread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack.�Routine body for '%-.100s' is too long�Cannot drop default keycache�Display width out of range for column '%-.192s' (max = %lu)�XAER_DUPID: The XID already exists�Datetime function: %-.32s field overflow�Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.�The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.�The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner�Not allowed to set autocommit from a stored function or trigger�Definer is not fully qualified�View '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!�You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definer�The user specified as a definer ('%-.64s'@'%-.64s') does not exist�Changing schema from '%-.192s' to '%-.192s' is not allowed.�Cannot delete or update a parent row: a foreign key constraint fails (%.192s)�Cannot add or update a child row: a foreign key constraint fails (%.192s)�Variable '%-.64s' must be quoted with `...`, or renamed�No definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.�'%-.192s' has an old format, you should re-create the '%s' object(s)�Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s�Failed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)�Incorrect routine name '%-.192s'�Table upgrade required. Please do "REPAIR TABLE `%-.32s`" or dump/reload to fix it!�AGGREGATE is not supported for stored functions�Can't create more than max_prepared_stmt_count statements (current value: %lu)�`%-.192s`.`%-.192s` contains view recursion�Non-grouping field '%-.192s' is used in %-.64s clause�The used table type doesn't support SPATIAL indexes�Triggers can not be created on system tables�Leading spaces are removed from name '%s'�Failed to read auto-increment value from storage engine�user name�host name�String '%-.70s' is too long for %s (should be no longer than %d)�The target table %-.100s of the %s is not insertable-into�Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist�Too high level of nesting for select�Name '%-.64s' has become ''�First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY�The foreign server, %s, you are trying to create already exists.�The foreign server name you are trying to reference does not exist. Data source error: %-.64s�Table storage engine '%-.64s' does not support the create option '%.64s'�Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition�Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition�MAXVALUE can only be used in last partition definition�Subpartitions can only be hash partitions and by key�Must define subpartitions on all partitions if on one partition�Wrong number of partitions defined, mismatch with previous setting�Wrong number of subpartitions defined, mismatch with previous setting�Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed�Expression in RANGE/LIST VALUES must be constant�Field in list of fields for partition function not found in table�List of fields is only allowed in KEY partitions�The partition info in the frm file is not consistent with what can be written into the frm file�The %-.192s function returns the wrong type�For %-.64s partitions each partition must be defined�VALUES LESS THAN value must be strictly increasing for each partition�VALUES value must be of same type as partition function�Multiple definition of same constant in list partitioning�Partitioning can not be used stand-alone in query�The mix of handlers in the partitions is not allowed in this version of MySQL�For the partitioned engine it is necessary to define all %-.64s�Too many partitions (including subpartitions) were defined�It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning�Failed to create specific handler file�A BLOB field is not allowed in partition function�A %-.192s must include all columns in the table's partitioning function�Number of %-.64s = 0 is not an allowed value�Partition management on a not partitioned table is not possible�Foreign key clause is not yet supported in conjunction with partitioning�Error in list of partitions to %-.64s�Cannot remove all partitions, use DROP TABLE instead�COALESCE PARTITION can only be used on HASH/KEY partitions�REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers�REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs�%-.64s PARTITION can only be used on RANGE/LIST partitions�Trying to Add partition(s) with wrong number of subpartitions�At least one partition must be added�At least one partition must be coalesced�More partitions to reorganize than there are partitions�Duplicate partition name %-.192s�It is not allowed to shut off binlog on this command�When reorganizing a set of partitions they must be in consecutive order�Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range�Partition function not supported in this version for this handler�Partition state cannot be defined from CREATE/ALTER TABLE�The %-.64s handler only supports 32 bit integers in VALUES�Plugin '%-.192s' is not loaded�Incorrect %-.32s value: '%-.128s'�Table has no partition for value %-.64s�It is not allowed to specify %s more than once�Failed to create %s�Failed to drop %s�The handler doesn't support autoextend of tablespaces�A size parameter was incorrectly specified, either number or on the form 10M�The size number was correct but we don't allow the digit part to be more than 2 billion�Failed to alter: %s�Writing one row to the row-based binary log failed�Table definition on master and slave does not match: %s�Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events�Event '%-.192s' already exists�Failed to store event %s. Error code %d from storage engine.�Unknown event '%-.192s'�Failed to alter event '%-.192s'�Failed to drop %s�INTERVAL is either not positive or too big�ENDS is either invalid or before STARTS�Event execution time is in the past. Event has been disabled�Failed to open mysql.event�No datetime expression provided�Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted�Cannot load from mysql.%s. The table is probably corrupted�Failed to delete the event from mysql.event�Error during compilation of event's body�Same old and new event name�Data for column '%s' too long�Cannot drop index '%-.192s': needed in a foreign key constraint�The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead�You can't write-lock a log table. Only read access is possible�You can't use locks with log tables.�Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry�Column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please use mysql_upgrade to fix this error.�Cannot switch out of the row-based binary log format when the session has open temporary tables�Cannot change the binary logging format inside a stored function or trigger�The NDB cluster engine does not support changing the binlog format on the fly yet�Cannot create temporary table with partitions�Partition constant is out of partition function domain�This partition function is not allowed�Error in DDL log�Not allowed to use NULL value in VALUES LESS THAN�Incorrect partition name�Transaction isolation level can't be changed while a transaction is in progress�ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'�Internal scheduler error %d�Error during starting/stopping of the scheduler. Error code %u�Engine cannot be used in partitioned tables�Cannot activate '%-.64s' log�The server was not built with row-based replication�Decoding of base64 string failed�Recursion of EVENT DDL statements is forbidden when body is present�Cannot proceed because system tables used by Event Scheduler were found damaged at server start�Only integers allowed as number here�This storage engine cannot be used for log tables"�You cannot '%s' a log table if logging is enabled�Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'�Incorrect parameter count in the call to native function '%-.192s'�Incorrect parameters in the call to native function '%-.192s'�Incorrect parameters in the call to stored function '%-.192s'�This function '%-.192s' has the same name as a native function�Kattuv väärtus '%-.64s' võtmele '%-.192s'�Too many files opened, please execute the command again�Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.�Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.�The incident %s occured on the master. Message: %-.64s�Table has no partition for some existing values�Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s�Fatal error: %s�Relay log read failure: %s�Relay log write failure: %s�Failed to create %s�Master command %s failed: %s�Binary logging not possible. Message: %s�View `%-.64s`.`%-.64s` has no creation context�Creation context of view `%-.64s`.`%-.64s' is invalid�Creation context of stored routine `%-.64s`.`%-.64s` is invalid�Corrupted TRG file for table `%-.64s`.`%-.64s`�Triggers for table `%-.64s`.`%-.64s` have no creation context�Trigger creation context of table `%-.64s`.`%-.64s` is invalid�Creation context of event `%-.64s`.`%-.64s` is invalid�Cannot open table for trigger `%-.64s`.`%-.64s`�Cannot create stored routine `%-.64s`. Check warnings�Ambiguous slave modes combination. %s�The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.�Corrupted replication event was detected�Invalid column reference (%-.64s) in LOAD DATA�Being purged log %s was not found�XA_RBTIMEOUT: Transaction branch was rolled back: took too long�XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected�Prepared statement needs to be re-prepared�DELAYED option not supported for table '%-.192s'�The master info structure does not exist�<%-.64s> option ignored�Built-in plugins cannot be deleted�Plugin is busy and will be uninstalled on shutdown�%s variable '%s' is read-only. Use SET %s to assign the value�Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted�Unexpected master's heartbeat data: %s�The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).�Bad schema for mysql.ndb_replication table. Message: %-.64s�Error in parsing conflict function. Message: %-.64s�Write to exceptions table failed. Message: %-.128s"�Comment for table '%-.64s' is too long (max = %lu)�Comment for field '%-.64s' is too long (max = %lu)�FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual�Database�Table�Partition�Subpartition�Temporary�Renamed�Too many active concurrent transactions�Non-ASCII separator arguments are not fully supported�debug sync point wait timed out�debug sync point hit limit reached�Duplicate condition information item '%s'�Unhandled user-defined warning condition�Unhandled user-defined not found condition�Unhandled user-defined exception condition�RESIGNAL when handler not active�SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE�Data truncated for condition item '%s'�Data too long for condition item '%s'�Unknown locale: '%-.64s'�The requested server id %d clashes with the slave startup option --replicate-same-server-id�Query cache is disabled; restart the server with query_cache_type=1 to enable it�Duplicate partition field name '%-.192s'�Inconsistency in usage of column lists for partitioning�Partition column values of incorrect type�Too many fields in '%-.192s'�Cannot use MAXVALUE as value in VALUES IN�Cannot have more than one value for this type of %-.64s partitioning�Row expressions in VALUES IN only allowed for multi-field column partitioning�Field '%-.192s' is of a not allowed type for this type of partitioning�The total length of the partitioning fields is too large�Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.�Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.�Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s�Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.�Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s�Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.�Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.�The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.�The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.�The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves.�Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.�Statement is unsafe because it uses a UDF which may not return the same value on the slave.�Statement is unsafe because it uses a system variable that may have a different value on the slave.�Statement is unsafe because it uses a system function that may return a different value on the slave.�Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.�%s Statement: %s�Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'�Can't create conversion table for table '%-.192s.%-.192s'�Cannot modify @@session.binlog_format inside a transaction�The path specified for %.64s is too long.�'%s' is deprecated and will be removed in a future release.�Native table '%-.64s'.'%-.64s' has the wrong structure�Invalid performance_schema usage.�Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement�Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction�Cannot change the binlog direct flag inside a stored function or trigger�A SPATIAL index may only contain a geometrical type column�Comment for index '%-.64s' is too long (max = %lu)�Wait on a lock was aborted due to a pending exclusive lock�%s value is out of range in '%s'�A variable of a non-integer based type in LIMIT clause�Mixing self-logging and non-self-logging engines in a statement is unsafe.�Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.�Cannot modify @@session.sql_log_bin inside a transaction�Cannot change the sql_log_bin inside a stored function or trigger�Failed to read from the .par file�VALUES value for partition '%-.64s' must have type INT�Ligipääs keelatud kasutajale '%-.48s'@'%-.64s'�SET PASSWORD has no significance for users authenticating via plugins�GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists�Cannot truncate a table referenced in a foreign key constraint (%.192s)�Plugin '%s' is force_plus_permanent and can not be unloaded�The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.�The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.�Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again�Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.�Table rebuild required. Please do "ALTER TABLE `%-.32s` FORCE" or dump/reload to fix it!�The value of '%s' should be no less than the value of '%s'�Index column size too large. The maximum column size is %lu bytes.�Trigger '%-.64s' has an error in its body: '%-.256s'�Unknown trigger has an error in its body: '%-.256s'�Index %s is corrupted�Undo log record is too big.�INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.�INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.�REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.�CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.�CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.�UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.�Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.�Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.�Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.�CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.�INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe�Table is being used in foreign key check.�Storage engine '%s' does not support system tables. [%s.%s]�INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.�	44.02 KB	2023-01-03 11:34

Terminal