PAL.C.T MINI SHELL
țț Śî Ô , - 0 $ : F R - % D 3 # ) ) 6 * ? M 8 2 / ? 2 $ + * @ C / ' Y E ; © * 3 G L % ) " ) 7 0 % ( ) ! * # ' < D 9 " C U P 1 _ G O T : n M A + S " 4 5 H 0 4 ł 1 + # " + L " $ L | | ; $ 5 5 ! J > ) M ` ] + - & = . p M 9 L $ ; 3 c > 9 ; O : 6 ( * ) + ) + 5 B G ] - ; 3 ; o # ' 6 { 0 5 5 ^ # 7 , , . T @ N U o ] o h , I 0 @ 1 D C E 7 W T 6 . , - - 8 ' ! + 7 O # B B N I . 2 + 3 ! 5 H C ! 3 = $ # 6 , ' # 0 & = u 4 : o a ! - L N . * & A / C G - T „ X G č = ! L 9 o R 9 ` M 5 , y . E ) ) 2 % D , 5 ' < % ' € = ! " ! $ 4 0 F - " ( - 7 : B P 7 " 5 % / 4 A N H < 2 / / ! - A 0 5 & > " 6 % ! 2 * + ! L 2 - + D # 2 & N D 0 7 [ ; ] 2 W 5 3 ) E < 0 6 7 - c - D Ÿ Ć z ( J N 9 ; ? P Q 0 _ _ f H > ' 5 # ) P Š @ P C < N J 8 Á E c r ! F 0 O , 6 6 - * 8
A : M % w A _ I Z T D 6 @ B H ` = K < a + A L H < G K N C p 8 > H / G R ' R ? l { ? + ? B < " @ M B = 4 " ( / 6 M X 3 8 } = + ( = , ) @ W ? % ` L . D 1 D P i ? 0 4 ) D ` % 0 2 C > > ? ' 8 } 7 0 X ) / 6 @ / > ? 7 0 6 ] ) / " @ I + 1 % # 3 > n ' m 4 4 2 2 m
( 6 # * ) + + ! ? ' & \ K ) 8 * * E N G 9 § « ź © | }
€ \ d f
] : ; * < 7 " _ U I ; 3 ; ! 7 K r 9 B $ = 5 F L H < l Y ; C 5 4 Ń ć Ì Ń Ó · ț V * c 8 C h : ? ; G , " - a H = K N ? 7 8 ? @ S 5 œ 7 G Ï x ` = J O o s < i M + ' T { T _ = : G I á H ž â { " 5 = Á @ 7 ? > | c W . S % * T 2 E F ? 6 e h ? ) i + K ^ [ ~ K ^ g Ü? 1 9 ` + - 0 ) @ 3 " 1 U L 0 9 ! ( Ï j B h " 9 4 b : J l E H ^ c a 7 6 J 5 < > C / ? 3 4 - C 4 > 4 , : . ] [ O a > M > - < ? + . A ^ @ Ó D Ą Š U d u " K L ( # > 4 ; 7 4 . + / 6 hashchk isamchk NO YES Kan inte skapa filen '%-.200s' (Felkod: %M) Kan inte skapa tabellen %`s.%`s (Felkod: %M) Kan inte skapa databasen '%-.192s' (Felkod: %M) Databasen '%-.192s' existerar redan Kan inte radera databasen '%-.192s'; databasen finns inte Fel vid radering av databasen (Kan inte radera '%-.192s'. Felkod: %M) Fel vid radering av databasen (Kan inte radera biblioteket '%-.192s'. Felkod: %M) Kan inte radera filen '%-.192s' (Felkod: %M) Hittar inte posten i systemregistret Kan inte lĂ€sa filinformationen (stat) frĂ„n '%-.200s' (Felkod: %M) Kan inte inte lĂ€sa aktivt bibliotek. (Felkod: %M) Kan inte lĂ„sa filen. (Felkod: %M) Kan inte anvĂ€nda '%-.200s' (Felkod: %M) Hittar inte filen '%-.200s' (Felkod: %M) Kan inte lĂ€sa frĂ„n bibliotek '%-.192s' (Felkod: %M) Kan inte byta till '%-.192s' (Felkod: %M) Posten har förĂ€ndrats sedan den lĂ€stes i register '%-.192s' Disken Ă€r full (%s). VĂ€ntar tills det finns ledigt utrymme... (Felkod: %M) Kan inte skriva, dubbel söknyckel i register '%-.192s' Fick fel vid stĂ€ngning av '%-.192s' (Felkod: %M) Fick fel vid lĂ€sning av '%-.200s' (Felkod %M) Kan inte byta namn frĂ„n '%-.210s' till '%-.210s' (Felkod: %M) Fick fel vid skrivning till '%-.200s' (Felkod %M) '%-.192s' Ă€r lĂ„st mot anvĂ€ndning Sorteringen avbruten FormulĂ€r '%-.192s' finns inte i '%-.192s' Fick felkod %M frĂ„n databashanteraren %s Storage engine %s of the table %`s.%`s doesn't have this option Hittar inte posten '%-.192s' Felaktig fil: '%-.200s' Fatalt fel vid hantering av register '%-.200s'; kör en reparation Gammal nyckelfil '%-.192s'; reparera registret '%-.192s' Ă€r skyddad mot förĂ€ndring OvĂ€ntat slut pĂ„ minnet, starta om programmet och försök pĂ„ nytt (Behövde %d bytes) Sorteringsbufferten rĂ€cker inte till. Kontrollera startparametrarna OvĂ€ntat filslut vid lĂ€sning frĂ„n '%-.192s' (Felkod: %M) För mĂ„nga anslutningar Fick slut pĂ„ minnet. Kontrollera om mysqld eller nĂ„gon annan process anvĂ€nder allt tillgĂ€ngligt minne. Om inte, försök anvĂ€nda 'ulimit' eller allokera mera swap Kan inte hitta 'hostname' för din adress Fel vid initiering av kommunikationen med klienten AnvĂ€ndare '%s'@'%s' Ă€r ej berĂ€ttigad att anvĂ€nda databasen %-.192s AnvĂ€ndare '%s'@'%s' Ă€r ej berĂ€ttigad att logga in (AnvĂ€nder lösen: %s) Ingen databas i anvĂ€ndning OkĂ€nt kommando Kolumn '%-.192s' fĂ„r inte vara NULL OkĂ€nd databas: '%-.192s' Tabellen '%-.192s' finns redan OkĂ€nd tabell '%-.100s' Kolumn '%-.192s' i %-.192s Ă€r inte unik Servern gĂ„r nu ned OkĂ€nd kolumn '%-.192s' i %-.192s '%-.192s' finns inte i GROUP BY Kan inte anvĂ€nda GROUP BY med '%-.192s' Kommandot har bĂ„de sum functions och enkla funktioner Antalet kolumner motsvarar inte antalet vĂ€rden Kolumnnamn '%-.100s' Ă€r för lĂ„ngt Kolumnnamn '%-.192s finns flera gĂ„nger Nyckelnamn '%-.192s' finns flera gĂ„nger Dublett '%-.192s' för nyckel %d Felaktigt kolumntyp för kolumn '%-.192s' %s nĂ€ra '%-.80s' pĂ„ rad %d FrĂ„gan var tom Icke unikt tabell/alias: '%-.192s' Ogiltigt DEFAULT vĂ€rde för '%-.192s' Flera PRIMARY KEY anvĂ€nda För mĂ„nga nycklar anvĂ€nda. Man fĂ„r ha högst %d nycklar För mĂ„nga nyckeldelar anvĂ€nda. Man fĂ„r ha högst %d nyckeldelar För lĂ„ng nyckel. Högsta tillĂ„tna nyckellĂ€ngd Ă€r %d Nyckelkolumn '%-.192s' finns inte BLOB column %`s can't be used in key specification in the %s table För stor kolumnlĂ€ngd angiven för '%-.192s' (max= %lu). AnvĂ€nd en BLOB instĂ€llet Det fĂ„r finnas endast ett AUTO_INCREMENT-fĂ€lt och detta mĂ„ste vara en nyckel You should never see it %s: Normal avslutning
%s: Fick signal %d. Avslutar!
%s: Avslutning klar
%s: StÀnger av trÄd %ld; anvÀndare: '%-.48s'
Kan inte skapa IP-socket Tabellen '%-.192s' har inget index som motsvarar det angivna i CREATE INDEX. Skapa om tabellen FÀltseparatorerna Àr vad som förvÀntades. Kontrollera mot manualen Man kan inte anvÀnda fast radlÀngd med blobs. AnvÀnd 'fields terminated by' Textfilen '%-.128s' mÄste finnas i databasbiblioteket eller vara lÀsbar för alla Filen '%-.200s' existerar redan Rader: %ld Bortagna: %ld Dubletter: %ld Varningar: %ld Rader: %ld Dubletter: %ld Felaktig delnyckel. Nyckeldelen Àr inte en strÀng eller den angivna lÀngden Àr lÀngre Àn kolumnlÀngden Man kan inte radera alla fÀlt med ALTER TABLE. AnvÀnd DROP TABLE istÀllet Kan inte ta bort '%-.192s'. Kontrollera att fÀltet/nyckel finns Rader: %ld Dubletter: %ld Varningar: %ld Table '%-.192s' Àr anvÀnd tvÄ gÄnger. BÄde för '%s' och för att hÀmta data Finns ingen trÄd med id %lu Du Àr inte Àgare till trÄd %lu Inga tabeller angivna För mÄnga alternativ till kolumn %-.192s för SET Kan inte generera ett unikt filnamn %-.200s.(1-999)
Tabell '%-.192s' kan inte uppdateras emedan den Ă€r lĂ„st för lĂ€sning Tabell '%-.192s' Ă€r inte lĂ„st med LOCK TABLES BLOB fĂ€lt '%-.192s' kan inte ha ett DEFAULT-vĂ€rde Felaktigt databasnamn '%-.100s' Felaktigt tabellnamn '%-.100s' Den angivna frĂ„gan skulle lĂ€sa mer Ă€n MAX_JOIN_SIZE rader. Kontrollera din WHERE och anvĂ€nd SET SQL_BIG_SELECTS=1 eller SET MAX_JOIN_SIZE=# ifall du vill hantera stora joins OkĂ€nt fel OkĂ€nd procedur: %-.192s Felaktigt antal parametrar till procedur %-.192s Felaktiga parametrar till procedur %-.192s OkĂ€nd tabell '%-.192s' i '%-.32s' FĂ€lt '%-.192s' Ă€r redan anvĂ€nt Felaktig anvĂ€ndning av SQL grupp function Tabell '%-.192s' har en extension som inte finns i denna version av MariaDB Tabeller mĂ„ste ha minst 1 kolumn Tabellen '%-.192s' Ă€r full OkĂ€nd teckenuppsĂ€ttning: '%-.64s' För mĂ„nga tabeller. MariaDB can ha högst %d tabeller i en och samma join För mĂ„nga fĂ€lt För stor total radlĂ€ngd. Den högst tillĂ„tna radlĂ€ngden, förutom BLOBs, Ă€r %ld. Ăndra nĂ„gra av dina fĂ€lt till BLOB TrĂ„dstacken tog slut: Har anvĂ€nt %ld av %ld bytes. AnvĂ€nd 'mysqld --thread_stack=#' ifall du behöver en större stack Felaktigt referens i OUTER JOIN. Kontrollera ON-uttrycket Tabell hanteraren kan inte indexera NULL kolumner för den givna index typen. Ăndra '%-.192s' till NOT NULL eller anvĂ€nd en annan hanterare Kan inte ladda funktionen '%-.192s' Kan inte initialisera funktionen '%-.192s'; '%-.80s' Man fĂ„r inte ange sökvĂ€g för dynamiska bibliotek Funktionen '%-.192s' finns redan Kan inte öppna det dynamiska biblioteket '%-.192s' (Felkod: %d, %-.128s) Hittar inte funktionen '%-.128s' in det dynamiska biblioteket Funktionen '%-.192s' Ă€r inte definierad Denna dator, '%-.64s', Ă€r blockerad pga mĂ„nga felaktig paket. Gör 'mysqladmin flush-hosts' för att ta bort alla blockeringarna Denna dator, '%-.64s', har inte privileger att anvĂ€nda denna MariaDB server Du anvĂ€nder MariaDB som en anonym anvĂ€ndare och som sĂ„dan fĂ„r du inte Ă€ndra ditt lösenord För att Ă€ndra lösenord för andra mĂ„ste du ha rĂ€ttigheter att uppdatera mysql-databasen Hittade inte anvĂ€ndaren i 'user'-tabellen Rader: %ld Uppdaterade: %ld Varningar: %ld Kan inte skapa en ny trĂ„d (errno %M) Antalet kolumner motsvarar inte antalet vĂ€rden pĂ„ rad: %lu Kunde inte stĂ€nga och öppna tabell '%-.192s Felaktig anvĂ€nding av NULL Fick fel '%-.64s' frĂ„n REGEXP Man fĂ„r ha bĂ„de GROUP-kolumner (MIN(),MAX(),COUNT()...) och fĂ€lt i en frĂ„ga om man inte har en GROUP BY-del Det finns inget privilegium definierat för anvĂ€ndare '%-.48s' pĂ„ '%-.64s' %-.32s ej tillĂ„tet för '%s'@'%s' för tabell '%-.192s' %-.32s ej tillĂ„tet för '%s'@'%s' för kolumn '%-.192s' i tabell '%-.192s' Felaktigt GRANT-privilegium anvĂ€nt Felaktigt maskinnamn eller anvĂ€ndarnamn anvĂ€nt med GRANT Det finns ingen tabell som heter '%-.192s.%-.192s' Det finns inget privilegium definierat för anvĂ€ndare '%-.48s' pĂ„ '%-.64s' för tabell '%-.192s' Du kan inte anvĂ€nda detta kommando med denna MariaDB version Du har nĂ„got fel i din syntax DELAYED INSERT-trĂ„den kunde inte lĂ„sa tabell '%-.192s' Det finns redan 'max_delayed_threads' trĂ„dar i anvĂ€nding Avbröt lĂ€nken för trĂ„d %ld till db '%-.192s', anvĂ€ndare '%-.48s' (%-.64s) Kommunkationspaketet Ă€r större Ă€n 'max_allowed_packet' Fick lĂ€sfel frĂ„n klienten vid lĂ€sning frĂ„n 'PIPE' Fick fatalt fel frĂ„n 'fcntl()' Kommunikationspaketen kom i fel ordning Kunde inte packa up kommunikationspaketet Fick ett fel vid lĂ€sning frĂ„n klienten Fick 'timeout' vid lĂ€sning frĂ„n klienten Fick ett fel vid skrivning till klienten Fick 'timeout' vid skrivning till klienten ResultatstrĂ€ngen Ă€r lĂ€ngre Ă€n max_allowed_packet Den anvĂ€nda tabelltypen (%s) kan inte hantera BLOB/TEXT-kolumner Den anvĂ€nda tabelltypen (%s) kan inte hantera AUTO_INCREMENT-kolumner INSERT DELAYED kan inte anvĂ€ndas med tabell '%-.192s', emedan den Ă€r lĂ„st med LOCK TABLES Felaktigt kolumnnamn '%-.100s' The storage engine %s can't index column %`s Tabellerna i MERGE-tabellen Ă€r inte identiskt definierade Kan inte skriva till tabell '%-.192s'; UNIQUE-test Du har inte angett nĂ„gon nyckellĂ€ngd för BLOB '%-.192s' Alla delar av en PRIMARY KEY mĂ„ste vara NOT NULL; Om du vill ha en nyckel med NULL, anvĂ€nd UNIQUE istĂ€llet Resultet bestod av mera Ă€n en rad Denna tabelltyp krĂ€ver en PRIMARY KEY Denna version av MariaDB Ă€r inte kompilerad med RAID Du anvĂ€nder 'sĂ€ker uppdateringsmod' och försökte uppdatera en tabell utan en WHERE-sats som anvĂ€nder sig av en nyckel Nyckel '%-.192s' finns inte in tabell '%-.192s' Kan inte öppna tabellen Tabellhanteraren för denna tabell kan inte göra %s Du fĂ„r inte utföra detta kommando i en transaktion Fick fel %M vid COMMIT Fick fel %M vid ROLLBACK Fick fel %M vid FLUSH_LOGS Fick fel %M vid CHECKPOINT Avbröt lĂ€nken för trĂ„d %ld till db '%-.192s', anvĂ€ndare '%-.48s', host '%-.64s' (%-.64s) You should never see it Binlog closed, cannot RESET MASTER Failed rebuilding the index of dumped table '%-.192s' Fel frĂ„n master: '%-.64s' Fick nĂ€tverksfel vid lĂ€sning frĂ„n master Fick nĂ€tverksfel vid skrivning till master Hittar inte ett FULLTEXT-index i kolumnlistan Kan inte utföra kommandot emedan du har en lĂ„st tabell eller an aktiv transaktion OkĂ€nd systemvariabel: '%-.64s' Tabell '%-.192s' Ă€r trasig och bör repareras med REPAIR TABLE Tabell '%-.192s' Ă€r trasig och senast (automatiska?) reparation misslyckades Warning: NĂ„gra icke transaktionella tabeller kunde inte Ă„terstĂ€llas vid ROLLBACK Transaktionen krĂ€vde mera Ă€n 'max_binlog_cache_size' minne. Ăka denna mysqld-variabel och försök pĂ„ nytt Denna operation kan inte göras under replikering; Du har en aktiv förbindelse till '%2$*1$s'. Gör STOP SLAVE '%2$*1$s' först Denna operation kan endast göras under replikering; Konfigurera slaven och gör START SLAVE Servern Ă€r inte konfigurerade som en replikationsslav. Ăndra konfigurationsfilen eller gör CHANGE MASTER TO Kunde inte initialisera replikationsstrukturerna för '%.*s'. See MariaDB fel fil för mera information Kunde inte starta en trĂ„d för replikering AnvĂ€ndare '%-.64s' har redan 'max_user_connections' aktiva inloggningar Man kan endast anvĂ€nda konstantuttryck med SET Fick inte ett lĂ„s i tid ; Försök att starta om transaktionen Antal lĂ„s överskrider antalet reserverade lĂ„s UpdateringslĂ„s kan inte göras nĂ€r man anvĂ€nder READ UNCOMMITTED DROP DATABASE Ă€r inte tillĂ„tet nĂ€r man har ett globalt lĂ€slĂ„s CREATE DATABASE Ă€r inte tillĂ„tet nĂ€r man har ett globalt lĂ€slĂ„s Felaktiga argument till %s '%s'@'%s' har inte rĂ€ttighet att skapa nya anvĂ€ndare Felaktig tabelldefinition; alla tabeller i en MERGE-tabell mĂ„ste vara i samma databas Fick 'DEADLOCK' vid lĂ„sförsök av block/rad. Försök att starta om transaktionen Tabelltypen (%s) har inte hantering av FULLTEXT-index Kan inte lĂ€gga till 'FOREIGN KEY constraint' FOREIGN KEY-konflikt: Kan inte skriva barn FOREIGN KEY-konflikt: Kan inte radera fader Fick fel vid anslutning till master: %-.128s Fick fel vid utförande av command pĂ„ mastern: %-.128s Fick fel vid utförande av %s: %-.128s Felaktig anvĂ€nding av %s and %s SELECT-kommandona har olika antal kolumner Kan inte utföra kommandot emedan du har ett READ-lĂ„s Blandning av transaktionella och icke-transaktionella tabeller Ă€r inaktiverat Option '%s' anvĂ€ndes tvĂ„ gĂ„nger AnvĂ€ndare '%-.64s' har överskridit '%s' (nuvarande vĂ€rde: %ld) Du har inte privlegiet '%-.128s' som behövs för denna operation Variabel '%-.64s' Ă€r en SESSION variabel och kan inte Ă€ndrad med SET GLOBAL Variabel '%-.64s' Ă€r en GLOBAL variabel och bör sĂ€ttas med SET GLOBAL Variabel '%-.64s' har inte ett DEFAULT-vĂ€rde Variabel '%-.64s' kan inte sĂ€ttas till '%-.200s' Fel typ av argument till variabel '%-.64s' Variabeln '%-.64s' kan endast sĂ€ttas, inte lĂ€sas Fel anvĂ€nding/placering av '%s' Denna version av MariaDB kan Ă€nnu inte utföra '%s' Fick fatalt fel %d: '%-.320s' frĂ„n master vid lĂ€sning av binĂ€rloggen Slav SQL trĂ„den ignorerade frĂ„gan pga en replicate-*-table regel Variabel '%-.192s' Ă€r av typ %s Felaktig FOREIGN KEY-definition för '%-.192s': %s Nyckelreferensen och tabellreferensen stĂ€mmer inte överens Operand should contain %d column(s) Subquery returnerade mer Ă€n 1 rad OkĂ€nd PREPARED STATEMENT id (%.*s) var given till %s HjĂ€lpdatabasen finns inte eller Ă€r skadad Cyklisk referens i subqueries Konvertar kolumn '%s' frĂ„n %s till %s Referens '%-.64s' stöds inte (%s) Varje 'derived table' mĂ„ste ha sitt eget alias Select %u reducerades vid optimiering Tabell '%-.192s' frĂ„n en SELECT kan inte anvĂ€ndas i %-.32s Klienten stöder inte autentiseringsprotokollet som begĂ€rts av servern; övervĂ€g uppgradering av klientprogrammet. Alla delar av en SPATIAL index mĂ„ste vara NOT NULL COLLATION '%s' Ă€r inte tillĂ„tet för CHARACTER SET '%s' Slaven har redan startat Slaven har redan stoppat 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 %lu doesn'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 '%s' at row %lu Out of range value for column '%s' at row %lu Data truncated for column '%s' at row %lu AnvĂ€nder handler %s för tabell '%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 MariaDB slave was compiled without SSL support; they can be used later if MariaDB 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 Felaktigt index namn '%-.100s' Felaktigt katalog namn '%-.100s' Storleken av "Query cache" kunde inte sĂ€ttas till %llu, ny storlek Ă€r %lu Kolumn '%-.192s' kan inte vara del av ett FULLTEXT index OkĂ€nd nyckel cache '%-.100s' MariaDB 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 Tabell %-.100s anvĂ€nd med '%s' Ă€r inte uppdateringsbar '%s' Ă€r inte aktiverad; För att aktivera detta mĂ„ste du bygga om MariaDB med '%s' definierad MariaDB Ă€r startad med %s. Pga av detta kan du inte anvĂ€nda detta kommando 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 '%-.200s' from %s Got temporary error %d '%-.200s' from %s Unknown or incorrect time zone: '%-.64s' Invalid TIMESTAMP value in column '%s' at row %lu 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 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 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' ANALYZE/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 %lu Illegal %s '%-.192s' value found during parsing CHECK OPTION on non-updatable view '%-.192s.%-.192s' CHECK OPTION failed '%-.192s.%-.192s' %-.32s command denied to user '%s'@'%s' 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 MariaDB 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: %M 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 %lu 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 %llu specified for '%-.192s'. Maximum is %u. Too big precision %llu specified for '%-.192s'. Maximum is %u. 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 '%-.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 Invalid definer 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' Upgrade required. Please do "REPAIR %s %`s" 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 storage engine %s 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' Syntaxfel: %-.64s PARTITIONering krĂ€ver definition av VALUES %-.64s för varje partition Endast %-.64s partitionering kan anvĂ€nda VALUES %-.64s i definition av partitionen MAXVALUE kan bara anvĂ€ndas i definitionen av den sista partitionen Subpartitioner kan bara vara hash och key partitioner Subpartitioner mĂ„ste definieras pĂ„ alla partitioner om pĂ„ en Antal partitioner definierade och antal partitioner Ă€r inte lika Antal subpartitioner definierade och antal subpartitioner Ă€r inte lika Konstanta uttryck eller slumpmĂ€ssiga uttryck Ă€r inte tillĂ„tna (sub)partitioneringsfunktioner Uttryck i RANGE/LIST VALUES mĂ„ste vara ett konstant uttryck FĂ€lt i listan av fĂ€lt för partitionering med key inte funnen i tabellen En lista av fĂ€lt Ă€r endast tillĂ„tet för KEY partitioner Partitioneringsinformationen i frm-filen Ă€r inte konsistent med vad som kan skrivas i frm-filen %-.192s-funktionen returnerar felaktig typ För %-.64s partitionering sĂ„ mĂ„ste varje partition definieras VĂ€rden i VALUES LESS THAN mĂ„ste vara strikt vĂ€xande för varje partition VĂ€rden i VALUES mĂ„ste vara av samma typ som partitioneringsfunktionen Multipel definition av samma konstant i list partitionering Partitioneringssyntax kan inte anvĂ€ndas pĂ„ egen hand i en SQL-frĂ„ga Denna mix av lagringsmotorer Ă€r inte tillĂ„ten i denna version av MariaDB För partitioneringsmotorn sĂ„ Ă€r det nödvĂ€ndigt att definiera alla %-.64s För mĂ„nga partitioner (inkluderande subpartitioner) definierades Det Ă€r endast möjligt att blanda RANGE/LIST partitionering med HASH/KEY partitionering för subpartitionering Misslyckades med att skapa specifik fil i lagringsmotor Ett BLOB-fĂ€lt Ă€r inte tillĂ„tet i partitioneringsfunktioner A %-.192s must include all columns in the table's partitioning function Antal %-.64s = 0 Ă€r inte ett tillĂ„ten vĂ€rde Partitioneringskommando pĂ„ en opartitionerad tabell Ă€r inte möjligt Foreign key klausul Ă€r inte Ă€nnu implementerad i kombination med partitionering Fel i listan av partitioner att %-.64s Det Ă€r inte tillĂ„tet att ta bort alla partitioner, anvĂ€nd DROP TABLE istĂ€llet COALESCE PARTITION kan bara anvĂ€ndas pĂ„ HASH/KEY partitioner REORGANIZE PARTITION kan bara anvĂ€ndas för att omorganisera partitioner, inte för att Ă€ndra deras antal REORGANIZE PARTITION utan parametrar kan bara anvĂ€ndas pĂ„ auto-partitionerade tabeller som anvĂ€nder HASH partitionering %-.64s PARTITION kan bara anvĂ€ndas pĂ„ RANGE/LIST-partitioner ADD PARTITION med fel antal subpartitioner Ă
tminstone en partition mĂ„ste lĂ€ggas till vid ADD PARTITION Ă
tminstone en partition mÄste slÄs ihop vid COALESCE PARTITION Fler partitioner att reorganisera Àn det finns partitioner Duplicerat partitionsnamn %-.192s Det Àr inte tillÄtet att stÀnga av binlog pÄ detta kommando NÀr ett antal partitioner omorganiseras mÄste de vara i konsekutiv ordning Reorganisering av rangepartitioner kan inte Àndra den totala intervallet utom för den sista partitionen dÀr intervallet kan utökas Partition function not supported in this version for this handler Partition state kan inte definieras frÄn CREATE/ALTER TABLE %-.64s stödjer endast 32 bitar i integers i 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 %M 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 You should never see it You should never see it 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 MariaDB %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. 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 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 You should never see it Cannot create temporary table with partitions Partitionskonstanten Àr utanför partitioneringsfunktionens domÀn Denna partitioneringsfunktion Àr inte tillÄten Error in DDL log Det Àr inte tillÄtet att anvÀnda NULL-vÀrden i VALUES LESS THAN Felaktigt partitionsnamn Transaction characteristics 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 %M Engine inte anvÀndas i en partitionerad tabell Cannot activate '%-.64s' log The server was not built with row-based replication Avkodning av base64 strÀng misslyckades 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 Storage engine %s 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 Dublett '%-.64s' för nyckel '%-.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 not changed. Specify a time in the future. The incident %s occured on the master. Message: %-.64s Table has no partition for some existing values Detta Àr inte sÀkert att logga i statement-format, för 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 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 '%-.192s' There is no master connection '%.*s' <%-.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). You should never see it Error in parsing conflict function. Message: %-.64s Write to exceptions table failed. Message: %-.128s" Comment for table '%-.64s' is too long (max = %u) Comment for field '%-.64s' is too long (max = %u) FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual Databas Tabell Partition Subpartition TemporÀr NamnÀndrad 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; set query_cache_type to ON or DEMAND 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 Misslyckades lÀsa frÄn .par filen VÀrden i VALUES för partition '%-.64s' mÄste ha typen INT AnvÀndare '%s'@'%s' Àr ej berÀttigad att logga in 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. 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 Table is being used in foreign key check. You should never see it 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 %u for the master delay exceeds the maximum %u Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided) Attributet '%-.64s' Àr olika mellan partition och tabell Tabellen att byta ut mot partition Àr partitionerad: '%-.64s' Tabellen att byta ut mot partition Àr temporÀr: '%-.64s' Subpartitionerad tabell, anvÀnd subpartition istÀllet för partition OkÀnd partition '%-.64s' i tabell '%-.64s' Tabellerna har olika definitioner Hittade en rad som inte passar i partitionen 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 '%-.64s' due to type or collation conversion on field '%-.64s' Tabellen att byta ut mot partition har foreign key referenser: '%-.64s' Key value '%-.192s' was not found in table '%-.192s.%-.192s' Data for column '%s' too long 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't update table '%-.192s' while '%-.192s' is being created. PARTITION () klausul för en icke partitionerad tabell Hittade en rad som inte passar i nÄgon given partition 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 stöds ej för partitionerade tabeller. Invalid condition number Sending passwords in plain text without SSL/TLS is extremely insecure. Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives. FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera barntabell '%.192s' pÄ grund av nyckel '%.192s' FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera en barntabell pÄ grund av UNIQUE-test 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 'SET %.200s' cannot invoke a stored function. The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL. Skipping transaction %.200s because it has already been executed and logged. Malformed GTID set specification '%.200s'. Malformed GTID set encoding. Malformed GTID specification '%.200s'. Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the server with a new server_uuid. Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active. CHANGE MASTER TO MASTER_AUTO_POSITION = 1 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 <-> UPGRADE_STEP_1 <-> UPGRADE_STEP_2 <-> ON. Also note that this value must be stepped up or down simultaneously on all servers; see the Manual for instructions. The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK. Unknown EXPLAIN format name: '%s' Cannot execute statement in a READ ONLY transaction. Comment for table partition '%-.64s' is too long (max = %lu) Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log. InnoDB presently supports one FULLTEXT index creation at a time Cannot create FULLTEXT index on temporary InnoDB table Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index Creating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again. Unknown ALGORITHM '%s' Unknown LOCK type '%s' CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode. Consider using RESET SLAVE or START SLAVE UNTIL. Cannot recover after SLAVE errored out in parallel execution mode. Additional error messages can be found in the MySQL error log. Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log. Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted Slave must silently retry current transaction There is a foreign key check running on table '%-.192s'. Cannot discard the table. 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 '%-.192s' Tablespace for table '%-.192s' exists. Please DISCARD the tablespace before IMPORT. Tablespace has been discarded for table '%-.192s' Internal error: %-.192s ALTER TABLE '%-.192s' IMPORT TABLESPACE failed with error %lu : '%s' Index corrupt: %s YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead. Your password does not satisfy the current policy requirements You must SET PASSWORD before executing this statement Failed to add the foreign key constaint. Missing index for constraint '%s' in the foreign table '%s' Failed to add the foreign key constaint. Missing index for constraint '%s' in the referenced table '%s' Failed to add the foreign key constraint '%s' to system tables Failed to open the referenced table '%s' Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s' Duplicate foreign key constraint name '%s' The password hash doesn't have the expected format. Check if the correct password algorithm is being used with the PASSWORD() function. Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s' Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULL Duplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release. Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s' Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s' Malformed communication packet. Running in read-only 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 'AUTOMATIC' after COMMIT or ROLLBACK. Current GTID_NEXT is '%s'. 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 '%s' to '%s'. GTID_EXECUTED was changed from '%s' to '%s'. Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to. %s is not supported for this operation. Try %s. %s is not supported. Reason: %s. Try %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 INPLACE 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 Dublett för nyckel '%-.192s' Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'. cannot silently convert NULL values, as required in this SQL_MODE Your password has expired. To log in you must change it using a client that supports expired passwords. Hittade en rad i fel 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 '%s' 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): '%-.192s' 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 '%-.48s'@'%-.64s' (using password: %s). Disconnecting. InnoDB is in read only mode. STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete. STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete. Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data. Temporary file write failure. Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index. " A computed column cannot be based on a computed column Function or expression is not allowed for column '%s' Generated value for computed column '%s' cannot be converted to type '%s' Primary key cannot be defined upon a computed column Key/Index cannot be defined on a non-stored computed column Cannot define foreign key with %s clause on a computed column The value specified for computed column '%s' in table '%s' ignored This is not yet supported for computed columns Constant expression in computed column function is not allowed Expression for computed column cannot return a row %s storage engine does not support computed columns Unknown option '%-.64s' Incorrect value '%-.64s' for option '%-.64s' You should never see it You should never see it You should never see it Got overflow when converting '%-.128s' to %-.32s. Value truncated. Truncated value '%-.128s' when converting to %-.32s Encountered illegal value '%-.128s' 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 'in_to_exists' or 'materialization' optimizer_switch flags must be 'on'. Query cache is disabled (resize or similar command in progress); repeat this command later Query cache is globally disabled and you can't enable it only for this session View '%-.192s'.'%-.192s' 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 examined at least %llu rows, which exceeds LIMIT ROWS EXAMINED (%llu). The query result may be incomplete. Det finns ingen tabell som heter '%-.192s.%-.192s' i handlern Target is not running an EXPLAINable command Connection '%.*s' conflicts with existing connection '%.*s' Master '%.*s': Can't %s SLAVE '%.*s' SLAVE '%.*s' started SLAVE '%.*s' stopped Engine %s failed to discover table %`-.192s.%`-.192s with '%s' 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'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's binlog. Since the master's binlog contains GTIDs with higher sequence numbers, it probably means that the slave has diverged due to executing extra erroneous transactions This operation is not allowed if any GTID has been logged to the binary log. Run RESET MASTER first to erase the log Unknown query id: %lld Bad base64 data as position %u Invalid role specification %`s. The current user is invalid. Cannot grant role '%s' to: %s. Cannot revoke role '%s' 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 '%-.192s' is a view When using GTID, @@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 Plugin '%-.192s' already installed 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't create user '%-.64s'@'%-.64s'; it already exists Can't drop user '%-.64s'@'%-.64s'; it doesn't exist Can't create role '%-.64s'; it already exists Can't drop role '%-.64s'; it doesn't exist Cannot convert '%s' character 0x%-.64s to '%s' Incorrect default value '%-.128s' for column '%.192s' You are not owner of query %lu
ß
yôÊáœ~orÀ5ÖJ ={țÁEÇêeŸuçŁQk źáŻG{ś?ù»ă+]üôçÉÍŚŚô?wûM3X^¶Úæ>{Ž7ÙŸìŽKă>èoČÎnĘ\ÿȘÊjży· đR Łőăg/î=ȚÿfúOçÖr·oŚNVÊvżú~ÿY+ üżNGêuśű·ĂźțëčHWûyëwÆ[eQ¶ÊšŸSÚbÖ>öÍËÇ țł>ä}Gçmx[o[<ȚÚ{đęÏź_ĆïqF ÚÛvM IENDźB`