sGz'vMy%Y.\1XEbTyPeu > g ' E j   C h = o L d { _9]e,KaIbn(M9J)g0a t3RDo/Cs U >!z!!!]"{""",#s##$.$r$%:%R%x%%%&I&&&'3'r''''((((7))*o**4+++%,M,k,,,7----.V....3/W/~///0C0000@1112;2h222233y3333"4C4y44445:5d55 6:6m6667,77777B88889P999 :6:::K;;)5>>>?F???"@N@@@:AZAAAABHBtBBBBBBC1CLCsCCCCD-EMEEEEEF%F:FQFdF|FFFFGG0GFGcGGGH(HPH}HHH0IxIIII"JGJvJJJ9KKL?LqLLLLLMKMYMMMM%NcNNNNO3OEObOOOOOCPUPPPP#QFQ\QQQQR`RRRRRXSSS"TyTTT UUbUUUV;VhVVVZZZZ=[[[\m\\2]z]]][^^^^^ ___``aaabSbbb#cc)dddeseeefTffffg!g+glgggh4hhhKiii5jljjj$kjkkk>lolll0mvmmmnjnnnGonooopUpppp4qqq4rrrrrrsNsstJttttu(uWuku}uuvXvlvvvTwswwwww%xMxxxxyZyyyyy)zzzzR{{A||| }D}k}|}}}~~~~$XyBtBÁ@k ԃjzń :p߅\Æ|ԇ6ۈ?rE"V)28BOYaߌ,U̍ 2Xq͎Ay/}Đ/ڒ19;ߖ}ٗ=(9Й 5qʚ)~Ǜ5pȜ"Yz T*ʠMMŢ+᤭~QmΨܩڪ0Zrի׫ث٫ګ۫ܫݫޫ߫  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~9n+Z̮Eޯ P°"\B"`ChashchkisamchkNEJJAKan ikke oprette filen '%-.200s' (Fejlkode: %d)Kan ikke oprette tabellen '%-.200s' (Fejlkode: %d)Kan ikke oprette databasen '%-.192s' (Fejlkode: %d)Kan ikke oprette databasen '%-.192s'; databasen eksistererKan ikke slette (droppe) '%-.192s'; databasen eksisterer ikkeFejl ved sletning (drop) af databasen (kan ikke slette '%-.192s', Fejlkode %d)Fejl ved sletting af database (kan ikke slette folderen '%-.192s', Fejlkode %d)Fejl ved sletning af '%-.192s' (Fejlkode: %d)Kan ikke læse posten i systemfolderenKan ikke læse status af '%-.200s' (Fejlkode: %d)Kan ikke læse aktive folder (Fejlkode: %d)Kan ikke låse fil (Fejlkode: %d)Kan ikke åbne fil: '%-.200s' (Fejlkode: %d)Kan ikke finde fila: '%-.200s' (Fejlkode: %d)Kan ikke læse folder '%-.192s' (Fejlkode: %d)Kan ikke skifte folder til '%-.192s' (Fejlkode: %d)Posten er ændret siden sidste læsning '%-.192s'Ikke mere diskplads (%s). Venter på at få frigjort plads...Kan ikke skrive, flere ens nøgler i tabellen '%-.192s'Fejl ved lukning af '%-.192s' (Fejlkode: %d)Fejl ved læsning af '%-.200s' (Fejlkode: %d)Fejl ved omdøbning af '%-.210s' til '%-.210s' (Fejlkode: %d)Fejl ved skriving av filen '%-.200s' (Fejlkode: %d)'%-.192s' er låst mod opdateringerSortering afbrudtView '%-.192s' eksisterer ikke for '%-.192s'Modtog fejl %d fra tabel håndteringenDenne mulighed eksisterer ikke for tabeltypen '%-.192s'Kan ikke finde posten i '%-.192s'Forkert indhold i: '%-.200s'Fejl i indeksfilen til tabellen '%-.200s'; prøv at reparere denGammel indeksfil for tabellen '%-.192s'; reparer den'%-.192s' er skrivebeskyttetIkke mere hukommelse. Genstart serveren og prøv igen (mangler %d bytes)Ikke mere sorteringshukommelse. Øg sorteringshukommelse (sort buffer size) for serverenUventet afslutning på fil (eof) ved læsning af filen '%-.192s' (Fejlkode: %d)For mange forbindelser (connections)Udgået for tråde/hukommelseKan ikke få værtsnavn for din adresseForkert håndtryk (handshake)Adgang nægtet bruger: '%s'@'%s' til databasen '%-.192s'Adgang nægtet bruger: '%s'@'%s' (Bruger adgangskode: %s)Ingen database valgtUkendt kommandoKolonne '%-.192s' kan ikke være NULLUkendt database '%-.192s'Tabellen '%-.192s' findes alleredeUkendt tabel '%-.100s'Felt: '%-.192s' i tabel %-.192s er ikke entydigtDatabase nedlukning er i gangUkendt kolonne '%-.192s' i tabel %-.192sBrugte '%-.192s' som ikke var i group byKan ikke gruppere på '%-.192s'Udtrykket har summer (sum) funktioner og kolonner i samme udtrykKolonne tæller stemmer ikke med antallet af værdierNavnet '%-.100s' er for langtFeltnavnet '%-.192s' findes alleredeIndeksnavnet '%-.192s' findes alleredeEns værdier '%-.192s' for indeks %dForkert kolonnespecifikaton for felt '%-.192s'%s nær '%-.80s' på linje %dForespørgsel var tomTabellen/aliaset: '%-.192s' er ikke uniktUgyldig standardværdi for '%-.192s'Flere primærnøgler specificeretFor mange nøgler specificeret. Kun %d nøgler må brugesFor mange nøgledele specificeret. Kun %d dele må brugesSpecificeret nøgle var for lang. Maksimal nøglelængde er %dNøglefeltet '%-.192s' eksisterer ikke i tabellenBLOB feltet '%-.192s' kan ikke bruges ved specifikation af indeksFor stor feltlængde for kolonne '%-.192s' (maks = %lu). Brug BLOB i stedetDer kan kun specificeres eet AUTO_INCREMENT-felt, og det skal være indekseretYou should never see it%s: Normal nedlukning %s: Fangede signal %d. Afslutter!! %s: Server lukket %s: Forceret nedlukning af tråd: %ld bruger: '%-.48s' Kan ikke oprette IP socketTabellen '%-.192s' har ikke den nøgle, som blev brugt i CREATE INDEX. Genopret tabellenFelt adskiller er ikke som forventet, se dokumentationenMan kan ikke bruge faste feltlængder med BLOB. Brug i stedet 'fields terminated by'.Filen '%-.128s' skal være i database-folderen, eller kunne læses af alleFilen '%-.200s' eksisterer alleredePoster: %ld Fjernet: %ld Sprunget over: %ld Advarsler: %ldPoster: %ld Ens: %ldForkert indeksdel. Den anvendte nøgledel er ikke en streng eller længden er større end nøglelængdenMan kan ikke slette alle felter med ALTER TABLE. Brug DROP TABLE i stedet.Kan ikke udføre DROP '%-.192s'. Undersøg om feltet/nøglen eksisterer.Poster: %ld Ens: %ld Advarsler: %ldYou can't specify target table '%-.192s' for update in FROM clauseUkendt tråd id: %luDu er ikke ejer af tråden %luIngen tabeller i brugFor mange tekststrenge til specifikationen af SET i kolonne %-.192sKan ikke lave unikt log-filnavn %-.200s.(1-999) Tabellen '%-.192s' var låst med READ lås og kan ikke opdateresTabellen '%-.192s' var ikke låst med LOCK TABLESBLOB feltet '%-.192s' kan ikke have en standard værdiUgyldigt database navn '%-.100s'Ugyldigt tabel navn '%-.100s'SELECT ville undersøge for mange poster og ville sandsynligvis tage meget lang tid. Undersøg WHERE delen og brug SET SQL_BIG_SELECTS=1 hvis udtrykket er korrektUkendt fejlUkendt procedure %-.192sForkert antal parametre til proceduren %-.192sForkert(e) parametre til proceduren %-.192sUkendt tabel '%-.192s' i %-.32sFeltet '%-.192s' er anvendt to gangeForkert brug af grupperings-funktionTabellen '%-.192s' bruger et filtypenavn som ikke findes i denne MariaDB versionEn tabel skal have mindst een kolonneTabellen '%-.192s' er fuldUkendt tegnsæt: '%-.64s'For mange tabeller. MariaDB kan kun bruge %d tabeller i et joinFor mange felterFor store poster. Max post størrelse, uden BLOB's, er %ld. Du må lave nogle felter til BLOB'sThread stack brugt: Brugt: %ld af en %ld stak. Brug 'mysqld --thread_stack=#' for at allokere en større stak om nødvendigtKrydsreferencer fundet i OUTER JOIN; check dine ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerKan ikke læse funktionen '%-.192s'Kan ikke starte funktionen '%-.192s'; %-.80sAngivelse af sti ikke tilladt for delt bibliotekFunktionen '%-.192s' findes alleredeKan ikke åbne delt bibliotek '%-.192s' (errno: %d, %-.128s)Kan ikke finde funktionen '%-.128s' i bibliotekFunktionen '%-.192s' er ikke defineretVærten '%-.64s' er blokeret på grund af mange fejlforespørgsler. Lås op med 'mysqladmin flush-hosts'Værten '%-.64s' kan ikke tilkoble denne MariaDB-serverDu bruger MariaDB som anonym bruger. Anonyme brugere må ikke ændre adgangskoderDu skal have tilladelse til at opdatere tabeller i MariaDB databasen for at ændre andres adgangskoderKan ikke finde nogen tilsvarende poster i bruger tabellenPoster fundet: %ld Ændret: %ld Advarsler: %ldKan ikke danne en ny tråd (fejl nr. %d). Hvis computeren ikke er løbet tør for hukommelse, kan du se i brugervejledningen for en mulig operativ-system - afhængig fejlKolonne antallet stemmer ikke overens med antallet af værdier i post %luKan ikke genåbne tabel '%-.192sForkert brug af nulværdi (NULL)Fik fejl '%-.64s' fra regexpSammenblanding af GROUP kolonner (MIN(),MAX(),COUNT()...) uden GROUP kolonner er ikke tilladt, hvis der ikke er noget GROUP BY prædikatDenne tilladelse findes ikke for brugeren '%-.48s' på vært '%-.64s'%-.16s-kommandoen er ikke tilladt for brugeren '%s'@'%s' for tabellen '%-.192s'%-.16s-kommandoen er ikke tilladt for brugeren '%s'@'%s' for kolonne '%-.192s' in tabellen '%-.192s'Forkert GRANT/REVOKE kommando. Se i brugervejledningen hvilke privilegier der kan specificeres.Værts- eller brugernavn for langt til GRANTTabellen '%-.192s.%-.192s' eksisterer ikkeDenne tilladelse eksisterer ikke for brugeren '%-.48s' på vært '%-.64s' for tabellen '%-.192s'Den brugte kommando er ikke tilladt med denne udgave af MariaDBDer er en fejl i SQL syntaksenForsinket indsættelse tråden (delayed insert thread) kunne ikke opnå lås på tabellen %-.192sFor mange slettede tråde (threads) i brugAfbrudt forbindelse %ld til database: '%-.192s' bruger: '%-.48s' (%-.64s)Modtog en datapakke som var større end 'max_allowed_packet'Fik læsefejl fra forbindelse (connection pipe)Fik fejlmeddelelse fra fcntl()Modtog ikke datapakker i korrekt rækkefølgeKunne ikke dekomprimere kommunikations-pakke (communication packet)Fik fejlmeddelelse ved læsning af kommunikations-pakker (communication packets)Timeout-fejl ved læsning af kommunukations-pakker (communication packets)Fik fejlmeddelelse ved skrivning af kommunukations-pakker (communication packets)Timeout-fejl ved skrivning af kommunukations-pakker (communication packets)Strengen med resultater er større end 'max_allowed_packet'Denne tabeltype understøtter ikke brug af BLOB og TEXT kolonnerDenne tabeltype understøtter ikke brug af AUTO_INCREMENT kolonnerINSERT DELAYED kan ikke bruges med tabellen '%-.192s', fordi tabellen er låst med LOCK TABLESForkert kolonnenavn '%-.100s'Den brugte tabeltype kan ikke indeksere kolonnen '%-.192s'Tabellerne i MERGE er ikke defineret ensKan ikke skrive til tabellen '%-.192s' fordi det vil bryde CONSTRAINT reglerBLOB kolonnen '%-.192s' brugt i nøglespecifikation uden nøglelængdeAlle dele af en PRIMARY KEY skal være NOT NULL; Hvis du skal bruge NULL i nøglen, brug UNIQUE istedetResultatet bestod af mere end een rækkeDenne tabeltype kræver en primærnøgleDenne udgave af MariaDB er ikke oversat med understøttelse af RAIDDu bruger sikker opdaterings modus ('safe update mode') og du forsøgte at opdatere en tabel uden en WHERE klausul, der gør brug af et KEY feltNøglen '%-.192s' eksisterer ikke i tabellen '%-.192s'Kan ikke åbne tabellenDenne tabeltype understøtter ikke %sDu må ikke bruge denne kommando i en transaktionModtog fejl %d mens kommandoen COMMIT blev udførtModtog fejl %d mens kommandoen ROLLBACK blev udførtModtog fejl %d mens kommandoen FLUSH_LOGS blev udførtModtog fejl %d mens kommandoen CHECKPOINT blev udførtAfbrød forbindelsen %ld til databasen '%-.192s' bruger: '%-.48s' vært: '%-.64s' (%-.64s)Denne tabeltype unserstøtter ikke binært tabeldumpBinlog closed, cannot RESET MASTERKunne ikke genopbygge indekset for den dumpede tabel '%-.192s'Fejl fra master: '%-.64s'Netværksfejl ved læsning fra masterNetværksfejl ved skrivning til masterKan ikke finde en FULLTEXT nøgle som svarer til kolonne listenKan ikke udføre den givne kommando fordi der findes aktive, låste tabeller eller fordi der udføres en transaktionUkendt systemvariabel '%-.64s'Tabellen '%-.192s' er markeret med fejl og bør repareresTabellen '%-.192s' er markeret med fejl og sidste (automatiske?) REPAIR fejledeAdvarsel: Visse data i tabeller der ikke understøtter transaktioner kunne ikke tilbagestillesFler-udtryks transaktion krævede mere plads en 'max_binlog_cache_size' bytes. Forhøj værdien af denne variabel og prøv igenDenne handling kunne ikke udføres med kørende slave, brug først kommandoen STOP SLAVEDenne handling kræver en kørende slave. Konfigurer en slave og brug kommandoen START SLAVEDenne server er ikke konfigureret som slave. Ret in config-filen eller brug kommandoen CHANGE MASTER TOCould not initialize master info structure; more error messages can be found in the MariaDB error logKunne ikke danne en slave-tråd; check systemressourcerneBrugeren %-.64s har allerede mere end 'max_user_connections' aktive forbindelserDu må kun bruge konstantudtryk med SETLock wait timeout overskredetDet totale antal låse overstiger størrelsen på låse-tabellenUpdate lås kan ikke opnås under en READ UNCOMMITTED transaktionDROP DATABASE er ikke tilladt mens en tråd holder på globalt read lockCREATE DATABASE er ikke tilladt mens en tråd holder på globalt read lockIncorrect arguments to %s'%s'@'%s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to master: %-.128sError running query on master: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MariaDB 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 rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MariaDB clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Slave is already runningSlave already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %lu doesn't contain data for all columnsRow %lu was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %luOut of range value for column '%s' at row %luData truncated for column '%s' at row %luUsing 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 usersCan't revoke all privileges for one or more of the requested usersIllegal 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 startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START SLAVE UNTILIt 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 restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %llu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MariaDB is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MariaDB built with '%s' to have it workingThe MariaDB server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.32s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetModtog fejl %d '%-.200s' fra %sModtog temporary fejl %d '%-.200s' fra %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %luInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored. 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 interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'View's SELECT and view's field list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %luIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%s'@'%s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MariaDB serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.64s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %luBad SQLSTATE: '%s'%s: ready for connections. Version: '%s' socket: '%s' port: %d %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %u specified for '%-.192s'. Maximum is %lu.Too big precision %u specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error: %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error: %-.64sTrigger in wrong schemaThread stack overrun: %ld bytes used of a %ld byte stack, and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. The trigger will be activated under the authorization of the invoker, which may have insufficient privileges. Please recreate the trigger.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The table mysql.proc is missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.32s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error: %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MariaDBFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning functionNumber of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign key clause is not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on master and slave does not match: %sSlave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MariaDB %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryColumn count of mysql.%s is wrong. Expected %d, found %d. Created with 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 tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction isolation level can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function '%-.192s'This function '%-.192s' has the same name as a native functionEns værdier '%-.64s' for indeks '%-.192s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.The incident %s occured on the master. Message: %-.64sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sMaster command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous slave modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The master info structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected master's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128s"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 ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the slave startup option --replicate-same-server-idQuery cache is disabled; set query_cache_type to ON or DEMAND to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the slave.Statement is unsafe because it uses a system variable that may have a different value on the slave.Statement is unsafe because it uses a system function that may return a different value on the slave.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAdgang nægtet bruger: '%s'@'%s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `slave_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.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 corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on master and the slave.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on master and the slave.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.CREATE TABLE... SELECT... on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on master and the slave.INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.You should never see itINSERT into autoincrement field which is not the first part in the composed primary key is unsafe."A computed column cannot be based on a computed columnFunction 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 columnKey/Index cannot be defined on a non-stored computed columnCannot define foreign key with %s clause on a computed columnThe value specified for computed column '%s' in table '%s' ignoredThis is not yet supported for computed columnsConstant expression in computed column function is not allowedExpression for computed column cannot return a row%s storage engine does not support computed columnsUnknown option '%-.64s'Incorrect value '%-.64s' for option '%-.64s'Replication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Can't execute the given '%s' command as onlineGot overflow when converting '%-.128s' to %-.32s. Value truncated.Truncated value '%-.128s' when converting to %-.32sEncountered illegal value '%-.128s' when converting to %-.32sEncountered illegal format of dynamic column stringDynamic column implementation limit reachedIllegal value used as argument of dynamic column functionDynamic column contains unknown character setAt least one of the 'in_to_exists' or 'materialization' optimizer_switch flags must be 'on'.Query cache is disabled (resize or similar command in progress); repeat this command laterQuery cache is globally disabled and you can't enable it only for this sessionView '%-.192s'.'%-.192s' ORDER BY clause ignored because there is other ORDER BY clause already.Connection was killedInternal error: '%-.192s'Cannot modify @@session.skip_replication inside a transactionCannot modify @@session.skip_replication inside a stored function or triggerQuery execution was interrupted. The query examined at least %llu rows, which exceeds LIMIT ROWS EXAMINED (%llu). The query result may be incomplete.Table '%-.192s.%-.192s' doesn't exist in engine