PAL.C.T MINI SHELL
þþ Ô H 3 N i c ] p @ : D I @ N H N N Z ; N < F P F , ( ; $ @ 5 6 m a - ~
x S< \ ? 4 - 2 - # 0 1 5 : 5 C . - * 0 3 * < 5 1 > J G 0 C o ! F ! H * u y o 6 B " ÷ f V 2 ` # 9 % B L I C L 3 $ Ì 2 H E 1 1 . \ 2 ! , J ¬ ^ x 0 8 = 9 ` E 3 ^ g O / · > 3 - 3 v Q o x N / n H
^ 2 d K 1 ) 7 : : C : C G 4 9 j $ - K O K d o > % L L 2 4 6 6 x _ B , F C M | 1 ? V a Î i ¥ j t " m % 4 i k - x | 7 . @ C + 4 + 2 4 a g 8 Z | Z Z > = 2 P 3 P p j ( . : 2 8 p F 7 0 , ( ; Y ° G B + 1 . ! E l x . C J O / s U : | ÷ Ò X û i ' - A ? 5 ª 6 d O q S D 1 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 O M % w A _ I Z G 7 5 @ C F a 1 B 1 ` , 5 F 8 : 2 P @ ; b ' 2 H - @ I & 5 ; [ j ; > % ) 8 ! 5 H r B : ; " ( / 6 M X 3 8 } = + ( = , ) @ W ? % ` L . 7 ' 2 P i ? , 4 ! D ` % 0 2 C > > ? 9 8 } 7 0 f ) / 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 " 7 ! F L H < l Y ; C 5 4 Ñ å Ì Ñ Ó · þ V * c 8 C h < : 8 < - " . a F = K N ? - 1 ? @ S 5 œ 8 G Ï | m ` = 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 ! ( Ï 0 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 0 - < ? + . A ^ @ Ó D ¡ Š U d u " K L ( # > 4 ; 7 4 . + / 6 íñhashchk isamchk NO YES ãã¡ã€ã« '%-.200s' ãäœæã§ããŸããã(ãšã©ãŒçªå·: %M) %`s.%`s ããŒãã«ãäœããŸãã.(errno: %M) ããŒã¿ããŒã¹ '%-.192s' ãäœæã§ããŸããã(ãšã©ãŒçªå·: %M) ããŒã¿ããŒã¹ '%-.192s' ãäœæã§ããŸãããããŒã¿ããŒã¹ã¯ãã§ã«ååšããŸãã ããŒã¿ããŒã¹ '%-.192s' ãåé€ã§ããŸãããããŒã¿ããŒã¹ã¯ååšããŸããã ããŒã¿ããŒã¹åé€ãšã©ãŒ ('%-.192s' ãåé€ã§ããŸããããšã©ãŒçªå·: %M) ããŒã¿ããŒã¹åé€ãšã©ãŒ (ãã£ã¬ã¯ã㪠'%-.192s' ãåé€ã§ããŸããããšã©ãŒçªå·: %M) ãã¡ã€ã« '%-.192s' ã®åé€ãšã©ãŒ (ãšã©ãŒçªå·: %M) ã·ã¹ãã è¡šã®ã¬ã³ãŒããèªã¿èŸŒããŸããã '%-.200s' ã®ç¶æ
ãååŸã§ããŸããã(ãšã©ãŒçªå·: %M) äœæ¥ãã£ã¬ã¯ããªãååŸã§ããŸããã(ãšã©ãŒçªå·: %M) ãã¡ã€ã«ãããã¯ã§ããŸããã(ãšã©ãŒçªå·: %M) ãã¡ã€ã« '%-.200s' ããªãŒãã³ã§ããŸããã(ãšã©ãŒçªå·: %M) ãã¡ã€ã« '%-.200s' ãèŠã€ãããŸããã(ãšã©ãŒçªå·: %M) ãã£ã¬ã¯ã㪠'%-.192s' ãèªã¿èŸŒããŸããã(ãšã©ãŒçªå·: %M) ãã£ã¬ã¯ã㪠'%-.192s' ã«ç§»åã§ããŸããã(ãšã©ãŒçªå·: %M) è¡š '%-.192s' ã®æåŸã®èªã¿èŸŒã¿æç¹ãããã¬ã³ãŒããå€åããŸããã ãã£ã¹ã¯é åäžè¶³ã§ã(%s)ã(ãšã©ãŒçªå·: %M) æžã蟌ããŸãããè¡š '%-.192s' ã«éè€ããããŒããããŸãã '%-.192s' ã®ã¯ããŒãºæãšã©ãŒ (ãšã©ãŒçªå·: %M) ãã¡ã€ã« '%-.200s' ã®èªã¿èŸŒã¿ãšã©ãŒ (ãšã©ãŒçªå·: %M) '%-.210s' ã®ååã '%-.210s' ã«å€æŽã§ããŸãã (ãšã©ãŒçªå·: %M) ãã¡ã€ã« '%-.200s' ã®æžã蟌ã¿ãšã©ãŒ (ãšã©ãŒçªå·: %M) '%-.192s' ã¯ããã¯ãããŠããŸãã ãœãŒãåŠçãäžæããŸããã ãã¥ãŒ '%-.192s' 㯠'%-.192s' ã«ååšããŸããã Got error %M from storage engine %s Storage engine %s of the table %`s.%`s doesn't have this option '%-.192s' ã«ã¬ã³ãŒããèŠã€ãããŸããã ãã¡ã€ã« '%-.200s' å
ã®æ
å ±ãäžæ£ã§ãã è¡š '%-.200s' ã®çŽ¢åŒãã¡ã€ã«(key file)ã®å
容ãäžæ£ã§ãã修埩ãè©Šè¡ããŠãã ããã è¡š '%-.192s' ã®çŽ¢åŒãã¡ã€ã«(key file)ã¯å€ã圢åŒã§ãã修埩ããŠãã ããã è¡š '%-.192s' ã¯èªã¿èŸŒã¿å°çšã§ãã ã¡ã¢ãªãäžè¶³ããŠããŸãããµãŒããŒãåèµ·åããŠã¿ãŠãã ããã(%d ãã€ãã®å²ãåœãŠã«å€±æ) ãœãŒãã¡ã¢ãªãäžè¶³ããŠããŸãããœãŒããããã¡ãµã€ãº(sort buffer size)ã®å¢å ãæ€èšããŠãã ããã ãã¡ã€ã« '%-.192s' ãèªã¿èŸŒã¿äžã«äºæãããã¡ã€ã«ã®çµç«¯ã«éããŸããã(ãšã©ãŒçªå·: %M) æ¥ç¶ãå€ãããŸãã ã¡ã¢ãªãäžè¶³ããŠããŸããmysqld ããã®ä»ã®ããã»ã¹ãã¡ã¢ãªãŒã䜿ãåã£ãŠããªãã確èªããŠäžãããã¡ã¢ãªãŒã䜿ãåã£ãŠããªãå Žåã'ulimit'ã®èšå®ç㧠mysqld ã®ã¡ã¢ãªãŒäœ¿çšæ倧éãå€ãããããã¹ã¯ããé åãå¢ããå¿
èŠããããããããŸããã IPã¢ãã¬ã¹ãããã¹ãåã解決ã§ããŸããã ãã³ãã·ã§ã€ã¯ãšã©ãŒ ãŠãŒã¶ãŒ '%s'@'%s' ã® '%-.192s' ããŒã¿ããŒã¹ãžã®ã¢ã¯ã»ã¹ãæåŠããŸã ãŠãŒã¶ãŒ '%s'@'%s' ãæåŠããŸã.uUsing password: %s) ããŒã¿ããŒã¹ãéžæãããŠããŸããã äžæãªã³ãã³ãã§ãã å '%-.192s' 㯠null ã«ã§ããŸããã '%-.192s' ã¯äžæãªããŒã¿ããŒã¹ã§ãã è¡š '%-.192s' ã¯ãã§ã«ååšããŸãã '%-.100s' ã¯äžæãªè¡šã§ãã å '%-.192s' 㯠%-.192s å
ã§ææ§ã§ãã ãµãŒããŒãã·ã£ããããŠã³äžã§ãã å '%-.192s' 㯠'%-.192s' ã«ã¯ãããŸããã '%-.192s' ã¯GROUP BYå¥ã§æå®ãããŠããŸããã '%-.192s' ã§ã®ã°ã«ãŒãåã¯ã§ããŸããã éèšé¢æ°ãšéåžžã®åãåæã«æå®ãããŠããŸãã åæ°ãå€ã®åæ°ãšäžèŽããŸããã èå¥åå '%-.100s' ã¯é·ãããŸãã åå '%-.192s' ã¯éè€ããŠãŸãã 玢åŒå '%-.192s' ã¯éè€ããŠããŸãã '%-.192s' ã¯çŽ¢åŒ %d ã§éè€ããŠããŸãã å '%-.192s' ã®å®çŸ©ãäžæ£ã§ãã %s : '%-.80s' ä»è¿ %d è¡ç® ã¯ãšãªã空ã§ãã è¡šåïŒå¥å '%-.192s' ã¯äžæã§ã¯ãããŸããã '%-.192s' ãžã®ããã©ã«ãå€ãç¡å¹ã§ãã PRIMARY KEY ãè€æ°å®çŸ©ãããŠããŸãã 玢åŒã®æ°ãå€ãããŸããæ倧 %d åãŸã§ã§ãã 玢åŒã®ããŒåæå®ãå€ãããŸããæ倧 %d åãŸã§ã§ãã 玢åŒã®ããŒãé·ãããŸããæ倧 %d ãã€ããŸã§ã§ãã ããŒå '%-.192s' ã¯è¡šã«ãããŸããã BLOB column %`s can't be used in key specification in the %s table å '%-.192s' ã®ãµã€ãºå®çŸ©ã倧ããããŸã (æ倧 %lu ãŸã§)ã代ããã« BLOB ãŸã㯠TEXT ã䜿çšããŠãã ããã äžæ£ãªè¡šå®çŸ©ã§ããAUTO_INCREMENTåã¯ïŒåãŸã§ã§ã玢åŒãå®çŸ©ããå¿
èŠããããŸãã You should never see it %s: éåžžã·ã£ããããŠã³
%s: ã·ã°ãã« %d ãåä¿¡ããŸããã匷å¶çµäºããŸãïŒ
%s: ã·ã£ããããŠã³å®äº
%s: ã¹ã¬ãã %ld ã匷å¶çµäºããŸã (ãŠãŒã¶ãŒ: '%-.48s')
IPãœã±ãããäœæã§ããŸããã è¡š '%-.192s' ã«ä»¥åCREATE INDEXã§äœæããã玢åŒããããŸãããè¡šãäœãçŽããŠãã ããã ãã£ãŒã«ãåºåãæåãäºæãã¬äœ¿ããæ¹ãããŠããŸããããã¥ã¢ã«ã確èªããŠäžããã BLOBã«ã¯åºå®é·ã¬ã³ãŒãã䜿çšã§ããŸããã'FIELDS TERMINATED BY'å¥ã䜿çšããŠäžããã ãã¡ã€ã« '%-.128s' ã¯ããŒã¿ããŒã¹ãã£ã¬ã¯ããªã«ããããå
šãŠã®ãŠãŒã¶ãŒããèªããå¿
èŠããããŸãã ãã¡ã€ã« '%-.200s' ã¯ãã§ã«ååšããŸãã ã¬ã³ãŒãæ°: %ld åé€: %ld ã¹ããã: %ld èŠå: %ld ã¬ã³ãŒãæ°: %ld éè€: %ld ããŒã®ãã¬ãã£ãã¯ã¹ãäžæ£ã§ããããŒãæååã§ã¯ãªããããã¬ãã£ãã¯ã¹é·ãããŒãããé·ãããã¹ãã¬ãŒãžãšã³ãžã³ãäžæ玢åŒã®ãã¬ãã£ãã¯ã¹æå®ããµããŒãããŠããŸããã ALTER TABLE ã§ã¯å
šãŠã®åã®åé€ã¯ã§ããŸãããDROP TABLE ã䜿çšããŠãã ããã '%-.192s' ãåé€ã§ããŸãããåïŒçŽ¢åŒã®ååšã確èªããŠäžããã ã¬ã³ãŒãæ°: %ld éè€æ°: %ld èŠå: %ld Table '%-.192s' is specified twice, both as a target for '%s' and as a separate source for data äžæãªã¹ã¬ããIDã§ã: %lu ã¹ã¬ãã %lu ã®ãªãŒããŒã§ã¯ãããŸããã è¡šãæå®ãããŠããŸããã SETåã®å '%-.192s' ã®ã¡ã³ããŒã®æ°ãå€ãããŸãã äžæãªãã°ãã¡ã€ã«å %-.200s.(1-999) ãçæã§ããŸããã
è¡š '%-.192s' ã¯READããã¯ãããŠããŠãæŽæ°ã§ããŸããã è¡š '%-.192s' 㯠LOCK TABLES ã§ããã¯ãããŠããŸããã BLOB/TEXT å '%-.192s' ã«ã¯ããã©ã«ãå€ãæå®ã§ããŸããã ããŒã¿ããŒã¹å '%-.100s' ã¯äžæ£ã§ãã è¡šå '%-.100s' ã¯äžæ£ã§ãã SELECTãMAX_JOIN_SIZEãè¶
ããè¡æ°ãåŠçããŸãããWHEREå¥ã確èªããSELECTæã«åé¡ããªããã°ã SET SQL_BIG_SELECTS=1 ãŸã㯠SET MAX_JOIN_SIZE=# ã䜿çšããŠäžããã äžæãªãšã©ãŒ '%-.192s' ã¯äžæãªããã·ãŒãžã£ã§ãã ããã·ãŒãžã£ '%-.192s' ãžã®ãã©ã¡ãŒã¿æ°ãäžæ£ã§ãã ããã·ãŒãžã£ '%-.192s' ãžã®ãã©ã¡ãŒã¿ãäžæ£ã§ãã '%-.192s' 㯠%-.32s ã§ã¯äžæãªè¡šã§ãã å '%-.192s' ã¯2åæå®ãããŠããŸãã éèšé¢æ°ã®äœ¿çšæ¹æ³ãäžæ£ã§ãã è¡š '%-.192s' ã¯ããã®MySQLããŒãžã§ã³ã«ã¯ç¡ãæ©èœã䜿çšããŠããŸãã è¡šã«ã¯æäœã§ã1åã®åãå¿
èŠã§ãã è¡š '%-.192s' ã¯æºæ¯ã§ãã äžæãªæåã³ãŒãã»ãã: '%-.64s' è¡šãå€ãããŸããMySQLãJOINã§ãã衚㯠%d åãŸã§ã§ãã åãå€ãããŸãã è¡ãµã€ãºã倧ããããŸãããã®è¡šã®æ倧è¡ãµã€ãºã¯ BLOB ãå«ãŸãã« %ld ã§ããæ ŒçŽæã®ãªãŒããŒããããå«ãŸããŸã(ããã¥ã¢ã«ã確èªããŠãã ãã)ãåãTEXTãŸãã¯BLOBã«å€æŽããå¿
èŠããããŸãã ã¹ã¬ããã¹ã¿ãã¯äžè¶³ã§ã(䜿çš: %ld ; ãµã€ãº: %ld)ãå¿
èŠã«å¿ããŠããã倧ããå€ã§ 'mysqld --thread_stack=#' ã®æå®ãããŠãã ããã OUTER JOINã«çžäºäŸåãèŠã€ãããŸãããONå¥ã®æ¡ä»¶ã確èªããŠäžããã Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler é¢æ° '%-.192s' ãããŒãã§ããŸããã é¢æ° '%-.192s' ãåæåã§ããŸããã; %-.80s å
±æã©ã€ãã©ãªã«ã¯ãã¹ãæå®ã§ããŸããã é¢æ° '%-.192s' ã¯ãã§ã«å®çŸ©ãããŠããŸãã å
±æã©ã€ãã©ãª '%-.192s' ãéãäºãã§ããŸããã(ãšã©ãŒçªå·: %d, %-.128s) é¢æ° '%-.128s' ã¯å
±æã©ã€ãã©ãªãŒäžã«ãããŸããã é¢æ° '%-.192s' ã¯å®çŸ©ãããŠããŸããã æ¥ç¶ãšã©ãŒãå€ãããããã¹ã '%-.64s' ã¯æåŠãããŸããã'mysqladmin flush-hosts' ã§è§£é€ã§ããŸãã ãã¹ã '%-.64s' ããã®ãã® MySQL server ãžã®æ¥ç¶ã¯èš±å¯ãããŠããŸããã MySQL ãå¿åãŠãŒã¶ãŒã§äœ¿çšããŠããã®ã§ããã¹ã¯ãŒãã®å€æŽã¯ã§ããŸããã ä»ã®ãŠãŒã¶ãŒã®ãã¹ã¯ãŒããå€æŽããããã«ã¯ãmysqlããŒã¿ããŒã¹ã®è¡šãæŽæ°ããæš©éãå¿
èŠã§ãã ãŠãŒã¶ãŒããŒãã«ã«è©²åœããã¬ã³ãŒããèŠã€ãããŸããã 該åœããè¡: %ld å€æŽ: %ld èŠå: %ld æ°èŠã«ã¹ã¬ãããäœæã§ããŸããã(ãšã©ãŒçªå· %M) ããã䜿çšå¯èœã¡ã¢ãªãŒã®äžè¶³ã§ãªããã°ãOSäŸåã®ãã°ã§ããå¯èœæ§ããããŸãã %lu è¡ç®ã§ãåã®æ°ãå€ã®æ°ãšäžèŽããŸããã è¡šãåãªãŒãã³ã§ããŸããã: '%-.192s' NULL å€ã®äœ¿çšæ¹æ³ãäžé©åã§ãã regexp ããšã©ãŒ '%-.64s' ãè¿ããŸããã GROUP BYå¥ãç¡ãå Žåãéèšé¢æ°(MIN(),MAX(),COUNT(),...)ãšéåžžã®åãåæã«äœ¿çšã§ããŸããã ãŠãŒã¶ãŒ '%-.48s' (ãã¹ã '%-.64s' äž) ã¯èš±å¯ãããŠããŸããã ã³ãã³ã %-.32s 㯠ãŠãŒã¶ãŒ '%s'@'%s' ,ããŒãã« '%-.192s' ã«å¯ŸããŠèš±å¯ãããŠããŸãã ã³ãã³ã %-.32s 㯠ãŠãŒã¶ãŒ '%s'@'%s'
ã«ã©ã '%-.192s' ããŒãã« '%-.192s' ã«å¯ŸããŠèš±å¯ãããŠããŸãã äžæ£ãª GRANT/REVOKE ã³ãã³ãã§ããã©ã®æš©éã§å©çšå¯èœãã¯ããã¥ã¢ã«ãåç
§ããŠäžããã GRANTã³ãã³ããžã®ããã¹ãåããŠãŒã¶ãŒåãé·ãããŸãã è¡š '%-.192s.%-.192s' ã¯ååšããŸããã ãŠãŒã¶ãŒ '%-.48s' (ãã¹ã '%-.64s' äž) ã®è¡š '%-.192s' ãžã®æš©éã¯å®çŸ©ãããŠããŸããã ãã®MySQLããŒãžã§ã³ã§ã¯å©çšã§ããªãã³ãã³ãã§ãã SQLæ§æãšã©ãŒã§ããããŒãžã§ã³ã«å¯Ÿå¿ããããã¥ã¢ã«ãåç
§ããŠæ£ããæ§æã確èªããŠãã ããã 'Delayed insert'ã¹ã¬ãããè¡š '%-.192s' ã®ããã¯ãååŸã§ããŸããã§ããã 'Delayed insert'ã¹ã¬ãããå€ãããŸãã æ¥ç¶ %ld ãäžæãããŸãããããŒã¿ããŒã¹: '%-.192s' ãŠãŒã¶ãŒ: '%-.48s' (%-.64s) 'max_allowed_packet'ããã倧ããªãã±ãããåä¿¡ããŸããã æ¥ç¶ãã€ãã®èªã¿èŸŒã¿ãšã©ãŒã§ãã fcntl()ããšã©ãŒãè¿ããŸããã äžæ£ãªé åºã®ãã±ãããåä¿¡ããŸããã å§çž®ãã±ããã®å±éãã§ããŸããã§ããã ãã±ããã®åä¿¡ã§ãšã©ãŒãçºçããŸããã ãã±ããã®åä¿¡ã§ã¿ã€ã ã¢ãŠããçºçããŸããã ãã±ããã®éä¿¡ã§ãšã©ãŒãçºçããŸããã ãã±ããã®éä¿¡ã§ã¿ã€ã ã¢ãŠããçºçããŸããã çµæã®æååã 'max_allowed_packet' ããã倧ããã§ãã Storage engine %s doesn't support BLOB/TEXT columns Storage engine %s doesn't support AUTO_INCREMENT columns è¡š '%-.192s' ã¯LOCK TABLESã§ããã¯ãããŠãããããINSERT DELAYEDã䜿çšã§ããŸããã åå '%-.100s' ã¯äžæ£ã§ãã The storage engine %s can't index column %`s MERGEè¡šã®æ§æè¡šããªãŒãã³ã§ããŸãããåå®çŸ©ãç°ãªãããMyISAMè¡šã§ã¯ãªãããååšããŸããã äžææ§å¶çŽéåã®ãããè¡š '%-.192s' ã«æžã蟌ããŸããã BLOBå '%-.192s' ãããŒã«äœ¿çšããã«ã¯é·ãæå®ãå¿
èŠã§ãã PRIMARY KEYã®åã¯å
šãŠNOT NULLã§ãªããã°ãããŸãããUNIQUE玢åŒã§ããã°NULLãå«ãããšãå¯èœã§ãã çµæã2è¡ä»¥äžã§ãã 䜿çšã®ã¹ãã¬ãŒãžãšã³ãžã³ã§ã¯ãPRIMARY KEYãå¿
èŠã§ãã ãã®ããŒãžã§ã³ã®MySQLã¯RAIDãµããŒããå«ããŠã³ã³ãã€ã«ãããŠããŸããã 'safe update mode'ã§ã玢åŒãå©çšããWHEREå¥ã®ç¡ãæŽæ°åŠçãå®è¡ããããšããŸããã çŽ¢åŒ '%-.192s' ã¯è¡š '%-.192s' ã«ã¯ååšããŸããã è¡šããªãŒãã³ã§ããŸããã ãã®è¡šã®ã¹ãã¬ãŒãžãšã³ãžã³ã¯ '%s' ãå©çšã§ããŸããã ãã®ã³ãã³ãã¯ãã©ã³ã¶ã¯ã·ã§ã³å
ã§å®è¡ã§ããŸããã COMMITäžã«ãšã©ãŒ %M ãçºçããŸããã ROLLBACKäžã«ãšã©ãŒ %M ãçºçããŸããã FLUSH_LOGSäžã«ãšã©ãŒ %M ãçºçããŸããã CHECKPOINTäžã«ãšã©ãŒ %M ãçºçããŸããã æ¥ç¶ %ld ãäžæãããŸãããããŒã¿ããŒã¹: '%-.192s' ãŠãŒã¶ãŒ: '%-.48s' ãã¹ã: '%-.64s' (%-.64s) You should never see it ãã€ããªãã°ãã¯ããŒãºãããŠããŸããRESET MASTER ãå®è¡ã§ããŸããã ãã³ãè¡š '%-.192s' ã®çŽ¢åŒåæ§ç¯ã«å€±æããŸããã ãã¹ã¿ãŒã§ãšã©ãŒãçºç: '%-.64s' ãã¹ã¿ãŒããã®ããŒã¿åä¿¡äžã®ãããã¯ãŒã¯ãšã©ãŒ ãã¹ã¿ãŒãžã®ããŒã¿éä¿¡äžã®ãããã¯ãŒã¯ãšã©ãŒ åãªã¹ãã«å¯Ÿå¿ããå
šæ玢åŒ(FULLTEXT)ãèŠã€ãããŸããã ãã§ã«ã¢ã¯ãã£ããªè¡šããã¯ããã©ã³ã¶ã¯ã·ã§ã³ããããããã³ãã³ããå®è¡ã§ããŸããã '%-.64s' ã¯äžæãªã·ã¹ãã å€æ°ã§ãã è¡š '%-.192s' ã¯å£ããŠããŸãã修埩ãå¿
èŠã§ãã è¡š '%-.192s' ã¯å£ããŠããŸãã修埩(èªåïŒ)ã«ã倱æããŠããŸãã ãã©ã³ã¶ã¯ã·ã§ã³å¯Ÿå¿ã§ã¯ãªãè¡šãžã®å€æŽã¯ããŒã«ããã¯ãããŸããã è€æ°ã¹ããŒãã¡ã³ãããæããã©ã³ã¶ã¯ã·ã§ã³ã 'max_binlog_cache_size' 以äžã®å®¹éãå¿
èŠãšããŸããããã®ã·ã¹ãã å€æ°ãå¢å ããŠãåè©Šè¡ããŠãã ããã This operation cannot be performed as you have a running slave '%2$*1$s'; run STOP SLAVE '%2$*1$s' first ãã®åŠçã¯ã皌åäžã®ã¹ã¬ãŒãã§ãªããã°å®è¡ã§ããŸãããã¹ã¬ãŒãã®èšå®ãããŠSTART SLAVEã³ãã³ããå®è¡ããŠãã ããã ãã®ãµãŒããŒã¯ã¹ã¬ãŒããšããŠèšå®ãããŠããŸãããã³ã³ãã£ã°ãã¡ã€ã«ãCHANGE MASTER TOã³ãã³ãã§èšå®ããŠäžããã 'master info '%.*s''æ§é äœã®åæåãã§ããŸããã§ãããMariaDBãšã©ãŒãã°ã§ãšã©ãŒã¡ãã»ãŒãžã確èªããŠãã ããã ã¹ã¬ãŒãã¹ã¬ãããäœæã§ããŸãããã·ã¹ãã ãªãœãŒã¹ã確èªããŠãã ããã ãŠãŒã¶ãŒ '%-.64s' ã¯ãã§ã« 'max_user_connections' 以äžã®ã¢ã¯ãã£ããªæ¥ç¶ãè¡ã£ãŠããŸãã SETåŠçã倱æããŸããã ããã¯åŸ
ã¡ãã¿ã€ã ã¢ãŠãããŸããããã©ã³ã¶ã¯ã·ã§ã³ãåè©Šè¡ããŠãã ããã ããã¯ã®æ°ãå€ãããŸãã èªã¿èŸŒã¿å°çšãã©ã³ã¶ã¯ã·ã§ã³ã§ãã ã°ããŒãã«ãªãŒãããã¯ãä¿æããŠããéã¯ãDROP DATABASE ãå®è¡ã§ããŸããã ã°ããŒãã«ãªãŒãããã¯ãä¿æããŠããéã¯ãCREATE DATABASE ãå®è¡ã§ããŸããã %s ã®åŒæ°ãäžæ£ã§ã '%s'@'%s' is not allowed to create new users äžæ£ãªè¡šå®çŸ©ã§ããMERGEè¡šã®æ§æè¡šã¯ãã¹ãŠåãããŒã¿ããŒã¹å
ã«ãªããã°ãªããŸããã ããã¯ååŸäžã«ãããããã¯ãæ€åºãããŸããããã©ã³ã¶ã¯ã·ã§ã³ãåè©Šè¡ããŠãã ããã The storage engine %s doesn't support FULLTEXT indexes å€éšããŒå¶çŽãè¿œå ã§ããŸããã 芪ããŒããããŸãããå€éšããŒå¶çŽéåã§ãã åã¬ã³ãŒãããããŸããå€éšããŒå¶çŽéåã§ãã ãã¹ã¿ãŒãžã®æ¥ç¶ãšã©ãŒ: %-.128s ãã¹ã¿ãŒã§ã®ã¯ãšãªå®è¡ãšã©ãŒ: %-.128s %s ã³ãã³ãã®å®è¡ãšã©ãŒ: %-.128s %s ã® %s ã«é¢ããäžæ£ãªäœ¿çšæ³ã§ãã 䜿çšã®SELECTæãè¿ãåæ°ãéããŸãã 競åãããªãŒãããã¯ãä¿æããŠããã®ã§ãã¯ãšãªãå®è¡ã§ããŸããã ãã©ã³ã¶ã¯ã·ã§ã³å¯Ÿå¿ã®è¡šãšé察å¿ã®è¡šã®åæ䜿çšã¯ç¡å¹åãããŠããŸãã ãªãã·ã§ã³ '%s' ã2床䜿çšãããŠããŸãã ãŠãŒã¶ãŒ '%-.64s' ã¯ãªãœãŒã¹ã®äžé '%s' ã«éããŸããã(çŸåšå€: %ld) ã¢ã¯ã»ã¹ã¯æåŠãããŸããããã®æäœã«ã¯ %-.128s æš©éã(è€æ°ã®å Žåã¯ã©ãã1ã€)å¿
èŠã§ãã å€æ° '%-.64s' ã¯ã»ãã·ã§ã³å€æ°ã§ããSET GLOBALã§ã¯äœ¿çšã§ããŸããã å€æ° '%-.64s' ã¯ã°ããŒãã«å€æ°ã§ããSET GLOBALã䜿çšããŠãã ããã å€æ° '%-.64s' ã«ã¯ããã©ã«ãå€ããããŸããã å€æ° '%-.64s' ã«å€ '%-.200s' ãèšå®ã§ããŸããã å€æ° '%-.64s' ãžã®å€ã®åãäžæ£ã§ãã å€æ° '%-.64s' ã¯æžã蟌ã¿å°çšã§ããèªã¿èŸŒã¿ã¯ã§ããŸããã '%s' ã®äœ¿çšæ³ãŸãã¯å Žæãäžæ£ã§ãã ãã®ããŒãžã§ã³ã®MariaDBã§ã¯ããŸã '%s' ãå©çšã§ããŸããã èŽåœçãªãšã©ãŒ %d: '%-.320s' ããã¹ã¿ãŒã§ãã€ããªãã°èªã¿èŸŒã¿äžã«çºçããŸããã replicate-*-table ã«ãŒã«ã«åŸã£ãŠãã¹ã¬ãŒãSQLã¹ã¬ããã¯ã¯ãšãªãç¡èŠããŸããã å€æ° '%-.192s' 㯠%s å€æ°ã§ãã å€éšã㌠'%-.192s' ã®å®çŸ©ã®äžæ£: %s å€éšããŒã®åç
§è¡šãšå®çŸ©ãäžèŽããŸããã ãªãã©ã³ãã« %d åã®åãå¿
èŠã§ãã ãµãã¯ãšãªã2è¡ä»¥äžã®çµæãè¿ããŸãã '%.*s' ã¯ããªãã¢ãŒãã¹ããŒãã¡ã³ãã®äžæãªãã³ãã«ã§ãã(%s ã§æå®ãããŸãã) ãã«ãããŒã¿ããŒã¹ã¯å£ããŠãããååšããŸããã ãµãã¯ãšãªã®åç
§ãã«ãŒãããŠããŸãã å '%s' ã %s ãã %s ãžå€æããŸãã '%-.64s' ã®åç
§ã¯ã§ããŸããã(%s) å°åºè¡šã«ã¯å¥åãå¿
é ã§ãã Select %u ã¯æé©åã«ãã£ãŠæžããããŸããã ç¹å®ã®SELECTã®ã¿ã§äœ¿çšã®è¡š '%-.192s' 㯠%-.32s ã§ã¯äœ¿çšã§ããŸããã ã¯ã©ã€ã¢ã³ãã¯ãµãŒããŒãèŠæ±ããèªèšŒãããã³ã«ã«å¯Ÿå¿ã§ããŸãããMariaDBã¯ã©ã€ã¢ã³ãã®ã¢ããã°ã¬ãŒããæ€èšããŠãã ããã 空é玢åŒã®ããŒå㯠NOT NULL ã§ãªããã°ãããŸããã COLLATION '%s' 㯠CHARACTER SET '%s' ã«é©çšã§ããŸããã ã¹ã¬ãŒãã¯ãã§ã«çšŒåäžã§ãã ã¹ã¬ãŒãã¯ãã§ã«åæ¢ããŠããŸãã å±éåŸã®ããŒã¿ã倧ããããŸããæ倧ãµã€ãºã¯ %d ã§ãã(å±éåŸããŒã¿ã®é·ãæ
å ±ãå£ããŠããå¯èœæ§ããããŸãã) ZLIB: ã¡ã¢ãªäžè¶³ã§ãã ZLIB: åºåãããã¡ã«ååãªç©ºãããããŸããã(å±éåŸããŒã¿ã®é·ãæ
å ±ãå£ããŠããå¯èœæ§ããããŸãã) ZLIB: å
¥åããŒã¿ãå£ããŠããŸãã Row %u was cut by GROUP_CONCAT() è¡ %lu ã¯ãã¹ãŠã®åãžã®ããŒã¿ãå«ãã§ããŸããã è¡ %lu ã¯ããŒã¿ãåãæšãŠãããŸãããåãããå€ãããŒã¿ãå«ãã§ããŸããã åã«ããã©ã«ãå€ãèšå®ãããŸãããNOT NULLã®å '%s' ã« è¡ %lu 㧠NULL ãäžããããŸããã Out of range value for column '%s' at row %lu å '%s' ã® è¡ %lu ã§ããŒã¿ãåãæšãŠãããŸããã ã¹ãã¬ãŒãžãšã³ãžã³ %s ãè¡š '%s' ã«å©çšãããŠããŸãã ç
§åé åº (%s,%s) ãš (%s,%s) ã®æ··åšã¯æäœ '%s' ã§ã¯äžæ£ã§ãã Cannot drop one or more of the requested users æå®ããããŠãŒã¶ãŒããæå®ãããå
šãŠã®æš©éãå¥å¥ªããããšãã§ããŸããã§ããã ç
§åé åº (%s,%s), (%s,%s), (%s,%s) ã®æ··åšã¯æäœ '%s' ã§ã¯äžæ£ã§ãã æäœ '%s' ã§ã¯äžæ£ãªç
§åé åºã®æ··åšã§ãã å€æ° '%-.64s' ã¯æ§é å€æ°ã®æ§æèŠçŽ ã§ã¯ãããŸããã(XXXX.å€æ°å ãšããæå®ã¯ã§ããŸããã) äžæãªç
§åé åº: '%-.64s' ãã®MySQLã¹ã¬ãŒãã¯SSLãµããŒããå«ããŠã³ã³ãã€ã«ãããŠããªãã®ã§ãCHANGE MASTER ã®SSLãã©ã¡ãŒã¿ã¯ç¡èŠãããŸãããä»åŸSSLãµããŒããæã€MySQLã¹ã¬ãŒããèµ·åããéã«å©çšãããŸãã ãµãŒããŒã¯ --secure-auth ã¢ãŒãã§çšŒåããŠããŸããããã '%s'@'%s' ã¯å€ã圢åŒã®ãã¹ã¯ãŒãã䜿çšããŠããŸããæ°ãã圢åŒã®ãã¹ã¯ãŒãã«å€æŽããŠãã ããã ãã£ãŒã«ããŸãã¯åç
§ '%-.192s%s%-.192s%s%-.192s' 㯠SELECT #%d ã§ã¯ãªããSELECT #%d ã§è§£æ±ºãããŸããã START SLAVE UNTIL ãžã®ãã©ã¡ãŒã¿ãŸãã¯ãã®çµã¿åãããäžæ£ã§ãã START SLAVE UNTIL ã§æ®µéçã«ã¬ããªã±ãŒã·ã§ã³ãè¡ãéã«ã¯ã--skip-slave-start ãªãã·ã§ã³ã䜿ãããšãæšå¥šããŸãã䜿ããªãå Žåãã¹ã¬ãŒãã®mysqldãäžæ
®ã®åèµ·åããããšåé¡ãçºçããŸãã ã¹ã¬ãŒãSQLã¹ã¬ãããéå§ãããªããããUNTILãªãã·ã§ã³ã¯ç¡èŠãããŸããã 玢åŒå '%-.100s' ã¯äžæ£ã§ãã ã«ã¿ãã°å '%-.100s' ã¯äžæ£ã§ãã Query cache failed to set size %llu; new query cache size is %lu å '%-.192s' ã¯å
šæ玢åŒã®ããŒã«ã¯ã§ããŸããã '%-.100s' ã¯äžæãªããŒãã£ãã·ã¥ã§ãã MariaDB㯠--skip-name-resolve ã¢ãŒãã§èµ·åããŠããŸãããã®ãªãã·ã§ã³ãå€ããŠåèµ·åããªããã°ããã®æš©éæäœã¯æ©èœããŸããã '%s' ã¯äžæãªã¹ãã¬ãŒãžãšã³ãžã³ã§ãã '%s' ã¯å°æ¥ã®ãªãªãŒã¹ã§å»æ¢äºå®ã§ãã代ããã« %s ã䜿çšããŠãã ããã 察象衚 %-.100s ã¯æŽæ°å¯èœã§ã¯ãªãã®ã§ã%s ãè¡ããŸããã æ©èœ '%s' ã¯ç¡å¹ã§ããå©çšããããã«ã¯ '%s' ãå«ããŠãã«ãããMariaDBãå¿
èŠã§ãã MariaDBãµãŒããŒã %s ãªãã·ã§ã³ã§å®è¡ãããŠããã®ã§ããã®ã¹ããŒãã¡ã³ãã¯å®è¡ã§ããŸããã å '%-.100s' ã§ãéè€ããå€ '%-.64s' ã %s ã«æå®ãããŠããŸãã äžæ£ãª %-.32s ã®å€ãåãæšãŠãããŸããã: '%-.128s' äžæ£ãªè¡šå®çŸ©ã§ããDEFAULTå¥ãŸãã¯ON UPDATEå¥ã« CURRENT_TIMESTAMP ããšããªãTIMESTAMPåã®åã¯1ã€ãŸã§ã§ãã å '%-.192s' ã« ON UPDATEå¥ã¯ç¡å¹ã§ãã This command is not supported in the prepared statement protocol yet ãšã©ãŒ %d '%-.200s' ã %s ããè¿ãããŸããã äžæãšã©ãŒ %d '%-.200s' ã %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 ã¹ã¬ããã¹ã¿ãã¯äžè¶³ã§ã(䜿çš: %ld ; ãµã€ãº: %ld ; èŠæ±: %ld)ããã倧ããå€ã§ 'mysqld --thread_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) 察象衚 %-.100s ã¯æ¿å
¥å¯èœã§ã¯ãªãã®ã§ã%s ãè¡ããŸããã Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist Too high level of nesting for select Name '%-.64s' has become '' First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY The foreign server, %s, you are trying to create already exists. The foreign server name you are trying to reference does not exist. Data source error: %-.64s Table storage engine '%-.64s' does not support the create option '%.64s' Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition MAXVALUE can only be used in last partition definition Subpartitions can only be hash partitions and by key Must define subpartitions on all partitions if on one partition Wrong number of partitions defined, mismatch with previous setting Wrong number of subpartitions defined, mismatch with previous setting Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed Expression in RANGE/LIST VALUES must be constant Field in list of fields for partition function not found in table List of fields is only allowed in KEY partitions The partition info in the frm file is not consistent with what can be written into the frm file The %-.192s function returns the wrong type For %-.64s partitions each partition must be defined VALUES LESS THAN value must be strictly increasing for each partition VALUES value must be of same type as partition function Multiple definition of same constant in list partitioning Partitioning can not be used stand-alone in query The mix of handlers in the partitions is not allowed in this version of MariaDB For the partitioned engine it is necessary to define all %-.64s Too many partitions (including subpartitions) were defined It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning Failed to create specific handler file A BLOB field is not allowed in partition function A %-.192s must include all columns in the table's partitioning function Number of %-.64s = 0 is not an allowed value Partition management on a not partitioned table is not possible Foreign key clause is not yet supported in conjunction with partitioning Error in list of partitions to %-.64s Cannot remove all partitions, use DROP TABLE instead COALESCE PARTITION can only be used on HASH/KEY partitions REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs %-.64s PARTITION can only be used on RANGE/LIST partitions Trying to Add partition(s) with wrong number of subpartitions At least one partition must be added At least one partition must be coalesced More partitions to reorganize than there are partitions Duplicate partition name %-.192s It is not allowed to shut off binlog on this command When reorganizing a set of partitions they must be in consecutive order Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range Partition function not supported in this version for this handler Partition state cannot be defined from CREATE/ALTER TABLE The %-.64s handler only supports 32 bit integers in VALUES Plugin '%-.192s' is not loaded Incorrect %-.32s value: '%-.128s' Table has no partition for value %-.64s It is not allowed to specify %s more than once Failed to create %s Failed to drop %s The handler doesn't support autoextend of tablespaces A size parameter was incorrectly specified, either number or on the form 10M The size number was correct but we don't allow the digit part to be more than 2 billion Failed to alter: %s Writing one row to the row-based binary log failed Table definition on master and slave does not match: %s Slave running with --log-slave-updates must use row-based binary logging to be able to replicate row-based binary log events Event '%-.192s' already exists Failed to store event %s. Error code %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 Partition constant is out of partition function domain This partition function is not allowed Error in DDL log Not allowed to use NULL value in VALUES LESS THAN Incorrect partition name Transaction characteristics can'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 cannot be used in partitioned tables Cannot activate '%-.64s' log The server was not built with row-based replication Decoding of base64 string failed Recursion of EVENT DDL statements is forbidden when body is present Cannot proceed because system tables used by Event Scheduler were found damaged at server start Only integers allowed as number here 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 '%-.64s' ã¯çŽ¢åŒ '%-.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 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s Fatal error: %s Relay log read failure: %s Relay log write failure: %s Failed to create %s Master command %s failed: %s Binary logging not possible. Message: %s View `%-.64s`.`%-.64s` has no creation context Creation context of view `%-.64s`.`%-.64s' is invalid Creation context of stored routine `%-.64s`.`%-.64s` is invalid Corrupted TRG file for table `%-.64s`.`%-.64s` Triggers for table `%-.64s`.`%-.64s` have no creation context Trigger creation context of table `%-.64s`.`%-.64s` is invalid Creation context of event `%-.64s`.`%-.64s` is invalid Cannot open table for trigger `%-.64s`.`%-.64s` Cannot create stored routine `%-.64s`. Check warnings 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 Database Table Partition Subpartition Temporary Renamed Too many active concurrent transactions Non-ASCII separator arguments are not fully supported debug sync point wait timed out debug sync point hit limit reached Duplicate condition information item '%s' Unhandled user-defined warning condition Unhandled user-defined not found condition Unhandled user-defined exception condition RESIGNAL when handler not active SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE Data truncated for condition item '%s' Data too long for condition item '%s' Unknown locale: '%-.64s' The requested server id %d clashes with the slave startup option --replicate-same-server-id Query cache is disabled; 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 Failed to read from the .par file VALUES value for partition '%-.64s' must have type INT Access denied for user '%s'@'%s' 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) Non matching attribute '%-.64s' between partition and table Table to exchange with partition is partitioned: '%-.64s' Table to exchange with partition is temporary: '%-.64s' Subpartitioned table, use subpartition instead of partition Unknown partition '%-.64s' in table '%-.64s' Tables have different definitions Found a row that does not match the partition Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size. Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s' Table to exchange with partition has foreign key references: '%-.64s' Key value '%-.192s' was not found in table '%-.192s.%-.192s' 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 () clause on non partitioned table Found a row not matching the given partition set You should never see it Failure while changing the type of replication repository: %s. The creation of some temporary tables could not be rolled back. Some temporary tables were dropped, but these operations could not be rolled back. %s is not supported in multi-threaded slave mode. %s The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata. Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s. %s FULLTEXT index is not supported for partitioned tables. Invalid condition number Sending passwords in plain text without SSL/TLS is extremely insecure. Storing 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 for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s' Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child table Setting authentication options is not possible when only the Slave SQL Thread is being started. The table does not have FULLTEXT index to support this query The system variable %.200s cannot be set in stored functions or triggers. The system variable %.200s cannot be set when there is an ongoing transaction. The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST. When @@SESSION.GTID_NEXT_LIST == NULL, the system variable @@SESSION.GTID_NEXT cannot change inside a transaction. The statement '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 ã¯çŽ¢åŒ '%-.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. Found a row in wrong partition %s Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of slave_pending_jobs_size_max. Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table The binary log file '%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. Table '%-.192s.%-.192s' doesn't exist in engine 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`