INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (360,40,'CREATE EVENT','Syntax:\nCREATE\n    [DEFINER = { user | CURRENT_USER }]\n    EVENT\n    [IF NOT EXISTS]\n    event_name\n    ON SCHEDULE schedule\n    [ON COMPLETION [NOT] PRESERVE]\n    [ENABLE | DISABLE | DISABLE ON SLAVE]\n    [COMMENT \'comment\']\n    DO event_body;\n\nschedule:\n    AT timestamp [+ INTERVAL interval] ...\n  | EVERY interval\n    [STARTS timestamp [+ INTERVAL interval] ...]\n    [ENDS timestamp [+ INTERVAL interval] ...]\n\ninterval:\n    quantity {YEAR | QUARTER | MONTH | DAY | HOUR | MINUTE |\n              WEEK | SECOND | YEAR_MONTH | DAY_HOUR | DAY_MINUTE |\n              DAY_SECOND | HOUR_MINUTE | HOUR_SECOND | MINUTE_SECOND}\n\nThis statement creates and schedules a new event. The event will not\nrun unless the Event Scheduler is enabled. For information about\nchecking Event Scheduler status and enabling it if necessary, see\nhttp://dev.mysql.com/doc/refman/5.7/en/events-configuration.html.\n\nCREATE EVENT requires the EVENT privilege for the schema in which the\nevent is to be created. It might also require the SUPER privilege,\ndepending on the DEFINER value, as described later in this section.\n\nThe minimum requirements for a valid CREATE EVENT statement are as\nfollows:\n\no The keywords CREATE EVENT plus an event name, which uniquely\n  identifies the event in a database schema.\n\no An ON SCHEDULE clause, which determines when and how often the event\n  executes.\n\no A DO clause, which contains the SQL statement to be executed by an\n  event.\n\nThis is an example of a minimal CREATE EVENT statement:\n\nCREATE EVENT myevent\n    ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 HOUR\n    DO\n      UPDATE myschema.mytable SET mycol = mycol + 1;\n\nThe previous statement creates an event named myevent. This event\nexecutes once---one hour following its creation---by running an SQL\nstatement that increments the value of the myschema.mytable table\'s\nmycol column by 1.\n\nThe event_name must be a valid MySQL identifier with a maximum length\nof 64 characters. Event names are not case sensitive, so you cannot\nhave two events named myevent and MyEvent in the same schema. In\ngeneral, the rules governing event names are the same as those for\nnames of stored routines. See\nhttp://dev.mysql.com/doc/refman/5.7/en/identifiers.html.\n\nAn event is associated with a schema. If no schema is indicated as part\nof event_name, the default (current) schema is assumed. To create an\nevent in a specific schema, qualify the event name with a schema using\nschema_name.event_name syntax.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/create-event.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/create-event.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (361,7,'MBR DEFINITION','Its MBR (minimum bounding rectangle), or envelope. This is the bounding\ngeometry, formed by the minimum and maximum (X,Y) coordinates:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-class-geometry.html\n\n','((MINX MINY, MAXX MINY, MAXX MAXY, MINX MAXY, MINX MINY))\n','http://dev.mysql.com/doc/refman/5.7/en/gis-class-geometry.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (362,26,'ST_DIFFERENCE','ST_Difference(g1, g2)\n\nReturns a geometry that represents the point set difference of the\ngeometry values g1 and g2.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html\n\n','mysql> SET @g1 = POINT(1,1), @g2 = POINT(2,2);\nmysql> SELECT ST_AsText(ST_Difference(@g1, @g2));\n+------------------------------------+\n| ST_AsText(ST_Difference(@g1, @g2)) |\n+------------------------------------+\n| POINT(1 1)                         |\n+------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (363,25,'GEOMETRYCOLLECTION','GeometryCollection(g1,g2,...)\n\nConstructs a GeometryCollection.\n\nAs of MySQL 5.7.5, GeometryCollection() returns all the proper\ngeometries contained in the argument even if a nonsupported geometry is\npresent. Before 5.7.5, if the argument contains a nonsupported\ngeometry, the return value is NULL.\n\nAs of MySQL 5.7.8, GeometryCollection() with no arguments is permitted\nas a way to create an empty geometry.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-mysql-specific-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-mysql-specific-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (364,3,'*','Syntax:\n*\n\nMultiplication:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html\n\n','mysql> SELECT 3*5;\n        -> 15\nmysql> SELECT 18014398509481984*18014398509481984.0;\n        -> 324518553658426726783156020576256.0\nmysql> SELECT 18014398509481984*18014398509481984;\n        -> out-of-range error\n','http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (365,33,'ST_ASBINARY','ST_AsBinary(g), ST_AsWKB(g)\n\nConverts a value in internal geometry format to its WKB representation\nand returns the binary result.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-format-conversion-functions.html\n\n','SELECT ST_AsBinary(g) FROM geom;\n','http://dev.mysql.com/doc/refman/5.7/en/gis-format-conversion-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (366,38,'TO_BASE64','Syntax:\nTO_BASE64(str)\n\nConverts the string argument to base-64 encoded form and returns the\nresult as a character string with the connection character set and\ncollation. If the argument is not a string, it is converted to a string\nbefore conversion takes place. The result is NULL if the argument is\nNULL. Base-64 encoded strings can be decoded using the FROM_BASE64()\nfunction.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT TO_BASE64(\'abc\'), FROM_BASE64(TO_BASE64(\'abc\'));\n        -> \'JWJj\', \'abc\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (367,12,'DES_DECRYPT','Syntax:\nDES_DECRYPT(crypt_str[,key_str])\n\nDecrypts a string encrypted with DES_ENCRYPT(). If an error occurs,\nthis function returns NULL.\n\nThis function works only if MySQL has been configured with SSL support.\nSee http://dev.mysql.com/doc/refman/5.7/en/ssl-connections.html.\n\nIf no key_str argument is given, DES_DECRYPT() examines the first byte\nof the encrypted string to determine the DES key number that was used\nto encrypt the original string, and then reads the key from the DES key\nfile to decrypt the message. For this to work, the user must have the\nSUPER privilege. The key file can be specified with the --des-key-file\nserver option.\n\nIf you pass this function a key_str argument, that string is used as\nthe key for decrypting the message.\n\nIf the crypt_str argument does not appear to be an encrypted string,\nMySQL returns the given crypt_str.\n\n*Note*: The DES_ENCRYPT() and DES_DECRYPT() functions are deprecated as\nof MySQL 5.7.6, will be removed in a future MySQL release, and should\nno longer be used. Consider using AES_ENCRYPT() and AES_DECRYPT()\ninstead.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (368,2,'ST_AREA','ST_Area(poly)\n\nReturns a double-precision number indicating the area of the argument,\nas measured in its spatial reference system. For arguments of dimension\n0 or 1, the result is 0.\n\nAdditionally, as of MySQL 5.7.5: The result is the sum of the area\nvalues of all components for a geometry collection. If a geometry\ncollection is empty, its area is returned as 0.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','mysql> SET @poly = \'Polygon((0 0,0 3,3 0,0 0),(1 1,1 2,2 1,1 1))\';\nmysql> SELECT ST_Area(ST_GeomFromText(@poly));\n+---------------------------------+\n| ST_Area(ST_GeomFromText(@poly)) |\n+---------------------------------+\n|                               4 |\n+---------------------------------+\n\nmysql> SET @mpoly =\n    -> \'MultiPolygon(((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1)))\';\nmysql> SELECT ST_Area(ST_GeomFromText(@mpoly));\n+----------------------------------+\n| ST_Area(ST_GeomFromText(@mpoly)) |\n+----------------------------------+\n|                                8 |\n+----------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (369,13,'ENDPOINT','EndPoint(ls)\n\nST_EndPoint() and EndPoint() are synonyms. For more information, see\nthe description of ST_EndPoint().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (370,16,'COUNT','Syntax:\nCOUNT(expr)\n\nReturns a count of the number of non-NULL values of expr in the rows\nretrieved by a SELECT statement. The result is a BIGINT value.\n\nCOUNT() returns 0 if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','mysql> SELECT student.student_name,COUNT(*)\n    ->        FROM student,course\n    ->        WHERE student.student_id=course.student_id\n    ->        GROUP BY student_name;\n','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (371,28,'INSERT','Syntax:\nINSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name\n    [PARTITION (partition_name,...)] \n    [(col_name,...)]\n    {VALUES | VALUE} ({expr | DEFAULT},...),(...),...\n    [ ON DUPLICATE KEY UPDATE\n      col_name=expr\n        [, col_name=expr] ... ]\n\nOr:\n\nINSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name\n    [PARTITION (partition_name,...)]\n    SET col_name={expr | DEFAULT}, ...\n    [ ON DUPLICATE KEY UPDATE\n      col_name=expr\n        [, col_name=expr] ... ]\n\nOr:\n\nINSERT [LOW_PRIORITY | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name\n    [PARTITION (partition_name,...)] \n    [(col_name,...)]\n    SELECT ...\n    [ ON DUPLICATE KEY UPDATE\n      col_name=expr\n        [, col_name=expr] ... ]\n\nINSERT inserts new rows into an existing table. The INSERT ... VALUES\nand INSERT ... SET forms of the statement insert rows based on\nexplicitly specified values. The INSERT ... SELECT form inserts rows\nselected from another table or tables. INSERT ... SELECT is discussed\nfurther in [HELP INSERT SELECT].\n\nWhen inserting into a partitioned table, you can control which\npartitions and subpartitions accept new rows. The PARTITION option\ntakes a comma-separated list of the names of one or more partitions or\nsubpartitions (or both) of the table. If any of the rows to be inserted\nby a given INSERT statement do not match one of the partitions listed,\nthe INSERT statement fails with the error Found a row not matching the\ngiven partition set. See\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-selection.html, for\nmore information and examples.\n\nIn MySQL 5.7, the DELAYED keyword is accepted but ignored by the\nserver. See [HELP INSERT DELAYED], for the reasons for this.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/insert.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/insert.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (372,7,'JSON_ARRAY_APPEND','JSON_ARRAY_APPEND(json_doc, path, val[, path, val] ...)\n\nAppends values to the end of the indicated arrays within a JSON\ndocument and returns the result. Returns NULL if any argument is NULL.\nAn error occurs if the json_doc argument is not a valid JSON document\nor any path argument is not a valid path expression or contains a * or\n** wildcard.\n\nThe path/value pairs are evaluated left to right. The document produced\nby evaluating one pair becomes the new value against which the next\npair is evaluated.\n\nPairs for which the path does not identify any array in the JSON\ndocument are ignored. If a path selects a scalar or object value, the\nvalue is autowrapped within an array and the new value is added to that\narray.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html\n\n','mysql> SET @j = \'["a", ["b", "c"], "d"]\';\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$[1]\', 1);\n+----------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$[1]\', 1) |\n+----------------------------------+\n| ["a", ["b", "c", 1], "d"]        |\n+----------------------------------+\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$[0]\', 2);\n+----------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$[0]\', 2) |\n+----------------------------------+\n| [["a", 2], ["b", "c"], "d"]      |\n+----------------------------------+\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$[1][0]\', 3);\n+-------------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$[1][0]\', 3) |\n+-------------------------------------+\n| ["a", [["b", 3], "c"], "d"]         |\n+-------------------------------------+\n\nmysql> SET @j = \'{"a": 1, "b": [2, 3], "c": 4}\';\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$.b\', \'x\');\n+------------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$.b\', \'x\')  |\n+------------------------------------+\n| {"a": 1, "b": [2, 3, "x"], "c": 4} |\n+------------------------------------+\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$.c\', \'y\');\n+--------------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$.c\', \'y\')    |\n+--------------------------------------+\n| {"a": 1, "b": [2, 3], "c": [4, "y"]} |\n+--------------------------------------+\n\nmysql> SET @j = \'{"a": 1}\';\nmysql> SELECT JSON_ARRAY_APPEND(@j, \'$\', \'z\');\n+---------------------------------+\n| JSON_ARRAY_APPEND(@j, \'$\', \'z\') |\n+---------------------------------+\n| [{"a": 1}, "z"]                 |\n+---------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (373,4,'MLINEFROMTEXT','MLineFromText(wkt[,srid]), MultiLineStringFromText(wkt[,srid])\n\nST_MLineFromText(), ST_MultiLineStringFromText(), MLineFromText(), and\nMultiLineStringFromText() are synonyms. For more information, see the\ndescription of ST_MLineFromText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (374,33,'GEOMCOLLFROMWKB','GeomCollFromWKB(wkb[,srid]), GeometryCollectionFromWKB(wkb[,srid])\n\nST_GeomCollFromWKB(), ST_GeometryCollectionFromWKB(),\nGeomCollFromWKB(), and GeometryCollectionFromWKB() are synonyms. For\nmore information, see the description of ST_GeomCollFromWKB().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (375,23,'TINYTEXT','TINYTEXT [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 255 (28 − 1) characters. The\neffective maximum length is less if the value contains multibyte\ncharacters. Each TINYTEXT value is stored using a 1-byte length prefix\nthat indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (376,14,'DEFAULT','Syntax:\nDEFAULT(col_name)\n\nReturns the default value for a table column. An error results if the\ncolumn has no default value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> UPDATE t SET i = DEFAULT(i)+1 WHERE id < 100;\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (377,21,'OPTIMIZE TABLE','Syntax:\nOPTIMIZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE\n    tbl_name [, tbl_name] ...\n\nReorganizes the physical storage of table data and associated index\ndata, to reduce storage space and improve I/O efficiency when accessing\nthe table. The exact changes made to each table depend on the storage\nengine used by that table. This statement does not work with views.\n\nUse OPTIMIZE TABLE in these cases, depending on the type of table:\n\no After doing substantial insert, update, or delete operations on an\n  InnoDB table that has its own .ibd file because it was created with\n  the innodb_file_per_table option enabled. The table and indexes are\n  reorganized, and disk space can be reclaimed for use by the operating\n  system.\n\no After doing substantial insert, update, or delete operations on\n  columns that are part of a FULLTEXT index in an InnoDB table. Set the\n  configuration option innodb_optimize_fulltext_only=1 first. To keep\n  the index maintenance period to a reasonable time, set the\n  innodb_ft_num_word_optimize option to specify how many words to\n  update in the search index, and run a sequence of OPTIMIZE TABLE\n  statements until the search index is fully updated.\n\no After deleting a large part of a MyISAM or ARCHIVE table, or making\n  many changes to a MyISAM or ARCHIVE table with variable-length rows\n  (tables that have VARCHAR, VARBINARY, BLOB, or TEXT columns). Deleted\n  rows are maintained in a linked list and subsequent INSERT operations\n  reuse old row positions. You can use OPTIMIZE TABLE to reclaim the\n  unused space and to defragment the data file. After extensive changes\n  to a table, this statement may also improve performance of statements\n  that use the table, sometimes significantly.\n\nThis statement requires SELECT and INSERT privileges for the table.\n\nOPTIMIZE TABLE is also supported for partitioned tables. For\ninformation about using this statement with partitioned tables and\ntable partitions, see\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-maintenance.html.\n\nIn MySQL 5.7.1, gtid_next must be set to AUTOMATIC before issuing this\nstatement. This restriction does not apply in MySQL 5.7.2 or later.\n(Bug #16062608, Bug #16715809, Bug #69045)\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/optimize-table.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/optimize-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (378,12,'DECODE','Syntax:\nDECODE(crypt_str,pass_str)\n\nDECODE() decrypts the encrypted string crypt_str using pass_str as the\npassword. crypt_str should be a string returned from ENCODE().\n\n*Note*: The ENCODE() and DECODE() functions are deprecated in MySQL\n5.7, will be removed in a future MySQL release, and should no longer be\nused. Consider using AES_ENCRYPT() and AES_DECRYPT() instead.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (379,7,'JSON_ARRAY_INSERT','JSON_ARRAY_INSERT(json_doc, path, val[, path, val] ...)\n\nUpdates a JSON document, inserting into an array within the document\nand returning the modified document. Returns NULL if any argument is\nNULL. An error occurs if the json_doc argument is not a valid JSON\ndocument or any path argument is not a valid path expression or\ncontains a * or ** wildcard or does not end with an array element\nidentifier.\n\nThe path/value pairs are evaluated left to right. The document produced\nby evaluating one pair becomes the new value against which the next\npair is evaluated.\n\nPairs for which the path does not identify any array in the JSON\ndocument are ignored. If a path identifies an array element, the\ncorresponding value is inserted at that element position, shifting any\nfollowing values to the right. If a path identifies an array position\npast the end of an array, the value is inserted at the end of the\narray.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html\n\n','mysql> SET @j = \'["a", {"b": [1, 2]}, [3, 4]]\';\nmysql> SELECT JSON_ARRAY_INSERT(@j, \'$[1]\', \'x\');\n+------------------------------------+\n| JSON_ARRAY_INSERT(@j, \'$[1]\', \'x\') |\n+------------------------------------+\n| ["a", "x", {"b": [1, 2]}, [3, 4]]  |\n+------------------------------------+\nmysql> SELECT JSON_ARRAY_INSERT(@j, \'$[100]\', \'x\');\n+--------------------------------------+\n| JSON_ARRAY_INSERT(@j, \'$[100]\', \'x\') |\n+--------------------------------------+\n| ["a", {"b": [1, 2]}, [3, 4], "x"]    |\n+--------------------------------------+\nmysql> SELECT JSON_ARRAY_INSERT(@j, \'$[1].b[0]\', \'x\');\n+-----------------------------------------+\n| JSON_ARRAY_INSERT(@j, \'$[1].b[0]\', \'x\') |\n+-----------------------------------------+\n| ["a", {"b": ["x", 1, 2]}, [3, 4]]       |\n+-----------------------------------------+\nmysql> SELECT JSON_ARRAY_INSERT(@j, \'$[2][1]\', \'y\');\n+---------------------------------------+\n| JSON_ARRAY_INSERT(@j, \'$[2][1]\', \'y\') |\n+---------------------------------------+\n| ["a", {"b": [1, 2]}, [3, "y", 4]]     |\n+---------------------------------------+\nmysql> SELECT JSON_ARRAY_INSERT(@j, \'$[0]\', \'x\', \'$[2][1]\', \'y\');\n+----------------------------------------------------+\n| JSON_ARRAY_INSERT(@j, \'$[0]\', \'x\', \'$[2][1]\', \'y\') |\n+----------------------------------------------------+\n| ["x", "a", {"b": [1, 2]}, [3, 4]]                  |\n+----------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (380,20,'<=>','Syntax:\n<=>\n\nNULL-safe equal. This operator performs an equality comparison like the\n= operator, but returns 1 rather than NULL if both operands are NULL,\nand 0 rather than NULL if one operand is NULL.\n\nThe <=> operator is equivalent to the standard SQL IS NOT DISTINCT FROM\noperator.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT 1 <=> 1, NULL <=> NULL, 1 <=> NULL;\n        -> 1, 1, 0\nmysql> SELECT 1 = 1, NULL = NULL, 1 = NULL;\n        -> 1, NULL, NULL\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (381,27,'RESET','Syntax:\nRESET reset_option [, reset_option] ...\n\nThe RESET statement is used to clear the state of various server\noperations. You must have the RELOAD privilege to execute RESET.\n\nRESET acts as a stronger version of the FLUSH statement. See [HELP\nFLUSH].\n\nThe RESET statement causes an implicit commit. See\nhttp://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html.\n\nIn MySQL 5.7.1, gtid_next must be set to AUTOMATIC before issuing this\nstatement. This restriction does not apply in MySQL 5.7.2 or later.\n(Bug #16062608, Bug #16715809, Bug #69045)\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/reset.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/reset.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (382,14,'GET_LOCK','Syntax:\nGET_LOCK(str,timeout)\n\nTries to obtain a lock with a name given by the string str, using a\ntimeout of timeout seconds. A negative timeout value means infinite\ntimeout. The lock is exclusive. While held by one session, other\nsessions cannot obtain a lock of the same name.\n\nReturns 1 if the lock was obtained successfully, 0 if the attempt timed\nout (for example, because another client has previously locked the\nname), or NULL if an error occurred (such as running out of memory or\nthe thread was killed with mysqladmin kill).\n\nA lock obtained with GET_LOCK() is released explicitly by executing\nRELEASE_LOCK() or implicitly when your session terminates (either\nnormally or abnormally). Lock release may also occur with another call\nto GET_LOCK():\n\no Before 5.7.5, only a single simultaneous lock can be acquired and\n  GET_LOCK() releases any existing lock.\n\no In MySQL 5.7.5, GET_LOCK() was reimplemented using the metadata\n  locking (MDL) subsystem and its capabilities were extended. Multiple\n  simultaneous locks can be acquired and GET_LOCK() does not release\n  any existing locks. It is even possible for a given session to\n  acquire multiple locks for the same name. Other sessions cannot\n  acquire a lock with that name until the acquiring session releases\n  all its locks for the name.\n\n  As a result of the MDL reimplementation, locks acquired with\n  GET_LOCK() appear in the Performance Schema metadata_locks table. The\n  OBJECT_TYPE column says USER LEVEL LOCK and the OBJECT_NAME column\n  indicates the lock name. Also, the capability of acquiring multiple\n  locks introduces the possibility of deadlock among clients. When this\n  happens, the server chooses a caller and terminates its\n  lock-acquisition request with an ER_USER_LOCK_DEADLOCK error. This\n  error does not cause transactions to roll back.\n\nThe difference in lock acquisition behavior as of MySQL 5.7.5 can be\nseen by the following example. Suppose that you execute these\nstatements:\n\nSELECT GET_LOCK(\'lock1\',10);\nSELECT GET_LOCK(\'lock2\',10);\nSELECT RELEASE_LOCK(\'lock2\');\nSELECT RELEASE_LOCK(\'lock1\');\n\nIn MySQL 5.7.5 or later, the second GET_LOCK() acquires a second lock\nand both RELEASE_LOCK() calls return 1 (success). Before MySQL 5.7.5,\nthe second GET_LOCK() releases the first lock (\'lock1\') and the second\nRELEASE_LOCK() returns NULL (failure) because there is no \'lock1\' to\nrelease.\n\nMySQL 5.7.5 and later enforces a maximum length on lock names of 64\ncharacters. Previously, no limit was enforced.\n\nLocks obtained with GET_LOCK() are not released when transactions\ncommit or roll back.\n\nGET_LOCK() can be used to implement application locks or to simulate\nrecord locks. Names are locked on a server-wide basis. If a name has\nbeen locked within one session, GET_LOCK() blocks any request by\nanother session for a lock with the same name. This enables clients\nthat agree on a given lock name to use the name to perform cooperative\nadvisory locking. But be aware that it also enables a client that is\nnot among the set of cooperating clients to lock a name, either\ninadvertently or deliberately, and thus prevent any of the cooperating\nclients from locking that name. One way to reduce the likelihood of\nthis is to use lock names that are database-specific or\napplication-specific. For example, use lock names of the form\ndb_name.str or app_name.str.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (383,23,'BIGINT','BIGINT[(M)] [UNSIGNED] [ZEROFILL]\n\nA large integer. The signed range is -9223372036854775808 to\n9223372036854775807. The unsigned range is 0 to 18446744073709551615.\n\nSERIAL is an alias for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (384,32,'CURTIME','Syntax:\nCURTIME([fsp])\n\nReturns the current time as a value in \'HH:MM:SS\' or HHMMSS format,\ndepending on whether the function is used in a string or numeric\ncontext. The value is expressed in the current time zone.\n\nIf the fsp argument is given to specify a fractional seconds precision\nfrom 0 to 6, the return value includes a fractional seconds part of\nthat many digits.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT CURTIME();\n        -> \'23:50:26\'\nmysql> SELECT CURTIME() + 0;\n        -> 235026.000000\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (385,37,'ST_DIMENSION','ST_Dimension(g)\n\nReturns the inherent dimension of the geometry value g. The result can\nbe −1, 0, 1, or 2. The meaning of these values is given in\nhttp://dev.mysql.com/doc/refman/5.7/en/gis-class-geometry.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html\n\n','mysql> SELECT ST_Dimension(ST_GeomFromText(\'LineString(1 1,2 2)\'));\n+------------------------------------------------------+\n| ST_Dimension(ST_GeomFromText(\'LineString(1 1,2 2)\')) |\n+------------------------------------------------------+\n|                                                    1 |\n+------------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (386,27,'SET','Syntax:\nSET variable_assignment [, variable_assignment] ...\n\nvariable_assignment:\n      user_var_name = expr\n    | [GLOBAL | SESSION] system_var_name = expr\n    | [@@global. | @@session. | @@]system_var_name = expr\n\nThe SET statement assigns values to different types of variables that\naffect the operation of the server or your client.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/set-statement.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/set-statement.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (387,7,'JSON_MERGE','JSON_MERGE(json_doc, json_doc[, json_doc] ...)\n\nMerges two or more JSON documents and returns the merged result.\nReturns NULL if any argument is NULL. An error occurs if any argument\nis not a valid JSON document.\n\nMerging takes place according to the following rules. For additional\ninformation, see\nhttp://dev.mysql.com/doc/refman/5.7/en/json.html#json-normalization.\n\no Adjacent arrays are merged to a single array.\n\no Adjacent objects are merged to a single object.\n\no A scalar value is autowrapped as an array and merged as an array.\n\no An adjacent array and object are merged by autowrapping the object as\n  an array and merging the two arrays.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-creation-functions.html\n\n','mysql> SELECT JSON_MERGE(\'[1, 2]\', \'[true, false]\');\n+---------------------------------------+\n| JSON_MERGE(\'[1, 2]\', \'[true, false]\') |\n+---------------------------------------+\n| [1, 2, true, false]                   |\n+---------------------------------------+\nmysql> SELECT JSON_MERGE(\'{"name": "x"}\', \'{"id": 47}\');\n+-------------------------------------------+\n| JSON_MERGE(\'{"name": "x"}\', \'{"id": 47}\') |\n+-------------------------------------------+\n| {"id": 47, "name": "x"}                   |\n+-------------------------------------------+\nmysql> SELECT JSON_MERGE(\'1\', \'true\');\n+-------------------------+\n| JSON_MERGE(\'1\', \'true\') |\n+-------------------------+\n| [1, true]               |\n+-------------------------+\nmysql> SELECT JSON_MERGE(\'[1, 2]\', \'{"id": 47}\');\n+------------------------------------+\n| JSON_MERGE(\'[1, 2]\', \'{"id": 47}\') |\n+------------------------------------+\n| [1, 2, {"id": 47}]                 |\n+------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-creation-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (388,3,'CONV','Syntax:\nCONV(N,from_base,to_base)\n\nConverts numbers between different number bases. Returns a string\nrepresentation of the number N, converted from base from_base to base\nto_base. Returns NULL if any argument is NULL. The argument N is\ninterpreted as an integer, but may be specified as an integer or a\nstring. The minimum base is 2 and the maximum base is 36. If to_base is\na negative number, N is regarded as a signed number. Otherwise, N is\ntreated as unsigned. CONV() works with 64-bit precision.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT CONV(\'a\',16,2);\n        -> \'1010\'\nmysql> SELECT CONV(\'6E\',18,8);\n        -> \'172\'\nmysql> SELECT CONV(-17,10,-18);\n        -> \'-H\'\nmysql> SELECT CONV(10+\'10\'+\'10\'+0xa,10,10);\n        -> \'40\'\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (389,4,'ST_MPOINTFROMTEXT','ST_MPointFromText(wkt[,srid]), ST_MultiPointFromText(wkt[,srid])\n\nConstructs a MultiPoint value using its WKT representation and SRID.\n\nAs of MySQL 5.7.9, spatial functions such as ST_MPointFromText() and\nST_GeomFromText() that accept WKT-format representations of MultiPoint\nvalues permit individual points within values to be surrounded by\nparentheses. For example, both of the following function calls are\nvalid, whereas before MySQL 5.7.9 the second one produces an error:\n\nST_MPointFromText(\'MULTIPOINT (1 1, 2 2, 3 3)\')\nST_MPointFromText(\'MULTIPOINT ((1 1), (2 2), (3 3))\')\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (390,28,'LOAD XML','Syntax:\nLOAD XML [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE \'file_name\'\n    [REPLACE | IGNORE]\n    INTO TABLE [db_name.]tbl_name\n    [CHARACTER SET charset_name]\n    [ROWS IDENTIFIED BY \'<tagname>\']\n    [IGNORE number {LINES | ROWS}]\n    [(field_name_or_user_var,...)]\n    [SET col_name = expr,...]\n\nThe LOAD XML statement reads data from an XML file into a table. The\nfile_name must be given as a literal string. The tagname in the\noptional ROWS IDENTIFIED BY clause must also be given as a literal\nstring, and must be surrounded by angle brackets (< and >).\n\nLOAD XML acts as the complement of running the mysql client in XML\noutput mode (that is, starting the client with the --xml option). To\nwrite data from a table to an XML file, you can invoke the mysql client\nwith the --xml and -e options from the system shell, as shown here:\n\nshell> mysql --xml -e \'SELECT * FROM mydb.mytable\' > file.xml\n\nTo read the file back into a table, use LOAD XML INFILE. By default,\nthe <row> element is considered to be the equivalent of a database\ntable row; this can be changed using the ROWS IDENTIFIED BY clause.\n\nThis statement supports three different XML formats:\n\no Column names as attributes and column values as attribute values:\n\n<row column1="value1" column2="value2" .../>\n\no Column names as tags and column values as the content of these tags:\n\n<row>\n  <column1>value1</column1>\n  <column2>value2</column2>\n</row>\n\no Column names are the name attributes of <field> tags, and values are\n  the contents of these tags:\n\n<row>\n  <field name=\'column1\'>value1</field>\n  <field name=\'column2\'>value2</field>\n</row>\n\n  This is the format used by other MySQL tools, such as mysqldump.\n\nAll three formats can be used in the same XML file; the import routine\nautomatically detects the format for each row and interprets it\ncorrectly. Tags are matched based on the tag or attribute name and the\ncolumn name.\n\nPrior to MySQL 5.7.9, LOAD XML did not handle empty XML elements in the\nform <element/> correctly. (Bug #67542, Bug #16171518)\n\nThe following clauses work essentially the same way for LOAD XML as\nthey do for LOAD DATA:\n\no LOW_PRIORITY or CONCURRENT\n\no LOCAL\n\no REPLACE or IGNORE\n\no CHARACTER SET\n\no SET\n\nSee [HELP LOAD DATA], for more information about these clauses.\n\n(field_name_or_user_var, ...) is a comma-separated list of one or more\nXML fields or user variables. The name of a user variable used for this\npurpose must match the name of a field from the XML file, prefixed with\n@. You can use field names to select only desired fields. User\nvariables can be employed to store the corresponding field values for\nsubsequent re-use.\n\nThe IGNORE number LINES or IGNORE number ROWS clause causes the first\nnumber rows in the XML file to be skipped. It is analogous to the LOAD\nDATA statement\'s IGNORE ... LINES clause.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/load-xml.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/load-xml.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (391,15,'ASSIGN-VALUE','Syntax:\n:=\n\nAssignment operator. Causes the user variable on the left hand side of\nthe operator to take on the value to its right. The value on the right\nhand side may be a literal value, another variable storing a value, or\nany legal expression that yields a scalar value, including the result\nof a query (provided that this value is a scalar value). You can\nperform multiple assignments in the same SET statement. You can perform\nmultiple assignments in the same statement-\n\nUnlike =, the := operator is never interpreted as a comparison\noperator. This means you can use := in any valid SQL statement (not\njust in SET statements) to assign a value to a variable.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/assignment-operators.html\n\n','mysql> SELECT @var1, @var2;\n        -> NULL, NULL\nmysql> SELECT @var1 := 1, @var2;\n        -> 1, NULL\nmysql> SELECT @var1, @var2;\n        -> 1, NULL\nmysql> SELECT @var1, @var2 := @var1;\n        -> 1, 1\nmysql> SELECT @var1, @var2;\n        -> 1, 1\n\nmysql> SELECT @var1:=COUNT(*) FROM t1;\n        -> 4\nmysql> SELECT @var1;\n        -> 4\n','http://dev.mysql.com/doc/refman/5.7/en/assignment-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (392,27,'SHOW OPEN TABLES','Syntax:\nSHOW OPEN TABLES [{FROM | IN} db_name]\n    [LIKE \'pattern\' | WHERE expr]\n\nSHOW OPEN TABLES lists the non-TEMPORARY tables that are currently open\nin the table cache. See\nhttp://dev.mysql.com/doc/refman/5.7/en/table-cache.html. The FROM\nclause, if present, restricts the tables shown to those present in the\ndb_name database. The LIKE clause, if present, indicates which table\nnames to match. The WHERE clause can be given to select rows using more\ngeneral conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-open-tables.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-open-tables.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (393,32,'EXTRACT','Syntax:\nEXTRACT(unit FROM date)\n\nThe EXTRACT() function uses the same kinds of unit specifiers as\nDATE_ADD() or DATE_SUB(), but extracts parts from the date rather than\nperforming date arithmetic.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT EXTRACT(YEAR FROM \'2009-07-02\');\n       -> 2009\nmysql> SELECT EXTRACT(YEAR_MONTH FROM \'2009-07-02 01:02:03\');\n       -> 200907\nmysql> SELECT EXTRACT(DAY_MINUTE FROM \'2009-07-02 01:02:03\');\n       -> 20102\nmysql> SELECT EXTRACT(MICROSECOND\n    ->                FROM \'2003-01-02 10:30:00.000123\');\n        -> 123\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (394,12,'ENCRYPT','Syntax:\nENCRYPT(str[,salt])\n\nEncrypts str using the Unix crypt() system call and returns a binary\nstring. The salt argument must be a string with at least two characters\nor the result will be NULL. If no salt argument is given, a random\nvalue is used.\n\n*Note*: The ENCRYPT() function is deprecated as of MySQL 5.7.6, will be\nremoved in a future MySQL release, and should no longer be used.\nConsider using AES_ENCRYPT() instead.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT ENCRYPT(\'hello\');\n        -> \'VxuFAJXVARROc\'\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (395,27,'SHOW STATUS','Syntax:\nSHOW [GLOBAL | SESSION] STATUS\n    [LIKE \'pattern\' | WHERE expr]\n\n*Note*: As of MySQL 5.7.6, the value of the show_compatibility_56\nsystem variable affects the information available from and privileges\nrequired for the statement described here. For details, see the\ndescription of that variable in\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nSHOW STATUS provides server status information (see\nhttp://dev.mysql.com/doc/refman/5.7/en/server-status-variables.html).\nThis statement does not require any privilege. It requires only the\nability to connect to the server.\n\nStatus variable information is also available from these sources:\n\no Performance Schema tables. See\n  http://dev.mysql.com/doc/refman/5.7/en/performance-schema-status-vari\n  able-tables.html.\n\no The GLOBAL_STATUS and SESSION_STATUS tables. See\n  http://dev.mysql.com/doc/refman/5.7/en/status-table.html.\n\no The mysqladmin extended-status command. See\n  http://dev.mysql.com/doc/refman/5.7/en/mysqladmin.html.\n\nFor SHOW STATUS, a LIKE clause, if present, indicates which variable\nnames to match. A WHERE clause can be given to select rows using more\ngeneral conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html.\n\nSHOW STATUS accepts an optional GLOBAL or SESSION variable scope\nmodifier:\n\no With a GLOBAL modifier, the statement displays the global status\n  values. A global status variable may represent status for some aspect\n  of the server itself (for example, Aborted_connects), or the\n  aggregated status over all connections to MySQL (for example,\n  Bytes_received and Bytes_sent). If a variable has no global value,\n  the session value is displayed.\n\no With a SESSION modifier, the statement displays the status variable\n  values for the current connection. If a variable has no session\n  value, the global value is displayed. LOCAL is a synonym for SESSION.\n\no If no modifier is present, the default is SESSION.\n\nThe scope for each status variable is listed at\nhttp://dev.mysql.com/doc/refman/5.7/en/server-status-variables.html.\n\nEach invocation of the SHOW STATUS statement uses an internal temporary\ntable and increments the global Created_tmp_tables value.\nWith a LIKE clause, the statement displays only rows for those\nvariables with names that match the pattern:\n\nmysql> SHOW STATUS LIKE \'Key%\';\n+--------------------+----------+\n| Variable_name      | Value    |\n+--------------------+----------+\n| Key_blocks_used    | 14955    |\n| Key_read_requests  | 96854827 |\n| Key_reads          | 162040   |\n| Key_write_requests | 7589728  |\n| Key_writes         | 3813196  |\n+--------------------+----------+\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-status.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-status.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (396,2,'ST_NUMINTERIORRINGS','ST_NumInteriorRing(poly), ST_NumInteriorRings(poly)\n\nReturns the number of interior rings in the Polygon value poly.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','mysql> SET @poly =\n    -> \'Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))\';\nmysql> SELECT ST_NumInteriorRings(ST_GeomFromText(@poly));\n+---------------------------------------------+\n| ST_NumInteriorRings(ST_GeomFromText(@poly)) |\n+---------------------------------------------+\n|                                           1 |\n+---------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (397,7,'JSON_KEYS','JSON_KEYS(json_doc[, path])\n\nReturns the keys from the top-level value of a JSON object as a JSON\narray, or, if a path argument is given, the top-level keys from the\nselected path. Returns NULL if any argument is NULL, the json_doc\nargument is not an object, or path, if given, does not locate an\nobject. An error occurs if the json_doc argument is not a valid JSON\ndocument or the path argument is not a valid path expression or\ncontains a * or ** wildcard.\n\nThe result array is empty if the selected object is empty. If the\ntop-level value has nested subobjects, the return value does not\ninclude keys from those subobjects.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html\n\n','mysql> SELECT JSON_KEYS(\'{"a": 1, "b": {"c": 30}}\');\n+---------------------------------------+\n| JSON_KEYS(\'{"a": 1, "b": {"c": 30}}\') |\n+---------------------------------------+\n| ["a", "b"]                            |\n+---------------------------------------+\nmysql> SELECT JSON_KEYS(\'{"a": 1, "b": {"c": 30}}\', \'$.b\');\n+----------------------------------------------+\n| JSON_KEYS(\'{"a": 1, "b": {"c": 30}}\', \'$.b\') |\n+----------------------------------------------+\n| ["c"]                                        |\n+----------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (398,14,'INET6_ATON','Syntax:\nINET6_ATON(expr)\n\nGiven an IPv6 or IPv4 network address as a string, returns a binary\nstring that represents the numeric value of the address in network byte\norder (big endian). Because numeric-format IPv6 addresses require more\nbytes than the largest integer type, the representation returned by\nthis function has the VARBINARY data type: VARBINARY(16) for IPv6\naddresses and VARBINARY(4) for IPv4 addresses. If the argument is not a\nvalid address, INET6_ATON() returns NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> SELECT HEX(INET6_ATON(\'fdfe::5a55:caff:fefa:9089\'));\n        -> \'FDFE0000000000005A55CAFFFEFA9089\'\nmysql> SELECT HEX(INET6_ATON(\'10.0.5.9\'));\n        -> \'0A000509\'\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (399,27,'SHOW SLAVE HOSTS','Syntax:\nSHOW SLAVE HOSTS\n\nDisplays a list of replication slaves currently registered with the\nmaster.\n\nSHOW SLAVE HOSTS should be executed on a server that acts as a\nreplication master. The statement displays information about servers\nthat are or have been connected as replication slaves, with each row of\nthe result corresponding to one slave server, as shown here:\n\nmysql> SHOW SLAVE HOSTS;\n+-----------+-----------+-------+-----------+--------------------------------------+\n| Server_id | Host      | Port  | Master_id | Slave_UUID                           |\n+-----------+-----------+-------+-----------+--------------------------------------+\n|  192168010 | iconnect2 | 3306 | 192168011 | 14cb6624-7f93-11e0-b2c0-c80aa9429562 |\n| 1921680101 | athena    | 3306 | 192168011 | 07af4990-f41f-11df-a566-7ac56fdaf645 |\n+------------+-----------+------+-----------+--------------------------------------+\n\no Server_id: The unique server ID of the slave server, as configured in\n  the slave server\'s option file, or on the command line with\n  --server-id=value.\n\no Host: The host name of the slave server as specified on the slave\n  with the --report-host option. This can differ from the machine name\n  as configured in the operating system.\n\no User: The slave server user name as, specified on the slave with the\n  --report-user option. Statement output includes this column only if\n  the master server is started with the --show-slave-auth-info option.\n\no Password: The slave server password as, specified on the slave with\n  the --report-password option. Statement output includes this column\n  only if the master server is started with the --show-slave-auth-info\n  option.\n\no Port: The port on the master to which the slave server is listening,\n  as specified on the slave with the --report-port option.\n\n  A zero in this column means that the slave port (--report-port) was\n  not set.\n\no Master_id: The unique server ID of the master server that the slave\n  server is replicating from. This is the server ID of the server on\n  which SHOW SLAVE HOSTS is executed, so this same value is listed for\n  each row in the result.\n\no Slave_UUID: The globally unique ID of this slave, as generated on the\n  slave and found in the slave\'s auto.cnf file.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-slave-hosts.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-slave-hosts.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (400,8,'START TRANSACTION','Syntax:\nSTART TRANSACTION\n    [transaction_characteristic [, transaction_characteristic] ...]\n\ntransaction_characteristic:\n    WITH CONSISTENT SNAPSHOT\n  | READ WRITE\n  | READ ONLY\n\nBEGIN [WORK]\nCOMMIT [WORK] [AND [NO] CHAIN] [[NO] RELEASE]\nROLLBACK [WORK] [AND [NO] CHAIN] [[NO] RELEASE]\nSET autocommit = {0 | 1}\n\nThese statements provide control over use of transactions:\n\no START TRANSACTION or BEGIN start a new transaction.\n\no COMMIT commits the current transaction, making its changes permanent.\n\no ROLLBACK rolls back the current transaction, canceling its changes.\n\no SET autocommit disables or enables the default autocommit mode for\n  the current session.\n\nBy default, MySQL runs with autocommit mode enabled. This means that as\nsoon as you execute a statement that updates (modifies) a table, MySQL\nstores the update on disk to make it permanent. The change cannot be\nrolled back.\n\nTo disable autocommit mode implicitly for a single series of\nstatements, use the START TRANSACTION statement:\n\nSTART TRANSACTION;\nSELECT @A:=SUM(salary) FROM table1 WHERE type=1;\nUPDATE table2 SET summary=@A WHERE type=1;\nCOMMIT;\n\nWith START TRANSACTION, autocommit remains disabled until you end the\ntransaction with COMMIT or ROLLBACK. The autocommit mode then reverts\nto its previous state.\n\nSTART TRANSACTION permits several modifiers that control transaction\ncharacteristics. To specify multiple modifiers, separate them by\ncommas.\n\no The WITH CONSISTENT SNAPSHOT modifier starts a consistent read for\n  storage engines that are capable of it. This applies only to InnoDB.\n  The effect is the same as issuing a START TRANSACTION followed by a\n  SELECT from any InnoDB table. See\n  http://dev.mysql.com/doc/refman/5.7/en/innodb-consistent-read.html.\n  The WITH CONSISTENT SNAPSHOT modifier does not change the current\n  transaction isolation level, so it provides a consistent snapshot\n  only if the current isolation level is one that permits a consistent\n  read. The only isolation level that permits a consistent read is\n  REPEATABLE READ. For all other isolation levels, the WITH CONSISTENT\n  SNAPSHOT clause is ignored. As of MySQL 5.7.2, a warning is generated\n  when the WITH CONSISTENT SNAPSHOT clause is ignored.\n\no The READ WRITE and READ ONLY modifiers set the transaction access\n  mode. They permit or prohibit changes to tables used in the\n  transaction. The READ ONLY restriction prevents the transaction from\n  modifying or locking both transactional and nontransactional tables\n  that are visible to other transactions; the transaction can still\n  modify or lock temporary tables.\n\n  MySQL enables extra optimizations for queries on InnoDB tables when\n  the transaction is known to be read-only. Specifying READ ONLY\n  ensures these optimizations are applied in cases where the read-only\n  status cannot be determined automatically. See\n  http://dev.mysql.com/doc/refman/5.7/en/innodb-performance-ro-txn.html\n  for more information.\n\n  If no access mode is specified, the default mode applies. Unless the\n  default has been changed, it is read/write. It is not permitted to\n  specify both READ WRITE and READ ONLY in the same statement.\n\n  In read-only mode, it remains possible to change tables created with\n  the TEMPORARY keyword using DML statements. Changes made with DDL\n  statements are not permitted, just as with permanent tables.\n\n  For additional information about transaction access mode, including\n  ways to change the default mode, see [HELP ISOLATION].\n\n  If the read_only system variable is enabled, explicitly starting a\n  transaction with START TRANSACTION READ WRITE requires the SUPER\n  privilege.\n\n*Important*: Many APIs used for writing MySQL client applications (such\nas JDBC) provide their own methods for starting transactions that can\n(and sometimes should) be used instead of sending a START TRANSACTION\nstatement from the client. See\nhttp://dev.mysql.com/doc/refman/5.7/en/connectors-apis.html, or the\ndocumentation for your API, for more information.\n\nTo disable autocommit mode explicitly, use the following statement:\n\nSET autocommit=0;\n\nAfter disabling autocommit mode by setting the autocommit variable to\nzero, changes to transaction-safe tables (such as those for InnoDB or\nNDB (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster.html)) are\nnot made permanent immediately. You must use COMMIT to store your\nchanges to disk or ROLLBACK to ignore the changes.\n\nautocommit is a session variable and must be set for each session. To\ndisable autocommit mode for each new connection, see the description of\nthe autocommit system variable at\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nBEGIN and BEGIN WORK are supported as aliases of START TRANSACTION for\ninitiating a transaction. START TRANSACTION is standard SQL syntax, is\nthe recommended way to start an ad-hoc transaction, and permits\nmodifiers that BEGIN does not.\n\nThe BEGIN statement differs from the use of the BEGIN keyword that\nstarts a BEGIN ... END compound statement. The latter does not begin a\ntransaction. See [HELP BEGIN END].\n\n*Note*: Within all stored programs (stored procedures and functions,\ntriggers, and events), the parser treats BEGIN [WORK] as the beginning\nof a BEGIN ... END block. Begin a transaction in this context with\nSTART TRANSACTION instead.\n\nThe optional WORK keyword is supported for COMMIT and ROLLBACK, as are\nthe CHAIN and RELEASE clauses. CHAIN and RELEASE can be used for\nadditional control over transaction completion. The value of the\ncompletion_type system variable determines the default completion\nbehavior. See\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nThe AND CHAIN clause causes a new transaction to begin as soon as the\ncurrent one ends, and the new transaction has the same isolation level\nas the just-terminated transaction. The RELEASE clause causes the\nserver to disconnect the current client session after terminating the\ncurrent transaction. Including the NO keyword suppresses CHAIN or\nRELEASE completion, which can be useful if the completion_type system\nvariable is set to cause chaining or release completion by default.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/commit.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/commit.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (401,32,'TIME_FORMAT','Syntax:\nTIME_FORMAT(time,format)\n\nThis is used like the DATE_FORMAT() function, but the format string may\ncontain format specifiers only for hours, minutes, seconds, and\nmicroseconds. Other specifiers produce a NULL value or 0.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT TIME_FORMAT(\'100:00:00\', \'%H %k %h %I %l\');\n        -> \'100 100 04 04 4\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (402,40,'CREATE DATABASE','Syntax:\nCREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name\n    [create_specification] ...\n\ncreate_specification:\n    [DEFAULT] CHARACTER SET [=] charset_name\n  | [DEFAULT] COLLATE [=] collation_name\n\nCREATE DATABASE creates a database with the given name. To use this\nstatement, you need the CREATE privilege for the database. CREATE\nSCHEMA is a synonym for CREATE DATABASE.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/create-database.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/create-database.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (403,16,'VAR_POP','Syntax:\nVAR_POP(expr)\n\nReturns the population standard variance of expr. It considers rows as\nthe whole population, not as a sample, so it has the number of rows as\nthe denominator. You can also use VARIANCE(), which is equivalent but\nis not standard SQL.\n\nVAR_POP() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (404,38,'CONCAT_WS','Syntax:\nCONCAT_WS(separator,str1,str2,...)\n\nCONCAT_WS() stands for Concatenate With Separator and is a special form\nof CONCAT(). The first argument is the separator for the rest of the\narguments. The separator is added between the strings to be\nconcatenated. The separator can be a string, as can the rest of the\narguments. If the separator is NULL, the result is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT CONCAT_WS(\',\',\'First name\',\'Second name\',\'Last Name\');\n        -> \'First name,Second name,Last Name\'\nmysql> SELECT CONCAT_WS(\',\',\'First name\',NULL,\'Last Name\');\n        -> \'First name,Last Name\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (405,23,'TEXT','TEXT[(M)] [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 65,535 (216 − 1) characters.\nThe effective maximum length is less if the value contains multibyte\ncharacters. Each TEXT value is stored using a 2-byte length prefix that\nindicates the number of bytes in the value.\n\nAn optional length M can be given for this type. If this is done, MySQL\ncreates the column as the smallest TEXT type large enough to hold\nvalues M characters long.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (406,19,'~','Syntax:\n~\n\nInvert all bits.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/bit-functions.html\n\n','mysql> SELECT 5 & ~1;\n        -> 4\n','http://dev.mysql.com/doc/refman/5.7/en/bit-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (407,3,'ASIN','Syntax:\nASIN(X)\n\nReturns the arc sine of X, that is, the value whose sine is X. Returns\nNULL if X is not in the range -1 to 1.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT ASIN(0.2);\n        -> 0.20135792079033\nmysql> SELECT ASIN(\'foo\');\n\n+-------------+\n| ASIN(\'foo\') |\n+-------------+\n|           0 |\n+-------------+\n1 row in set, 1 warning (0.00 sec)\n\nmysql> SHOW WARNINGS;\n+---------+------+-----------------------------------------+\n| Level   | Code | Message                                 |\n+---------+------+-----------------------------------------+\n| Warning | 1292 | Truncated incorrect DOUBLE value: \'foo\' |\n+---------+------+-----------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (408,17,'ROW_COUNT','Syntax:\nROW_COUNT()\n\nIn MySQL 5.7, ROW_COUNT() returns a value as follows:\n\no DDL statements: 0. This applies to statements such as CREATE TABLE or\n  DROP TABLE.\n\no DML statements other than SELECT: The number of affected rows. This\n  applies to statements such as UPDATE, INSERT, or DELETE (as before),\n  but now also to statements such as ALTER TABLE and LOAD DATA INFILE.\n\no SELECT: -1 if the statement returns a result set, or the number of\n  rows "affected" if it does not. For example, for SELECT * FROM t1,\n  ROW_COUNT() returns -1. For SELECT * FROM t1 INTO OUTFILE\n  \'file_name\', ROW_COUNT() returns the number of rows written to the\n  file.\n\no SIGNAL statements: 0.\n\nFor UPDATE statements, the affected-rows value by default is the number\nof rows actually changed. If you specify the CLIENT_FOUND_ROWS flag to\nmysql_real_connect() when connecting to mysqld, the affected-rows value\nis the number of rows "found"; that is, matched by the WHERE clause.\n\nFor REPLACE statements, the affected-rows value is 2 if the new row\nreplaced an old row, because in this case, one row was inserted after\nthe duplicate was deleted.\n\nFor INSERT ... ON DUPLICATE KEY UPDATE statements, the affected-rows\nvalue per row is 1 if the row is inserted as a new row, 2 if an\nexisting row is updated, and 0 if an existing row is set to its current\nvalues. If you specify the CLIENT_FOUND_ROWS flag, the affected-rows\nvalue is 1 (not 0) if an existing row is set to its current values.\n\nThe ROW_COUNT() value is similar to the value from the\nmysql_affected_rows() C API function and the row count that the mysql\nclient displays following statement execution.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','mysql> INSERT INTO t VALUES(1),(2),(3);\nQuery OK, 3 rows affected (0.00 sec)\nRecords: 3  Duplicates: 0  Warnings: 0\n\nmysql> SELECT ROW_COUNT();\n+-------------+\n| ROW_COUNT() |\n+-------------+\n|           3 |\n+-------------+\n1 row in set (0.00 sec)\n\nmysql> DELETE FROM t WHERE i IN(1,2);\nQuery OK, 2 rows affected (0.00 sec)\n\nmysql> SELECT ROW_COUNT();\n+-------------+\n| ROW_COUNT() |\n+-------------+\n|           2 |\n+-------------+\n1 row in set (0.00 sec)\n','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (409,7,'MBRCOVEREDBY','MBRCoveredBy(g1,g2)\n\nReturns 1 or 0 to indicate whether the minimum bounding rectangle of g1\nis covered by the minimum bounding rectangle of g2. This tests the\nopposite relationship as MBRCovers().\n\nMBRCoveredBy() and MBRCovers() handle their arguments and return a\nvalue as follows:\n\no Return NULL if either argument is NULL or an empty geometry\n\no Return ER_GIS_INVALID_DATA if either argument is not a valid geometry\n  byte string (SRID plus WKB value)\n\no Otherwise, return non-NULL\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html\n\n','mysql> SET @g1 = ST_GeomFromText(\'Polygon((0 0,0 3,3 3,3 0,0 0))\');\nmysql> SET @g2 = ST_GeomFromText(\'Point(1 1)\');\nmysql> SELECT MBRCovers(@g1,@g2), MBRCoveredby(@g1,@g2);\n+--------------------+-----------------------+\n| MBRCovers(@g1,@g2) | MBRCoveredby(@g1,@g2) |\n+--------------------+-----------------------+\n|                  1 |                     0 |\n+--------------------+-----------------------+\nmysql> SELECT MBRCovers(@g2,@g1), MBRCoveredby(@g2,@g1);\n+--------------------+-----------------------+\n| MBRCovers(@g2,@g1) | MBRCoveredby(@g2,@g1) |\n+--------------------+-----------------------+\n|                  0 |                     1 |\n+--------------------+-----------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (410,3,'SIGN','Syntax:\nSIGN(X)\n\nReturns the sign of the argument as -1, 0, or 1, depending on whether X\nis negative, zero, or positive.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT SIGN(-32);\n        -> -1\nmysql> SELECT SIGN(0);\n        -> 0\nmysql> SELECT SIGN(234);\n        -> 1\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (411,23,'FLOAT','FLOAT[(M,D)] [UNSIGNED] [ZEROFILL]\n\nA small (single-precision) floating-point number. Permissible values\nare -3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to\n3.402823466E+38. These are the theoretical limits, based on the IEEE\nstandard. The actual range might be slightly smaller depending on your\nhardware or operating system.\n\nM is the total number of digits and D is the number of digits following\nthe decimal point. If M and D are omitted, values are stored to the\nlimits permitted by the hardware. A single-precision floating-point\nnumber is accurate to approximately 7 decimal places.\n\nUNSIGNED, if specified, disallows negative values.\n\nUsing FLOAT might give you some unexpected problems because all\ncalculations in MySQL are done with double precision. See\nhttp://dev.mysql.com/doc/refman/5.7/en/no-matching-rows.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (412,17,'CHARSET','Syntax:\nCHARSET(str)\n\nReturns the character set of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','mysql> SELECT CHARSET(\'abc\');\n        -> \'latin1\'\nmysql> SELECT CHARSET(CONVERT(\'abc\' USING utf8));\n        -> \'utf8\'\nmysql> SELECT CHARSET(USER());\n        -> \'utf8\'\n','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (413,32,'SUBDATE','Syntax:\nSUBDATE(date,INTERVAL expr unit), SUBDATE(expr,days)\n\nWhen invoked with the INTERVAL form of the second argument, SUBDATE()\nis a synonym for DATE_SUB(). For information on the INTERVAL unit\nargument, see the discussion for DATE_ADD().\n\nmysql> SELECT DATE_SUB(\'2008-01-02\', INTERVAL 31 DAY);\n        -> \'2007-12-02\'\nmysql> SELECT SUBDATE(\'2008-01-02\', INTERVAL 31 DAY);\n        -> \'2007-12-02\'\n\nThe second form enables the use of an integer value for days. In such\ncases, it is interpreted as the number of days to be subtracted from\nthe date or datetime expression expr.\n\nmysql> SELECT SUBDATE(\'2008-01-02 12:00:00\', 31);\n        -> \'2007-12-02 12:00:00\'\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (414,7,'JSON_CONTAINS','JSON_CONTAINS(json_doc, val[, path])\n\nReturns 0 or 1 to indicate whether a specific value is contained\nanywhere in a target JSON document, or, if a path argument is given, at\na specific path within the target document. Returns NULL if any\nargument is NULL or the path argument does not identify a section of\nthe target document. An error occurs if either document argument is not\na valid JSON document or the path argument is not a valid path\nexpression or contains a * or ** wildcard.\n\nTo check only whether any data exists at the path, use\nJSON_CONTAINS_PATH() instead.\n\nThe following rules define containment:\n\no A candidate scalar is contained in a target scalar if and only if\n  they are comparable and are equal. Two scalar values are comparable\n  if they have the same JSON_TYPE() types, with the exception that\n  values of types INTEGER and DECIMAL are also comparable to each\n  other.\n\no A candidate array is contained in a target array if and only if every\n  element in the candidate is contained in some element of the target.\n\no A candidate nonarray is contained in a target array if and only if\n  the candidate is contained in some element of the target.\n\no A candidate object is contained in a target object if and only if for\n  each key in the candidate there is a key with the same name in the\n  target and the value associated with the candidate key is contained\n  in the value associated with the target key.\n\nOtherwise, the candidate value is not contained in the target document.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html\n\n','mysql> SET @j = \'{"a": 1, "b": 2, "c": {"d": 4}}\';\nmysql> SET @j2 = \'1\';\nmysql> SELECT JSON_CONTAINS(@j, @j2, \'$.a\');\n+-------------------------------+\n| JSON_CONTAINS(@j, @j2, \'$.a\') |\n+-------------------------------+\n|                             1 |\n+-------------------------------+\nmysql> SELECT JSON_CONTAINS(@j, @j2, \'$.b\');\n+-------------------------------+\n| JSON_CONTAINS(@j, @j2, \'$.b\') |\n+-------------------------------+\n|                             0 |\n+-------------------------------+\n\nmysql> SET @j2 = \'{"d": 4}\';\nmysql> SELECT JSON_CONTAINS(@j, @j2, \'$.a\');\n+-------------------------------+\n| JSON_CONTAINS(@j, @j2, \'$.a\') |\n+-------------------------------+\n|                             0 |\n+-------------------------------+\nmysql> SELECT JSON_CONTAINS(@j, @j2, \'$.c\');\n+-------------------------------+\n| JSON_CONTAINS(@j, @j2, \'$.c\') |\n+-------------------------------+\n|                             1 |\n+-------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (415,32,'DAYOFYEAR','Syntax:\nDAYOFYEAR(date)\n\nReturns the day of the year for date, in the range 1 to 366.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DAYOFYEAR(\'2007-02-03\');\n        -> 34\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (416,3,'%','Syntax:\nN % M, N MOD M\n\nModulo operation. Returns the remainder of N divided by M. For more\ninformation, see the description for the MOD() function in\nhttp://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (417,33,'ASTEXT','AsText(g), AsWKT(g)\n\nST_AsText(), ST_AsWKT(), AsText(), and AsWKT() are synonyms. For more\ninformation, see the description of ST_AsText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-format-conversion-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-format-conversion-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (418,24,'DECLARE CONDITION','Syntax:\nDECLARE condition_name CONDITION FOR condition_value\n\ncondition_value:\n    mysql_error_code\n  | SQLSTATE [VALUE] sqlstate_value\n\nThe DECLARE ... CONDITION statement declares a named error condition,\nassociating a name with a condition that needs specific handling. The\nname can be referred to in a subsequent DECLARE ... HANDLER statement\n(see [HELP DECLARE HANDLER]).\n\nCondition declarations must appear before cursor or handler\ndeclarations.\n\nThe condition_value for DECLARE ... CONDITION can be a MySQL error code\n(a number) or an SQLSTATE value (a 5-character string literal). You\nshould not use MySQL error code 0 or SQLSTATE values that begin with\n\'00\', because those indicate success rather than an error condition.\nFor a list of MySQL error codes and SQLSTATE values, see\nhttp://dev.mysql.com/doc/refman/5.7/en/error-messages-server.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/declare-condition.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/declare-condition.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (419,32,'MONTHNAME','Syntax:\nMONTHNAME(date)\n\nReturns the full name of the month for date. The language used for the\nname is controlled by the value of the lc_time_names system variable\n(http://dev.mysql.com/doc/refman/5.7/en/locale-support.html).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT MONTHNAME(\'2008-02-03\');\n        -> \'February\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (420,26,'NUMGEOMETRIES','NumGeometries(gc)\n\nST_NumGeometries() and NumGeometries() are synonyms. For more\ninformation, see the description of ST_NumGeometries().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-geometrycollection-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-geometrycollection-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (421,8,'CHANGE MASTER TO','Syntax:\nCHANGE MASTER TO option [, option] ... [ channel_option ] \n\noption:\n    MASTER_BIND = \'interface_name\'\n  | MASTER_HOST = \'host_name\'\n  | MASTER_USER = \'user_name\'\n  | MASTER_PASSWORD = \'password\'\n  | MASTER_PORT = port_num\n  | MASTER_CONNECT_RETRY = interval\n  | MASTER_RETRY_COUNT = count\n  | MASTER_DELAY = interval\n  | MASTER_HEARTBEAT_PERIOD = interval\n  | MASTER_LOG_FILE = \'master_log_name\'\n  | MASTER_LOG_POS = master_log_pos\n  | MASTER_AUTO_POSITION = {0|1}\n  | RELAY_LOG_FILE = \'relay_log_name\'\n  | RELAY_LOG_POS = relay_log_pos\n  | MASTER_SSL = {0|1}\n  | MASTER_SSL_CA = \'ca_file_name\'\n  | MASTER_SSL_CAPATH = \'ca_directory_name\'\n  | MASTER_SSL_CERT = \'cert_file_name\'\n  | MASTER_SSL_CRL = \'crl_file_name\'\n  | MASTER_SSL_CRLPATH = \'crl_directory_name\'\n  | MASTER_SSL_KEY = \'key_file_name\'\n  | MASTER_SSL_CIPHER = \'cipher_list\'\n  | MASTER_SSL_VERIFY_SERVER_CERT = {0|1}\n  | IGNORE_SERVER_IDS = (server_id_list)\n\nchannel_option: \n    FOR CHANNEL channel\n\nserver_id_list:\n    [server_id [, server_id] ... ]\n\nCHANGE MASTER TO changes the parameters that the slave server uses for\nconnecting to the master server, for reading the master binary log, and\nreading the slave relay log. It also updates the contents of the master\ninfo and relay log info repositories (see\nhttp://dev.mysql.com/doc/refman/5.7/en/slave-logs.html).\n\nPrior to MySQL 5.7.4, the slave replication threads must be stopped,\nusing STOP SLAVE if necessary, before issuing this statement. In MySQL\n5.7.4 and later, you can issue CHANGE MASTER TO statements on a running\nslave without doing this, depending on the states of the slave SQL\nthread and slave I/O thread. The rules governing such use are provided\nlater in this section.\n\nWhen using a multi-threaded slave (in other words\nslave_parallel_workers is greater than 0), stopping the slave can cause\n"gaps" in the sequence of transactions that have been executed from the\nrelay log, regardless of whether the slave was stopped intentionally or\notherwise. When such gaps exist, issuing CHANGE MASTER TO fails. The\nsolution in this situation is to issue START SLAVE UNTIL\nSQL_AFTER_MTS_GAPS which ensures that the gaps are closed.\n\nThe optional FOR CHANNEL channel clause added in MySQL 5.7.6 enables\nyou to choose which replication channel the statement applies to. If no\nclause is set and no extra channels exist, the statement applies to the\ndefault channel and behaves the same as versions of MySQL prior to\n5.7.6. Providing a FOR CHANNEL channel clause applies the CHANGE MASTER\nTO statement to a specific replication channel, and is used to add a\nnew channel or modify an existing channel. For example, to add a new\nchannel called channel2:\n\nCHANGE MASTER TO MASTER_NAME=host1, MASTER_PORT=3002 FOR CHANNEL channel2\n\nWhen using multiple replication channels, if a CHANGE MASTER TO\nstatement does not have a channel defined using a FOR CHANNEL channel\nclause an error is generated. See\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-channels.html for\nmore information.\n\nOptions not specified retain their value, except as indicated in the\nfollowing discussion. Thus, in most cases, there is no need to specify\noptions that do not change. For example, in MySQL 5.7.3 and earlier, if\nthe password to connect to your MySQL master has changed, you just need\nto issue these statements to tell the slave about the new password:\n\nSTOP SLAVE; -- if replication was running\nCHANGE MASTER TO MASTER_PASSWORD=\'new3cret\';\nSTART SLAVE; -- if you want to restart replication\n\nIn MySQL 5.7.4 and later, the STOP SLAVE and START SLAVE statements are\nnot needed with the CHANGE MASTER TO statement just shown if the I/O\nthread is stopped, as discussed later in this section.\n\nMASTER_HOST, MASTER_USER, MASTER_PASSWORD, and MASTER_PORT provide\ninformation to the slave about how to connect to its master:\n\no MASTER_HOST and MASTER_PORT are the host name (or IP address) of the\n  master host and its TCP/IP port.\n\n  *Note*: Replication cannot use Unix socket files. You must be able to\n  connect to the master MySQL server using TCP/IP.\n\n  If you specify the MASTER_HOST or MASTER_PORT option, the slave\n  assumes that the master server is different from before (even if the\n  option value is the same as its current value.) In this case, the old\n  values for the master binary log file name and position are\n  considered no longer applicable, so if you do not specify\n  MASTER_LOG_FILE and MASTER_LOG_POS in the statement,\n  MASTER_LOG_FILE=\'\' and MASTER_LOG_POS=4 are silently appended to it.\n\n  Setting MASTER_HOST=\'\' (that is, setting its value explicitly to an\n  empty string) is not the same as not setting MASTER_HOST at all.\n  Beginning with MySQL 5.5, trying to set MASTER_HOST to an empty\n  string fails with an error. Previously, setting MASTER_HOST to an\n  empty string caused START SLAVE subsequently to fail. (Bug #28796)\n\n  Values used for MASTER_HOST and other CHANGE MASTER TO options are\n  checked for linefeed (\\n or 0x0A) characters; the presence of such\n  characters in these values causes the statement to fail with\n  ER_MASTER_INFO. (Bug #11758581, Bug #50801)\n\no MASTER_USER and MASTER_PASSWORD are the user name and password of the\n  account to use for connecting to the master.\n\n  MASTER_USER cannot be made empty; setting MASTER_USER = \'\' or leaving\n  it unset when setting a value for MASTER_PASSWORD causes an error\n  (Bug #13427949).\n\n  The password used for a MySQL Replication slave account in a CHANGE\n  MASTER TO statement is limited to 32 characters in length; prior to\n  MySQL 5.7.5, if the password was longer, the statement succeeded, but\n  any excess characters were silently truncated. In MySQL 5.7.5 and\n  later, trying to use a password of more than 32 characters causes\n  CHANGE MASTER TO to fail. (Bug #11752299, Bug #43439)\n\n  The text of a running CHANGE MASTER TO statement, including values\n  for MASTER_USER and MASTER_PASSWORD, can be seen in the output of a\n  concurrent SHOW PROCESSLIST statement. (The complete text of a START\n  SLAVE statement is also visible to SHOW PROCESSLIST.)\n\nThe MASTER_SSL_xxx options provide information about using SSL for the\nconnection. They correspond to the --ssl-xxx options described in\nhttp://dev.mysql.com/doc/refman/5.7/en/ssl-options.html, and\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-solutions-ssl.html.\nThese options can be changed even on slaves that are compiled without\nSSL support. They are saved to the master info repository, but are\nignored if the slave does not have SSL support enabled.\n\nAs of MySQL 5.7.3, the MASTER_SSL=1 is prescriptive, not advisory. When\ngiven, the slave connection to the master must use SSL or the\nconnection attempt fails. Before 5.7.3, an SSL connection is permitted\nbut not required. This is analogous to the client-side meaning of the\n--ssl command-line option; see\nhttp://dev.mysql.com/doc/refman/5.7/en/ssl-options.html.\n\nMASTER_CONNECT_RETRY specifies how many seconds to wait between connect\nretries. The default is 60.\n\nMASTER_RETRY_COUNT limits the number of reconnection attempts and\nupdates the value of the Master_Retry_Count column in the output of\nSHOW SLAVE STATUS. The default value is 24 * 3600 = 86400.\nMASTER_RETRY_COUNT is intended to replace the older\n--master-retry-count server option, and is now the preferred method for\nsetting this limit. You are encouraged not to rely on\n--master-retry-count in new applications and, when upgrading to MySQL\n5.7, to update any existing applications that rely on it, so that they\nuse CHANGE MASTER TO ... MASTER_RETRY_COUNT instead.\n\nMASTER_DELAY specifies how many seconds behind the master the slave\nmust lag. An event received from the master is not executed until at\nleast interval seconds later than its execution on the master. The\ndefault is 0. An error occurs if interval is not a nonnegative integer\nin the range from 0 to 231−1. For more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html.\n\nIn MySQL 5.7.4 and later, a CHANGE MASTER TO statement employing the\nMASTER_DELAY option can be executed on a running slave when the slave\nSQL thread is stopped.\n\nMASTER_BIND is for use on replication slaves having multiple network\ninterfaces, and determines which of the slave\'s network interfaces is\nchosen for connecting to the master.\n\nThe address configured with this option, if any, can be seen in the\nMaster_Bind column of the output from SHOW SLAVE STATUS. If you are\nusing slave status log tables (server started with\n--master-info-repository=TABLE), the value can also be seen as the\nMaster_bind column of the mysql.slave_master_info table.\n\nMASTER_HEARTBEAT_PERIOD sets the interval in seconds between\nreplication heartbeats. Whenever the master\'s binary log is updated\nwith an event, the waiting period for the next heartbeat is reset.\ninterval is a decimal value having the range 0 to 4294967 seconds and a\nresolution in milliseconds; the smallest nonzero value is 0.001.\nHeartbeats are sent by the master only if there are no unsent events in\nthe binary log file for a period longer than interval.\n\nPrior to MySQL 5.7.4, not including MASTER_HEARTBEAT_PERIOD caused\nCHANGE MASTER TO to reset the heartbeat period (Slave_heartbeat_period)\nto the default, and Slave_received_heartbeats to 0. (Bug #18185490)\n\nIf you are logging master connection information to tables,\nMASTER_HEARTBEAT_PERIOD can be seen as the value of the Heartbeat\ncolumn of the mysql.slave_master_info table.\n\nSetting interval to 0 disables heartbeats altogether. The default value\nfor interval is equal to the value of slave_net_timeout divided by 2.\n\nSetting @@global.slave_net_timeout to a value less than that of the\ncurrent heartbeat interval results in a warning being issued. The\neffect of issuing RESET SLAVE on the heartbeat interval is to reset it\nto the default value.\n\nMASTER_LOG_FILE and MASTER_LOG_POS are the coordinates at which the\nslave I/O thread should begin reading from the master the next time the\nthread starts. RELAY_LOG_FILE and RELAY_LOG_POS are the coordinates at\nwhich the slave SQL thread should begin reading from the relay log the\nnext time the thread starts. If you specify either of MASTER_LOG_FILE\nor MASTER_LOG_POS, you cannot specify RELAY_LOG_FILE or RELAY_LOG_POS.\nIf you specify either of MASTER_LOG_FILE or MASTER_LOG_POS, you also\ncannot specify MASTER_AUTO_POSITION = 1 (described later in this\nsection). If neither of MASTER_LOG_FILE or MASTER_LOG_POS is specified,\nthe slave uses the last coordinates of the slave SQL thread before\nCHANGE MASTER TO was issued. This ensures that there is no\ndiscontinuity in replication, even if the slave SQL thread was late\ncompared to the slave I/O thread, when you merely want to change, say,\nthe password to use.\n\nIn MySQL 5.7.4 and later, a CHANGE MASTER TO statement employing\nRELAY_LOG_FILE, RELAY_LOG_POS, or both options can be executed on a\nrunning slave when the slave SQL thread is stopped.\n\nIf MASTER_AUTO_POSITION = 1 is used with CHANGE MASTER TO, the slave\nattempts to connect to the master using the GTID-based replication\nprotocol. In MySQL 5.7.4 and later, this option can be employed by\nCHANGE MASTER TO only if both the slave SQL and slave I/O threads are\nstopped.\n\nWhen using GTIDs, the slave tells the master which transactions it has\nalready received, executed, or both. To compute this set, it reads the\nglobal value of gtid_executed and the value of the Retrieved_gtid_set\ncolumn from SHOW SLAVE STATUS. Since the GTID of the last transmitted\ntransaction is included in Retrieved_gtid_set even if the transaction\nwas only partially transmitted, the last received GTID is subtracted\nfrom this set. Thus, the slave computes the following set:\n\nUNION(@@global.gtid_executed, Retrieved_gtid_set - last_received_GTID)\n\nThis set is sent to the master as part of the initial handshake, and\nthe master sends back all transactions that it has executed which are\nnot part of the set. If any of these transactions have been already\npurged from the master\'s binary log, the master sends the error\nER_MASTER_HAS_PURGED_REQUIRED_GTIDS to the slave, and replication does\nnot start.\n\nWhen GTID-based replication is employed, the coordinates represented by\nMASTER_LOG_FILE and MASTER_LOG_POS are not used, and global transaction\nidentifiers are used instead. Thus the use of either or both of these\noptions together with MASTER_AUTO_POSITION causes an error.\n\nBeginning with MySQL 5.7.1, you can see whether replication is running\nwith autopositioning enabled by checking the output of SHOW SLAVE\nSTATUS. (Bug #15992220)\n\ngtid_mode must also be enabled before issuing CHANGE MASTER TO ...\nMASTER_AUTO_POSITION = 1. Otherwise, the statement fails with an error.\n\nTo revert to the older file-based replication protocol after using\nGTIDs, you can issue a new CHANGE MASTER TO statement that specifies\nMASTER_AUTO_POSITION = 0, as well as at least one of MASTER_LOG_FILE or\nMASTER_LOG_POSITION.\n\nPrior to MySQL 5.7.4, CHANGE MASTER TO deletes all relay log files and\nstarts a new one, unless you specify RELAY_LOG_FILE or RELAY_LOG_POS.\nIn that case, relay log files are kept; the relay_log_purge global\nvariable is set silently to 0. In MySQL 5.7.4 and later, relay logs are\npreserved when neither the slave SQL thread nor the slave I/O thread is\nstopped; if both threads are stopped, all relay log files are deleted\nunless you at least one of RELAY_LOG_FILE or RELAY_LOG_POS is\nspecified.\n\nRELAY_LOG_FILE can use either an absolute or relative path, and uses\nthe same base name as MASTER_LOG_FILE. (Bug #12190)\n\nIGNORE_SERVER_IDS takes a comma-separated list of 0 or more server IDs.\nEvents originating from the corresponding servers are ignored, with the\nexception of log rotation and deletion events, which are still recorded\nin the relay log.\n\nIn circular replication, the originating server normally acts as the\nterminator of its own events, so that they are not applied more than\nonce. Thus, this option is useful in circular replication when one of\nthe servers in the circle is removed. Suppose that you have a circular\nreplication setup with 4 servers, having server IDs 1, 2, 3, and 4, and\nserver 3 fails. When bridging the gap by starting replication from\nserver 2 to server 4, you can include IGNORE_SERVER_IDS = (3) in the\nCHANGE MASTER TO statement that you issue on server 4 to tell it to use\nserver 2 as its master instead of server 3. Doing so causes it to\nignore and not to propagate any statements that originated with the\nserver that is no longer in use.\n\nIf a CHANGE MASTER TO statement is issued without any IGNORE_SERVER_IDS\noption, any existing list is preserved. To clear the list of ignored\nservers, it is necessary to use the option with an empty list:\n\nCHANGE MASTER TO IGNORE_SERVER_IDS = ();\n\nPrior to MySQL 5.7.5, RESET SLAVE ALL has no effect on the server ID\nlist. In MySQL 5.7.5 and later, RESET SLAVE ALL clears\nIGNORE_SERVER_IDS. (Bug #18816897)\n\nIf IGNORE_SERVER_IDS contains the server\'s own ID and the server was\nstarted with the --replicate-same-server-id option enabled, an error\nresults.\n\nIn MySQL 5.7, the master info repository and the output of SHOW SLAVE\nSTATUS provide the list of servers that are currently ignored. For more\ninformation, see\nhttp://dev.mysql.com/doc/refman/5.7/en/slave-logs-status.html, and\n[HELP SHOW SLAVE STATUS].\n\nIn MySQL 5.7, invoking CHANGE MASTER TO causes the previous values for\nMASTER_HOST, MASTER_PORT, MASTER_LOG_FILE, and MASTER_LOG_POS to be\nwritten to the error log, along with other information about the\nslave\'s state prior to execution.\n\nIn MySQL 5.7, CHANGE MASTER TO causes an implicit commit of an ongoing\ntransaction. See\nhttp://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html.\n\nIn MySQL 5.7.4 and later, the strict requirement to execute STOP SLAVE\nprior to issuing any CHANGE MASTER TO statement (and START SLAVE\nafterward) is removed. Instead of depending on whether the slave is\nstopped, the behavior of CHANGE MASTER TO depends (in MySQL 5.7.4 and\nlater) on the states of the slave SQL thread and slave I/O threads;\nwhich of these threads is stopped or running now determines the options\nthat can or cannot be used with a CHANGE MASTER TO statement at a given\npoint in time. The rules for making this determination are listed here:\n\no If the SQL thread is stopped, you can execute CHANGE MASTER TO using\n  any combination that is otherwise allowed of RELAY_LOG_FILE,\n  RELAY_LOG_POS, and MASTER_DELAY options, even if the slave I/O thread\n  is running. No other options may be used with this statement when the\n  I/O thread is running.\n\no If the I/O thread is stopped, you can execute CHANGE MASTER TO using\n  any of the options for this statement (in any allowed combination)\n  except RELAY_LOG_FILE, RELAY_LOG_POS, or MASTER_DELAY, even when the\n  SQL thread is running. These three options may not be used when the\n  I/O thread is running.\n\no Both the SQL thread and the I/O thread must be stopped before issuing\n  a CHANGE MASTER TO statement that employs MASTER_AUTO_POSITION = 1.\n\nYou can check the current state of the slave SQL and I/O threads using\nSHOW SLAVE STATUS.\n\nFor more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-solutions-switch.htm\nl.\n\nIf you are using statement-based replication and temporary tables, it\nis possible for a CHANGE MASTER TO statement following a STOP SLAVE\nstatement to leave behind temporary tables on the slave. In MySQL 5.7.4\nand later, a warning (ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO) is now\nissued whenever this occurs. You can avoid this in such cases by making\nsure that the value of the Slave_open_temp_tables system status\nvariable is equal to 0 prior to executing such a CHANGE MASTER TO\nstatement.\n\nCHANGE MASTER TO is useful for setting up a slave when you have the\nsnapshot of the master and have recorded the master binary log\ncoordinates corresponding to the time of the snapshot. After loading\nthe snapshot into the slave to synchronize it with the master, you can\nrun CHANGE MASTER TO MASTER_LOG_FILE=\'log_name\', MASTER_LOG_POS=log_pos\non the slave to specify the coordinates at which the slave should begin\nreading the master binary log.\n\nThe following example changes the master server the slave uses and\nestablishes the master binary log coordinates from which the slave\nbegins reading. This is used when you want to set up the slave to\nreplicate the master:\n\nCHANGE MASTER TO\n  MASTER_HOST=\'master2.mycompany.com\',\n  MASTER_USER=\'replication\',\n  MASTER_PASSWORD=\'bigs3cret\',\n  MASTER_PORT=3306,\n  MASTER_LOG_FILE=\'master2-bin.001\',\n  MASTER_LOG_POS=4,\n  MASTER_CONNECT_RETRY=10;\n\nThe next example shows an operation that is less frequently employed.\nIt is used when the slave has relay log files that you want it to\nexecute again for some reason. To do this, the master need not be\nreachable. You need only use CHANGE MASTER TO and start the SQL thread\n(START SLAVE SQL_THREAD):\n\nCHANGE MASTER TO\n  RELAY_LOG_FILE=\'slave-relay-bin.006\',\n  RELAY_LOG_POS=4025;\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/change-master-to.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/change-master-to.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (422,32,'TIMESTAMP FUNCTION','Syntax:\nTIMESTAMP(expr), TIMESTAMP(expr1,expr2)\n\nWith a single argument, this function returns the date or datetime\nexpression expr as a datetime value. With two arguments, it adds the\ntime expression expr2 to the date or datetime expression expr1 and\nreturns the result as a datetime value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT TIMESTAMP(\'2003-12-31\');\n        -> \'2003-12-31 00:00:00\'\nmysql> SELECT TIMESTAMP(\'2003-12-31 12:00:00\',\'12:00:00\');\n        -> \'2004-01-01 00:00:00\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (423,40,'DROP DATABASE','Syntax:\nDROP {DATABASE | SCHEMA} [IF EXISTS] db_name\n\nDROP DATABASE drops all tables in the database and deletes the\ndatabase. Be very careful with this statement! To use DROP DATABASE,\nyou need the DROP privilege on the database. DROP SCHEMA is a synonym\nfor DROP DATABASE.\n\n*Important*: When a database is dropped, user privileges on the\ndatabase are not automatically dropped. See [HELP GRANT].\n\nIF EXISTS is used to prevent an error from occurring if the database\ndoes not exist.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/drop-database.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/drop-database.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (424,27,'SHOW GRANTS','Syntax:\nSHOW GRANTS [FOR user]\n\nThis statement lists the GRANT statement or statements that must be\nissued to duplicate the privileges that are granted to a MySQL user\naccount. SHOW GRANTS requires the SELECT privilege for the mysql\ndatabase, except to see the privileges for the current user.\n\nThe account is named using the same format as for the GRANT statement;\nfor example, \'jeffrey\'@\'localhost\'. If you specify only the user name\npart of the account name, a host name part of \'%\' is used. For\nadditional information about specifying account names, see [HELP\nGRANT].\n\nmysql> SHOW GRANTS FOR \'root\'@\'localhost\';\n+---------------------------------------------------------------------+\n| Grants for root@localhost                                           |\n+---------------------------------------------------------------------+\n| GRANT ALL PRIVILEGES ON *.* TO \'root\'@\'localhost\' WITH GRANT OPTION |\n+---------------------------------------------------------------------+\n\nTo list the privileges granted to the account that you are using to\nconnect to the server, you can use any of the following statements:\n\nSHOW GRANTS;\nSHOW GRANTS FOR CURRENT_USER;\nSHOW GRANTS FOR CURRENT_USER();\n\nIf SHOW GRANTS FOR CURRENT_USER (or any of the equivalent syntaxes) is\nused in DEFINER context, such as within a stored procedure that is\ndefined with SQL SECURITY DEFINER), the grants displayed are those of\nthe definer and not the invoker.\n\nSHOW GRANTS does not display the authentication plugin associated with\nthe account. To see that information, use SHOW CREATE USER.\n\nSHOW GRANTS displays only the privileges granted explicitly to the\nnamed account. Other privileges might be available to the account, but\nthey are not displayed. For example, if an anonymous account exists,\nthe named account might be able to use its privileges, but SHOW GRANTS\nwill not display them.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-grants.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-grants.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (425,7,'JSON_CONTAINS_PATH','JSON_CONTAINS_PATH(json_doc, one_or_all, path[, path] ...)\n\nReturns 0 or 1 to indicate whether a JSON document contains data at a\ngiven path or paths. Returns NULL if any argument is NULL. An error\noccurs if the json_doc argument is not a valid JSON document, any path\nargument is not a valid path expression, or one_or_all is not \'one\' or\n\'all\'.\n\nTo check for a specific value at a path, use JSON_CONTAINS() instead.\n\nThe return value is 0 if no specified path exists within the document.\nOtherwise, the return value depends on the one_or_all argument:\n\no \'one\': 1 if at least one path exists within the document, 0\n  otherwise.\n\no \'all\': 1 if all paths exist within the document, 0 otherwise.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html\n\n','mysql> SET @j = \'{"a": 1, "b": 2, "c": {"d": 4}}\';\nmysql> SELECT JSON_CONTAINS_PATH(@j, \'one\', \'$.a\', \'$.e\');\n+---------------------------------------------+\n| JSON_CONTAINS_PATH(@j, \'one\', \'$.a\', \'$.e\') |\n+---------------------------------------------+\n|                                           1 |\n+---------------------------------------------+\nmysql> SELECT JSON_CONTAINS_PATH(@j, \'all\', \'$.a\', \'$.e\');\n+---------------------------------------------+\n| JSON_CONTAINS_PATH(@j, \'all\', \'$.a\', \'$.e\') |\n+---------------------------------------------+\n|                                           0 |\n+---------------------------------------------+\nmysql> SELECT JSON_CONTAINS_PATH(@j, \'one\', \'$.c.d\');\n+----------------------------------------+\n| JSON_CONTAINS_PATH(@j, \'one\', \'$.c.d\') |\n+----------------------------------------+\n|                                      1 |\n+----------------------------------------+\nmysql> SELECT JSON_CONTAINS_PATH(@j, \'one\', \'$.a.d\');\n+----------------------------------------+\n| JSON_CONTAINS_PATH(@j, \'one\', \'$.a.d\') |\n+----------------------------------------+\n|                                      0 |\n+----------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (426,33,'ST_MPOINTFROMWKB','ST_MPointFromWKB(wkb[,srid]), ST_MultiPointFromWKB(wkb[,srid])\n\nConstructs a MultiPoint value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (427,3,'CRC32','Syntax:\nCRC32(expr)\n\nComputes a cyclic redundancy check value and returns a 32-bit unsigned\nvalue. The result is NULL if the argument is NULL. The argument is\nexpected to be a string and (if possible) is treated as one if it is\nnot.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT CRC32(\'MySQL\');\n        -> 3259397556\nmysql> SELECT CRC32(\'mysql\');\n        -> 2501908538\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (428,13,'STARTPOINT','StartPoint(ls)\n\nST_StartPoint() and StartPoint() are synonyms. For more information,\nsee the description of ST_StartPoint().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (429,24,'DECLARE VARIABLE','Syntax:\nDECLARE var_name [, var_name] ... type [DEFAULT value]\n\nThis statement declares local variables within stored programs. To\nprovide a default value for a variable, include a DEFAULT clause. The\nvalue can be specified as an expression; it need not be a constant. If\nthe DEFAULT clause is missing, the initial value is NULL.\n\nLocal variables are treated like stored routine parameters with respect\nto data type and overflow checking. See [HELP CREATE PROCEDURE].\n\nVariable declarations must appear before cursor or handler\ndeclarations.\n\nLocal variable names are not case sensitive. Permissible characters and\nquoting rules are the same as for other identifiers, as described in\nhttp://dev.mysql.com/doc/refman/5.7/en/identifiers.html.\n\nThe scope of a local variable is the BEGIN ... END block within which\nit is declared. The variable can be referred to in blocks nested within\nthe declaring block, except those blocks that declare a variable with\nthe same name.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/declare-local-variable.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/declare-local-variable.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (430,4,'MPOLYFROMTEXT','MPolyFromText(wkt[,srid]), MultiPolygonFromText(wkt[,srid])\n\nST_MPolyFromText(), ST_MultiPolygonFromText(), MPolyFromText(), and\nMultiPolygonFromText() are synonyms. For more information, see the\ndescription of ST_MPolyFromText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (431,20,'NOT BETWEEN','Syntax:\nexpr NOT BETWEEN min AND max\n\nThis is the same as NOT (expr BETWEEN min AND max).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (432,32,'YEARWEEK','Syntax:\nYEARWEEK(date), YEARWEEK(date,mode)\n\nReturns year and week for a date. The mode argument works exactly like\nthe mode argument to WEEK(). The year in the result may be different\nfrom the year in the date argument for the first and the last week of\nthe year.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT YEARWEEK(\'1987-01-01\');\n        -> 198653\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (433,16,'BIT_OR','Syntax:\nBIT_OR(expr)\n\nReturns the bitwise OR of all bits in expr. The calculation is\nperformed with 64-bit (BIGINT) precision.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (434,3,'LOG10','Syntax:\nLOG10(X)\n\nReturns the base-10 logarithm of X. If X is less than or equal to\n0.0E0, the function returns NULL and (as of MySQL 5.7.4) a warning\n"Invalid argument for logarithm" is reported.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT LOG10(2);\n        -> 0.30102999566398\nmysql> SELECT LOG10(100);\n        -> 2\nmysql> SELECT LOG10(-100);\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (435,23,'DECIMAL','DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL]\n\nA packed "exact" fixed-point number. M is the total number of digits\n(the precision) and D is the number of digits after the decimal point\n(the scale). The decimal point and (for negative numbers) the "-" sign\nare not counted in M. If D is 0, values have no decimal point or\nfractional part. The maximum number of digits (M) for DECIMAL is 65.\nThe maximum number of supported decimals (D) is 30. If D is omitted,\nthe default is 0. If M is omitted, the default is 10.\n\nUNSIGNED, if specified, disallows negative values.\n\nAll basic calculations (+, -, *, /) with DECIMAL columns are done with\na precision of 65 digits.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (436,40,'CREATE FUNCTION','The CREATE FUNCTION statement is used to create stored functions and\nuser-defined functions (UDFs):\n\no For information about creating stored functions, see [HELP CREATE\n  PROCEDURE].\n\no For information about creating user-defined functions, see [HELP\n  CREATE FUNCTION UDF].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/create-function.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/create-function.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (437,20,'<','Syntax:\n<\n\nLess than:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT 2 < 2;\n        -> 0\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (438,12,'MD5','Syntax:\nMD5(str)\n\nCalculates an MD5 128-bit checksum for the string. The value is\nreturned as a string of 32 hex digits, or NULL if the argument was\nNULL. The return value can, for example, be used as a hash key. See the\nnotes at the beginning of this section about storing hash values\nefficiently.\n\nThe return value is a nonbinary string in the connection character set.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT MD5(\'testing\');\n        -> \'ae2b1fca515949e5d54fb22b8ed95575\'\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (439,32,'DAYOFMONTH','Syntax:\nDAYOFMONTH(date)\n\nReturns the day of the month for date, in the range 1 to 31, or 0 for\ndates such as \'0000-00-00\' or \'2008-00-00\' that have a zero day part.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DAYOFMONTH(\'2007-02-03\');\n        -> 3\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (440,32,'UNIX_TIMESTAMP','Syntax:\nUNIX_TIMESTAMP(), UNIX_TIMESTAMP(date)\n\nIf called with no argument, returns a Unix timestamp (seconds since\n\'1970-01-01 00:00:00\' UTC) as an unsigned integer. If UNIX_TIMESTAMP()\nis called with a date argument, it returns the value of the argument as\nseconds since \'1970-01-01 00:00:00\' UTC. date may be a DATE string, a\nDATETIME string, a TIMESTAMP, or a number in the format YYMMDD or\nYYYYMMDD. The server interprets date as a value in the current time\nzone and converts it to an internal value in UTC. Clients can set their\ntime zone as described in\nhttp://dev.mysql.com/doc/refman/5.7/en/time-zone-support.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT UNIX_TIMESTAMP();\n        -> 1196440210\nmysql> SELECT UNIX_TIMESTAMP(\'2007-11-30 10:30:19\');\n        -> 1196440219\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (441,26,'ST_INTERSECTION','ST_Intersection(g1, g2)\n\nReturns a geometry that represents the point set intersection of the\ngeometry values g1 and g2.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html\n\n','mysql> SET @g1 = ST_GeomFromText(\'LineString(1 1, 3 3)\');\nmysql> SET @g2 = ST_GeomFromText(\'LineString(1 3, 3 1)\');\nmysql> SELECT ST_AsText(ST_Intersection(@g1, @g2));\n+--------------------------------------+\n| ST_AsText(ST_Intersection(@g1, @g2)) |\n+--------------------------------------+\n| POINT(2 2)                           |\n+--------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (442,10,'RENAME USER','Syntax:\nRENAME USER old_user TO new_user\n    [, old_user TO new_user] ...\n\nThe RENAME USER statement renames existing MySQL accounts. An error\noccurs for old accounts that do not exist or new accounts that already\nexist.\n\nTo use RENAME USER, you must have the global CREATE USER privilege or\nthe UPDATE privilege for the mysql database. When the read_only system\nvariable is enabled, RENAME USER additionally requires the SUPER\nprivilege.\n\nEach account name uses the format described in\nhttp://dev.mysql.com/doc/refman/5.7/en/account-names.html. For example:\n\nRENAME USER \'jeffrey\'@\'localhost\' TO \'jeff\'@\'127.0.0.1\';\n\nIf you specify only the user name part of the account name, a host name\npart of \'%\' is used.\n\nRENAME USER causes the privileges held by the old user to be those held\nby the new user. However, RENAME USER does not automatically drop or\ninvalidate databases or objects within them that the old user created.\nThis includes stored programs or views for which the DEFINER attribute\nnames the old user. Attempts to access such objects may produce an\nerror if they execute in definer security context. (For information\nabout security context, see\nhttp://dev.mysql.com/doc/refman/5.7/en/stored-programs-security.html.)\n\nThe privilege changes take effect as indicated in\nhttp://dev.mysql.com/doc/refman/5.7/en/privilege-changes.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/rename-user.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/rename-user.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (443,13,'NUMPOINTS','NumPoints(ls)\n\nST_NumPoints() and NumPoints() are synonyms. For more information, see\nthe description of ST_NumPoints().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (444,32,'LOCALTIMESTAMP','Syntax:\nLOCALTIMESTAMP, LOCALTIMESTAMP([fsp])\n\nLOCALTIMESTAMP and LOCALTIMESTAMP() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (445,32,'ADDDATE','Syntax:\nADDDATE(date,INTERVAL expr unit), ADDDATE(expr,days)\n\nWhen invoked with the INTERVAL form of the second argument, ADDDATE()\nis a synonym for DATE_ADD(). The related function SUBDATE() is a\nsynonym for DATE_SUB(). For information on the INTERVAL unit argument,\nsee the discussion for DATE_ADD().\n\nmysql> SELECT DATE_ADD(\'2008-01-02\', INTERVAL 31 DAY);\n        -> \'2008-02-02\'\nmysql> SELECT ADDDATE(\'2008-01-02\', INTERVAL 31 DAY);\n        -> \'2008-02-02\'\n\nWhen invoked with the days form of the second argument, MySQL treats it\nas an integer number of days to be added to expr.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT ADDDATE(\'2008-01-02\', 31);\n        -> \'2008-02-02\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (446,40,'ALTER FUNCTION','Syntax:\nALTER FUNCTION func_name [characteristic ...]\n\ncharacteristic:\n    COMMENT \'string\'\n  | LANGUAGE SQL\n  | { CONTAINS SQL | NO SQL | READS SQL DATA | MODIFIES SQL DATA }\n  | SQL SECURITY { DEFINER | INVOKER }\n\nThis statement can be used to change the characteristics of a stored\nfunction. More than one change may be specified in an ALTER FUNCTION\nstatement. However, you cannot change the parameters or body of a\nstored function using this statement; to make such changes, you must\ndrop and re-create the function using DROP FUNCTION and CREATE\nFUNCTION.\n\nYou must have the ALTER ROUTINE privilege for the function. (That\nprivilege is granted automatically to the function creator.) If binary\nlogging is enabled, the ALTER FUNCTION statement might also require the\nSUPER privilege, as described in\nhttp://dev.mysql.com/doc/refman/5.7/en/stored-programs-logging.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/alter-function.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/alter-function.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (447,8,'DEALLOCATE PREPARE','Syntax:\n{DEALLOCATE | DROP} PREPARE stmt_name\n\nTo deallocate a prepared statement produced with PREPARE, use a\nDEALLOCATE PREPARE statement that refers to the prepared statement\nname. Attempting to execute a prepared statement after deallocating it\nresults in an error. If too many prepared statements are created and\nnot deallocated by either the DEALLOCATE PREPARE statement or the end\nof the session, you might encounter the upper limit enforced by the\nmax_prepared_stmt_count system variable.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/deallocate-prepare.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/deallocate-prepare.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (448,14,'IS_FREE_LOCK','Syntax:\nIS_FREE_LOCK(str)\n\nChecks whether the lock named str is free to use (that is, not locked).\nReturns 1 if the lock is free (no one is using the lock), 0 if the lock\nis in use, and NULL if an error occurs (such as an incorrect argument).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (449,26,'CONVEXHULL','ConvexHull(g)\n\nST_ConvexHull() and ConvexHull() are synonyms. For more information,\nsee the description of ST_ConvexHull().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (450,31,'TOUCHES','Touches(g1,g2)\n\nST_Touches() and Touches() are synonyms. For more information, see the\ndescription of ST_Touches().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (451,23,'AUTO_INCREMENT','The AUTO_INCREMENT attribute can be used to generate a unique identity\nfor new rows:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/example-auto-increment.html\n\n','CREATE TABLE animals (\n     id MEDIUMINT NOT NULL AUTO_INCREMENT,\n     name CHAR(30) NOT NULL,\n     PRIMARY KEY (id)\n);\n\nINSERT INTO animals (name) VALUES\n    (\'dog\'),(\'cat\'),(\'penguin\'),\n    (\'lax\'),(\'whale\'),(\'ostrich\');\n\nSELECT * FROM animals;\n','http://dev.mysql.com/doc/refman/5.7/en/example-auto-increment.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (452,12,'UNCOMPRESS','Syntax:\nUNCOMPRESS(string_to_uncompress)\n\nUncompresses a string compressed by the COMPRESS() function. If the\nargument is not a compressed value, the result is NULL. This function\nrequires MySQL to have been compiled with a compression library such as\nzlib. Otherwise, the return value is always NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT UNCOMPRESS(COMPRESS(\'any string\'));\n        -> \'any string\'\nmysql> SELECT UNCOMPRESS(\'any string\');\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (453,4,'GEOMCOLLFROMTEXT','GeomCollFromText(wkt[,srid]), GeometryCollectionFromText(wkt[,srid])\n\nST_GeomCollFromText(), ST_GeometryCollectionFromText(),\nST_GeomCollFromTxt(), GeomCollFromText(), and\nGeometryCollectionFromText() are synonyms. For more information, see\nthe description of ST_GeomCollFromText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (454,2,'ST_INTERIORRINGN','ST_InteriorRingN(poly,N)\n\nReturns the N-th interior ring for the Polygon value poly as a\nLineString. Rings are numbered beginning with 1.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','mysql> SET @poly =\n    -> \'Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))\';\nmysql> SELECT ST_AsText(ST_InteriorRingN(ST_GeomFromText(@poly),1));\n+-------------------------------------------------------+\n| ST_AsText(ST_InteriorRingN(ST_GeomFromText(@poly),1)) |\n+-------------------------------------------------------+\n| LINESTRING(1 1,1 2,2 2,2 1,1 1)                       |\n+-------------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (455,17,'LAST_INSERT_ID','Syntax:\nLAST_INSERT_ID(), LAST_INSERT_ID(expr)\n\nWith no argument, LAST_INSERT_ID() returns a BIGINT UNSIGNED (64-bit)\nvalue representing the first automatically generated value successfully\ninserted for an AUTO_INCREMENT column as a result of the most recently\nexecuted INSERT statement. The value of LAST_INSERT_ID() remains\nunchanged if no rows are successfully inserted.\n\nWith an argument, LAST_INSERT_ID() returns an unsigned integer.\n\nFor example, after inserting a row that generates an AUTO_INCREMENT\nvalue, you can get the value like this:\n\nmysql> SELECT LAST_INSERT_ID();\n        -> 195\n\nThe currently executing statement does not affect the value of\nLAST_INSERT_ID(). Suppose that you generate an AUTO_INCREMENT value\nwith one statement, and then refer to LAST_INSERT_ID() in a\nmultiple-row INSERT statement that inserts rows into a table with its\nown AUTO_INCREMENT column. The value of LAST_INSERT_ID() will remain\nstable in the second statement; its value for the second and later rows\nis not affected by the earlier row insertions. (However, if you mix\nreferences to LAST_INSERT_ID() and LAST_INSERT_ID(expr), the effect is\nundefined.)\n\nIf the previous statement returned an error, the value of\nLAST_INSERT_ID() is undefined. For transactional tables, if the\nstatement is rolled back due to an error, the value of LAST_INSERT_ID()\nis left undefined. For manual ROLLBACK, the value of LAST_INSERT_ID()\nis not restored to that before the transaction; it remains as it was at\nthe point of the ROLLBACK.\n\nPrior to MySQL 5.7.3, this function was not replicated correctly if\nreplication filtering rules were in use. (Bug #17234370, Bug #69861)\n\nWithin the body of a stored routine (procedure or function) or a\ntrigger, the value of LAST_INSERT_ID() changes the same way as for\nstatements executed outside the body of these kinds of objects. The\neffect of a stored routine or trigger upon the value of\nLAST_INSERT_ID() that is seen by following statements depends on the\nkind of routine:\n\no If a stored procedure executes statements that change the value of\n  LAST_INSERT_ID(), the changed value is seen by statements that follow\n  the procedure call.\n\no For stored functions and triggers that change the value, the value is\n  restored when the function or trigger ends, so following statements\n  will not see a changed value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (456,3,'FLOOR','Syntax:\nFLOOR(X)\n\nReturns the largest integer value not greater than X.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT FLOOR(1.23);\n        -> 1\nmysql> SELECT FLOOR(-1.23);\n        -> -2\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (457,3,'COS','Syntax:\nCOS(X)\n\nReturns the cosine of X, where X is given in radians.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT COS(PI());\n        -> -1\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (458,16,'STD','Syntax:\nSTD(expr)\n\nReturns the population standard deviation of expr. This is an extension\nto standard SQL. The standard SQL function STDDEV_POP() can be used\ninstead.\n\nThis function returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (459,32,'DATE FUNCTION','Syntax:\nDATE(expr)\n\nExtracts the date part of the date or datetime expression expr.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DATE(\'2003-12-31 01:02:03\');\n        -> \'2003-12-31\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (460,3,'TAN','Syntax:\nTAN(X)\n\nReturns the tangent of X, where X is given in radians.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT TAN(PI());\n        -> -1.2246063538224e-16\nmysql> SELECT TAN(PI()+1);\n        -> 1.5574077246549\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (461,32,'WEEKOFYEAR','Syntax:\nWEEKOFYEAR(date)\n\nReturns the calendar week of the date as a number in the range from 1\nto 53. WEEKOFYEAR() is a compatibility function that is equivalent to\nWEEK(date,3).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT WEEKOFYEAR(\'2008-02-20\');\n        -> 8\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (462,26,'ST_CONVEXHULL','ST_ConvexHull(g)\n\nReturns a geometry that represents the convex hull of the geometry\nvalue g.\n\nThis function computes a geometry\'s convex hull by first checking\nwhether its vertex points are colinear. The function returns a linear\nhull if so, a polygon hull otherwise. This function processes geometry\ncollections by extracting all vertex points of all components of the\ncollection, creating a MultiPoint value from them, and computing its\nconvex hull. If the argument is an empty geometry collection, the\nreturn value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html\n\n','mysql> SET @g = \'MULTIPOINT(5 0,25 0,15 10,15 25)\';\nmysql> SELECT ST_AsText(ST_ConvexHull(GeomFromText(@g)));\n+--------------------------------------------+\n| ST_AsText(ST_ConvexHull(GeomFromText(@g))) |\n+--------------------------------------------+\n| POLYGON((5 0,25 0,15 25,5 0))              |\n+--------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-operator-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (463,32,'SUBTIME','Syntax:\nSUBTIME(expr1,expr2)\n\nSUBTIME() returns expr1 − expr2 expressed as a value in the same\nformat as expr1. expr1 is a time or datetime expression, and expr2 is a\ntime expression.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT SUBTIME(\'2007-12-31 23:59:59.999999\',\'1 1:1:1.000002\');\n        -> \'2007-12-30 22:58:58.999997\'\nmysql> SELECT SUBTIME(\'01:00:00.999999\', \'02:00:00.999998\');\n        -> \'-00:59:59.999999\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (464,3,'LOG2','Syntax:\nLOG2(X)\n\nReturns the base-2 logarithm of X. If X is less than or equal to 0.0E0,\nthe function returns NULL and (as of MySQL 5.7.4) a warning "Invalid\nargument for logarithm" is reported.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT LOG2(65536);\n        -> 16\nmysql> SELECT LOG2(-100);\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (465,12,'UNCOMPRESSED_LENGTH','Syntax:\nUNCOMPRESSED_LENGTH(compressed_string)\n\nReturns the length that the compressed string had before being\ncompressed.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT UNCOMPRESSED_LENGTH(COMPRESS(REPEAT(\'a\',30)));\n        -> 30\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (466,3,'POW','Syntax:\nPOW(X,Y)\n\nReturns the value of X raised to the power of Y.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT POW(2,2);\n        -> 4\nmysql> SELECT POW(2,-2);\n        -> 0.25\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (467,40,'DROP TABLE','Syntax:\nDROP [TEMPORARY] TABLE [IF EXISTS]\n    tbl_name [, tbl_name] ...\n    [RESTRICT | CASCADE]\n\nDROP TABLE removes one or more tables. You must have the DROP privilege\nfor each table. All table data and the table definition are removed, so\nbe careful with this statement! If any of the tables named in the\nargument list do not exist, MySQL returns an error indicating by name\nwhich nonexisting tables it was unable to drop, but it also drops all\nof the tables in the list that do exist.\n\n*Important*: When a table is dropped, user privileges on the table are\nnot automatically dropped. See [HELP GRANT].\n\nFor a partitioned table, DROP TABLE permanently removes the table\ndefinition, all of its partitions, and all of the data which was stored\nin those partitions. It also removes the partitioning definition (.par)\nfile associated with the dropped table.\n\nUse IF EXISTS to prevent an error from occurring for tables that do not\nexist. A NOTE is generated for each nonexistent table when using IF\nEXISTS. See [HELP SHOW WARNINGS].\n\nRESTRICT and CASCADE are permitted to make porting easier. In MySQL\n5.7, they do nothing.\n\n*Note*: DROP TABLE automatically commits the current active\ntransaction, unless you use the TEMPORARY keyword.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/drop-table.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/drop-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (468,32,'NOW','Syntax:\nNOW([fsp])\n\nReturns the current date and time as a value in \'YYYY-MM-DD HH:MM:SS\'\nor YYYYMMDDHHMMSS format, depending on whether the function is used in\na string or numeric context. The value is expressed in the current time\nzone.\n\nIf the fsp argument is given to specify a fractional seconds precision\nfrom 0 to 6, the return value includes a fractional seconds part of\nthat many digits.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT NOW();\n        -> \'2007-12-15 23:50:26\'\nmysql> SELECT NOW() + 0;\n        -> 20071215235026.000000\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (469,27,'SHOW ENGINES','Syntax:\nSHOW [STORAGE] ENGINES\n\nSHOW ENGINES displays status information about the server\'s storage\nengines. This is particularly useful for checking whether a storage\nengine is supported, or to see what the default engine is. This\ninformation can also be obtained from the INFORMATION_SCHEMA ENGINES\ntable. See http://dev.mysql.com/doc/refman/5.7/en/engines-table.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-engines.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-engines.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (470,4,'ST_POINTFROMTEXT','ST_PointFromText(wkt[,srid])\n\nConstructs a Point value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (471,13,'ST_ENDPOINT','ST_EndPoint(ls)\n\nReturns the Point that is the endpoint of the LineString value ls.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html\n\n','mysql> SET @ls = \'LineString(1 1,2 2,3 3)\';\nmysql> SELECT ST_AsText(ST_EndPoint(ST_GeomFromText(@ls)));\n+----------------------------------------------+\n| ST_AsText(ST_EndPoint(ST_GeomFromText(@ls))) |\n+----------------------------------------------+\n| POINT(3 3)                                   |\n+----------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (472,14,'IS_IPV6','Syntax:\nIS_IPV6(expr)\n\nReturns 1 if the argument is a valid IPv6 address specified as a\nstring, 0 otherwise. This function does not consider IPv4 addresses to\nbe valid IPv6 addresses.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> SELECT IS_IPV6(\'10.0.5.9\'), IS_IPV6(\'::1\');\n        -> 0, 1\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (473,23,'LONGBLOB','LONGBLOB\n\nA BLOB column with a maximum length of 4,294,967,295 or 4GB (232 − 1)\nbytes. The effective maximum length of LONGBLOB columns depends on the\nconfigured maximum packet size in the client/server protocol and\navailable memory. Each LONGBLOB value is stored using a 4-byte length\nprefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (474,31,'ST_OVERLAPS','ST_Overlaps(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 spatially overlaps g2. The term\nspatially overlaps is used if two geometries intersect and their\nintersection results in a geometry of the same dimension but not equal\nto either of the given geometries.\n\nAs of MySQL 5.7.5, this function returns 0 if called with an\ninapplicable geometry argument type combination. For example, it\nreturns 0 if called with geometries of different dimensions or any\nargument is a Point.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (475,23,'YEAR DATA TYPE','YEAR[(4)]\n\nA year in four-digit format. MySQL displays YEAR values in YYYY format,\nbut permits assignment of values to YEAR columns using either strings\nor numbers. Values display as 1901 to 2155, and 0000.\n\n*Note*: The YEAR(2) data type is deprecated and support for it is\nremoved in MySQL 5.7.5. To convert YEAR(2) columns to YEAR(4), see\nhttp://dev.mysql.com/doc/refman/5.7/en/migrating-to-year4.html.\n\nFor additional information about YEAR display format and interpretation\nof input values, see http://dev.mysql.com/doc/refman/5.7/en/year.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (476,16,'SUM','Syntax:\nSUM([DISTINCT] expr)\n\nReturns the sum of expr. If the return set has no rows, SUM() returns\nNULL. The DISTINCT keyword can be used to sum only the distinct values\nof expr.\n\nSUM() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (477,7,'JSON_SET','JSON_SET(json_doc, path, val[, path, val] ...)\n\nInserts or updates data in a JSON document and returns the result.\nReturns NULL if any argument is NULL or path, if given, does not locate\nan object. An error occurs if the json_doc argument is not a valid JSON\ndocument or the path argument is not a valid path expression or\ncontains a * or ** wildcard.\n\nThe path/value pairs are evaluated left to right. The document produced\nby evaluating one pair becomes the new value against which the next\npair is evaluated.\n\nA path/value pair for an existing path in the document overwrites the\nexisting document value with the new value. A path/value pair for a\nnonexisting path in the document adds the value to the document if the\npath identifies one of these types of values:\n\no A member not present in an existing object. The member is added to\n  the object and associated with the new value.\n\no A position past the end of an existing array. The array is extended\n  with the new value. If the existing value is not an array, it is\n  autowrapped as an array, then extended with the new value.\n\nOtherwise, a path/value pair for a nonexisting path in the document is\nignored and has no effect.\n\nThe JSON_SET(), JSON_INSERT(), and JSON_REPLACE() functions are\nrelated:\n\no JSON_SET() replaces existing values and adds nonexisting values.\n\no JSON_INSERT() inserts values without replacing existing values.\n\no JSON_REPLACE() replaces only existing values.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html\n\n','mysql> SET @j = \'{ "a": 1, "b": [2, 3]}\';\nmysql> SELECT JSON_SET(@j, \'$.a\', 10, \'$.c\', \'[true, false]\');\n+-------------------------------------------------+\n| JSON_SET(@j, \'$.a\', 10, \'$.c\', \'[true, false]\') |\n+-------------------------------------------------+\n| {"a": 10, "b": [2, 3], "c": "[true, false]"}    |\n+-------------------------------------------------+\nmysql> SELECT JSON_INSERT(@j, \'$.a\', 10, \'$.c\', \'[true, false]\');\n+----------------------------------------------------+\n| JSON_INSERT(@j, \'$.a\', 10, \'$.c\', \'[true, false]\') |\n+----------------------------------------------------+\n| {"a": 1, "b": [2, 3], "c": "[true, false]"}        |\n+----------------------------------------------------+\nmysql> SELECT JSON_REPLACE(@j, \'$.a\', 10, \'$.c\', \'[true, false]\');\n+-----------------------------------------------------+\n| JSON_REPLACE(@j, \'$.a\', 10, \'$.c\', \'[true, false]\') |\n+-----------------------------------------------------+\n| {"a": 10, "b": [2, 3]}                              |\n+-----------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (478,38,'REPEAT FUNCTION','Syntax:\nREPEAT(str,count)\n\nReturns a string consisting of the string str repeated count times. If\ncount is less than 1, returns an empty string. Returns NULL if str or\ncount are NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT REPEAT(\'MySQL\', 3);\n        -> \'MySQLMySQLMySQL\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (479,38,'SOUNDEX','Syntax:\nSOUNDEX(str)\n\nReturns a soundex string from str. Two strings that sound almost the\nsame should have identical soundex strings. A standard soundex string\nis four characters long, but the SOUNDEX() function returns an\narbitrarily long string. You can use SUBSTRING() on the result to get a\nstandard soundex string. All nonalphabetic characters in str are\nignored. All international alphabetic characters outside the A-Z range\nare treated as vowels.\n\n*Important*: When using SOUNDEX(), you should be aware of the following\nlimitations:\n\no This function, as currently implemented, is intended to work well\n  with strings that are in the English language only. Strings in other\n  languages may not produce reliable results.\n\no This function is not guaranteed to provide consistent results with\n  strings that use multibyte character sets, including utf-8.\n\n  We hope to remove these limitations in a future release. See Bug\n  #22638 for more information.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT SOUNDEX(\'Hello\');\n        -> \'H400\'\nmysql> SELECT SOUNDEX(\'Quadratically\');\n        -> \'Q36324\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (480,7,'MBRTOUCHES','MBRTouches(g1,g2)\n\nReturns 1 or 0 to indicate whether the minimum bounding rectangles of\nthe two geometries g1 and g2 touch. Two geometries spatially touch if\nthe interiors of the geometries do not intersect, but the boundary of\none of the geometries intersects either the boundary or the interior of\nthe other.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (481,40,'DROP EVENT','Syntax:\nDROP EVENT [IF EXISTS] event_name\n\nThis statement drops the event named event_name. The event immediately\nceases being active, and is deleted completely from the server.\n\nIf the event does not exist, the error ERROR 1517 (HY000): Unknown\nevent \'event_name\' results. You can override this and cause the\nstatement to generate a warning for nonexistent events instead using IF\nEXISTS.\n\nThis statement requires the EVENT privilege for the schema to which the\nevent to be dropped belongs.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/drop-event.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/drop-event.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (482,23,'VARBINARY','VARBINARY(M)\n\nThe VARBINARY type is similar to the VARCHAR type, but stores binary\nbyte strings rather than nonbinary character strings. M represents the\nmaximum column length in bytes.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (483,27,'LOAD INDEX','Syntax:\nLOAD INDEX INTO CACHE\n  tbl_index_list [, tbl_index_list] ...\n\ntbl_index_list:\n  tbl_name\n    [PARTITION (partition_list | ALL)]\n    [[INDEX|KEY] (index_name[, index_name] ...)]\n    [IGNORE LEAVES]\n\npartition_list:\n    partition_name[, partition_name][, ...]\n\nThe LOAD INDEX INTO CACHE statement preloads a table index into the key\ncache to which it has been assigned by an explicit CACHE INDEX\nstatement, or into the default key cache otherwise.\n\nLOAD INDEX INTO CACHE is used only for MyISAM tables. In MySQL 5.7, it\nis also supported for partitioned MyISAM tables; in addition, indexes\non partitioned tables can be preloaded for one, several, or all\npartitions.\n\nThe IGNORE LEAVES modifier causes only blocks for the nonleaf nodes of\nthe index to be preloaded.\n\nIGNORE LEAVES is also supported for partitioned MyISAM tables.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/load-index.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/load-index.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (484,28,'UNION','Syntax:\nSELECT ...\nUNION [ALL | DISTINCT] SELECT ...\n[UNION [ALL | DISTINCT] SELECT ...]\n\nUNION is used to combine the result from multiple SELECT statements\ninto a single result set.\n\nThe column names from the first SELECT statement are used as the column\nnames for the results returned. Selected columns listed in\ncorresponding positions of each SELECT statement should have the same\ndata type. (For example, the first column selected by the first\nstatement should have the same type as the first column selected by the\nother statements.)\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/union.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/union.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (485,32,'TO_DAYS','Syntax:\nTO_DAYS(date)\n\nGiven a date date, returns a day number (the number of days since year\n0).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT TO_DAYS(950501);\n        -> 728779\nmysql> SELECT TO_DAYS(\'2007-10-07\');\n        -> 733321\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (486,27,'SHOW INDEX','Syntax:\nSHOW {INDEX | INDEXES | KEYS}\n    {FROM | IN} tbl_name\n    [{FROM | IN} db_name]\n    [WHERE expr]\n\nSHOW INDEX returns table index information. The format resembles that\nof the SQLStatistics call in ODBC. This statement requires some\nprivilege for any column in the table.\nYou can use db_name.tbl_name as an alternative to the tbl_name FROM\ndb_name syntax. These two statements are equivalent:\n\nSHOW INDEX FROM mytable FROM mydb;\nSHOW INDEX FROM mydb.mytable;\n\nThe WHERE clause can be given to select rows using more general\nconditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html.\n\nYou can also list a table\'s indexes with the mysqlshow -k db_name\ntbl_name command.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-index.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-index.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (487,27,'SHOW CREATE DATABASE','Syntax:\nSHOW CREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name\n\nShows the CREATE DATABASE statement that creates the named database. If\nthe SHOW statement includes an IF NOT EXISTS clause, the output too\nincludes such a clause. SHOW CREATE SCHEMA is a synonym for SHOW CREATE\nDATABASE.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-create-database.html\n\n','mysql> SHOW CREATE DATABASE test\\G\n*************************** 1. row ***************************\n       Database: test\nCreate Database: CREATE DATABASE `test`\n                 /*!40100 DEFAULT CHARACTER SET latin1 */\n\nmysql> SHOW CREATE SCHEMA test\\G\n*************************** 1. row ***************************\n       Database: test\nCreate Database: CREATE DATABASE `test`\n                 /*!40100 DEFAULT CHARACTER SET latin1 */\n','http://dev.mysql.com/doc/refman/5.7/en/show-create-database.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (488,15,'!','Syntax:\nNOT, !\n\nLogical NOT. Evaluates to 1 if the operand is 0, to 0 if the operand is\nnonzero, and NOT NULL returns NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/logical-operators.html\n\n','mysql> SELECT NOT 10;\n        -> 0\nmysql> SELECT NOT 0;\n        -> 1\nmysql> SELECT NOT NULL;\n        -> NULL\nmysql> SELECT ! (1+1);\n        -> 0\nmysql> SELECT ! 1+1;\n        -> 1\n','http://dev.mysql.com/doc/refman/5.7/en/logical-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (489,24,'DECLARE HANDLER','Syntax:\nDECLARE handler_action HANDLER\n    FOR condition_value [, condition_value] ...\n    statement\n\nhandler_action:\n    CONTINUE\n  | EXIT\n  | UNDO\n\ncondition_value:\n    mysql_error_code\n  | SQLSTATE [VALUE] sqlstate_value\n  | condition_name\n  | SQLWARNING\n  | NOT FOUND\n  | SQLEXCEPTION\n\nThe DECLARE ... HANDLER statement specifies a handler that deals with\none or more conditions. If one of these conditions occurs, the\nspecified statement executes. statement can be a simple statement such\nas SET var_name = value, or a compound statement written using BEGIN\nand END (see [HELP BEGIN END]).\n\nHandler declarations must appear after variable or condition\ndeclarations.\n\nThe handler_action value indicates what action the handler takes after\nexecution of the handler statement:\n\no CONTINUE: Execution of the current program continues.\n\no EXIT: Execution terminates for the BEGIN ... END compound statement\n  in which the handler is declared. This is true even if the condition\n  occurs in an inner block.\n\no UNDO: Not supported.\n\nThe condition_value for DECLARE ... HANDLER indicates the specific\ncondition or class of conditions that activates the handler:\n\no A MySQL error code (a number) or an SQLSTATE value (a 5-character\n  string literal). You should not use MySQL error code 0 or SQLSTATE\n  values that begin with \'00\', because those indicate success rather\n  than an error condition. For a list of MySQL error codes and SQLSTATE\n  values, see\n  http://dev.mysql.com/doc/refman/5.7/en/error-messages-server.html.\n\no A condition name previously specified with DECLARE ... CONDITION. A\n  condition name can be associated with a MySQL error code or SQLSTATE\n  value. See [HELP DECLARE CONDITION].\n\no SQLWARNING is shorthand for the class of SQLSTATE values that begin\n  with \'01\'.\n\no NOT FOUND is shorthand for the class of SQLSTATE values that begin\n  with \'02\'. This is relevant within the context of cursors and is used\n  to control what happens when a cursor reaches the end of a data set.\n  If no more rows are available, a No Data condition occurs with\n  SQLSTATE value \'02000\'. To detect this condition, you can set up a\n  handler for it (or for a NOT FOUND condition). For an example, see\n  http://dev.mysql.com/doc/refman/5.7/en/cursors.html. This condition\n  also occurs for SELECT ... INTO var_list statements that retrieve no\n  rows.\n\no SQLEXCEPTION is shorthand for the class of SQLSTATE values that do\n  not begin with \'00\', \'01\', or \'02\'.\n\nFor information about how the server chooses handlers when a condition\noccurs, see http://dev.mysql.com/doc/refman/5.7/en/handler-scope.html.\n\nIf a condition occurs for which no handler has been declared, the\naction taken depends on the condition class:\n\no For SQLEXCEPTION conditions, the stored program terminates at the\n  statement that raised the condition, as if there were an EXIT\n  handler. If the program was called by another stored program, the\n  calling program handles the condition using the handler selection\n  rules applied to its own handlers.\n\no For SQLWARNING conditions, the program continues executing, as if\n  there were a CONTINUE handler.\n\no For NOT FOUND conditions, if the condition was raised normally, the\n  action is CONTINUE. If it was raised by SIGNAL or RESIGNAL, the\n  action is EXIT.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/declare-handler.html\n\n','mysql> CREATE TABLE test.t (s1 INT, PRIMARY KEY (s1));\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> delimiter //\n\nmysql> CREATE PROCEDURE handlerdemo ()\n    -> BEGIN\n    ->   DECLARE CONTINUE HANDLER FOR SQLSTATE \'23000\' SET @x2 = 1;\n    ->   SET @x = 1;\n    ->   INSERT INTO test.t VALUES (1);\n    ->   SET @x = 2;\n    ->   INSERT INTO test.t VALUES (1);\n    ->   SET @x = 3;\n    -> END;\n    -> //\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> CALL handlerdemo()//\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT @x//\n    +------+\n    | @x   |\n    +------+\n    | 3    |\n    +------+\n    1 row in set (0.00 sec)\n','http://dev.mysql.com/doc/refman/5.7/en/declare-handler.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (490,23,'DOUBLE','DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL]\n\nA normal-size (double-precision) floating-point number. Permissible\nvalues are -1.7976931348623157E+308 to -2.2250738585072014E-308, 0, and\n2.2250738585072014E-308 to 1.7976931348623157E+308. These are the\ntheoretical limits, based on the IEEE standard. The actual range might\nbe slightly smaller depending on your hardware or operating system.\n\nM is the total number of digits and D is the number of digits following\nthe decimal point. If M and D are omitted, values are stored to the\nlimits permitted by the hardware. A double-precision floating-point\nnumber is accurate to approximately 15 decimal places.\n\nUNSIGNED, if specified, disallows negative values.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (491,23,'TIME','TIME[(fsp)]\n\nA time. The range is \'-838:59:59.000000\' to \'838:59:59.000000\'. MySQL\ndisplays TIME values in \'HH:MM:SS[.fraction]\' format, but permits\nassignment of values to TIME columns using either strings or numbers.\n\nAn optional fsp value in the range from 0 to 6 may be given to specify\nfractional seconds precision. A value of 0 signifies that there is no\nfractional part. If omitted, the default precision is 0.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (492,17,'SYSTEM_USER','Syntax:\nSYSTEM_USER()\n\nSYSTEM_USER() is a synonym for USER().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (493,32,'CURRENT_DATE','Syntax:\nCURRENT_DATE, CURRENT_DATE()\n\nCURRENT_DATE and CURRENT_DATE() are synonyms for CURDATE().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (494,40,'TRUNCATE TABLE','Syntax:\nTRUNCATE [TABLE] tbl_name\n\nTRUNCATE TABLE empties a table completely. It requires the DROP\nprivilege.\n\nLogically, TRUNCATE TABLE is similar to a DELETE statement that deletes\nall rows, or a sequence of DROP TABLE and CREATE TABLE statements. To\nachieve high performance, it bypasses the DML method of deleting data.\nThus, it cannot be rolled back, it does not cause ON DELETE triggers to\nfire, and it cannot be performed for InnoDB tables with parent-child\nforeign key relationships.\n\nAlthough TRUNCATE TABLE is similar to DELETE, it is classified as a DDL\nstatement rather than a DML statement. It differs from DELETE in the\nfollowing ways in MySQL 5.7:\n\no Truncate operations drop and re-create the table, which is much\n  faster than deleting rows one by one, particularly for large tables.\n\no Truncate operations cause an implicit commit, and so cannot be rolled\n  back.\n\no Truncation operations cannot be performed if the session holds an\n  active table lock.\n\no TRUNCATE TABLE fails for an InnoDB table or NDB\n  (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster.html) table if\n  there are any FOREIGN KEY constraints from other tables that\n  reference the table. Foreign key constraints between columns of the\n  same table are permitted.\n\no Truncation operations do not return a meaningful value for the number\n  of deleted rows. The usual result is "0 rows affected," which should\n  be interpreted as "no information."\n\no As long as the table format file tbl_name.frm is valid, the table can\n  be re-created as an empty table with TRUNCATE TABLE, even if the data\n  or index files have become corrupted.\n\no Any AUTO_INCREMENT value is reset to its start value. This is true\n  even for MyISAM and InnoDB, which normally do not reuse sequence\n  values.\n\no When used with partitioned tables, TRUNCATE TABLE preserves the\n  partitioning; that is, the data and index files are dropped and\n  re-created, while the partition definitions (.par) file is\n  unaffected.\n\no The TRUNCATE TABLE statement does not invoke ON DELETE triggers.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/truncate-table.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/truncate-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (495,8,'START SLAVE','Syntax:\nSTART SLAVE [thread_types] [until_option] [connection_options] [channel_option]\n\nthread_types:\n    [thread_type [, thread_type] ... ]\n\nthread_type: \n    IO_THREAD | SQL_THREAD\n\nuntil_option:\n    UNTIL {   {SQL_BEFORE_GTIDS | SQL_AFTER_GTIDS} = gtid_set\n          |   MASTER_LOG_FILE = \'log_name\', MASTER_LOG_POS = log_pos\n          |   RELAY_LOG_FILE = \'log_name\', RELAY_LOG_POS = log_pos\n          |   SQL_AFTER_MTS_GAPS  }\n\nconnection_options: \n    [USER=\'user_name\'] [PASSWORD=\'user_pass\'] [DEFAULT_AUTH=\'plugin_name\'] [PLUGIN_DIR=\'plugin_dir\']\n\n\nchannel_option: \n    FOR CHANNEL channel\n\ngtid_set:\n    uuid_set [, uuid_set] ...\n    | \'\'\n\nuuid_set:\n    uuid:interval[:interval]...\n\nuuid:\n    hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhhhhhh\n\nh:\n    [0-9,A-F]\n\ninterval:\n    n[-n]\n\n    (n >= 1) \n\nSTART SLAVE with no thread_type options starts both of the slave\nthreads. The I/O thread reads events from the master server and stores\nthem in the relay log. The SQL thread reads events from the relay log\nand executes them. START SLAVE requires the SUPER privilege.\n\nIf START SLAVE succeeds in starting the slave threads, it returns\nwithout any error. However, even in that case, it might be that the\nslave threads start and then later stop (for example, because they do\nnot manage to connect to the master or read its binary log, or some\nother problem). START SLAVE does not warn you about this. You must\ncheck the slave\'s error log for error messages generated by the slave\nthreads, or check that they are running satisfactorily with SHOW SLAVE\nSTATUS.\n\nIn MySQL 5.7, START SLAVE causes an implicit commit of an ongoing\ntransaction. See\nhttp://dev.mysql.com/doc/refman/5.7/en/implicit-commit.html.\n\nBeginning with MySQL 5.7.1, gtid_next must be set to AUTOMATIC before\nissuing this statement (Bug #16062608).\n\nThe optional FOR CHANNEL channel clause added in MySQL 5.7.6 enables\nyou to choose which replication channel the statement applies to. If no\nclause is set and no extra channels exist, the statement applies to the\ndefault channel and behaves the same as versions of MySQL prior to\n5.7.6. Providing a FOR CHANNEL channel clause applies the START SLAVE\nstatement to a specific replication channel. If a START SLAVE statement\ndoes not have a channel defined when using multiple channels, this\nstatement starts the specified threads for all channels. Beginning with\nMySQL 5.7.9, this statement is disallowed for the\ngroup_replication_recovery channel. See\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-channels.html for\nmore information.\n\nMySQL 5.7 supports pluggable user-password authentication with START\nSLAVE with the USER, PASSWORD, DEFAULT_AUTH and PLUGIN_DIR options, as\ndescribed in the following list:\n\no USER: User name. Cannot be set to an empty or null string, or left\n  unset if PASSWORD is used.\n\no PASSWORD: Password.\n\no DEFAULT_AUTH: Name of plugin; default is MySQL native authentication.\n\no PLUGIN_DIR: Location of plugin.\n\nYou cannot use the SQL_THREAD option when specifying any of USER,\nPASSWORD, DEFAULT_AUTH, or PLUGIN_DIR, unless the IO_THREAD option is\nalso provided.\n\nSee\nhttp://dev.mysql.com/doc/refman/5.7/en/pluggable-authentication.html,\nfor more information.\n\nIf an insecure connection is used with any these options, the server\nissues the warning Sending passwords in plain text without SSL/TLS is\nextremely insecure.\n\nSTART SLAVE ... UNTIL supports two additional options for use with\nglobal transaction identifiers (GTIDs) (see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html). Each of\nthese takes a set of one or more global transaction identifiers\ngtid_set as an argument (see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html#\nreplication-gtids-concepts-gtid-sets, for more information).\n\nWhen no thread_type is specified, START SLAVE UNTIL SQL_BEFORE_GTIDS\ncauses the slave SQL thread to process transactions until it has\nreached the first transaction whose GTID is listed in the gtid_set.\nSTART SLAVE UNTIL SQL_AFTER_GTIDS causes the slave threads to process\nall transactions until the last transaction in the gtid_set has been\nprocessed by both threads. In other words, START SLAVE UNTIL\nSQL_BEFORE_GTIDS causes the slave SQL thread to process all\ntransactions occurring before the first GTID in the gtid_set is\nreached, and START SLAVE UNTIL SQL_AFTER_GTIDS causes the slave threads\nto handle all transactions, including those whose GTIDs are found in\ngtid_set, until each has encountered a transaction whose GTID is not\npart of the set. SQL_BEFORE_GTIDS and SQL_AFTER_GTIDS each support the\nSQL_THREAD and IO_THREAD options, although using IO_THREAD with them\ncurrently has no effect.\n\nFor example, START SLAVE SQL_THREAD UNTIL SQL_BEFORE_GTIDS =\n3E11FA47-71CA-11E1-9E33-C80AA9429562:11-56 causes the slave SQL thread\nto process all transactions originating from the master whose\nserver_uuid is 3E11FA47-71CA-11E1-9E33-C80AA9429562 until it encounters\nthe transaction having sequence number 11; it then stops without\nprocessing this transaction. In other words, all transactions up to and\nincluding the transaction with sequence number 10 are processed.\nExecuting START SLAVE SQL_THREAD UNTIL SQL_AFTER_GTIDS =\n3E11FA47-71CA-11E1-9E33-C80AA9429562:11-56, on the other hand, would\ncause the slave SQL thread to obtain all transactions just mentioned\nfrom the master, including all of the transactions having the sequence\nnumbers 11 through 56, and then to stop without processing any\nadditional transactions; that is, the transaction having sequence\nnumber 56 would be the last transaction fetched by the slave SQL\nthread.\n\nPrior to MySQL 5.7.3, SQL_AFTER_GTIDS did not stop the slave once the\nindicated transaction was completed, but waited until another GTID\nevent was received (Bug #14767986).\n\nWhen using a multi-threaded slave, there is a chance of gaps in the\nsequence of transactions that have been executed from the relay log in\nthe following cases:\n\no killing the coordinator thread\n\no after an error occurs in the worker threads\n\no mysqld shuts down unexpectedly\n\nUse the START SLAVE UNTIL SQL_AFTER_MTS_GAPS statement to cause a\nmulti-threaded slave\'s worker threads to only run until no more gaps\nare found in the relay log, and then to stop. This statement can take\nan SQL_THREAD option, but the effects of the statement remain\nunchanged. It has no effect on the slave I/O thread (and cannot be used\nwith the IO_THREAD option).\n\nIssuing START SLAVE on a multi-threaded slave with gaps in the sequence\nof transactions executed from the relay log generates a warning. In\nsuch a situation, the solution is to use START SLAVE UNTIL\nSQL_AFTER_MTS_GAPS, then issue RESET SLAVE to remove any remaining\nrelay logs. See\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-features-transaction\n-inconsistencies.html for more information.\n\nTo change a failed multi-threaded slave to single-threaded mode, you\ncan issue the following series of statements, in the order shown:\n\nSTART SLAVE UNTIL SQL_AFTER_MTS_GAPS;\n\nSET @@GLOBAL.slave_parallel_workers = 0;\n\nSTART SLAVE SQL_THREAD;\n\n*Note*: It is possible to view the entire text of a running START SLAVE\n... statement, including any USER or PASSWORD values used, in the\noutput of SHOW PROCESSLIST. This is also true for the text of a running\nCHANGE MASTER TO statement, including any values it employs for\nMASTER_USER or MASTER_PASSWORD.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/start-slave.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/start-slave.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (496,2,'AREA','Area(poly)\n\nST_Area() and Area() are synonyms. For more information, see the\ndescription of ST_Area().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (497,27,'SHOW WARNINGS','Syntax:\nSHOW WARNINGS [LIMIT [offset,] row_count]\nSHOW COUNT(*) WARNINGS\n\nSHOW WARNINGS is a diagnostic statement that displays information about\nthe conditions (errors, warnings, and notes) resulting from executing a\nstatement in the current session. Warnings are generated for DML\nstatements such as INSERT, UPDATE, and LOAD DATA INFILE as well as DDL\nstatements such as CREATE TABLE and ALTER TABLE.\n\nThe LIMIT clause has the same syntax as for the SELECT statement. See\nhttp://dev.mysql.com/doc/refman/5.7/en/select.html.\n\nSHOW WARNINGS is also used following EXPLAIN EXTENDED, to display the\nextra information generated by EXPLAIN when the EXTENDED keyword is\nused. See http://dev.mysql.com/doc/refman/5.7/en/explain-extended.html.\n\nAs of MySQL 5.7.2, SHOW WARNINGS displays information about the\nconditions resulting from execution of the most recent nondiagnostic\nstatement in the current session. If the most recent statement resulted\nin an error during parsing, SHOW WARNINGS shows the resulting\nconditions, regardless of statement type (diagnostic or nondiagnostic).\n\nBefore MySQL 5.7.2, SHOW WARNINGS displays information about the\nconditions resulting from the most recent statement in the current\nsession that generated messages. It shows nothing if the most recent\nstatement used a table and generated no messages. (That is, statements\nthat use a table but generate no messages clear the message list.)\nStatements that do not use tables and do not generate messages have no\neffect on the message list.\n\nThe SHOW COUNT(*) WARNINGS diagnostic statement displays the total\nnumber of errors, warnings, and notes. You can also retrieve this\nnumber from the warning_count system variable:\n\nSHOW COUNT(*) WARNINGS;\nSELECT @@warning_count;\n\nA difference in these statements is that the first is a diagnostic\nstatement that does not clear the message list. The second, because it\nis a SELECT statement is considered nondiagnostic and, as of MySQL\n5.7.2, does clear the message list.\n\nA related diagnostic statement, SHOW ERRORS, shows only error\nconditions (it excludes warnings and notes), and SHOW COUNT(*) ERRORS\nstatement displays the total number of errors. See [HELP SHOW ERRORS].\nGET DIAGNOSTICS can be used to examine information for individual\nconditions. See [HELP GET DIAGNOSTICS].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-warnings.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-warnings.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (498,4,'ST_LINEFROMTEXT','ST_LineFromText(wkt[,srid]), ST_LineStringFromText(wkt[,srid])\n\nConstructs a LineString value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (499,10,'DROP USER','Syntax:\nDROP USER [IF EXISTS] user [, user] ...\n\nThe DROP USER statement removes one or more MySQL accounts and their\nprivileges. It removes privilege rows for the account from all grant\ntables.\n\nTo use DROP USER, you must have the global CREATE USER privilege or the\nDELETE privilege for the mysql database. When the read_only system\nvariable is enabled, DROP USER additionally requires the SUPER\nprivilege.\n\nAn error occurs if you try to drop an account that does not exist.\n\nAs of MySQL 5.7.8, the IF EXISTS clause can be used, which causes the\nstatement to produce a warning for each named account that does not\nexist, rather than an error.\n\nEach account name uses the format described in\nhttp://dev.mysql.com/doc/refman/5.7/en/account-names.html. For example:\n\nDROP USER \'jeffrey\'@\'localhost\';\n\nIf you specify only the user name part of the account name, a host name\npart of \'%\' is used.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/drop-user.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/drop-user.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (500,38,'SUBSTRING','Syntax:\nSUBSTRING(str,pos), SUBSTRING(str FROM pos), SUBSTRING(str,pos,len),\nSUBSTRING(str FROM pos FOR len)\n\nThe forms without a len argument return a substring from string str\nstarting at position pos. The forms with a len argument return a\nsubstring len characters long from string str, starting at position\npos. The forms that use FROM are standard SQL syntax. It is also\npossible to use a negative value for pos. In this case, the beginning\nof the substring is pos characters from the end of the string, rather\nthan the beginning. A negative value may be used for pos in any of the\nforms of this function.\n\nFor all forms of SUBSTRING(), the position of the first character in\nthe string from which the substring is to be extracted is reckoned as\n1.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT SUBSTRING(\'Quadratically\',5);\n        -> \'ratically\'\nmysql> SELECT SUBSTRING(\'foobarbar\' FROM 4);\n        -> \'barbar\'\nmysql> SELECT SUBSTRING(\'Quadratically\',5,6);\n        -> \'ratica\'\nmysql> SELECT SUBSTRING(\'Sakila\', -3);\n        -> \'ila\'\nmysql> SELECT SUBSTRING(\'Sakila\', -5, 3);\n        -> \'aki\'\nmysql> SELECT SUBSTRING(\'Sakila\' FROM -4 FOR 2);\n        -> \'ki\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (501,37,'ISEMPTY','IsEmpty(g)\n\nST_IsEmpty() and IsEmpty() are synonyms. For more information, see the\ndescription of ST_IsEmpty().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (502,27,'SHOW FUNCTION STATUS','Syntax:\nSHOW FUNCTION STATUS\n    [LIKE \'pattern\' | WHERE expr]\n\nThis statement is similar to SHOW PROCEDURE STATUS but for stored\nfunctions. See [HELP SHOW PROCEDURE STATUS].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-function-status.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-function-status.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (503,38,'LTRIM','Syntax:\nLTRIM(str)\n\nReturns the string str with leading space characters removed.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT LTRIM(\'  barbar\');\n        -> \'barbar\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (504,31,'ST_CROSSES','ST_Crosses(g1,g2)\n\nReturns 1 if g1 spatially crosses g2. Returns NULL if g1 is a Polygon\nor a MultiPolygon, or if g2 is a Point or a MultiPoint. Otherwise,\nreturns 0.\n\nAs of MySQL 5.7.5, this function returns 0 if called with an\ninapplicable geometry argument type combination. For example, it\nreturns 0 if the first argument is a Polygon or MultiPolygon and/or the\nsecond argument is a Point or MultiPoint.\n\nThe term spatially crosses denotes a spatial relation between two given\ngeometries that has the following properties:\n\no The two geometries intersect\n\no Their intersection results in a geometry that has a dimension that is\n  one less than the maximum dimension of the two given geometries\n\no Their intersection is not equal to either of the two given geometries\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (505,4,'ST_MPOLYFROMTEXT','ST_MPolyFromText(wkt[,srid]), ST_MultiPolygonFromText(wkt[,srid])\n\nConstructs a MultiPolygon value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (506,7,'MBRDISJOINT','MBRDisjoint(g1,g2)\n\nReturns 1 or 0 to indicate whether the minimum bounding rectangles of\nthe two geometries g1 and g2 are disjoint (do not intersect).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mysql-specific.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (507,14,'VALUES','Syntax:\nVALUES(col_name)\n\nIn an INSERT ... ON DUPLICATE KEY UPDATE statement, you can use the\nVALUES(col_name) function in the UPDATE clause to refer to column\nvalues from the INSERT portion of the statement. In other words,\nVALUES(col_name) in the UPDATE clause refers to the value of col_name\nthat would be inserted, had no duplicate-key conflict occurred. This\nfunction is especially useful in multiple-row inserts. The VALUES()\nfunction is meaningful only in the ON DUPLICATE KEY UPDATE clause of\nINSERT statements and returns NULL otherwise. See\nhttp://dev.mysql.com/doc/refman/5.7/en/insert-on-duplicate.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> INSERT INTO table (a,b,c) VALUES (1,2,3),(4,5,6)\n    -> ON DUPLICATE KEY UPDATE c=VALUES(a)+VALUES(b);\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (508,28,'CALL','Syntax:\nCALL sp_name([parameter[,...]])\nCALL sp_name[()]\n\nThe CALL statement invokes a stored procedure that was defined\npreviously with CREATE PROCEDURE.\n\nStored procedures that take no arguments can be invoked without\nparentheses. That is, CALL p() and CALL p are equivalent.\n\nCALL can pass back values to its caller using parameters that are\ndeclared as OUT or INOUT parameters. When the procedure returns, a\nclient program can also obtain the number of rows affected for the\nfinal statement executed within the routine: At the SQL level, call the\nROW_COUNT() function; from the C API, call the mysql_affected_rows()\nfunction.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/call.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/call.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (509,12,'ENCODE','Syntax:\nENCODE(str,pass_str)\n\nENCODE() encrypts str using pass_str as the password. The result is a\nbinary string of the same length as str. To decrypt the result, use\nDECODE().\n\n*Note*: The ENCODE() and DECODE() functions are deprecated in MySQL\n5.7, will be removed in a future MySQL release, and should no longer be\nused.\n\nIf you still need to use ENCODE(), a salt value must be used with it to\nreduce risk. For example:\n\nENCODE(\'cleartext\', CONCAT(\'my_random_salt\',\'my_secret_password\'))\n\nA new random salt value must be used whenever a password is updated.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (510,38,'SUBSTRING_INDEX','Syntax:\nSUBSTRING_INDEX(str,delim,count)\n\nReturns the substring from string str before count occurrences of the\ndelimiter delim. If count is positive, everything to the left of the\nfinal delimiter (counting from the left) is returned. If count is\nnegative, everything to the right of the final delimiter (counting from\nthe right) is returned. SUBSTRING_INDEX() performs a case-sensitive\nmatch when searching for delim.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT SUBSTRING_INDEX(\'www.mysql.com\', \'.\', 2);\n        -> \'www.mysql\'\nmysql> SELECT SUBSTRING_INDEX(\'www.mysql.com\', \'.\', -2);\n        -> \'mysql.com\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (511,11,'ST_X','ST_X(p)\n\nReturns the X-coordinate value for the Point object p as a\ndouble-precision number.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-point-property-functions.html\n\n','mysql> SELECT ST_X(POINT(56.7, 53.34));\n+--------------------------+\n| ST_X(POINT(56.7, 53.34)) |\n+--------------------------+\n|                     56.7 |\n+--------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-point-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (512,32,'TIMESTAMPADD','Syntax:\nTIMESTAMPADD(unit,interval,datetime_expr)\n\nAdds the integer expression interval to the date or datetime expression\ndatetime_expr. The unit for interval is given by the unit argument,\nwhich should be one of the following values: MICROSECOND\n(microseconds), SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, QUARTER, or\nYEAR.\n\nThe unit value may be specified using one of keywords as shown, or with\na prefix of SQL_TSI_. For example, DAY and SQL_TSI_DAY both are legal.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT TIMESTAMPADD(MINUTE,1,\'2003-01-02\');\n        -> \'2003-01-02 00:01:00\'\nmysql> SELECT TIMESTAMPADD(WEEK,1,\'2003-01-02\');\n        -> \'2003-01-09\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (513,3,'TRUNCATE','Syntax:\nTRUNCATE(X,D)\n\nReturns the number X, truncated to D decimal places. If D is 0, the\nresult has no decimal point or fractional part. D can be negative to\ncause D digits left of the decimal point of the value X to become zero.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT TRUNCATE(1.223,1);\n        -> 1.2\nmysql> SELECT TRUNCATE(1.999,1);\n        -> 1.9\nmysql> SELECT TRUNCATE(1.999,0);\n        -> 1\nmysql> SELECT TRUNCATE(-1.999,1);\n        -> -1.9\nmysql> SELECT TRUNCATE(122,-2);\n       -> 100\nmysql> SELECT TRUNCATE(10.28*100,0);\n       -> 1028\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (514,27,'SHOW','SHOW has many forms that provide information about databases, tables,\ncolumns, or status information about the server. This section describes\nthose following:\n\nSHOW {BINARY | MASTER} LOGS\nSHOW BINLOG EVENTS [IN \'log_name\'] [FROM pos] [LIMIT [offset,] row_count]\nSHOW CHARACTER SET [like_or_where]\nSHOW COLLATION [like_or_where]\nSHOW [FULL] COLUMNS FROM tbl_name [FROM db_name] [like_or_where]\nSHOW CREATE DATABASE db_name\nSHOW CREATE EVENT event_name\nSHOW CREATE FUNCTION func_name\nSHOW CREATE PROCEDURE proc_name\nSHOW CREATE TABLE tbl_name\nSHOW CREATE TRIGGER trigger_name\nSHOW CREATE VIEW view_name\nSHOW DATABASES [like_or_where]\nSHOW ENGINE engine_name {STATUS | MUTEX}\nSHOW [STORAGE] ENGINES\nSHOW ERRORS [LIMIT [offset,] row_count]\nSHOW EVENTS\nSHOW FUNCTION CODE func_name\nSHOW FUNCTION STATUS [like_or_where]\nSHOW GRANTS FOR user\nSHOW INDEX FROM tbl_name [FROM db_name]\nSHOW MASTER STATUS\nSHOW OPEN TABLES [FROM db_name] [like_or_where]\nSHOW PLUGINS\nSHOW PROCEDURE CODE proc_name\nSHOW PROCEDURE STATUS [like_or_where]\nSHOW PRIVILEGES\nSHOW [FULL] PROCESSLIST\nSHOW PROFILE [types] [FOR QUERY n] [OFFSET n] [LIMIT n]\nSHOW PROFILES\nSHOW SLAVE HOSTS\nSHOW SLAVE STATUS [NONBLOCKING]\nSHOW [GLOBAL | SESSION] STATUS [like_or_where]\nSHOW TABLE STATUS [FROM db_name] [like_or_where]\nSHOW [FULL] TABLES [FROM db_name] [like_or_where]\nSHOW TRIGGERS [FROM db_name] [like_or_where]\nSHOW [GLOBAL | SESSION] VARIABLES [like_or_where]\nSHOW WARNINGS [LIMIT [offset,] row_count]\n\nlike_or_where:\n    LIKE \'pattern\'\n  | WHERE expr\n\nIf the syntax for a given SHOW statement includes a LIKE \'pattern\'\npart, \'pattern\' is a string that can contain the SQL "%" and "_"\nwildcard characters. The pattern is useful for restricting statement\noutput to matching values.\n\nSeveral SHOW statements also accept a WHERE clause that provides more\nflexibility in specifying which rows to display. See\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (515,27,'SHOW VARIABLES','Syntax:\nSHOW [GLOBAL | SESSION] VARIABLES\n    [LIKE \'pattern\' | WHERE expr]\n\n*Note*: As of MySQL 5.7.6, the value of the show_compatibility_56\nsystem variable affects the information available from and privileges\nrequired for the statement described here. For details, see the\ndescription of that variable in\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nSHOW VARIABLES shows the values of MySQL system variables (see\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html).\nThis statement does not require any privilege. It requires only the\nability to connect to the server.\n\nSystem variable information is also available from these sources:\n\no Performance Schema tables. See\n  http://dev.mysql.com/doc/refman/5.7/en/performance-schema-system-vari\n  able-tables.html.\n\no The GLOBAL_VARIABLES and SESSION_VARIABLES tables. See\n  http://dev.mysql.com/doc/refman/5.7/en/variables-table.html.\n\no The mysqladmin variables command. See\n  http://dev.mysql.com/doc/refman/5.7/en/mysqladmin.html.\n\nFor SHOW VARIABLES, a LIKE clause, if present, indicates which variable\nnames to match. A WHERE clause can be given to select rows using more\ngeneral conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html.\n\nSHOW VARIABLES accepts an optional GLOBAL or SESSION variable scope\nmodifier:\n\no With a GLOBAL modifier, the statement displays global system variable\n  values. These are the values used to initialize the corresponding\n  session variables for new connections to MySQL. If a variable has no\n  global value, no value is displayed.\n\no With a SESSION modifier, the statement displays the system varaible\n  values that are in effect for the current connection. If a variable\n  has no session value, the global value is displayed. LOCAL is a\n  synonym for SESSION.\n\no If no modifier is present, the default is SESSION.\n\nThe scope for each system variable is listed at\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nSHOW VARIABLES is subject to a version-dependent display-width limit.\nFor variables with very long values that are not completely displayed,\nuse SELECT as a workaround. For example:\n\nSELECT @@GLOBAL.innodb_data_file_path;\n\nMost system variables can be set at server startup (read-only variables\nsuch as version_comment are exceptions). Many can be changed at runtime\nwith the SET statement. See\nhttp://dev.mysql.com/doc/refman/5.7/en/using-system-variables.html, and\n[HELP SET].\nWith a LIKE clause, the statement displays only rows for those\nvariables with names that match the pattern. To obtain the row for a\nspecific variable, use a LIKE clause as shown:\n\nSHOW VARIABLES LIKE \'max_join_size\';\nSHOW SESSION VARIABLES LIKE \'max_join_size\';\n\nTo get a list of variables whose name match a pattern, use the "%"\nwildcard character in a LIKE clause:\n\nSHOW VARIABLES LIKE \'%size%\';\nSHOW GLOBAL VARIABLES LIKE \'%size%\';\n\nWildcard characters can be used in any position within the pattern to\nbe matched. Strictly speaking, because "_" is a wildcard that matches\nany single character, you should escape it as "\\_" to match it\nliterally. In practice, this is rarely necessary.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-variables.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-variables.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (516,27,'BINLOG','Syntax:\nBINLOG \'str\'\n\nBINLOG is an internal-use statement. It is generated by the mysqlbinlog\nprogram as the printable representation of certain events in binary log\nfiles. (See http://dev.mysql.com/doc/refman/5.7/en/mysqlbinlog.html.)\nThe \'str\' value is a base 64-encoded string the that server decodes to\ndetermine the data change indicated by the corresponding event. This\nstatement requires the SUPER privilege.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/binlog.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/binlog.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (517,31,'ST_DISJOINT','ST_Disjoint(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 is spatially disjoint from (does\nnot intersect) g2.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (518,3,'ATAN2','Syntax:\nATAN(Y,X), ATAN2(Y,X)\n\nReturns the arc tangent of the two variables X and Y. It is similar to\ncalculating the arc tangent of Y / X, except that the signs of both\narguments are used to determine the quadrant of the result.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT ATAN(-2,2);\n        -> -0.78539816339745\nmysql> SELECT ATAN2(PI(),0);\n        -> 1.5707963267949\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (519,15,'AND','Syntax:\nAND, &&\n\nLogical AND. Evaluates to 1 if all operands are nonzero and not NULL,\nto 0 if one or more operands are 0, otherwise NULL is returned.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/logical-operators.html\n\n','mysql> SELECT 1 AND 1;\n        -> 1\nmysql> SELECT 1 AND 0;\n        -> 0\nmysql> SELECT 1 AND NULL;\n        -> NULL\nmysql> SELECT 0 AND NULL;\n        -> 0\nmysql> SELECT NULL AND 0;\n        -> 0\n','http://dev.mysql.com/doc/refman/5.7/en/logical-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (520,32,'HOUR','Syntax:\nHOUR(time)\n\nReturns the hour for time. The range of the return value is 0 to 23 for\ntime-of-day values. However, the range of TIME values actually is much\nlarger, so HOUR can return values greater than 23.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT HOUR(\'10:05:03\');\n        -> 10\nmysql> SELECT HOUR(\'272:59:59\');\n        -> 272\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (521,28,'SELECT','Syntax:\nSELECT\n    [ALL | DISTINCT | DISTINCTROW ]\n      [HIGH_PRIORITY]\n      [MAX_STATEMENT_TIME = N]\n      [STRAIGHT_JOIN]\n      [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT]\n      [SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS]\n    select_expr [, select_expr ...]\n    [FROM table_references\n      [PARTITION partition_list]\n    [WHERE where_condition]\n    [GROUP BY {col_name | expr | position}\n      [ASC | DESC], ... [WITH ROLLUP]]\n    [HAVING where_condition]\n    [ORDER BY {col_name | expr | position}\n      [ASC | DESC], ...]\n    [LIMIT {[offset,] row_count | row_count OFFSET offset}]\n    [PROCEDURE procedure_name(argument_list)]\n    [INTO OUTFILE \'file_name\'\n        [CHARACTER SET charset_name]\n        export_options\n      | INTO DUMPFILE \'file_name\'\n      | INTO var_name [, var_name]]\n    [FOR UPDATE | LOCK IN SHARE MODE]]\n\nSELECT is used to retrieve rows selected from one or more tables, and\ncan include UNION statements and subqueries. See [HELP UNION], and\nhttp://dev.mysql.com/doc/refman/5.7/en/subqueries.html.\n\nThe most commonly used clauses of SELECT statements are these:\n\no Each select_expr indicates a column that you want to retrieve. There\n  must be at least one select_expr.\n\no table_references indicates the table or tables from which to retrieve\n  rows. Its syntax is described in [HELP JOIN].\n\no SELECT supports explicit partition selection using the PARTITION with\n  a list of partitions or subpartitions (or both) following the name of\n  the table in a table_reference (see [HELP JOIN]). In this case, rows\n  are selected only from the partitions listed, and any other\n  partitions of the table are ignored. For more information and\n  examples, see\n  http://dev.mysql.com/doc/refman/5.7/en/partitioning-selection.html.\n\n  SELECT ... PARTITION from tables using storage engines such as MyISAM\n  that perform table-level locks (and thus partition locks) lock only\n  the partitions or subpartitions named by the PARTITION option.\n\n  See\n  http://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-locki\n  ng.html, for more information.\n\no The WHERE clause, if given, indicates the condition or conditions\n  that rows must satisfy to be selected. where_condition is an\n  expression that evaluates to true for each row to be selected. The\n  statement selects all rows if there is no WHERE clause.\n\n  In the WHERE expression, you can use any of the functions and\n  operators that MySQL supports, except for aggregate (summary)\n  functions. See\n  http://dev.mysql.com/doc/refman/5.7/en/expressions.html, and\n  http://dev.mysql.com/doc/refman/5.7/en/functions.html.\n\nSELECT can also be used to retrieve rows computed without reference to\nany table.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/select.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/select.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (522,16,'GROUP_CONCAT','Syntax:\nGROUP_CONCAT(expr)\n\nThis function returns a string result with the concatenated non-NULL\nvalues from a group. It returns NULL if there are no non-NULL values.\nThe full syntax is as follows:\n\nGROUP_CONCAT([DISTINCT] expr [,expr ...]\n             [ORDER BY {unsigned_integer | col_name | expr}\n                 [ASC | DESC] [,col_name ...]]\n             [SEPARATOR str_val])\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','mysql> SELECT student_name,\n    ->     GROUP_CONCAT(test_score)\n    ->     FROM student\n    ->     GROUP BY student_name;\n','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (523,17,'BENCHMARK','Syntax:\nBENCHMARK(count,expr)\n\nThe BENCHMARK() function executes the expression expr repeatedly count\ntimes. It may be used to time how quickly MySQL processes the\nexpression. The result value is always 0. The intended use is from\nwithin the mysql client, which reports query execution times:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','mysql> SELECT BENCHMARK(1000000,ENCODE(\'hello\',\'goodbye\'));\n+----------------------------------------------+\n| BENCHMARK(1000000,ENCODE(\'hello\',\'goodbye\')) |\n+----------------------------------------------+\n|                                            0 |\n+----------------------------------------------+\n1 row in set (4.74 sec)\n','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (524,38,'FROM_BASE64','Syntax:\nFROM_BASE64(str)\n\nTakes a string encoded with the base-64 encoded rules used by\nTO_BASE64() and returns the decoded result as a binary string. The\nresult is NULL if the argument is NULL or not a valid base-64 string.\nSee the description of TO_BASE64() for details about the encoding and\ndecoding rules.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT TO_BASE64(\'abc\'), FROM_BASE64(TO_BASE64(\'abc\'));\n        -> \'JWJj\', \'abc\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (525,27,'SHOW ENGINE','Syntax:\nSHOW ENGINE engine_name {STATUS | MUTEX}\n\nSHOW ENGINE displays operational information about a storage engine. It\nrequires the PROCESS privilege. The statement has these variants:\n\nSHOW ENGINE INNODB STATUS\nSHOW ENGINE INNODB MUTEX\nSHOW ENGINE PERFORMANCE_SCHEMA STATUS\n\nSHOW ENGINE INNODB STATUS displays extensive information from the\nstandard InnoDB Monitor about the state of the InnoDB storage engine.\nFor information about the standard monitor and other InnoDB Monitors\nthat provide information about InnoDB processing, see\nhttp://dev.mysql.com/doc/refman/5.7/en/innodb-monitors.html.\n\nSHOW ENGINE INNODB MUTEX displays InnoDB mutex and rw-lock statistics.\n\n*Note*: InnoDB mutexes and rwlocks can also be monitored using\nPerformance Schema tables. See\nhttp://dev.mysql.com/doc/refman/5.7/en/monitor-innodb-mutex-waits-perfo\nrmance-schema.html.\n\nSHOW ENGINE INNODB MUTEX output was removed in MySQL 5.7.2. It was\nrevised and reintroduced in MySQL 5.7.8.\n\nIn MySQL 5.7.8, mutex statistics collection is configured dynamically\nusing the following options:\n\no To enable the collection of mutex statistics, run:\n\nSET GLOBAL innodb_monitor_enable=\'latch\';\n\no To reset mutex statistics, run:\n\nSET GLOBAL innodb_monitor_reset=\'latch\';\n\no To disable the collection of mutex statistics, run:\n\nSET GLOBAL innodb_monitor_disable=\'latch\';\n\nCollection of mutex statistics for SHOW ENGINE INNODB MUTEX can also be\nenabled by setting innodb_monitor_enable=\'all\', or disabled by setting\ninnodb_monitor_disable=\'all\'.\n\nSHOW ENGINE INNODB MUTEX output has the following columns:\n\no Type\n\n  Always InnoDB.\n\no Name\n\n  Prior to MySQL 5.7.8, the Name field reports the source file where\n  the mutex is implemented, and the line number in the file where the\n  mutex is created. The line number is specific to your version of\n  MySQL. As of MySQL 5.7.8, only the mutex name is reported. File name\n  and line number are still reported for rwlocks.\n\no Status\n\n  The mutex status.\n\n  Prior to MySQL 5.7.8, the Status field displays several values if\n  WITH_DEBUG was defined at MySQL compilation time. If WITH_DEBUG was\n  not defined, the statement displays only the os_waits value. In the\n  latter case (without WITH_DEBUG), the information on which the output\n  is based is insufficient to distinguish regular mutexes and mutexes\n  that protect rwlocks (which permit multiple readers or a single\n  writer). Consequently, the output may appear to contain multiple rows\n  for the same mutex. Pre-MySQL 5.7.8 Status field values include:\n\n  o count indicates how many times the mutex was requested.\n\n  o spin_waits indicates how many times the spinlock had to run.\n\n  o spin_rounds indicates the number of spinlock rounds. (spin_rounds\n    divided by spin_waits provides the average round count.)\n\n  o os_waits indicates the number of operating system waits. This\n    occurs when the spinlock did not work (the mutex was not locked\n    during the spinlock and it was necessary to yield to the operating\n    system and wait).\n\n  o os_yields indicates the number of times a thread trying to lock a\n    mutex gave up its timeslice and yielded to the operating system (on\n    the presumption that permitting other threads to run will free the\n    mutex so that it can be locked).\n\n  o os_wait_times indicates the amount of time (in ms) spent in\n    operating system waits. In MySQL 5.7 timing is disabled and this\n    value is always 0.\n\n  As of MySQL 5.7.8, the Status field reports the number of spins,\n  waits, and calls. Statistics for low-level operating system mutexes,\n  which are implemented outside of InnoDB, are not reported.\n\n  o spins indicates the number of spins.\n\n  o waits indicates the number of mutex waits.\n\n  o calls indicates how many times the mutex was requested.\n\nSHOW ENGINE INNODB MUTEX skips the mutexes and rw-locks of buffer pool\nblocks, as the amount of output can be overwhelming on systems with a\nlarge buffer pool. (There is one mutex and one rw-lock in each 16K\nbuffer pool block, and there are 65,536 blocks per gigabyte.) SHOW\nENGINE INNODB MUTEX also does not list any mutexes or rw-locks that\nhave never been waited on (os_waits=0). Thus, SHOW ENGINE INNODB MUTEX\nonly displays information about mutexes and rw-locks outside of the\nbuffer pool that have caused at least one OS-level wait.\n\nUse SHOW ENGINE PERFORMANCE_SCHEMA STATUS to inspect the internal\noperation of the Performance Schema code:\n\nmysql> SHOW ENGINE PERFORMANCE_SCHEMA STATUS\\G\n...\n*************************** 3. row ***************************\n  Type: performance_schema\n  Name: events_waits_history.size\nStatus: 76\n*************************** 4. row ***************************\n  Type: performance_schema\n  Name: events_waits_history.count\nStatus: 10000\n*************************** 5. row ***************************\n  Type: performance_schema\n  Name: events_waits_history.memory\nStatus: 760000\n...\n*************************** 57. row ***************************\n  Type: performance_schema\n  Name: performance_schema.memory\nStatus: 26459600\n...\n\nThis statement is intended to help the DBA understand the effects that\ndifferent Performance Schema options have on memory requirements.\n\nName values consist of two parts, which name an internal buffer and a\nbuffer attribute, respectively. Interpret buffer names as follows:\n\no An internal buffer that is not exposed as a table is named within\n  parentheses. Examples: (pfs_cond_class).size,\n  (pfs_mutex_class).memory.\n\no An internal buffer that is exposed as a table in the\n  performance_schema database is named after the table, without\n  parentheses. Examples: events_waits_history.size,\n  mutex_instances.count.\n\no A value that applies to the Performance Schema as a whole begins with\n  performance_schema. Example: performance_schema.memory.\n\nBuffer attributes have these meanings:\n\no size is the size of the internal record used by the implementation,\n  such as the size of a row in a table. size values cannot be changed.\n\no count is the number of internal records, such as the number of rows\n  in a table. count values can be changed using Performance Schema\n  configuration options.\n\no For a table, tbl_name.memory is the product of size and count. For\n  the Performance Schema as a whole, performance_schema.memory is the\n  sum of all the memory used (the sum of all other memory values).\n\nSome size and count attributes were named row_size and row_count before\nMySQL 5.7.1.\n\nIn some cases, there is a direct relationship between a Performance\nSchema configuration parameter and a SHOW ENGINE value. For example,\nevents_waits_history_long.count corresponds to\nperformance_schema_events_waits_history_long_size. In other cases, the\nrelationship is more complex. For example, events_waits_history.count\ncorresponds to performance_schema_events_waits_history_size (the number\nof rows per thread) multiplied by\nperformance_schema_max_thread_instances ( the number of threads).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-engine.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-engine.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (526,14,'NAME_CONST','Syntax:\nNAME_CONST(name,value)\n\nReturns the given value. When used to produce a result set column,\nNAME_CONST() causes the column to have the given name. The arguments\nshould be constants.\n\nmysql> SELECT NAME_CONST(\'myname\', 14);\n+--------+\n| myname |\n+--------+\n|     14 |\n+--------+\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (527,14,'RELEASE_LOCK','Syntax:\nRELEASE_LOCK(str)\n\nReleases the lock named by the string str that was obtained with\nGET_LOCK(). Returns 1 if the lock was released, 0 if the lock was not\nestablished by this thread (in which case the lock is not released),\nand NULL if the named lock did not exist. The lock does not exist if it\nwas never obtained by a call to GET_LOCK() or if it has previously been\nreleased.\n\nThe DO statement is convenient to use with RELEASE_LOCK(). See [HELP\nDO].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (528,32,'WEEKDAY','Syntax:\nWEEKDAY(date)\n\nReturns the weekday index for date (0 = Monday, 1 = Tuesday, ... 6 =\nSunday).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT WEEKDAY(\'2008-02-03 22:23:00\');\n        -> 6\nmysql> SELECT WEEKDAY(\'2007-11-06\');\n        -> 1\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (529,32,'TIME_TO_SEC','Syntax:\nTIME_TO_SEC(time)\n\nReturns the time argument, converted to seconds.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT TIME_TO_SEC(\'22:23:00\');\n        -> 80580\nmysql> SELECT TIME_TO_SEC(\'00:39:38\');\n        -> 2378\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (530,32,'CONVERT_TZ','Syntax:\nCONVERT_TZ(dt,from_tz,to_tz)\n\nCONVERT_TZ() converts a datetime value dt from the time zone given by\nfrom_tz to the time zone given by to_tz and returns the resulting\nvalue. Time zones are specified as described in\nhttp://dev.mysql.com/doc/refman/5.7/en/time-zone-support.html. This\nfunction returns NULL if the arguments are invalid.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT CONVERT_TZ(\'2004-01-01 12:00:00\',\'GMT\',\'MET\');\n        -> \'2004-01-01 13:00:00\'\nmysql> SELECT CONVERT_TZ(\'2004-01-01 12:00:00\',\'+00:00\',\'+10:00\');\n        -> \'2004-01-01 22:00:00\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (531,38,'EXPORT_SET','Syntax:\nEXPORT_SET(bits,on,off[,separator[,number_of_bits]])\n\nReturns a string such that for every bit set in the value bits, you get\nan on string and for every bit not set in the value, you get an off\nstring. Bits in bits are examined from right to left (from low-order to\nhigh-order bits). Strings are added to the result from left to right,\nseparated by the separator string (the default being the comma\ncharacter ","). The number of bits examined is given by number_of_bits,\nwhich has a default of 64 if not specified. number_of_bits is silently\nclipped to 64 if larger than 64. It is treated as an unsigned integer,\nso a value of −1 is effectively the same as 64.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT EXPORT_SET(5,\'Y\',\'N\',\',\',4);\n        -> \'Y,N,Y,N\'\nmysql> SELECT EXPORT_SET(6,\'1\',\'0\',\',\',10);\n        -> \'0,1,1,0,0,0,0,0,0,0\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (532,38,'CAST','Syntax:\nCAST(expr AS type)\n\nThe CAST() function takes an expression of any type and produces a\nresult value of a specified type, similar to CONVERT(). See the\ndescription of CONVERT() for more information.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/cast-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/cast-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (533,38,'SOUNDS LIKE','Syntax:\nexpr1 SOUNDS LIKE expr2\n\nThis is the same as SOUNDEX(expr1) = SOUNDEX(expr2).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (534,32,'PERIOD_DIFF','Syntax:\nPERIOD_DIFF(P1,P2)\n\nReturns the number of months between periods P1 and P2. P1 and P2\nshould be in the format YYMM or YYYYMM. Note that the period arguments\nP1 and P2 are not date values.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT PERIOD_DIFF(200802,200703);\n        -> 11\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (535,16,'AVG','Syntax:\nAVG([DISTINCT] expr)\n\nReturns the average value of expr. The DISTINCT option can be used to\nreturn the average of the distinct values of expr.\n\nAVG() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html\n\n','mysql> SELECT student_name, AVG(test_score)\n    ->        FROM student\n    ->        GROUP BY student_name;\n','http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (536,38,'QUOTE','Syntax:\nQUOTE(str)\n\nQuotes a string to produce a result that can be used as a properly\nescaped data value in an SQL statement. The string is returned enclosed\nby single quotation marks and with each instance of backslash ("\\"),\nsingle quote ("\'"), ASCII NUL, and Control+Z preceded by a backslash.\nIf the argument is NULL, the return value is the word "NULL" without\nenclosing single quotation marks.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT QUOTE(\'Don\\\'t!\');\n        -> \'Don\\\'t!\'\nmysql> SELECT QUOTE(NULL);\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (537,20,'IN','Syntax:\nexpr IN (value,...)\n\nReturns 1 if expr is equal to any of the values in the IN list, else\nreturns 0. If all values are constants, they are evaluated according to\nthe type of expr and sorted. The search for the item then is done using\na binary search. This means IN is very quick if the IN value list\nconsists entirely of constants. Otherwise, type conversion takes place\naccording to the rules described in\nhttp://dev.mysql.com/doc/refman/5.7/en/type-conversion.html, but\napplied to all the arguments.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT 2 IN (0,3,5,7);\n        -> 0\nmysql> SELECT \'wefwf\' IN (\'wee\',\'wefwf\',\'weg\');\n        -> 1\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (538,32,'QUARTER','Syntax:\nQUARTER(date)\n\nReturns the quarter of the year for date, in the range 1 to 4.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT QUARTER(\'2008-04-01\');\n        -> 2\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (539,27,'HELP COMMAND','Syntax:\nmysql> help search_string\n\nIf you provide an argument to the help command, mysql uses it as a\nsearch string to access server-side help from the contents of the MySQL\nReference Manual. The proper operation of this command requires that\nthe help tables in the mysql database be initialized with help topic\ninformation (see\nhttp://dev.mysql.com/doc/refman/5.7/en/server-side-help-support.html).\n\nIf there is no match for the search string, the search fails:\n\nmysql> help me\n\nNothing found\nPlease try to run \'help contents\' for a list of all accessible topics\n\nUse help contents to see a list of the help categories:\n\nmysql> help contents\nYou asked for help about help category: "Contents"\nFor more information, type \'help <item>\', where <item> is one of the\nfollowing categories:\n   Account Management\n   Administration\n   Data Definition\n   Data Manipulation\n   Data Types\n   Functions\n   Functions and Modifiers for Use with GROUP BY\n   Geographic Features\n   Language Structure\n   Plugins\n   Storage Engines\n   Stored Routines\n   Table Maintenance\n   Transactions\n   Triggers\n\nIf the search string matches multiple items, mysql shows a list of\nmatching topics:\n\nmysql> help logs\nMany help items for your request exist.\nTo make a more specific request, please type \'help <item>\',\nwhere <item> is one of the following topics:\n   SHOW\n   SHOW BINARY LOGS\n   SHOW ENGINE\n   SHOW LOGS\n\nUse a topic as the search string to see the help entry for that topic:\n\nmysql> help show binary logs\nName: \'SHOW BINARY LOGS\'\nDescription:\nSyntax:\nSHOW BINARY LOGS\nSHOW MASTER LOGS\n\nLists the binary log files on the server. This statement is used as\npart of the procedure described in [purge-binary-logs], that shows how\nto determine which logs can be purged.\n\nmysql> SHOW BINARY LOGS;\n+---------------+-----------+\n| Log_name      | File_size |\n+---------------+-----------+\n| binlog.000015 |    724935 |\n| binlog.000016 |    733481 |\n+---------------+-----------+\n\nThe search string can contain the wildcard characters "%" and "_".\nThese have the same meaning as for pattern-matching operations\nperformed with the LIKE operator. For example, HELP rep% returns a list\nof topics that begin with rep:\n\nmysql> HELP rep%\nMany help items for your request exist.\nTo make a more specific request, please type \'help <item>\',\nwhere <item> is one of the following\ntopics:\n   REPAIR TABLE\n   REPEAT FUNCTION\n   REPEAT LOOP\n   REPLACE\n   REPLACE FUNCTION\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mysql-server-side-help.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/mysql-server-side-help.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (540,7,'JSON_REPLACE','JSON_REPLACE(json_doc, path, val[, path, val] ...)\n\nReplaces existing values in a JSON document and returns the result.\nReturns NULL if any argument is NULL. An error occurs if the json_doc\nargument is not a valid JSON document or any path argument is not a\nvalid path expression or contains a * or ** wildcard.\n\nThe path/value pairs are evaluated left to right. The document produced\nby evaluating one pair becomes the new value against which the next\npair is evaluated.\n\nA path/value pair for an existing path in the document overwrites the\nexisting document value with the new value. A path/value pair for a\nnonexisting path in the document is ignored and has no effect.\n\nFor a comparison of JSON_INSERT(), JSON_REPLACE(), and JSON_SET(), see\nthe discussion of JSON_SET().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html\n\n','mysql> SET @j = \'{ "a": 1, "b": [2, 3]}\';\nmysql> SELECT JSON_REPLACE(@j, \'$.a\', 10, \'$.c\', \'[true, false]\');\n+-----------------------------------------------------+\n| JSON_REPLACE(@j, \'$.a\', 10, \'$.c\', \'[true, false]\') |\n+-----------------------------------------------------+\n| {"a": 10, "b": [2, 3]}                              |\n+-----------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (541,38,'POSITION','Syntax:\nPOSITION(substr IN str)\n\nPOSITION(substr IN str) is a synonym for LOCATE(substr,str).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (542,14,'IS_USED_LOCK','Syntax:\nIS_USED_LOCK(str)\n\nChecks whether the lock named str is in use (that is, locked). If so,\nit returns the connection identifier of the client session that holds\nthe lock. Otherwise, it returns NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (543,4,'POLYFROMTEXT','PolyFromText(wkt[,srid]), PolygonFromText(wkt[,srid])\n\nST_PolyFromText(), ST_PolygonFromText(), PolyFromText(), and\nPolygonFromText() are synonyms. For more information, see the\ndescription of ST_PolyFromText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (544,37,'ST_SRID','ST_SRID(g)\n\nReturns an integer indicating the Spatial Reference System ID for the\ngeometry value g.\n\nIn MySQL, the SRID value is just an integer associated with the\ngeometry value. All calculations are done assuming Euclidean (planar)\ngeometry.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html\n\n','mysql> SELECT ST_SRID(ST_GeomFromText(\'LineString(1 1,2 2)\',101));\n+-----------------------------------------------------+\n| ST_SRID(ST_GeomFromText(\'LineString(1 1,2 2)\',101)) |\n+-----------------------------------------------------+\n|                                                 101 |\n+-----------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (545,10,'ALTER USER','Syntax:\nALTER USER syntax for MySQL 5.7.6 and up:\n\nThe ALTER USER statement modifies MySQL accounts. It provides control\nover account password expiration. As of MySQL 5.7.6, it also provides\ncontrol over authentication, SSL, and resource-limit properties, and\naccount locking and unlocking.\n\nTo use ALTER USER, you must have the global CREATE USER privilege or\nthe UPDATE privilege for the mysql database. When the read_only system\nvariable is enabled, ALTER USER additionally requires the SUPER\nprivilege.\n\nAn error occurs if you try to modify an account that does not exist.\n\nAs of MySQL 5.7.8, the IF EXISTS clause can be used, which causes the\nstatement to produce a warning for each named account that does not\nexist, rather than an error.\n\nALTER USER modifies the mysql.user table row for each affected account\naccording to the options specified in the statement. Unspecified\nproperties retain their current values.\n\nExample 1: Change an account\'s password and expire it. As a result, the\nuser must connect with the named password and choose a new one at the\nnext connection:\n\nALTER USER \'jeffrey\'@\'localhost\'\n  IDENTIFIED BY \'new-password\' PASSWORD EXPIRE;\n\nExample 2: Lock or unlock an account:\n\nALTER USER \'jeffrey\'@\'localhost\' ACCOUNT LOCK;\nALTER USER \'jeffrey\'@\'localhost\' ACCOUNT UNLOCK;\n\nExample 3: Require an account to connect using SSL and establish a\nlimit of 20 connections per hour:\n\nALTER USER \'jeffrey\'@\'localhost\'\n  REQUIRE SSL WITH MAX_CONNECTIONS_PER_HOUR 20;\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/alter-user.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/alter-user.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (546,12,'DES_ENCRYPT','Syntax:\nDES_ENCRYPT(str[,{key_num|key_str}])\n\nEncrypts the string with the given key using the Triple-DES algorithm.\n\nThis function works only if MySQL has been configured with SSL support.\nSee http://dev.mysql.com/doc/refman/5.7/en/ssl-connections.html.\n\nThe encryption key to use is chosen based on the second argument to\nDES_ENCRYPT(), if one was given. With no argument, the first key from\nthe DES key file is used. With a key_num argument, the given key number\n(0 to 9) from the DES key file is used. With a key_str argument, the\ngiven key string is used to encrypt str.\n\nThe key file can be specified with the --des-key-file server option.\n\nThe return string is a binary string where the first character is\nCHAR(128 | key_num). If an error occurs, DES_ENCRYPT() returns NULL.\n\nThe 128 is added to make it easier to recognize an encrypted key. If\nyou use a string key, key_num is 127.\n\nThe string length for the result is given by this formula:\n\nnew_len = orig_len + (8 - (orig_len % 8)) + 1\n\nEach line in the DES key file has the following format:\n\nkey_num des_key_str\n\nEach key_num value must be a number in the range from 0 to 9. Lines in\nthe file may be in any order. des_key_str is the string that is used to\nencrypt the message. There should be at least one space between the\nnumber and the key. The first key is the default key that is used if\nyou do not specify any key argument to DES_ENCRYPT().\n\nYou can tell MySQL to read new key values from the key file with the\nFLUSH DES_KEY_FILE statement. This requires the RELOAD privilege.\n\nOne benefit of having a set of default keys is that it gives\napplications a way to check for the existence of encrypted column\nvalues, without giving the end user the right to decrypt those values.\n\n*Note*: The DES_ENCRYPT() and DES_DECRYPT() functions are deprecated as\nof MySQL 5.7.6, will be removed in a future MySQL release, and should\nno longer be used. Consider using AES_ENCRYPT() and AES_DECRYPT()\ninstead.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT customer_address FROM customer_table \n     > WHERE crypted_credit_card = DES_ENCRYPT(\'credit_card_number\');\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (547,3,'CEIL','Syntax:\nCEIL(X)\n\nCEIL() is a synonym for CEILING().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (548,7,'WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS','Syntax:\nWAIT_UNTIL_SQL_THREAD_AFTER_GTIDS(gtid_set[, timeout][,channel])\n\nWait until the slave SQL thread has executed all of the transactions\nwhose global transaction identifiers are contained in gtid_set (see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html,\nfor a definition of "GTID sets"), or until timeout seconds have\nelapsed, whichever occurs first. timeout is optional; the default\ntimeout is 0 seconds, in which case the function waits until all of the\ntransactions in the GTID set have been executed.\n\nFor more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-gtids.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html\n\n','mysql> SELECT WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:1-5\');\n        -> 5\n','http://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (549,38,'LENGTH','Syntax:\nLENGTH(str)\n\nReturns the length of the string str, measured in bytes. A multibyte\ncharacter counts as multiple bytes. This means that for a string\ncontaining five 2-byte characters, LENGTH() returns 10, whereas\nCHAR_LENGTH() returns 5.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT LENGTH(\'text\');\n        -> 4\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (550,38,'WEIGHT_STRING','Syntax:\nWEIGHT_STRING(str [AS {CHAR|BINARY}(N)] [LEVEL levels] [flags])\n\nlevels: N [ASC|DESC|REVERSE] [, N [ASC|DESC|REVERSE]] ...\n\nThis function returns the weight string for the input string. The\nreturn value is a binary string that represents the sorting and\ncomparison value of the string. It has these properties:\n\no If WEIGHT_STRING(str1) = WEIGHT_STRING(str2), then str1 = str2 (str1\n  and str2 are considered equal)\n\no If WEIGHT_STRING(str1) < WEIGHT_STRING(str2), then str1 < str2 (str1\n  sorts before str2)\n\nWEIGHT_STRING() can be used for testing and debugging of collations,\nespecially if you are adding a new collation. See\nhttp://dev.mysql.com/doc/refman/5.7/en/adding-collation.html.\n\nThe input string, str, is a string expression. If the input is a\nnonbinary (character) string such as a CHAR, VARCHAR, or TEXT value,\nthe return value contains the collation weights for the string. If the\ninput is a binary (byte) string such as a BINARY, VARBINARY, or BLOB\nvalue, the return value is the same as the input (the weight for each\nbyte in a binary string is the byte value). If the input is NULL,\nWEIGHT_STRING() returns NULL.\n\nExamples:\n\nmysql> SET @s = _latin1 \'AB\' COLLATE latin1_swedish_ci;\nmysql> SELECT @s, HEX(@s), HEX(WEIGHT_STRING(@s));\n+------+---------+------------------------+\n| @s   | HEX(@s) | HEX(WEIGHT_STRING(@s)) |\n+------+---------+------------------------+\n| AB   | 4142    | 4142                   |\n+------+---------+------------------------+\n\nmysql> SET @s = _latin1 \'ab\' COLLATE latin1_swedish_ci;\nmysql> SELECT @s, HEX(@s), HEX(WEIGHT_STRING(@s));\n+------+---------+------------------------+\n| @s   | HEX(@s) | HEX(WEIGHT_STRING(@s)) |\n+------+---------+------------------------+\n| ab   | 6162    | 4142                   |\n+------+---------+------------------------+\n\nmysql> SET @s = CAST(\'AB\' AS BINARY);\nmysql> SELECT @s, HEX(@s), HEX(WEIGHT_STRING(@s));\n+------+---------+------------------------+\n| @s   | HEX(@s) | HEX(WEIGHT_STRING(@s)) |\n+------+---------+------------------------+\n| AB   | 4142    | 4142                   |\n+------+---------+------------------------+\n\nmysql> SET @s = CAST(\'ab\' AS BINARY);\nmysql> SELECT @s, HEX(@s), HEX(WEIGHT_STRING(@s));\n+------+---------+------------------------+\n| @s   | HEX(@s) | HEX(WEIGHT_STRING(@s)) |\n+------+---------+------------------------+\n| ab   | 6162    | 6162                   |\n+------+---------+------------------------+\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (551,31,'ST_EQUALS','ST_Equals(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 is spatially equal to g2.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html\n\n','mysql> SET @g1 = POINT(1,1), @g2 = POINT(2,2);\nmysql> SELECT ST_Equals(@g1, @g1), ST_Equals(@g1, @g2);\n+---------------------+---------------------+\n| ST_Equals(@g1, @g1) | ST_Equals(@g1, @g2) |\n+---------------------+---------------------+\n|                   1 |                   0 |\n+---------------------+---------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-object-shapes.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (552,40,'ALTER EVENT','Syntax:\nALTER\n    [DEFINER = { user | CURRENT_USER }]\n    EVENT event_name\n    [ON SCHEDULE schedule]\n    [ON COMPLETION [NOT] PRESERVE]\n    [RENAME TO new_event_name]\n    [ENABLE | DISABLE | DISABLE ON SLAVE]\n    [COMMENT \'comment\']\n    [DO event_body]\n\nThe ALTER EVENT statement changes one or more of the characteristics of\nan existing event without the need to drop and recreate it. The syntax\nfor each of the DEFINER, ON SCHEDULE, ON COMPLETION, COMMENT, ENABLE /\nDISABLE, and DO clauses is exactly the same as when used with CREATE\nEVENT. (See [HELP CREATE EVENT].)\n\nAny user can alter an event defined on a database for which that user\nhas the EVENT privilege. When a user executes a successful ALTER EVENT\nstatement, that user becomes the definer for the affected event.\n\nALTER EVENT works only with an existing event:\n\nmysql> ALTER EVENT no_such_event \n     >     ON SCHEDULE \n     >       EVERY \'2:3\' DAY_HOUR;\nERROR 1517 (HY000): Unknown event \'no_such_event\'\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/alter-event.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/alter-event.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (553,32,'DATE_SUB','Syntax:\nDATE_SUB(date,INTERVAL expr unit)\n\nSee the description for DATE_ADD().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (554,19,'|','Syntax:\n|\n\nBitwise OR:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/bit-functions.html\n\n','mysql> SELECT 29 | 15;\n        -> 31\n','http://dev.mysql.com/doc/refman/5.7/en/bit-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (555,4,'GEOMFROMTEXT','GeomFromText(wkt[,srid]), GeometryFromText(wkt[,srid])\n\nST_GeomFromText(), ST_GeometryFromText(), GeomFromText(), and\nGeometryFromText() are synonyms. For more information, see the\ndescription of ST_GeomFromText().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (556,14,'UUID_SHORT','Syntax:\nUUID_SHORT()\n\nReturns a "short" universal identifier as a 64-bit unsigned integer\n(rather than a string-form 128-bit identifier as returned by the UUID()\nfunction).\n\nThe value of UUID_SHORT() is guaranteed to be unique if the following\nconditions hold:\n\no The server_id of the current host is unique among your set of master\n  and slave servers\n\no server_id is between 0 and 255\n\no You do not set back your system time for your server between mysqld\n  restarts\n\no You do not invoke UUID_SHORT() on average more than 16 million times\n  per second between mysqld restarts\n\nThe UUID_SHORT() return value is constructed this way:\n\n  (server_id & 255) << 56\n+ (server_startup_time_in_seconds << 24)\n+ incremented_variable++;\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> SELECT UUID_SHORT();\n        -> 92395783831158784\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (557,32,'DATEDIFF','Syntax:\nDATEDIFF(expr1,expr2)\n\nDATEDIFF() returns expr1 − expr2 expressed as a value in days from\none date to the other. expr1 and expr2 are date or date-and-time\nexpressions. Only the date parts of the values are used in the\ncalculation.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DATEDIFF(\'2007-12-31 23:59:59\',\'2007-12-30\');\n        -> 1\nmysql> SELECT DATEDIFF(\'2010-11-30 23:59:59\',\'2010-12-31\');\n        -> -31\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (558,40,'DROP PROCEDURE','Syntax:\nDROP {PROCEDURE | FUNCTION} [IF EXISTS] sp_name\n\nThis statement is used to drop a stored procedure or function. That is,\nthe specified routine is removed from the server. You must have the\nALTER ROUTINE privilege for the routine. (If the\nautomatic_sp_privileges system variable is enabled, that privilege and\nEXECUTE are granted automatically to the routine creator when the\nroutine is created and dropped from the creator when the routine is\ndropped. See\nhttp://dev.mysql.com/doc/refman/5.7/en/stored-routines-privileges.html.\n)\n\nThe IF EXISTS clause is a MySQL extension. It prevents an error from\noccurring if the procedure or function does not exist. A warning is\nproduced that can be viewed with SHOW WARNINGS.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/drop-procedure.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/drop-procedure.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (559,7,'ST_LATFROMGEOHASH','ST_LatFromGeoHash(geohash_str)\n\nReturns the latitude from a geohash string value, as a DOUBLE value in\nthe range [−90, 90]. The result is NULL if any argument is NULL. An\nerror occurs if the argument is invalid.\n\nThe ST_LatFromGeoHash() decoding function reads no more than 433\ncharacters from the geohash_str argument. That represents the upper\nlimit on information in the internal representation of coordinate\nvalues. Characters past the 433rd are ignored, even if they are\notherwise illegal and produce an error.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-geohash-functions.html\n\n','mysql> SELECT ST_LatFromGeoHash(ST_GeoHash(45,-20,10));\n+------------------------------------------+\n| ST_LatFromGeoHash(ST_GeoHash(45,-20,10)) |\n+------------------------------------------+\n|                                      -20 |\n+------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-geohash-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (560,7,'ST_GEOMFROMGEOJSON','ST_GeomFromGeoJSON(str [, options [, srid]])\n\nParses a string str representing a GeoJSON object and returns a\ngeometry.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-geojson-functions.html\n\n','mysql> SET @json = \'{ "type": "Point", "coordinates": [102.0, 0.0]}\';\nmysql> SELECT ST_AsText(ST_GeomFromGeoJSON(@json));\n+--------------------------------------+\n| ST_AsText(ST_GeomFromGeoJSON(@json)) |\n+--------------------------------------+\n| POINT(102 0)                         |\n+--------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/spatial-geojson-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (561,5,'INSTALL PLUGIN','Syntax:\nINSTALL PLUGIN plugin_name SONAME \'shared_library_name\'\n\nThis statement installs a server plugin. It requires the INSERT\nprivilege for the mysql.plugin table.\n\nplugin_name is the name of the plugin as defined in the plugin\ndescriptor structure contained in the library file (see\nhttp://dev.mysql.com/doc/refman/5.7/en/plugin-data-structures.html).\nPlugin names are not case sensitive. For maximal compatibility, plugin\nnames should be limited to ASCII letters, digits, and underscore\nbecause they are used in C source files, shell command lines, M4 and\nBourne shell scripts, and SQL environments.\n\nshared_library_name is the name of the shared library that contains the\nplugin code. The name includes the file name extension (for example,\nlibmyplugin.so, libmyplugin.dll, or libmyplugin.dylib).\n\nThe shared library must be located in the plugin directory (the\ndirectory named by the plugin_dir system variable). The library must be\nin the plugin directory itself, not in a subdirectory. By default,\nplugin_dir is the plugin directory under the directory named by the\npkglibdir configuration variable, but it can be changed by setting the\nvalue of plugin_dir at server startup. For example, set its value in a\nmy.cnf file:\n\n[mysqld]\nplugin_dir=/path/to/plugin/directory\n\nIf the value of plugin_dir is a relative path name, it is taken to be\nrelative to the MySQL base directory (the value of the basedir system\nvariable).\n\nINSTALL PLUGIN loads and initializes the plugin code to make the plugin\navailable for use. A plugin is initialized by executing its\ninitialization function, which handles any setup that the plugin must\nperform before it can be used. When the server shuts down, it executes\nthe deinitialization function for each plugin that is loaded so that\nthe plugin has a chance to perform any final cleanup.\n\nINSTALL PLUGIN also registers the plugin by adding a line that\nindicates the plugin name and library file name to the mysql.plugin\ntable. At server startup, the server loads and initializes any plugin\nthat is listed in the mysql.plugin table. This means that a plugin is\ninstalled with INSTALL PLUGIN only once, not every time the server\nstarts. Plugin loading at startup does not occur if the server is\nstarted with the --skip-grant-tables option.\n\nA plugin library can contain multiple plugins. For each of them to be\ninstalled, use a separate INSTALL PLUGIN statement. Each statement\nnames a different plugin, but all of them specify the same library\nname.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/install-plugin.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/install-plugin.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (562,24,'DECLARE CURSOR','Syntax:\nDECLARE cursor_name CURSOR FOR select_statement\n\nThis statement declares a cursor and associates it with a SELECT\nstatement that retrieves the rows to be traversed by the cursor. To\nfetch the rows later, use a FETCH statement. The number of columns\nretrieved by the SELECT statement must match the number of output\nvariables specified in the FETCH statement.\n\nThe SELECT statement cannot have an INTO clause.\n\nCursor declarations must appear before handler declarations and after\nvariable and condition declarations.\n\nA stored program may contain multiple cursor declarations, but each\ncursor declared in a given block must have a unique name. For an\nexample, see http://dev.mysql.com/doc/refman/5.7/en/cursors.html.\n\nFor information available through SHOW statements, it is possible in\nmany cases to obtain equivalent information by using a cursor with an\nINFORMATION_SCHEMA table.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/declare-cursor.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/declare-cursor.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (563,28,'LOAD DATA','Syntax:\nLOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE \'file_name\'\n    [REPLACE | IGNORE]\n    INTO TABLE tbl_name\n    [PARTITION (partition_name,...)]\n    [CHARACTER SET charset_name]\n    [{FIELDS | COLUMNS}\n        [TERMINATED BY \'string\']\n        [[OPTIONALLY] ENCLOSED BY \'char\']\n        [ESCAPED BY \'char\']\n    ]\n    [LINES\n        [STARTING BY \'string\']\n        [TERMINATED BY \'string\']\n    ]\n    [IGNORE number {LINES | ROWS}]\n    [(col_name_or_user_var,...)]\n    [SET col_name = expr,...]\n\nThe LOAD DATA INFILE statement reads rows from a text file into a table\nat a very high speed. LOAD DATA INFILE is the complement of SELECT ...\nINTO OUTFILE. (See\nhttp://dev.mysql.com/doc/refman/5.7/en/select-into.html.) To write data\nfrom a table to a file, use SELECT ... INTO OUTFILE. To read the file\nback into a table, use LOAD DATA INFILE. The syntax of the FIELDS and\nLINES clauses is the same for both statements. Both clauses are\noptional, but FIELDS must precede LINES if both are specified.\n\nYou can also load data files by using the mysqlimport utility; it\noperates by sending a LOAD DATA INFILE statement to the server. The\n--local option causes mysqlimport to read data files from the client\nhost. You can specify the --compress option to get better performance\nover slow networks if the client and server support the compressed\nprotocol. See http://dev.mysql.com/doc/refman/5.7/en/mysqlimport.html.\n\nFor more information about the efficiency of INSERT versus LOAD DATA\nINFILE and speeding up LOAD DATA INFILE, see\nhttp://dev.mysql.com/doc/refman/5.7/en/insert-speed.html.\n\nThe file name must be given as a literal string. On Windows, specify\nbackslashes in path names as forward slashes or doubled backslashes.\nThe character_set_filesystem system variable controls the\ninterpretation of the file name.\n\nLOAD DATA supports explicit partition selection using the PARTITION\noption with a comma-separated list of more or more names of partitions,\nsubpartitions, or both. When this option is used, if any rows from the\nfile cannot be inserted into any of the partitions or subpartitions\nnamed in the list, the statement fails with the error Found a row not\nmatching the given partition set. For more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-selection.html.\n\nFor partitioned tables using storage engines that employ table locks,\nsuch as MyISAM, LOAD DATA cannot prune any partition locks. This does\nnot apply to tables using storage engines which employ row-level\nlocking, such as InnoDB. For more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-locking\n.html.\n\nThe server uses the character set indicated by the\ncharacter_set_database system variable to interpret the information in\nthe file. SET NAMES and the setting of character_set_client do not\naffect interpretation of input. If the contents of the input file use a\ncharacter set that differs from the default, it is usually preferable\nto specify the character set of the file by using the CHARACTER SET\nclause. A character set of binary specifies "no conversion."\n\nLOAD DATA INFILE interprets all fields in the file as having the same\ncharacter set, regardless of the data types of the columns into which\nfield values are loaded. For proper interpretation of file contents,\nyou must ensure that it was written with the correct character set. For\nexample, if you write a data file with mysqldump -T or by issuing a\nSELECT ... INTO OUTFILE statement in mysql, be sure to use a\n--default-character-set option so that output is written in the\ncharacter set to be used when the file is loaded with LOAD DATA INFILE.\n\n*Note*: It is not possible to load data files that use the ucs2, utf16,\nutf16le, or utf32 character set.\n\nIf you use LOW_PRIORITY, execution of the LOAD DATA statement is\ndelayed until no other clients are reading from the table. This affects\nonly storage engines that use only table-level locking (such as MyISAM,\nMEMORY, and MERGE).\n\nIf you specify CONCURRENT with a MyISAM table that satisfies the\ncondition for concurrent inserts (that is, it contains no free blocks\nin the middle), other threads can retrieve data from the table while\nLOAD DATA is executing. This option affects the performance of LOAD\nDATA a bit, even if no other thread is using the table at the same\ntime.\n\nWith row-based replication, CONCURRENT is replicated regardless of\nMySQL version. With statement-based replication CONCURRENT is not\nreplicated prior to MySQL 5.5.1 (see Bug #34628). For more information,\nsee\nhttp://dev.mysql.com/doc/refman/5.7/en/replication-features-load-data.h\ntml.\n\nThe LOCAL keyword affects expected location of the file and error\nhandling, as described later. LOCAL works only if your server and your\nclient both have been configured to permit it. For example, if mysqld\nwas started with --local-infile=0, LOCAL does not work. See\nhttp://dev.mysql.com/doc/refman/5.7/en/load-data-local.html.\n\nThe LOCAL keyword affects where the file is expected to be found:\n\no If LOCAL is specified, the file is read by the client program on the\n  client host and sent to the server. The file can be given as a full\n  path name to specify its exact location. If given as a relative path\n  name, the name is interpreted relative to the directory in which the\n  client program was started.\n\n  When using LOCAL with LOAD DATA, a copy of the file is created in the\n  server\'s temporary directory. This is not the directory determined by\n  the value of tmpdir or slave_load_tmpdir, but rather the operating\n  system\'s temporary directory, and is not configurable in the MySQL\n  Server. (Typically the system temporary directory is /tmp on Linux\n  systems and C:\\WINDOWS\\TEMP on Windows.) Lack of sufficient space for\n  the copy in this directory can cause the LOAD DATA LOCAL statement to\n  fail.\n\no If LOCAL is not specified, the file must be located on the server\n  host and is read directly by the server. The server uses the\n  following rules to locate the file:\n\n  o If the file name is an absolute path name, the server uses it as\n    given.\n\n  o If the file name is a relative path name with one or more leading\n    components, the server searches for the file relative to the\n    server\'s data directory.\n\n  o If a file name with no leading components is given, the server\n    looks for the file in the database directory of the default\n    database.\n\nIn the non-LOCAL case, these rules mean that a file named as\n./myfile.txt is read from the server\'s data directory, whereas the file\nnamed as myfile.txt is read from the database directory of the default\ndatabase. For example, if db1 is the default database, the following\nLOAD DATA statement reads the file data.txt from the database directory\nfor db1, even though the statement explicitly loads the file into a\ntable in the db2 database:\n\nLOAD DATA INFILE \'data.txt\' INTO TABLE db2.my_table;\n\nFor security reasons, when reading text files located on the server,\nthe files must either reside in the database directory or be readable\nby the user account used to run the server. Also, to use LOAD DATA\nINFILE on server files, you must have the FILE privilege. See\nhttp://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html. For\nnon-LOCAL load operations, if the secure_file_priv system variable is\nset to a nonempty directory name, the file to be loaded must be located\nin that directory.\n\nUsing LOCAL is a bit slower than letting the server access the files\ndirectly, because the contents of the file must be sent over the\nconnection by the client to the server. On the other hand, you do not\nneed the FILE privilege to load local files.\n\nLOCAL also affects error handling:\n\no With LOAD DATA INFILE, data-interpretation and duplicate-key errors\n  terminate the operation.\n\no With LOAD DATA LOCAL INFILE, data-interpretation and duplicate-key\n  errors become warnings and the operation continues because the server\n  has no way to stop transmission of the file in the middle of the\n  operation. For duplicate-key errors, this is the same as if IGNORE is\n  specified. IGNORE is explained further later in this section.\n\nThe REPLACE and IGNORE keywords control handling of input rows that\nduplicate existing rows on unique key values:\n\no If you specify REPLACE, input rows replace existing rows. In other\n  words, rows that have the same value for a primary key or unique\n  index as an existing row. See [HELP REPLACE].\n\no If you specify IGNORE, rows that duplicate an existing row on a\n  unique key value are discarded. For more information, see\n  http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#ignore-strict-co\n  mparison.\n\no If you do not specify either option, the behavior depends on whether\n  the LOCAL keyword is specified. Without LOCAL, an error occurs when a\n  duplicate key value is found, and the rest of the text file is\n  ignored. With LOCAL, the default behavior is the same as if IGNORE is\n  specified; this is because the server has no way to stop transmission\n  of the file in the middle of the operation.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/load-data.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/load-data.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (564,32,'LOCALTIME','Syntax:\nLOCALTIME, LOCALTIME([fsp])\n\nLOCALTIME and LOCALTIME() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (565,33,'ST_GEOMFROMWKB','ST_GeomFromWKB(wkb[,srid]), ST_GeometryFromWKB(wkb[,srid])\n\nConstructs a geometry value of any type using its WKB representation\nand SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (566,12,'SHA1','Syntax:\nSHA1(str), SHA(str)\n\nCalculates an SHA-1 160-bit checksum for the string, as described in\nRFC 3174 (Secure Hash Algorithm). The value is returned as a string of\n40 hex digits, or NULL if the argument was NULL. One of the possible\nuses for this function is as a hash key. See the notes at the beginning\nof this section about storing hash values efficiently. You can also use\nSHA1() as a cryptographic function for storing passwords. SHA() is\nsynonymous with SHA1().\n\nThe return value is a nonbinary string in the connection character set.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SELECT SHA1(\'abc\');\n        -> \'a9993e364706816aba3e25717850c26c9cd0d89d\'\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (567,23,'BLOB','BLOB[(M)]\n\nA BLOB column with a maximum length of 65,535 (216 − 1) bytes. Each\nBLOB value is stored using a 2-byte length prefix that indicates the\nnumber of bytes in the value.\n\nAn optional length M can be given for this type. If this is done, MySQL\ncreates the column as the smallest BLOB type large enough to hold\nvalues M bytes long.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (568,12,'PASSWORD','Syntax:\nPASSWORD(str)\n\n*Note*: This function is deprecated as of MySQL 5.7.6 and will be\nremoved in a future MySQL release.\n\nReturns a hashed password string calculated from the cleartext password\nstr. The return value is a nonbinary string in the connection character\nset, or NULL if the argument is NULL. This function is the SQL\ninterface to the algorithm used by the server to encrypt MySQL\npasswords for storage in the mysql.user grant table.\n\nThe old_passwords system variable controls the password hashing method\nused by the PASSWORD() function. It also influences password hashing\nperformed by CREATE USER and GRANT statements that specify a password\nusing an IDENTIFIED BY clause.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SET old_passwords = 0;\nmysql> SELECT PASSWORD(\'mypass\'), OLD_PASSWORD(\'mypass\');\n+-------------------------------------------+------------------------+\n| PASSWORD(\'mypass\')                        | OLD_PASSWORD(\'mypass\') |\n+-------------------------------------------+------------------------+\n| *6C8989366EAF75BB670AD8EA7A7FC1176A95CEF4 | 6f8c114b58f2ce9e       |\n+-------------------------------------------+------------------------+\n\nmysql> SET old_passwords = 1;\nmysql> SELECT PASSWORD(\'mypass\'), OLD_PASSWORD(\'mypass\');\n+--------------------+------------------------+\n| PASSWORD(\'mypass\') | OLD_PASSWORD(\'mypass\') |\n+--------------------+------------------------+\n| 6f8c114b58f2ce9e   | 6f8c114b58f2ce9e       |\n+--------------------+------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (569,32,'UTC_DATE','Syntax:\nUTC_DATE, UTC_DATE()\n\nReturns the current UTC date as a value in \'YYYY-MM-DD\' or YYYYMMDD\nformat, depending on whether the function is used in a string or\nnumeric context.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT UTC_DATE(), UTC_DATE() + 0;\n        -> \'2003-08-14\', 20030814\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (570,37,'DIMENSION','Dimension(g)\n\nST_Dimension() and Dimension() are synonyms. For more information, see\nthe description of ST_Dimension().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (571,23,'BIT','BIT[(M)]\n\nA bit-field type. M indicates the number of bits per value, from 1 to\n64. The default is 1 if M is omitted.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (572,8,'XA','Syntax:\nXA {START|BEGIN} xid [JOIN|RESUME]\n\nXA END xid [SUSPEND [FOR MIGRATE]]\n\nXA PREPARE xid\n\nXA COMMIT xid [ONE PHASE]\n\nXA ROLLBACK xid\n\nXA RECOVER [CONVERT XID]\n\nFor XA START, the JOIN and RESUME clauses are not supported.\n\nFor XA END the SUSPEND [FOR MIGRATE] clause is not supported.\n\nEach XA statement begins with the XA keyword, and most of them require\nan xid value. An xid is an XA transaction identifier. It indicates\nwhich transaction the statement applies to. xid values are supplied by\nthe client, or generated by the MySQL server. An xid value has from one\nto three parts:\n\nxid: gtrid [, bqual [, formatID ]]\n\ngtrid is a global transaction identifier, bqual is a branch qualifier,\nand formatID is a number that identifies the format used by the gtrid\nand bqual values. As indicated by the syntax, bqual and formatID are\noptional. The default bqual value is \'\' if not given. The default\nformatID value is 1 if not given.\n\ngtrid and bqual must be string literals, each up to 64 bytes (not\ncharacters) long. gtrid and bqual can be specified in several ways. You\ncan use a quoted string (\'ab\'), hex string (0x6162, X\'ab\'), or bit\nvalue (b\'nnnn\').\n\nformatID is an unsigned integer.\n\nThe gtrid and bqual values are interpreted in bytes by the MySQL\nserver\'s underlying XA support routines. However, while an SQL\nstatement containing an XA statement is being parsed, the server works\nwith some specific character set. To be safe, write gtrid and bqual as\nhex strings.\n\nxid values typically are generated by the Transaction Manager. Values\ngenerated by one TM must be different from values generated by other\nTMs. A given TM must be able to recognize its own xid values in a list\nof values returned by the XA RECOVER statement.\n\nFor XA START xid starts an XA transaction with the given xid value.\nEach XA transaction must have a unique xid value, so the value must not\ncurrently be used by another XA transaction. Uniqueness is assessed\nusing the gtrid and bqual values. All following XA statements for the\nXA transaction must be specified using the same xid value as that given\nin the XA START statement. If you use any of those statements but\nspecify an xid value that does not correspond to some existing XA\ntransaction, an error occurs.\n\nOne or more XA transactions can be part of the same global transaction.\nAll XA transactions within a given global transaction must use the same\ngtrid value in the xid value. For this reason, gtrid values must be\nglobally unique so that there is no ambiguity about which global\ntransaction a given XA transaction is part of. The bqual part of the\nxid value must be different for each XA transaction within a global\ntransaction. (The requirement that bqual values be different is a\nlimitation of the current MySQL XA implementation. It is not part of\nthe XA specification.)\n\nThe XA RECOVER statement returns information for those XA transactions\non the MySQL server that are in the PREPARED state. (See\nhttp://dev.mysql.com/doc/refman/5.7/en/xa-states.html.) The output\nincludes a row for each such XA transaction on the server, regardless\nof which client started it.\n\nXA RECOVER output rows look like this (for an example xid value\nconsisting of the parts \'abc\', \'def\', and 7):\n\nmysql> XA RECOVER;\n+----------+--------------+--------------+--------+\n| formatID | gtrid_length | bqual_length | data   |\n+----------+--------------+--------------+--------+\n|        7 |            3 |            3 | abcdef |\n+----------+--------------+--------------+--------+\n\nThe output columns have the following meanings:\n\no formatID is the formatID part of the transaction xid\n\no gtrid_length is the length in bytes of the gtrid part of the xid\n\no bqual_length is the length in bytes of the bqual part of the xid\n\no data is the concatenation of the gtrid and bqual parts of the xid\n\nXID values may contain nonprintable characters. As of MySQL 5.7.5, XA\nRECOVER permits an optional CONVERT XID clause so that clients can\nrequest XID values in hexadecimal.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/xa-statements.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/xa-statements.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (573,31,'EQUALS','Equals(g1,g2)\n\nMBREquals() and Equals() are synonyms. For more information, see the\ndescription of MBREquals().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mbr.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/spatial-relation-functions-mbr.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (574,2,'CENTROID','Centroid(mpoly)\n\nST_Centroid() and Centroid() are synonyms. For more information, see\nthe description of ST_Centroid().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (575,38,'OCTET_LENGTH','Syntax:\nOCTET_LENGTH(str)\n\nOCTET_LENGTH() is a synonym for LENGTH().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (576,32,'UTC_TIMESTAMP','Syntax:\nUTC_TIMESTAMP, UTC_TIMESTAMP([fsp])\n\nReturns the current UTC date and time as a value in \'YYYY-MM-DD\nHH:MM:SS\' or YYYYMMDDHHMMSS format, depending on whether the function\nis used in a string or numeric context.\n\nIf the fsp argument is given to specify a fractional seconds precision\nfrom 0 to 6, the return value includes a fractional seconds part of\nthat many digits.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT UTC_TIMESTAMP(), UTC_TIMESTAMP() + 0;\n        -> \'2003-08-14 18:08:04\', 20030814180804.000000\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (577,12,'AES_ENCRYPT','Syntax:\nAES_ENCRYPT(str,key_str[,init_vector])\n\nAES_ENCRYPT() and AES_DECRYPT() implement encryption and decryption of\ndata using the official AES (Advanced Encryption Standard) algorithm,\npreviously known as "Rijndael." The AES standard permits various key\nlengths. By default these functions implement AES with a 128-bit key\nlength. As of MySQL 5.7.4, key lengths of 196 or 256 bits can be used,\nas described later. The key length is a trade off between performance\nand security.\n\nAES_ENCRYPT() encrypts the string str using the key string key_str and\nreturns a binary string containing the encrypted output. AES_DECRYPT()\ndecrypts the encrypted string crypt_str using the key string key_str\nand returns the original cleartext string. If either function argument\nis NULL, the function returns NULL.\n\nThe str and crypt_str arguments can be any length, and padding is\nautomatically added to str so it is a multiple of a block as required\nby block-based algorithms such as AES. This padding is automatically\nremoved by the AES_DECRYPT() function. The length of crypt_str can be\ncalculated using this formula:\n\n16 * (trunc(string_length / 16) + 1)\n\nFor a key length of 128 bits, the most secure way to pass a key to the\nkey_str argument is to create a truly random 128-bit value and pass it\nas a binary value. For example:\n\nINSERT INTO t\nVALUES (1,AES_ENCRYPT(\'text\',UNHEX(\'F3229A0B371ED2D9441B830D21A390C3\')));\n\nA passphrase can be used to generate an AES key by hashing the\npassphrase. For example:\n\nINSERT INTO t VALUES (1,AES_ENCRYPT(\'text\', SHA2(\'My secret passphrase\',512)));\n\nDo not pass a password or passphrase directly to crypt_str, hash it\nfirst. Previous versions of this documentation suggested the former\napproach, but it is no longer recommended as the examples shown here\nare more secure.\n\nIf AES_DECRYPT() detects invalid data or incorrect padding, it returns\nNULL. However, it is possible for AES_DECRYPT() to return a non-NULL\nvalue (possibly garbage) if the input data or the key is invalid.\n\nAs of MySQL 5.7.4, AES_ENCRYPT() and AES_DECRYPT() permit control of\nthe block encryption mode and take an optional init_vector\ninitialization vector argument:\n\no The block_encryption_mode system variable controls the mode for\n  block-based encryption algorithms. Its default value is aes-128-ecb,\n  which signifies encryption using a key length of 128 bits and ECB\n  mode. For a description of the permitted values of this variable, see\n  http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\no The optional init_vector argument provides an initialization vector\n  for block encryption modes that require it.\n\nFor modes that require the optional init_vector argument, it must be 16\nbytes or longer (bytes in excess of 16 are ignored). An error occurs if\ninit_vector is missing.\n\nFor modes that do not require init_vector, it is ignored and a warning\nis generated if it is specified.\n\nA random string of bytes to use for the initialization vector can be\nproduced by calling RANDOM_BYTES(16). For encryption modes that require\nan initialization vector, the same vector must be used for encryption\nand decryption.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html\n\n','mysql> SET block_encryption_mode = \'aes-256-cbc\';\nmysql> SET @key_str = SHA2(\'My secret passphrase\',512);\nmysql> SET @init_vector = RANDOM_BYTES(16);\nmysql> SET @crypt_str = AES_ENCRYPT(\'text\',@key_str,@init_vector);\nmysql> SELECT AES_DECRYPT(@crypt_str,@key_str,@init_vector);\n+-----------------------------------------------+\n| AES_DECRYPT(@crypt_str,@key_str,@init_vector) |\n+-----------------------------------------------+\n| text                                          |\n+-----------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (578,3,'+','Syntax:\n+\n\nAddition:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html\n\n','mysql> SELECT 3+5;\n        -> 8\n','http://dev.mysql.com/doc/refman/5.7/en/arithmetic-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (579,7,'GTID_SUBTRACT','Syntax:\nGTID_SUBTRACT(set,subset)\n\nGiven two sets of global transaction IDs subset and set, returns only\nthose GTIDs from set that are not in subset.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html\n\n','mysql> SELECT GTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    ->     \'3E11FA47-71CA-11E1-9E33-C80AA9429562:21\')\\G\n*************************** 1. row ***************************\nGTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    \'3E11FA47-71CA-11E1-9E33-C80AA9429562:21\'): 3e11fa47-71ca-11e1-9e33-c80aa9429562:22-57\n1 row in set (0.00 sec)\n\nmysql> SELECT GTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    ->     \'3E11FA47-71CA-11E1-9E33-C80AA9429562:20-25\')\\G\n*************************** 1. row ***************************\nGTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    \'3E11FA47-71CA-11E1-9E33-C80AA9429562:20-25\'): 3e11fa47-71ca-11e1-9e33-c80aa9429562:26-57\n1 row in set (0.00 sec)\n\nmysql> SELECT GTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    ->     \'3E11FA47-71CA-11E1-9E33-C80AA9429562:23-24\')\\G\n*************************** 1. row ***************************\nGTID_SUBTRACT(\'3E11FA47-71CA-11E1-9E33-C80AA9429562:21-57\', \n    \'3E11FA47-71CA-11E1-9E33-C80AA9429562:23-24\'): 3e11fa47-71ca-11e1-9e33-c80aa9429562:21-22:25-57\n1 row in set (0.01 sec)\n','http://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (580,14,'INET_NTOA','Syntax:\nINET_NTOA(expr)\n\nGiven a numeric IPv4 network address in network byte order, returns the\ndotted-quad string representation of the address as a nonbinary string\nin the connection character set. INET_NTOA() returns NULL if it does\nnot understand its argument.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> SELECT INET_NTOA(167773449);\n        -> \'10.0.5.9\'\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (581,32,'DAYOFWEEK','Syntax:\nDAYOFWEEK(date)\n\nReturns the weekday index for date (1 = Sunday, 2 = Monday, ..., 7 =\nSaturday). These index values correspond to the ODBC standard.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DAYOFWEEK(\'2007-02-03\');\n        -> 7\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (582,3,'CEILING','Syntax:\nCEILING(X)\n\nReturns the smallest integer value not less than X.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT CEILING(1.23);\n        -> 2\nmysql> SELECT CEILING(-1.23);\n        -> -1\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (583,27,'SHOW PROCESSLIST','Syntax:\nSHOW [FULL] PROCESSLIST\n\nSHOW PROCESSLIST shows you which threads are running. You can also get\nthis information from the INFORMATION_SCHEMA PROCESSLIST table or the\nmysqladmin processlist command. If you have the PROCESS privilege, you\ncan see all threads. Otherwise, you can see only your own threads (that\nis, threads associated with the MySQL account that you are using). If\nyou do not use the FULL keyword, only the first 100 characters of each\nstatement are shown in the Info field.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-processlist.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-processlist.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (584,33,'LINEFROMWKB','LineFromWKB(wkb[,srid]), LineStringFromWKB(wkb[,srid])\n\nST_LineFromWKB(), ST_LineStringFromWKB(), LineFromWKB(), and\nLineStringFromWKB() are synonyms. For more information, see the\ndescription of ST_LineFromWKB().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (585,37,'GEOMETRYTYPE','GeometryType(g)\n\nST_GeometryType() and GeometryType() are synonyms. For more\ninformation, see the description of ST_GeometryType().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (586,40,'CREATE VIEW','Syntax:\nCREATE\n    [OR REPLACE]\n    [ALGORITHM = {UNDEFINED | MERGE | TEMPTABLE}]\n    [DEFINER = { user | CURRENT_USER }]\n    [SQL SECURITY { DEFINER | INVOKER }]\n    VIEW view_name [(column_list)]\n    AS select_statement\n    [WITH [CASCADED | LOCAL] CHECK OPTION]\n\nThe CREATE VIEW statement creates a new view, or replaces an existing\nview if the OR REPLACE clause is given. If the view does not exist,\nCREATE OR REPLACE VIEW is the same as CREATE VIEW. If the view does\nexist, CREATE OR REPLACE VIEW is the same as ALTER VIEW.\n\nThe select_statement is a SELECT statement that provides the definition\nof the view. (Selecting from the view selects, in effect, using the\nSELECT statement.) The select_statement can select from base tables or\nother views.\n\nThe view definition is "frozen" at creation time. Changes to the\nunderlying tables afterward do not affect the view definition. For\nexample, if a view is defined as SELECT * on a table, new columns added\nto the table later do not become part of the view.\n\nThe ALGORITHM clause affects how MySQL processes the view. The DEFINER\nand SQL SECURITY clauses specify the security context to be used when\nchecking access privileges at view invocation time. The WITH CHECK\nOPTION clause can be given to constrain inserts or updates to rows in\ntables referenced by the view. These clauses are described later in\nthis section.\n\nThe CREATE VIEW statement requires the CREATE VIEW privilege for the\nview, and some privilege for each column selected by the SELECT\nstatement. For columns used elsewhere in the SELECT statement, you must\nhave the SELECT privilege. If the OR REPLACE clause is present, you\nmust also have the DROP privilege for the view. CREATE VIEW might also\nrequire the SUPER privilege, depending on the DEFINER value, as\ndescribed later in this section.\n\nWhen a view is referenced, privilege checking occurs as described later\nin this section.\n\nA view belongs to a database. By default, a new view is created in the\ndefault database. To create the view explicitly in a given database,\nuse db_name.view_name syntax to qualify the view name with the database\nname:\n\nmysql> CREATE VIEW test.v AS SELECT * FROM t;\n\nWithin a database, base tables and views share the same namespace, so a\nbase table and a view cannot have the same name.\n\nColumns retrieved by the SELECT statement can be simple references to\ntable columns, or expressions that use functions, constant values,\noperators, and so forth.\n\nA view must have unique column names with no duplicates, just like a\nbase table. By default, the names of the columns retrieved by the\nSELECT statement are used for the view column names. To define explicit\nnames for the view columns, the optional column_list clause can be\ngiven as a list of comma-separated identifiers. The number of names in\ncolumn_list must be the same as the number of columns retrieved by the\nSELECT statement.\n\nUnqualified table or view names in the SELECT statement are interpreted\nwith respect to the default database. A view can refer to tables or\nviews in other databases by qualifying the table or view name with the\nappropriate database name.\n\nA view can be created from many kinds of SELECT statements. It can\nrefer to base tables or other views. It can use joins, UNION, and\nsubqueries. The SELECT need not even refer to any tables.\n\nThe following example defines a view that selects two columns from\nanother table as well as an expression calculated from those columns:\n\nmysql> CREATE TABLE t (qty INT, price INT);\nmysql> INSERT INTO t VALUES(3, 50);\nmysql> CREATE VIEW v AS SELECT qty, price, qty*price AS value FROM t;\nmysql> SELECT * FROM v;\n+------+-------+-------+\n| qty  | price | value |\n+------+-------+-------+\n|    3 |    50 |   150 |\n+------+-------+-------+\n\nA view definition is subject to the following restrictions:\n\no Before MySQL 5.7.7, the SELECT statement cannot contain a subquery in\n  the FROM clause.\n\no The SELECT statement cannot refer to system variables or user-defined\n  variables.\n\no Within a stored program, the SELECT statement cannot refer to program\n  parameters or local variables.\n\no The SELECT statement cannot refer to prepared statement parameters.\n\no Any table or view referred to in the definition must exist. After the\n  view has been created, it is possible to drop a table or view that\n  the definition refers to. In this case, use of the view results in an\n  error. To check a view definition for problems of this kind, use the\n  CHECK TABLE statement.\n\no The definition cannot refer to a TEMPORARY table, and you cannot\n  create a TEMPORARY view.\n\no You cannot associate a trigger with a view.\n\no Aliases for column names in the SELECT statement are checked against\n  the maximum column length of 64 characters (not the maximum alias\n  length of 256 characters).\n\nORDER BY is permitted in a view definition, but it is ignored if you\nselect from a view using a statement that has its own ORDER BY.\n\nFor other options or clauses in the definition, they are added to the\noptions or clauses of the statement that references the view, but the\neffect is undefined. For example, if a view definition includes a LIMIT\nclause, and you select from the view using a statement that has its own\nLIMIT clause, it is undefined which limit applies. This same principle\napplies to options such as ALL, DISTINCT, or SQL_SMALL_RESULT that\nfollow the SELECT keyword, and to clauses such as INTO, FOR UPDATE,\nLOCK IN SHARE MODE, and PROCEDURE.\n\nIf you create a view and then change the query processing environment\nby changing system variables, that may affect the results you get from\nthe view:\n\nmysql> CREATE VIEW v (mycol) AS SELECT \'abc\';\nQuery OK, 0 rows affected (0.01 sec)\n\nmysql> SET sql_mode = \'\';\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT "mycol" FROM v;\n+-------+\n| mycol |\n+-------+\n| mycol |\n+-------+\n1 row in set (0.01 sec)\n\nmysql> SET sql_mode = \'ANSI_QUOTES\';\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT "mycol" FROM v;\n+-------+\n| mycol |\n+-------+\n| abc   |\n+-------+\n1 row in set (0.00 sec)\n\nThe DEFINER and SQL SECURITY clauses determine which MySQL account to\nuse when checking access privileges for the view when a statement is\nexecuted that references the view. The valid SQL SECURITY\ncharacteristic values are DEFINER (the default) and INVOKER. These\nindicate that the required privileges must be held by the user who\ndefined or invoked the view, respectively.\n\nIf a user value is given for the DEFINER clause, it should be a MySQL\naccount specified as \'user_name\'@\'host_name\' (the same format used in\nthe GRANT statement), CURRENT_USER, or CURRENT_USER(). The default\nDEFINER value is the user who executes the CREATE VIEW statement. This\nis the same as specifying DEFINER = CURRENT_USER explicitly.\n\nIf you specify the DEFINER clause, these rules determine the valid\nDEFINER user values:\n\no If you do not have the SUPER privilege, the only valid user value is\n  your own account, either specified literally or by using\n  CURRENT_USER. You cannot set the definer to some other account.\n\no If you have the SUPER privilege, you can specify any syntactically\n  valid account name. If the account does not exist, a warning is\n  generated.\n\no Although it is possible to create a view with a nonexistent DEFINER\n  account, an error occurs when the view is referenced if the SQL\n  SECURITY value is DEFINER but the definer account does not exist.\n\nFor more information about view security, see\nhttp://dev.mysql.com/doc/refman/5.7/en/stored-programs-security.html.\n\nWithin a view definition, CURRENT_USER returns the view\'s DEFINER value\nby default. For views defined with the SQL SECURITY INVOKER\ncharacteristic, CURRENT_USER returns the account for the view\'s\ninvoker. For information about user auditing within views, see\nhttp://dev.mysql.com/doc/refman/5.7/en/account-activity-auditing.html.\n\nWithin a stored routine that is defined with the SQL SECURITY DEFINER\ncharacteristic, CURRENT_USER returns the routine\'s DEFINER value. This\nalso affects a view defined within such a routine, if the view\ndefinition contains a DEFINER value of CURRENT_USER.\n\nMySQL checks view privileges like this:\n\no At view definition time, the view creator must have the privileges\n  needed to use the top-level objects accessed by the view. For\n  example, if the view definition refers to table columns, the creator\n  must have some privilege for each column in the select list of the\n  definition, and the SELECT privilege for each column used elsewhere\n  in the definition. If the definition refers to a stored function,\n  only the privileges needed to invoke the function can be checked. The\n  privileges required at function invocation time can be checked only\n  as it executes: For different invocations, different execution paths\n  within the function might be taken.\n\no The user who references a view must have appropriate privileges to\n  access it (SELECT to select from it, INSERT to insert into it, and so\n  forth.)\n\no When a view has been referenced, privileges for objects accessed by\n  the view are checked against the privileges held by the view DEFINER\n  account or invoker, depending on whether the SQL SECURITY\n  characteristic is DEFINER or INVOKER, respectively.\n\no If reference to a view causes execution of a stored function,\n  privilege checking for statements executed within the function depend\n  on whether the function SQL SECURITY characteristic is DEFINER or\n  INVOKER. If the security characteristic is DEFINER, the function runs\n  with the privileges of the DEFINER account. If the characteristic is\n  INVOKER, the function runs with the privileges determined by the\n  view\'s SQL SECURITY characteristic.\n\nExample: A view might depend on a stored function, and that function\nmight invoke other stored routines. For example, the following view\ninvokes a stored function f():\n\nCREATE VIEW v AS SELECT * FROM t WHERE t.id = f(t.name);\n\nSuppose that f() contains a statement such as this:\n\nIF name IS NULL then\n  CALL p1();\nELSE\n  CALL p2();\nEND IF;\n\nThe privileges required for executing statements within f() need to be\nchecked when f() executes. This might mean that privileges are needed\nfor p1() or p2(), depending on the execution path within f(). Those\nprivileges must be checked at runtime, and the user who must possess\nthe privileges is determined by the SQL SECURITY values of the view v\nand the function f().\n\nThe DEFINER and SQL SECURITY clauses for views are extensions to\nstandard SQL. In standard SQL, views are handled using the rules for\nSQL SECURITY DEFINER. The standard says that the definer of the view,\nwhich is the same as the owner of the view\'s schema, gets applicable\nprivileges on the view (for example, SELECT) and may grant them. MySQL\nhas no concept of a schema "owner", so MySQL adds a clause to identify\nthe definer. The DEFINER clause is an extension where the intent is to\nhave what the standard has; that is, a permanent record of who defined\nthe view. This is why the default DEFINER value is the account of the\nview creator.\n\nThe optional ALGORITHM clause is a MySQL extension to standard SQL. It\naffects how MySQL processes the view. ALGORITHM takes three values:\nMERGE, TEMPTABLE, or UNDEFINED. The default algorithm is UNDEFINED if\nno ALGORITHM clause is present. For more information, see\nhttp://dev.mysql.com/doc/refman/5.7/en/view-algorithms.html.\n\nSome views are updatable. That is, you can use them in statements such\nas UPDATE, DELETE, or INSERT to update the contents of the underlying\ntable. For a view to be updatable, there must be a one-to-one\nrelationship between the rows in the view and the rows in the\nunderlying table. There are also certain other constructs that make a\nview nonupdatable.\n\nA generated column in a view is considered updatable because it is\npossible to assign to it. However, if such a column is updated\nexplicitly, the only permitted value is DEFAULT. For information about\ngenerated columns, see\nhttp://dev.mysql.com/doc/refman/5.7/en/create-table.html#create-table-g\nenerated-columns.\n\nThe WITH CHECK OPTION clause can be given for an updatable view to\nprevent inserts or updates to rows except those for which the WHERE\nclause in the select_statement is true.\n\nIn a WITH CHECK OPTION clause for an updatable view, the LOCAL and\nCASCADED keywords determine the scope of check testing when the view is\ndefined in terms of another view. The LOCAL keyword restricts the CHECK\nOPTION only to the view being defined. CASCADED causes the checks for\nunderlying views to be evaluated as well. When neither keyword is\ngiven, the default is CASCADED.\n\nFor more information about updatable views and the WITH CHECK OPTION\nclause, see\nhttp://dev.mysql.com/doc/refman/5.7/en/view-updatability.html, and\nhttp://dev.mysql.com/doc/refman/5.7/en/view-check-option.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/create-view.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/create-view.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (587,38,'TRIM','Syntax:\nTRIM([{BOTH | LEADING | TRAILING} [remstr] FROM] str), TRIM([remstr\nFROM] str)\n\nReturns the string str with all remstr prefixes or suffixes removed. If\nnone of the specifiers BOTH, LEADING, or TRAILING is given, BOTH is\nassumed. remstr is optional and, if not specified, spaces are removed.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT TRIM(\'  bar   \');\n        -> \'bar\'\nmysql> SELECT TRIM(LEADING \'x\' FROM \'xxxbarxxx\');\n        -> \'barxxx\'\nmysql> SELECT TRIM(BOTH \'x\' FROM \'xxxbarxxx\');\n        -> \'bar\'\nmysql> SELECT TRIM(TRAILING \'xyz\' FROM \'barxxyz\');\n        -> \'barx\'\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (588,14,'INET6_NTOA','Syntax:\nINET6_NTOA(expr)\n\nGiven an IPv6 or IPv4 network address represented in numeric form as a\nbinary string, returns the string representation of the address as a\nnonbinary string in the connection character set. If the argument is\nnot a valid address, INET6_NTOA() returns NULL.\n\nINET6_NTOA() has these properties:\n\no It does not use operating system functions to perform conversions,\n  thus the output string is platform independent.\n\no The return string has a maximum length of 39 (4 x 8 + 7). Given this\n  statement:\n\nCREATE TABLE t AS SELECT INET6_NTOA(expr) AS c1;\n\n  The resulting table would have this definition:\n\nCREATE TABLE t (c1 VARCHAR(39) CHARACTER SET utf8 DEFAULT NULL);\n\no The return string uses lowercase letters for IPv6 addresses.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html\n\n','mysql> SELECT INET6_NTOA(INET6_ATON(\'fdfe::5a55:caff:fefa:9089\'));\n        -> \'fdfe::5a55:caff:fefa:9089\'\nmysql> SELECT INET6_NTOA(INET6_ATON(\'10.0.5.9\'));\n        -> \'10.0.5.9\'\n\nmysql> SELECT INET6_NTOA(UNHEX(\'FDFE0000000000005A55CAFFFEFA9089\'));\n        -> \'fdfe::5a55:caff:fefa:9089\'\nmysql> SELECT INET6_NTOA(UNHEX(\'0A000509\'));\n        -> \'10.0.5.9\'\n','http://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (589,24,'SIGNAL','Syntax:\nSIGNAL condition_value\n    [SET signal_information_item\n    [, signal_information_item] ...]\n\ncondition_value:\n    SQLSTATE [VALUE] sqlstate_value\n  | condition_name\n\nsignal_information_item:\n    condition_information_item_name = simple_value_specification\n\ncondition_information_item_name:\n    CLASS_ORIGIN\n  | SUBCLASS_ORIGIN\n  | MESSAGE_TEXT\n  | MYSQL_ERRNO\n  | CONSTRAINT_CATALOG\n  | CONSTRAINT_SCHEMA\n  | CONSTRAINT_NAME\n  | CATALOG_NAME\n  | SCHEMA_NAME\n  | TABLE_NAME\n  | COLUMN_NAME\n  | CURSOR_NAME\n\ncondition_name, simple_value_specification:\n    (see following discussion)\n\nSIGNAL is the way to "return" an error. SIGNAL provides error\ninformation to a handler, to an outer portion of the application, or to\nthe client. Also, it provides control over the error\'s characteristics\n(error number, SQLSTATE value, message). Without SIGNAL, it is\nnecessary to resort to workarounds such as deliberately referring to a\nnonexistent table to cause a routine to return an error.\n\nNo special privileges are required to execute the SIGNAL statement.\n\nTo retrieve information from the diagnostics area, use the GET\nDIAGNOSTICS statement (see [HELP GET DIAGNOSTICS]). For information\nabout the diagnostics area, see\nhttp://dev.mysql.com/doc/refman/5.7/en/diagnostics-area.html.\n\nThe condition_value in a SIGNAL statement indicates the error value to\nbe returned. It can be an SQLSTATE value (a 5-character string literal)\nor a condition_name that refers to a named condition previously defined\nwith DECLARE ... CONDITION (see [HELP DECLARE CONDITION]).\n\nAn SQLSTATE value can indicate errors, warnings, or "not found." The\nfirst two characters of the value indicate its error class, as\ndiscussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/signal.html#signal-condition-inf\normation-items. Some signal values cause statement termination; see\nhttp://dev.mysql.com/doc/refman/5.7/en/signal.html#signal-effects.\n\nThe SQLSTATE value for a SIGNAL statement should not start with \'00\'\nbecause such values indicate success and are not valid for signaling an\nerror. This is true whether the SQLSTATE value is specified directly in\nthe SIGNAL statement or in a named condition referred to in the\nstatement. If the value is invalid, a Bad SQLSTATE error occurs.\n\nTo signal a generic SQLSTATE value, use \'45000\', which means "unhandled\nuser-defined exception."\n\nThe SIGNAL statement optionally includes a SET clause that contains\nmultiple signal items, in a comma-separated list of\ncondition_information_item_name = simple_value_specification\nassignments.\n\nEach condition_information_item_name may be specified only once in the\nSET clause. Otherwise, a Duplicate condition information item error\noccurs.\n\nValid simple_value_specification designators can be specified using\nstored procedure or function parameters, stored program local variables\ndeclared with DECLARE, user-defined variables, system variables, or\nliterals. A character literal may include a _charset introducer.\n\nFor information about permissible condition_information_item_name\nvalues, see\nhttp://dev.mysql.com/doc/refman/5.7/en/signal.html#signal-condition-inf\normation-items.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/signal.html\n\n','CREATE PROCEDURE p (pval INT)\nBEGIN\n  DECLARE specialty CONDITION FOR SQLSTATE \'45000\';\n  IF pval = 0 THEN\n    SIGNAL SQLSTATE \'01000\';\n  ELSEIF pval = 1 THEN\n    SIGNAL SQLSTATE \'45000\'\n      SET MESSAGE_TEXT = \'An error occurred\';\n  ELSEIF pval = 2 THEN\n    SIGNAL specialty\n      SET MESSAGE_TEXT = \'An error occurred\';\n  ELSE\n    SIGNAL SQLSTATE \'01000\'\n      SET MESSAGE_TEXT = \'A warning occurred\', MYSQL_ERRNO = 1000;\n    SIGNAL SQLSTATE \'45000\'\n      SET MESSAGE_TEXT = \'An error occurred\', MYSQL_ERRNO = 1001;\n  END IF;\nEND;\n','http://dev.mysql.com/doc/refman/5.7/en/signal.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (590,8,'SAVEPOINT','Syntax:\nSAVEPOINT identifier\nROLLBACK [WORK] TO [SAVEPOINT] identifier\nRELEASE SAVEPOINT identifier\n\nInnoDB supports the SQL statements SAVEPOINT, ROLLBACK TO SAVEPOINT,\nRELEASE SAVEPOINT and the optional WORK keyword for ROLLBACK.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/savepoint.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/savepoint.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (591,26,'ST_NUMGEOMETRIES','ST_NumGeometries(gc)\n\nReturns the number of geometries in the GeometryCollection value gc.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-geometrycollection-property-functions.html\n\n','mysql> SET @gc = \'GeometryCollection(Point(1 1),LineString(2 2, 3 3))\';\nmysql> SELECT ST_NumGeometries(ST_GeomFromText(@gc));\n+----------------------------------------+\n| ST_NumGeometries(ST_GeomFromText(@gc)) |\n+----------------------------------------+\n|                                      2 |\n+----------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-geometrycollection-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (592,7,'JSON_DEPTH','JSON_DEPTH(json_doc)\n\nReturns the maximum depth of a JSON document. Returns NULL if the\nargument is NULL. An error occurs if the argument is not a valid JSON\ndocument.\n\nAn empty array, empty object, or scalar value has depth 1. A nonempty\narray containing only elements of depth 1 or nonempty object containing\nonly member values of depth 1 has depth 2. Otherwise, a JSON document\nhas depth greater than 2.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-attribute-functions.html\n\n','mysql> SELECT JSON_DEPTH(\'{}\'), JSON_DEPTH(\'[]\'), JSON_DEPTH(\'true\');\n+------------------+------------------+--------------------+\n| JSON_DEPTH(\'{}\') | JSON_DEPTH(\'[]\') | JSON_DEPTH(\'true\') |\n+------------------+------------------+--------------------+\n|                1 |                1 |                  1 |\n+------------------+------------------+--------------------+\nmysql> SELECT JSON_DEPTH(\'[10, 20]\'), JSON_DEPTH(\'[[], {}]\');\n+------------------------+------------------------+\n| JSON_DEPTH(\'[10, 20]\') | JSON_DEPTH(\'[[], {}]\') |\n+------------------------+------------------------+\n|                      2 |                      2 |\n+------------------------+------------------------+\nmysql> SELECT JSON_DEPTH(\'[10, {"a": 20}]\');\n+-------------------------------+\n| JSON_DEPTH(\'[10, {"a": 20}]\') |\n+-------------------------------+\n|                             3 |\n+-------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-attribute-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (593,24,'LABELS','Syntax:\n[begin_label:] BEGIN\n    [statement_list]\nEND [end_label]\n\n[begin_label:] LOOP\n    statement_list\nEND LOOP [end_label]\n\n[begin_label:] REPEAT\n    statement_list\nUNTIL search_condition\nEND REPEAT [end_label]\n\n[begin_label:] WHILE search_condition DO\n    statement_list\nEND WHILE [end_label]\n\nLabels are permitted for BEGIN ... END blocks and for the LOOP, REPEAT,\nand WHILE statements. Label use for those statements follows these\nrules:\n\no begin_label must be followed by a colon.\n\no begin_label can be given without end_label. If end_label is present,\n  it must be the same as begin_label.\n\no end_label cannot be given without begin_label.\n\no Labels at the same nesting level must be distinct.\n\no Labels can be up to 16 characters long.\n\nTo refer to a label within the labeled construct, use an ITERATE or\nLEAVE statement. The following example uses those statements to\ncontinue iterating or terminate the loop:\n\nCREATE PROCEDURE doiterate(p1 INT)\nBEGIN\n  label1: LOOP\n    SET p1 = p1 + 1;\n    IF p1 < 10 THEN ITERATE label1; END IF;\n    LEAVE label1;\n  END LOOP label1;\nEND;\n\nThe scope of a block label does not include the code for handlers\ndeclared within the block. For details, see [HELP DECLARE HANDLER].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/statement-labels.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/statement-labels.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (594,33,'MPOINTFROMWKB','MPointFromWKB(wkb[,srid]), MultiPointFromWKB(wkb[,srid])\n\nST_MPointFromWKB(), ST_MultiPointFromWKB(), MPointFromWKB(), and\nMultiPointFromWKB() are synonyms. For more information, see the\ndescription of ST_MPointFromWKB().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (595,40,'ALTER TABLE','Syntax:\nALTER [IGNORE] TABLE tbl_name\n    [alter_specification [, alter_specification] ...]\n    [partition_options]\n\nalter_specification:\n    table_options\n  | ADD [COLUMN] col_name column_definition\n        [FIRST | AFTER col_name ]\n  | ADD [COLUMN] (col_name column_definition,...)\n  | ADD {INDEX|KEY} [index_name]\n        [index_type] (index_col_name,...) [index_option] ...\n  | ADD [CONSTRAINT [symbol]] PRIMARY KEY\n        [index_type] (index_col_name,...) [index_option] ...\n  | ADD [CONSTRAINT [symbol]]\n        UNIQUE [INDEX|KEY] [index_name]\n        [index_type] (index_col_name,...) [index_option] ...\n  | ADD FULLTEXT [INDEX|KEY] [index_name]\n        (index_col_name,...) [index_option] ...\n  | ADD SPATIAL [INDEX|KEY] [index_name]\n        (index_col_name,...) [index_option] ...\n  | ADD [CONSTRAINT [symbol]]\n        FOREIGN KEY [index_name] (index_col_name,...)\n        reference_definition\n  | ALGORITHM [=] {DEFAULT|INPLACE|COPY}\n  | ALTER [COLUMN] col_name {SET DEFAULT literal | DROP DEFAULT}\n  | CHANGE [COLUMN] old_col_name new_col_name column_definition\n        [FIRST|AFTER col_name]\n  | LOCK [=] {DEFAULT|NONE|SHARED|EXCLUSIVE}\n  | MODIFY [COLUMN] col_name column_definition\n        [FIRST | AFTER col_name]\n  | DROP [COLUMN] col_name\n  | DROP PRIMARY KEY\n  | DROP {INDEX|KEY} index_name\n  | DROP FOREIGN KEY fk_symbol\n  | DISABLE KEYS\n  | ENABLE KEYS\n  | RENAME [TO|AS] new_tbl_name\n  | RENAME {INDEX|KEY} old_index_name TO new_index_name\n  | ORDER BY col_name [, col_name] ...\n  | CONVERT TO CHARACTER SET charset_name [COLLATE collation_name]\n  | [DEFAULT] CHARACTER SET [=] charset_name [COLLATE [=] collation_name]\n  | DISCARD TABLESPACE\n  | IMPORT TABLESPACE\n  | FORCE\n  | {WITHOUT|WITH} VALIDATION\n  | ADD PARTITION (partition_definition)\n  | DROP PARTITION partition_names\n  | DISCARD PARTITION {partition_names | ALL} TABLESPACE\n  | IMPORT PARTITION {partition_names | ALL} TABLESPACE\n  | TRUNCATE PARTITION {partition_names | ALL}\n  | COALESCE PARTITION number\n  | REORGANIZE PARTITION partition_names INTO (partition_definitions)\n  | EXCHANGE PARTITION partition_name WITH TABLE tbl_name [{WITH|WITHOUT} VALIDATION]\n  | ANALYZE PARTITION {partition_names | ALL}\n  | CHECK PARTITION {partition_names | ALL}\n  | OPTIMIZE PARTITION {partition_names | ALL}\n  | REBUILD PARTITION {partition_names | ALL}\n  | REPAIR PARTITION {partition_names | ALL}\n  | REMOVE PARTITIONING\n  | UPGRADE PARTITIONING\n\nindex_col_name:\n    col_name [(length)] [ASC | DESC]\n\nindex_type:\n    USING {BTREE | HASH}\n\nindex_option:\n    KEY_BLOCK_SIZE [=] value\n  | index_type\n  | WITH PARSER parser_name\n  | COMMENT \'string\'\n\ntable_options:\n    table_option [[,] table_option] ...  (see CREATE TABLE options)\n\npartition_options:\n    (see CREATE TABLE options)\n\nALTER TABLE changes the structure of a table. For example, you can add\nor delete columns, create or destroy indexes, change the type of\nexisting columns, or rename columns or the table itself. You can also\nchange characteristics such as the storage engine used for the table or\nthe table comment.\n\nFollowing the table name, specify the alterations to be made. If none\nare given, ALTER TABLE does nothing.\n\nThe syntax for many of the permissible alterations is similar to\nclauses of the CREATE TABLE statement. See [HELP CREATE TABLE], for\nmore information.\n\ntable_options signifies table options of the kind that can be used in\nthe CREATE TABLE statement, such as ENGINE, AUTO_INCREMENT,\nAVG_ROW_LENGTH, MAX_ROWS, or ROW_FORMAT. For a list of all table\noptions and a description of each, see [HELP CREATE TABLE]. However,\nALTER TABLE ignores the DATA DIRECTORY and INDEX DIRECTORY table\noptions.\n\npartition_options signifies options that can be used with partitioned\ntables for repartitioning, for adding, dropping, discarding, importing,\nmerging, and splitting partitions, and for performing partitioning\nmaintenance. It is possible for an ALTER TABLE statement to contain a\nPARTITION BY or REMOVE PARTITIONING clause in an addition to other\nalter specifications, but the PARTITION BY or REMOVE PARTITIONING\nclause must be specified last after any other specifications. The ADD\nPARTITION, DROP PARTITION, DISCARD PARTITION, IMPORT PARTITION,\nCOALESCE PARTITION, REORGANIZE PARTITION, EXCHANGE PARTITION, ANALYZE\nPARTITION, CHECK PARTITION, and REPAIR PARTITION options cannot be\ncombined with other alter specifications in a single ALTER TABLE, since\nthe options just listed act on individual partitions. For more\ninformation about partition options, see [HELP CREATE TABLE], and\nhttp://dev.mysql.com/doc/refman/5.7/en/alter-table-partition-operations\n.html. For information about and examples of ALTER TABLE ... EXCHANGE\nPARTITION statements, see\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-management-exchange\n.html.\n\nPrior to MySQL 5.7.6, partitioned InnoDB tables used the generic\nha_partition partitioning handler employed by MyISAM and other storage\nengines not supplying their own partitioning handlers; in MySQL 5.7.6\nand later, such tables are created using the InnoDB storage engine\'s\nown (or "native") partitioning handler. Beginning with MySQL 5.7.9, you\ncan upgrade an InnoDB table that was created in MySQL 5.7.6 or earlier\n(that is, created using ha_partition) to the InnoDB native partition\nhandler using ALTER TABLE ... UPGRADE PARTITIONING. (Bug #76734, Bug\n#20727344) This version of ALTER TABLE does not accept any other\noptions and can be used only on a single table at a time.\n\n*Note*: You can also use mysql_upgrade in MySQL 5.7.9 or later to\nupgrade older partitioned InnoDB tables to the native partitioning\nhandler.\n\nSome operations may result in warnings if attempted on a table for\nwhich the storage engine does not support the operation. These warnings\ncan be displayed with SHOW WARNINGS. See [HELP SHOW WARNINGS].\n\nFor information on troubleshooting ALTER TABLE, see\nhttp://dev.mysql.com/doc/refman/5.7/en/alter-table-problems.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/alter-table.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/alter-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (596,23,'CHAR BYTE','The CHAR BYTE data type is an alias for the BINARY data type. This is a\ncompatibility feature.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (597,4,'ST_MLINEFROMTEXT','ST_MLineFromText(wkt[,srid]), ST_MultiLineStringFromText(wkt[,srid])\n\nConstructs a MultiLineString value using its WKT representation and\nSRID.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (598,20,'>','Syntax:\n>\n\nGreater than:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT 2 > 2;\n        -> 0\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (599,21,'ANALYZE TABLE','Syntax:\nANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE\n    tbl_name [, tbl_name] ...\n\nANALYZE TABLE analyzes and stores the key distribution for a table.\nDuring the analysis, the table is locked with a read lock for InnoDB\nand MyISAM. This statement works with InnoDB, NDB, and MyISAM tables.\nFor MyISAM tables, this statement is equivalent to using myisamchk\n--analyze. This statement does not work with views.\n\nFor more information on how the analysis works within InnoDB, see\nhttp://dev.mysql.com/doc/refman/5.7/en/innodb-persistent-stats.html and\nhttp://dev.mysql.com/doc/refman/5.7/en/innodb-analyze-table-complexity.\nhtml. Also see\nhttp://dev.mysql.com/doc/refman/5.7/en/innodb-restrictions.html. In\nparticular, when you enable the innodb_stats_persistent option, you\nmust run ANALYZE TABLE after loading substantial data into an InnoDB\ntable, or creating a new index for one.\n\nMySQL uses the stored key distribution to decide the order in which\ntables should be joined when you perform a join on something other than\na constant. In addition, key distributions can be used when deciding\nwhich indexes to use for a specific table within a query.\n\nThis statement requires SELECT and INSERT privileges for the table.\n\nANALYZE TABLE is supported for partitioned tables, and you can use\nALTER TABLE ... ANALYZE PARTITION to analyze one or more partitions;\nfor more information, see [HELP ALTER TABLE], and\nhttp://dev.mysql.com/doc/refman/5.7/en/partitioning-maintenance.html.\n\nIn MySQL 5.7.1, gtid_next must be set to AUTOMATIC before issuing this\nstatement. This restriction does not apply in MySQL 5.7.2 or later.\n(Bug #16062608, Bug #16715809, Bug #69045)\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (600,2,'ST_EXTERIORRING','ST_ExteriorRing(poly)\n\nReturns the exterior ring of the Polygon value poly as a LineString.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html\n\n','mysql> SET @poly =\n    -> \'Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))\';\nmysql> SELECT ST_AsText(ST_ExteriorRing(ST_GeomFromText(@poly)));\n+----------------------------------------------------+\n| ST_AsText(ST_ExteriorRing(ST_GeomFromText(@poly))) |\n+----------------------------------------------------+\n| LINESTRING(0 0,0 3,3 3,3 0,0 0)                    |\n+----------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (601,38,'FIELD','Syntax:\nFIELD(str,str1,str2,str3,...)\n\nReturns the index (position) of str in the str1, str2, str3, ... list.\nReturns 0 if str is not found.\n\nIf all arguments to FIELD() are strings, all arguments are compared as\nstrings. If all arguments are numbers, they are compared as numbers.\nOtherwise, the arguments are compared as double.\n\nIf str is NULL, the return value is 0 because NULL fails equality\ncomparison with any value. FIELD() is the complement of ELT().\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-functions.html\n\n','mysql> SELECT FIELD(\'ej\', \'Hej\', \'ej\', \'Heja\', \'hej\', \'foo\');\n        -> 2\nmysql> SELECT FIELD(\'fo\', \'Hej\', \'ej\', \'Heja\', \'hej\', \'foo\');\n        -> 0\n','http://dev.mysql.com/doc/refman/5.7/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (602,40,'CONSTRAINT','MySQL supports foreign keys, which let you cross-reference related data\nacross tables, and foreign key constraints, which help keep this\nspread-out data consistent. The essential syntax for a foreign key\nconstraint definition in a CREATE TABLE or ALTER TABLE statement looks\nlike this:\n\n[CONSTRAINT [symbol]] FOREIGN KEY\n    [index_name] (index_col_name, ...)\n    REFERENCES tbl_name (index_col_name,...)\n    [ON DELETE reference_option]\n    [ON UPDATE reference_option]\n\nreference_option:\n    RESTRICT | CASCADE | SET NULL | NO ACTION\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/create-table-foreign-keys.html\n\n','CREATE TABLE product (\n    category INT NOT NULL, id INT NOT NULL,\n    price DECIMAL,\n    PRIMARY KEY(category, id)\n)   ENGINE=INNODB;\n\nCREATE TABLE customer (\n    id INT NOT NULL,\n    PRIMARY KEY (id)\n)   ENGINE=INNODB;\n\nCREATE TABLE product_order (\n    no INT NOT NULL AUTO_INCREMENT,\n    product_category INT NOT NULL,\n    product_id INT NOT NULL,\n    customer_id INT NOT NULL,\n\n    PRIMARY KEY(no),\n    INDEX (product_category, product_id),\n    INDEX (customer_id),\n\n    FOREIGN KEY (product_category, product_id)\n      REFERENCES product(category, id)\n      ON UPDATE CASCADE ON DELETE RESTRICT,\n\n    FOREIGN KEY (customer_id)\n      REFERENCES customer(id)\n)   ENGINE=INNODB;\n','http://dev.mysql.com/doc/refman/5.7/en/create-table-foreign-keys.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (603,23,'ENUM','ENUM(\'value1\',\'value2\',...) [CHARACTER SET charset_name] [COLLATE\ncollation_name]\n\nAn enumeration. A string object that can have only one value, chosen\nfrom the list of values \'value1\', \'value2\', ..., NULL or the special \'\'\nerror value. ENUM values are represented internally as integers.\n\nAn ENUM column can have a maximum of 65,535 distinct elements. (The\npractical limit is less than 3000.) A table can have no more than 255\nunique element list definitions among its ENUM and SET columns\nconsidered as a group. For more information on these limits, see\nhttp://dev.mysql.com/doc/refman/5.7/en/limits-frm-file.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (604,13,'ST_LENGTH','ST_Length(ls)\n\nReturns a double-precision number indicating the length of the\nLineString or MultiLineString value ls in its associated spatial\nreference. The length of a MultiLineString value is equal to the sum of\nthe lengths of its elements.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html\n\n','mysql> SET @ls = \'LineString(1 1,2 2,3 3)\';\nmysql> SELECT ST_Length(ST_GeomFromText(@ls));\n+---------------------------------+\n| ST_Length(ST_GeomFromText(@ls)) |\n+---------------------------------+\n|              2.8284271247461903 |\n+---------------------------------+\n\nmysql> SET @mls = \'MultiLineString((1 1,2 2,3 3),(4 4,5 5))\';\nmysql> SELECT ST_Length(ST_GeomFromText(@mls));\n+----------------------------------+\n| ST_Length(ST_GeomFromText(@mls)) |\n+----------------------------------+\n|                4.242640687119286 |\n+----------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/gis-linestring-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (605,38,'STRCMP','Syntax:\nSTRCMP(expr1,expr2)\n\nSTRCMP() returns 0 if the strings are the same, -1 if the first\nargument is smaller than the second according to the current sort\norder, and 1 otherwise.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html\n\n','mysql> SELECT STRCMP(\'text\', \'text2\');\n        -> -1\nmysql> SELECT STRCMP(\'text2\', \'text\');\n        -> 1\nmysql> SELECT STRCMP(\'text\', \'text\');\n        -> 0\n','http://dev.mysql.com/doc/refman/5.7/en/string-comparison-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (606,28,'INSERT DELAYED','Syntax:\nINSERT DELAYED ...\n\nThe DELAYED option for the INSERT statement is a MySQL extension to\nstandard SQL. In previous versions of MySQL, it can be used for certain\nkinds of tables (such as MyISAM), such that when a client uses INSERT\nDELAYED, it gets an okay from the server at once, and the row is queued\nto be inserted when the table is not in use by any other thread.\n\nDELAYED inserts and replaces were deprecated in MySQL 5.6.6. In MySQL\n5.7, DELAYED is not supported. The server recognizes but ignores the\nDELAYED keyword, handles the insert as a nondelayed insert, and\ngenerates an ER_WARN_LEGACY_SYNTAX_CONVERTED warning ("INSERT DELAYED\nis no longer supported. The statement was converted to INSERT"). The\nDELAYED keyword is scheduled for removal in a future release.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/insert-delayed.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/insert-delayed.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (607,27,'SHOW PROCEDURE CODE','Syntax:\nSHOW PROCEDURE CODE proc_name\n\nThis statement is a MySQL extension that is available only for servers\nthat have been built with debugging support. It displays a\nrepresentation of the internal implementation of the named stored\nprocedure. A similar statement, SHOW FUNCTION CODE, displays\ninformation about stored functions (see [HELP SHOW FUNCTION CODE]).\n\nTo use either statement, you must be the owner of the routine or have\nSELECT access to the mysql.proc table.\n\nIf the named routine is available, each statement produces a result\nset. Each row in the result set corresponds to one "instruction" in the\nroutine. The first column is Pos, which is an ordinal number beginning\nwith 0. The second column is Instruction, which contains an SQL\nstatement (usually changed from the original source), or a directive\nwhich has meaning only to the stored-routine handler.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-procedure-code.html\n\n','mysql> DELIMITER //\nmysql> CREATE PROCEDURE p1 ()\n    -> BEGIN\n    ->   DECLARE fanta INT DEFAULT 55;\n    ->   DROP TABLE t2;\n    ->   LOOP\n    ->     INSERT INTO t3 VALUES (fanta);\n    ->     END LOOP;\n    ->   END//\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SHOW PROCEDURE CODE p1//\n+-----+----------------------------------------+\n| Pos | Instruction                            |\n+-----+----------------------------------------+\n|   0 | set fanta@0 55                         |\n|   1 | stmt 9 "DROP TABLE t2"                 |\n|   2 | stmt 5 "INSERT INTO t3 VALUES (fanta)" |\n|   3 | jump 2                                 |\n+-----+----------------------------------------+\n4 rows in set (0.00 sec)\n','http://dev.mysql.com/doc/refman/5.7/en/show-procedure-code.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (608,23,'MEDIUMTEXT','MEDIUMTEXT [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 16,777,215 (224 − 1)\ncharacters. The effective maximum length is less if the value contains\nmultibyte characters. Each MEDIUMTEXT value is stored using a 3-byte\nlength prefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (609,27,'SHOW COLLATION','Syntax:\nSHOW COLLATION\n    [LIKE \'pattern\' | WHERE expr]\n\nThis statement lists collations supported by the server. By default,\nthe output from SHOW COLLATION includes all available collations. The\nLIKE clause, if present, indicates which collation names to match. The\nWHERE clause can be given to select rows using more general conditions,\nas discussed in\nhttp://dev.mysql.com/doc/refman/5.7/en/extended-show.html. For example:\n\nmysql> SHOW COLLATION LIKE \'latin1%\';\n+-------------------+---------+----+---------+----------+---------+\n| Collation         | Charset | Id | Default | Compiled | Sortlen |\n+-------------------+---------+----+---------+----------+---------+\n| latin1_german1_ci | latin1  |  5 |         |          |       0 |\n| latin1_swedish_ci | latin1  |  8 | Yes     | Yes      |       0 |\n| latin1_danish_ci  | latin1  | 15 |         |          |       0 |\n| latin1_german2_ci | latin1  | 31 |         | Yes      |       2 |\n| latin1_bin        | latin1  | 47 |         | Yes      |       0 |\n| latin1_general_ci | latin1  | 48 |         |          |       0 |\n| latin1_general_cs | latin1  | 49 |         |          |       0 |\n| latin1_spanish_ci | latin1  | 94 |         |          |       0 |\n+-------------------+---------+----+---------+----------+---------+\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/show-collation.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/show-collation.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (610,3,'LOG','Syntax:\nLOG(X), LOG(B,X)\n\nIf called with one parameter, this function returns the natural\nlogarithm of X. If X is less than or equal to 0.0E0, the function\nreturns NULL and (as of MySQL 5.7.4) a warning "Invalid argument for\nlogarithm" is reported.\n\nThe inverse of this function (when called with a single argument) is\nthe EXP() function.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT LOG(2);\n        -> 0.69314718055995\nmysql> SELECT LOG(-2);\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (611,20,'!=','Syntax:\n<>, !=\n\nNot equal:\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT \'.01\' <> \'0.01\';\n        -> 1\nmysql> SELECT .01 <> \'0.01\';\n        -> 0\nmysql> SELECT \'zapp\' <> \'zappp\';\n        -> 1\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (612,24,'WHILE','Syntax:\n[begin_label:] WHILE search_condition DO\n    statement_list\nEND WHILE [end_label]\n\nThe statement list within a WHILE statement is repeated as long as the\nsearch_condition expression is true. statement_list consists of one or\nmore SQL statements, each terminated by a semicolon (;) statement\ndelimiter.\n\nA WHILE statement can be labeled. For the rules regarding label use,\nsee [HELP labels].\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/while.html\n\n','CREATE PROCEDURE dowhile()\nBEGIN\n  DECLARE v1 INT DEFAULT 5;\n\n  WHILE v1 > 0 DO\n    ...\n    SET v1 = v1 - 1;\n  END WHILE;\nEND;\n','http://dev.mysql.com/doc/refman/5.7/en/while.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (613,7,'JSON_APPEND','JSON_APPEND(json_doc, path, val[, path, val] ...)\n\nAppends values to the end of the indicated arrays within a JSON\ndocument and returns the result. This function was renamed to\nJSON_ARRAY_APPEND() in MySQL 5.7.9.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.7/en/json-modification-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (614,7,'JSON_LENGTH','JSON_LENGTH(json_doc[, path])\n\nReturns the length of JSON document, or, if a path argument is given,\nthe length of the value within the document identified by the path.\nReturns NULL if any argument is NULL or the path argument does not\nidentify a value in the document. An error occurs if the json_doc\nargument is not a valid JSON document or the path argument is not a\nvalid path expression or contains a * or ** wildcard.\n\nThe length of a document is determined as follows:\n\no The length of a scalar is 1.\n\no The length of an array is the number of array elements.\n\no The length of an object is the number of object members.\n\no The length does not count the length of nested arrays or objects.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/json-attribute-functions.html\n\n','mysql> SELECT JSON_LENGTH(\'[1, 2, {"a": 3}]\');\n+---------------------------------+\n| JSON_LENGTH(\'[1, 2, {"a": 3}]\') |\n+---------------------------------+\n|                               3 |\n+---------------------------------+\nmysql> SELECT JSON_LENGTH(\'{"a": 1, "b": {"c": 30}}\');\n+-----------------------------------------+\n| JSON_LENGTH(\'{"a": 1, "b": {"c": 30}}\') |\n+-----------------------------------------+\n|                                       2 |\n+-----------------------------------------+\nmysql> SELECT JSON_LENGTH(\'{"a": 1, "b": {"c": 30}}\', \'$.b\');\n+------------------------------------------------+\n| JSON_LENGTH(\'{"a": 1, "b": {"c": 30}}\', \'$.b\') |\n+------------------------------------------------+\n|                                              1 |\n+------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.7/en/json-attribute-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (615,32,'DAYNAME','Syntax:\nDAYNAME(date)\n\nReturns the name of the weekday for date. The language used for the\nname is controlled by the value of the lc_time_names system variable\n(http://dev.mysql.com/doc/refman/5.7/en/locale-support.html).\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html\n\n','mysql> SELECT DAYNAME(\'2007-02-03\');\n        -> \'Saturday\'\n','http://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (616,3,'RADIANS','Syntax:\nRADIANS(X)\n\nReturns the argument X, converted from degrees to radians. (Note that\nπ radians equals 180 degrees.)\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html\n\n','mysql> SELECT RADIANS(90);\n        -> 1.5707963267949\n','http://dev.mysql.com/doc/refman/5.7/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (617,17,'COLLATION','Syntax:\nCOLLATION(str)\n\nReturns the collation of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','mysql> SELECT COLLATION(\'abc\');\n        -> \'latin1_swedish_ci\'\nmysql> SELECT COLLATION(_utf8\'abc\');\n        -> \'utf8_general_ci\'\n','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (618,20,'COALESCE','Syntax:\nCOALESCE(value,...)\n\nReturns the first non-NULL value in the list, or NULL if there are no\nnon-NULL values.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html\n\n','mysql> SELECT COALESCE(NULL,1);\n        -> 1\nmysql> SELECT COALESCE(NULL,NULL,NULL);\n        -> NULL\n','http://dev.mysql.com/doc/refman/5.7/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (619,17,'VERSION','Syntax:\nVERSION()\n\nReturns a string that indicates the MySQL server version. The string\nuses the utf8 character set. The value might have a suffix in addition\nto the version number. See the description of the version system\nvariable in\nhttp://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html.\n\nURL: http://dev.mysql.com/doc/refman/5.7/en/information-functions.html\n\n','mysql> SELECT VERSION();\n        -> \'5.7.10-standard\'\n','http://dev.mysql.com/doc/refman/5.7/en/information-functions.html');

INSERT INTO help_keyword (help_keyword_id,name) VALUES (0,'JOIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (1,'HOST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (2,'SERIALIZABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (3,'CONTAINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (4,'SRID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (5,'AT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (6,'SCHEDULE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (7,'RETURNS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (8,'MASTER_SSL_CA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (9,'NCHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (10,'ONLY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (11,'ST_GEOMETRYN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (12,'ST_GEOMCOLLFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (13,'WORK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (14,'OPEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (15,'ST_INTERSECTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (16,'ESCAPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (17,'EVENTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (18,'MONTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (19,'PROFILES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (20,'ISCLOSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (21,'DUPLICATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (22,'ST_POINTN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (23,'REPLICATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (24,'UNLOCK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (25,'STATS_PERSISTENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (26,'INNODB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (27,'REPLICATE_REWRITE_DB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (28,'YEAR_MONTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (29,'WITHIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (30,'PREPARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (31,'LOCK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (32,'INT4');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (33,'POLYGON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (34,'MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (35,'SEPARATOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (36,'DELETE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (37,'JSON_SEARCH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (38,'ON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (39,'CONNECTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (40,'CLOSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (41,'MASTER_SSL_CRLPATH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (42,'USE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (43,'PRIVILEGES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (44,'SPATIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (45,'SQL_BUFFER_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (46,'SECURITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (47,'AUTOEXTEND_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (48,'ST_STARTPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (49,'ST_POLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (50,'LEVEL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (51,'BINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (52,'CURRENT_USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (53,'HOUR_MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (54,'UPDATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (55,'PRESERVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (56,'ST_SIMPLIFY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (57,'INTO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (58,'POLYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (59,'SQL_AFTER_GTIDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (60,'VARIABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (61,'ROLLBACK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (62,'TIMESTAMP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (63,'IMPORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (64,'CHECKSUM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (65,'THEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (66,'ENGINES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (67,'HANDLER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (68,'DAY_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (69,'HELP_DATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (70,'BOOLEAN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (71,'JSON_EXTRACT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (72,'MOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (73,'ST_GEOMETRYTYPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (74,'CLASS_ORIGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (75,'MPOLYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (76,'ITERATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (77,'DO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (78,'DATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (79,'FULLTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (80,'COMMENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (81,'ST_ASTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (82,'MASTER_CONNECT_RETRY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (83,'JSON_TYPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (84,'MASTER_LOG_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (85,'PRECISION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (86,'REQUIRE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (87,'ST_ASWKT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (88,'LONG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (89,'OPTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (90,'REORGANIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (91,'ELSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (92,'EXTERIORRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (93,'GEOMFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (94,'STATS_AUTO_RECALC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (95,'FROM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (96,'MULTIPOLYGON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (97,'LEFT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (98,'ELSEIF');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (99,'ST_ISCLOSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (100,'COMPACT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (101,'DEC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (102,'FOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (103,'WARNINGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (104,'ST_LONGFROMGEOHASH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (105,'ST_LINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (106,'STRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (107,'CONDITION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (108,'ENCLOSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (109,'AGGREGATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (110,'NUMBER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (111,'FIELDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (112,'JSON_INSERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (113,'JSON_UNQUOTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (114,'KILL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (115,'DISJOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (116,'TABLESPACE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (117,'OVERLAPS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (118,'INFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (119,'MBREQUAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (120,'HELP_VERSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (121,'ORDER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (122,'MASTER_SSL_CRL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (123,'ST_GEOMFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (124,'USING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (125,'REPLICATE_WILD_DO_TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (126,'MIDDLEINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (127,'GRANT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (128,'MBRINTERSECTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (129,'ST_MPOLYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (130,'JSON_ARRAY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (131,'GEOMETRYN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (132,'GEOMETRYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (133,'DEFAULT_AUTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (134,'FOREIGN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (135,'CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (136,'MYSQL_ERRNO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (137,'SCHEMAS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (138,'LEADING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (139,'CONSTRAINT_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (140,'CONVERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (141,'DYNAMIC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (142,'ST_ISVALID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (143,'POLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (144,'ENVELOPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (145,'ST_ISEMPTY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (146,'HAVING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (147,'STARTING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (148,'RELOAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (149,'ISSIMPLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (150,'AUTOCOMMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (151,'ST_Y');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (152,'REVOKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (153,'RANDOM_BYTES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (154,'EXPLAIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (155,'CSV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (156,'OUTFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (157,'LOW_PRIORITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (158,'FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (159,'ANY_VALUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (160,'NODEGROUP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (161,'SCHEMA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (162,'ST_TOUCHES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (163,'MLINEFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (164,'ST_POLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (165,'DUAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (166,'MULTIPOINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (167,'MULTIPOINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (168,'EXTENDED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (169,'CROSS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (170,'GROUP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (171,'NATIONAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (172,'ST_ISSIMPLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (173,'SHA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (174,'POINTN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (175,'IGNORE_SERVER_IDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (176,'MASTER_AUTO_POSITION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (177,'ASBINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (178,'ST_MLINEFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (179,'MBROVERLAPS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (180,'OWNER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (181,'TRUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (182,'CHARACTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (183,'SCHEMA_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (184,'TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (185,'ST_LINEFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (186,'CASCADE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (187,'RELAY_LOG_POS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (188,'ASWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (189,'LEAVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (190,'ST_GEOHASH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (191,'MODIFY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (192,'MATCH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (193,'MASTER_LOG_POS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (194,'DISTINCTROW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (195,'X');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (196,'CURSOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (197,'ST_UNION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (198,'CROSSES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (199,'GEOMETRYCOLLECTIONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (200,'CHAIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (201,'FLUSH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (202,'CREATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (203,'DESCRIBE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (204,'PROCESSLIST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (205,'DISCARD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (206,'SOUNDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (207,'PACK_KEYS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (208,'MULTILINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (209,'INTERSECTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (210,'FAST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (211,'GET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (212,'REPLICATE_WILD_IGNORE_TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (213,'LOOP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (214,'VARCHARACTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (215,'BEFORE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (216,'ALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (217,'REDUNDANT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (218,'USER_RESOURCES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (219,'PARTIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (220,'END');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (221,'ST_CONTAINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (222,'SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (223,'FLOAT8');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (224,'PREV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (225,'MBRCONTAINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (226,'OR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (227,'IDENTIFIED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (228,'POINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (229,'MASTER_SSL_CIPHER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (230,'SQL_SLAVE_SKIP_COUNTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (231,'BOTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (232,'YEAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (233,'UNIQUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (234,'TRIGGERS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (235,'RESIGNAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (236,'ST_NUMPOINTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (237,'MASTER_SSL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (238,'DATE_ADD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (239,'JSON_VALID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (240,'ST_ENVELOPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (241,'LIKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (242,'PLUGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (243,'MULTIPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (244,'FETCH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (245,'MBRWITHIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (246,'COLUMN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (247,'USAGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (248,'MEMORY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (249,'ST_MULTIPOINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (250,'QUERY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (251,'DISTANCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (252,'Y');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (253,'LINES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (254,'PLUGIN_DIR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (255,'SQL_THREAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (256,'INTERIORRINGN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (257,'NUMINTERIORRINGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (258,'REPLICATE_IGNORE_DB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (259,'MAX_QUERIES_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (260,'ST_POLYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (261,'TRANSACTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (262,'STDDEV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (263,'INT1');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (264,'RIGHT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (265,'MAX_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (266,'ALTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (267,'NATURAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (268,'MULTILINESTRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (269,'VARIABLES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (270,'ESCAPED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (271,'KEY_BLOCK_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (272,'MPOINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (273,'CHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (274,'UPGRADE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (275,'INTERVAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (276,'NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (277,'ST_POINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (278,'REFERENCES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (279,'ST_MAKEENVELOPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (280,'ST_WITHIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (281,'STORAGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (282,'ISOLATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (283,'EVERY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (284,'INT8');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (285,'ST_BUFFER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (286,'BUFFER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (287,'RESTRICT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (288,'JSON_OBJECT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (289,'UNCOMMITTED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (290,'LINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (291,'IS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (292,'ST_CENTROID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (293,'NOT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (294,'REPLICATE_DO_TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (295,'DATAFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (296,'ANALYSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (297,'DES_KEY_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (298,'COMPRESSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (299,'START');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (300,'PARTITIONING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (301,'IF');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (302,'ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (303,'PURGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (304,'USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (305,'EXIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (306,'ST_MULTILINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (307,'MERGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (308,'ST_DISTANCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (309,'SQL_NO_CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (310,'ST_MULTIPOLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (311,'DELAYED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (312,'ST_DISTANCE_SPHERE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (313,'ST_POLYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (314,'WRITE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (315,'JSON_QUOTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (316,'NEVER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (317,'DATABASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (318,'NULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (319,'POWER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (320,'POINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (321,'USE_FRM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (322,'TERMINATED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (323,'NVARCHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (324,'RETURN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (325,'DIRECTORY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (326,'AES_DECRYPT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (327,'GLENGTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (328,'SHUTDOWN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (329,'JSON_REMOVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (330,'ST_ASGEOJSON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (331,'CATALOG_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (332,'FILE_BLOCK_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (333,'FIXED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (334,'ST_BUFFER_STRATEGY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (335,'MULTIPOLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (336,'REPEAT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (337,'REPLACE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (338,'ST_SYMDIFFERENCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (339,'STARTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (340,'ST_NUMINTERIORRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (341,'COMPLETION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (342,'COLUMNS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (343,'DATETIME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (344,'MODE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (345,'INTEGER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (346,'VALUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (347,'ASWKT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (348,'MASTER_SSL_VERIFY_SERVER_CERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (349,'GEOMETRYCOLLECTIONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (350,'DROP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (351,'SQL_BIG_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (352,'SUBJECT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (353,'MASTER_RETRY_COUNT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (354,'ST_VALIDATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (355,'CHECK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (356,'FULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (357,'BY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (358,'ST_POINTFROMGEOHASH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (359,'NO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (360,'DAY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (361,'DATA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (362,'PARTITION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (363,'REAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (364,'SHARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (365,'LINESTRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (366,'MESSAGE_TEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (367,'MASTER_HEARTBEAT_PERIOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (368,'COLUMN_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (369,'X509');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (370,'LINEFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (371,'SUBCLASS_ORIGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (372,'WHERE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (373,'EVENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (374,'SUPER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (375,'IGNORE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (376,'SHA2');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (377,'QUICK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (378,'SIGNED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (379,'ST_GEOMCOLLFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (380,'FALSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (381,'POLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (382,'FORCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (383,'CHANGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (384,'TO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (385,'POINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (386,'TABLE_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (387,'VARYING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (388,'FEDERATED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (389,'MAX_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (390,'HOUR_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (391,'ST_DIFFERENCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (392,'GEOMETRYCOLLECTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (393,'ST_GEOMETRYCOLLECTIONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (394,'ST_ASBINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (395,'PROCEDURE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (396,'AGAINST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (397,'MAX_STATEMENT_TIME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (398,'ST_AREA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (399,'SQL_BEFORE_GTIDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (400,'ENDPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (401,'LONGBINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (402,'INSERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (403,'COUNT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (404,'JSON_ARRAY_APPEND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (405,'PORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (406,'MLINEFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (407,'EXISTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (408,'MUTEX');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (409,'GEOMCOLLFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (410,'RELEASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (411,'DEFAULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (412,'TYPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (413,'NO_WRITE_TO_BINLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (414,'JSON_ARRAY_INSERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (415,'OPTIMIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (416,'SQLSTATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (417,'RESET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (418,'INSTALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (419,'BIGINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (420,'ST_DIMENSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (421,'SET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (422,'JSON_MERGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (423,'ISSUER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (424,'ST_MPOINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (425,'STATUS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (426,'INNER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (427,'RELAYLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (428,'STOP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (429,'MRG_MYISAM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (430,'TRAILING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (431,'PARTITIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (432,'ST_NUMINTERIORRINGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (433,'JSON_KEYS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (434,'DEALLOCATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (435,'IO_THREAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (436,'CASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (437,'CIPHER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (438,'CONTINUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (439,'READ');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (440,'MINUTE_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (441,'ST_MULTIPOINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (442,'MIN_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (443,'ROW_COUNT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (444,'FUNCTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (445,'ST_GEOMETRYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (446,'INT3');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (447,'JSON_CONTAINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (448,'ADD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (449,'AVG_ROW_LENGTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (450,'ARCHIVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (451,'FLOAT4');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (452,'ASTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (453,'NUMGEOMETRIES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (454,'ALGORITHM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (455,'VIEW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (456,'REPEATABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (457,'JSON_CONTAINS_PATH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (458,'ST_MPOINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (459,'CONSTRAINT_CATALOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (460,'STARTPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (461,'MPOLYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (462,'UNSIGNED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (463,'DECIMAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (464,'INDEXES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (465,'ST_INTERSECTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (466,'HOSTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (467,'COMMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (468,'SNAPSHOT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (469,'DECLARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (470,'NUMPOINTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (471,'LOAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (472,'SQL_CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (473,'COLLATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (474,'ST_GEOMETRYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (475,'BYTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (476,'LINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (477,'GLOBAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (478,'WHEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (479,'CONVEXHULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (480,'TOUCHES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (481,'AS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (482,'ST_LINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (483,'GEOMCOLLFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (484,'ST_INTERIORRINGN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (485,'GRANTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (486,'REPLICATE_DO_DB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (487,'OUTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (488,'CURSOR_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (489,'EXPIRE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (490,'SQL_AFTER_MTS_GAPS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (491,'FLOOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (492,'WITH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (493,'STD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (494,'AFTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (495,'DISABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (496,'UNINSTALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (497,'ST_CONVEXHULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (498,'SONAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (499,'POW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (500,'INDEX');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (501,'DEFINER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (502,'MASTER_BIND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (503,'REMOVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (504,'MULTILINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (505,'ST_POINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (506,'ST_ENDPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (507,'ACCOUNT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (508,'ST_OVERLAPS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (509,'UNDO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (510,'JSON_SET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (511,'ZEROFILL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (512,'CLIENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (513,'MASTER_PASSWORD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (514,'RELAY_LOG_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (515,'MASTER_USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (516,'MBRTOUCHES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (517,'ENGINE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (518,'INSERT_METHOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (519,'SQL_CALC_FOUND_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (520,'UNION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (521,'MYISAM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (522,'DESC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (523,'TIME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (524,'EXPANSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (525,'NUMERIC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (526,'CODE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (527,'AREA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (528,'LOGFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (529,'EXTENT_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (530,'ST_LINEFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (531,'MAX_UPDATES_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (532,'INT2');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (533,'ENDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (534,'LOGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (535,'RECOVER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (536,'ISEMPTY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (537,'HEAP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (538,'RETURNED_SQLSTATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (539,'EXCHANGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (540,'BETWEEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (541,'ST_CROSSES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (542,'REPAIR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (543,'ST_MPOLYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (544,'MBRDISJOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (545,'CALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (546,'VALUES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (547,'ST_X');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (548,'TRUNCATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (549,'SHOW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (550,'BINLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (551,'ST_DISJOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (552,'AND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (553,'HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (554,'SELECT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (555,'DATABASES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (556,'WRAPPER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (557,'BOOL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (558,'MASTER_PORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (559,'CONCURRENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (560,'HELP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (561,'PROCESS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (562,'OPTIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (563,'CONSISTENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (564,'MAX_CONNECTIONS_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (565,'IN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (566,'DIAGNOSTICS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (567,'JSON_REPLACE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (568,'DUMPFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (569,'POLYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (570,'EXECUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (571,'ST_SRID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (572,'JSON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (573,'CEIL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (574,'ST_MULTILINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (575,'MASTER_HOST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (576,'ST_EQUALS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (577,'SERVER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (578,'MASTER_SSL_CERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (579,'MULTIPOLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (580,'DAY_MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (581,'DATE_SUB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (582,'REPLICATE_IGNORE_TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (583,'REBUILD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (584,'GEOMETRYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (585,'GEOMFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (586,'RENAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (587,'PARSER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (588,'ST_ASWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (589,'SOCKET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (590,'ST_LATFROMGEOHASH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (591,'ST_GEOMFROMGEOJSON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (592,'STRAIGHT_JOIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (593,'ST_GEOMETRYCOLLECTIONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (594,'ST_GEOMFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (595,'SHA1');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (596,'PASSWORD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (597,'OFFSET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (598,'NEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (599,'ERRORS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (600,'SQL_LOG_BIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (601,'TEMPORARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (602,'DIMENSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (603,'SQL_SMALL_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (604,'COMMITTED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (605,'ST_MULTIPOLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (606,'FILTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (607,'XA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (608,'EQUALS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (609,'DELAY_KEY_WRITE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (610,'BEGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (611,'PROFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (612,'MEDIUM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (613,'CENTROID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (614,'SSL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (615,'DAY_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (616,'AES_ENCRYPT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (617,'CEILING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (618,'LINEFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (619,'GEOMETRYTYPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (620,'STATS_SAMPLE_PAGES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (621,'SIGNAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (622,'PLUGINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (623,'ST_NUMGEOMETRIES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (624,'SAVEPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (625,'PRIMARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (626,'JSON_DEPTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (627,'LAST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (628,'MPOINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (629,'KEYS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (630,'LIMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (631,'KEY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (632,'UNTIL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (633,'ST_MLINEFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (634,'CONSTRAINT_SCHEMA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (635,'ST_EXTERIORRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (636,'ANALYZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (637,'CONSTRAINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (638,'SERIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (639,'ACTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (640,'INITIAL_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (641,'SESSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (642,'SLAVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (643,'ASC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (644,'ENABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (645,'OPTIONALLY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (646,'MAX_USER_CONNECTIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (647,'WHILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (648,'DISTINCT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (649,'LOCAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (650,'MASTER_SSL_KEY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (651,'JSON_APPEND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (652,'JSON_LENGTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (653,'NONE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (654,'TABLES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (655,'<>');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (656,'EXPORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (657,'RLIKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (658,'TRIGGER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (659,'COLLATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (660,'HIGH_PRIORITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (661,'BTREE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (662,'FIRST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (663,'COALESCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (664,'WAIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (665,'MASTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (666,'ROW_FORMAT');

INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,0);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,0);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,1);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,2);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (2,3);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (3,4);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,5);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,6);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,6);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,7);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,8);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,9);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,10);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,10);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,10);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (6,11);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (7,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,13);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (13,14);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (392,14);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,14);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,14);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (14,15);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (232,16);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,18);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (50,19);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (19,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,21);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (21,22);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,24);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,24);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,24);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,25);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,26);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,26);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,27);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,28);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,29);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (26,30);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (447,30);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,30);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (306,32);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (29,33);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,34);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,35);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,36);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,36);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,36);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,37);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (108,39);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,39);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (35,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,41);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,42);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (37,42);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,42);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (117,43);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (153,43);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,43);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,45);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,46);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,47);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (45,48);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (290,49);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,50);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (28,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,53);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,55);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,55);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (53,56);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (58,58);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,59);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (386,60);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,61);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (590,61);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,61);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (422,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (63,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,63);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,63);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (243,64);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,64);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (52,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (22,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,66);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (469,66);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,67);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,67);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,68);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (67,69);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,70);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (324,70);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (70,71);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (71,72);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (416,72);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (72,73);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,74);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,74);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,74);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (76,75);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (77,76);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (78,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (612,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (459,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (80,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,79);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,79);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,79);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (81,81);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,82);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (82,83);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,84);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,85);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,86);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,86);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,86);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (81,87);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,88);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (153,89);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,89);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,90);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (52,91);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,91);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (87,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (88,93);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,94);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (587,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (90,96);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,97);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (22,98);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (92,99);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,100);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,101);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (418,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (562,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,103);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,103);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (99,104);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (190,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,106);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (418,107);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,108);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,109);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,110);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (105,112);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (106,113);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (108,114);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (109,115);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (253,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,117);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,118);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,118);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (113,119);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (115,120);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (119,123);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (54,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (155,126);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (153,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (123,128);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (126,129);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (129,130);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (130,131);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (555,132);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,133);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,134);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,134);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,134);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,134);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,135);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (64,135);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (93,135);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,136);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,136);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,136);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,137);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (101,137);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (587,138);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,139);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,139);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,139);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,140);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (532,140);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,141);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,142);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (543,143);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (145,144);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (146,145);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,146);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,148);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (148,149);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,150);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (152,151);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (153,152);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (156,153);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,155);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,155);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,156);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,158);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (166,159);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (423,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (170,162);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (173,163);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (249,164);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,165);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (594,166);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (258,167);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,168);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,168);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,169);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,170);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,170);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,171);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,171);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (179,172);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (566,173);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (180,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,175);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,176);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (184,177);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (185,178);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (189,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,180);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,181);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (207,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (68,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (377,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (599,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (174,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (243,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (132,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (190,185);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,187);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (184,188);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (195,189);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,190);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,191);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,192);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,193);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,194);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (198,195);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (562,196);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (201,197);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (200,198);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (453,199);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,200);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (93,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (586,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (192,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (174,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (436,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (284,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (16,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (239,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (217,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,203);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,204);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (583,204);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,205);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (533,206);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,207);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (373,208);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (208,209);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,210);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,211);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,212);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (209,213);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,214);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (332,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (484,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (153,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,217);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,218);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,219);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (52,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (204,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (22,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (209,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (140,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (612,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (211,221);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,223);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,224);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (214,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (218,226);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,227);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,227);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,227);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,227);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (220,228);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,230);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (587,231);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,232);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,233);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (18,234);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,234);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,235);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (227,236);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,237);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,238);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,239);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (231,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,241);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (533,241);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (183,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (561,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (233,243);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (235,244);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (237,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,246);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,247);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,248);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,249);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,250);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (108,250);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (93,250);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (242,252);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,253);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,253);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (340,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (245,256);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (244,257);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,258);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,259);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,259);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,259);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (249,260);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,261);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,261);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (250,262);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (324,263);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,264);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,265);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (265,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (100,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (224,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (446,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,267);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (256,268);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,269);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (515,269);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,270);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,271);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (258,272);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (596,273);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,273);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,274);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,274);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,274);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,275);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,275);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,275);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,275);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,276);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (267,277);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (268,279);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,280);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (469,281);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,282);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,283);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (383,284);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (273,285);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (274,286);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,287);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,287);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,287);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (275,288);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,289);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (342,290);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (358,291);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (124,291);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (277,291);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (223,291);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (279,292);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (358,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (124,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (488,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,294);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,295);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (114,296);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,297);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,298);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,299);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,299);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,299);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,300);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (296,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (481,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (5,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (22,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (423,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (499,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,303);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (284,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (442,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (499,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,305);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (597,306);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (285,308);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,309);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (505,310);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,311);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,311);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (606,311);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (289,312);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (290,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (294,315);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,316);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,316);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (423,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (358,318);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,318);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (223,318);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (298,319);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (297,320);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,321);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,322);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,323);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (302,324);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,325);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,325);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (304,326);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,327);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (308,328);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,328);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (309,329);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (310,330);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,331);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,331);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,331);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,332);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,333);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,333);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (311,334);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (430,335);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (140,336);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,337);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,337);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,337);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (317,338);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,339);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (396,340);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,341);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,341);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,343);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,344);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,344);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (306,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (451,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (417,347);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,348);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (374,349);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (329,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (447,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (481,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (5,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (253,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (558,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (163,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (423,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (248,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (499,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,351);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,352);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,352);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,352);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,353);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,354);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,355);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,355);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,355);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (186,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (583,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (333,358);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,359);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,359);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,360);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,362);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,364);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (336,365);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,366);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,366);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,366);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,367);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,368);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,368);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,368);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,369);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,369);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,369);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (342,370);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,371);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,371);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,371);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,373);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,373);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (481,373);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (217,373);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,374);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (347,376);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,377);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,377);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,377);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,378);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (353,379);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,380);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (58,381);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,382);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,384);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (590,384);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,384);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (356,385);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,386);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,386);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,386);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,387);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,388);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,389);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,390);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (362,391);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (363,392);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (353,393);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (365,394);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (265,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (192,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (607,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (558,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (205,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (114,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,396);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,397);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (368,398);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,399);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (369,400);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,401);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (120,402);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,402);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (606,402);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (191,402);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (350,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (261,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (372,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,405);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (373,406);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (481,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (5,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (423,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (499,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,408);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (525,408);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (374,409);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (590,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (429,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (451,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,412);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (377,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (599,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (379,414);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (377,415);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,415);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,416);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,416);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (332,417);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (381,417);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (164,417);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (93,417);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (561,418);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,419);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (385,420);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (207,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (386,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (303,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (293,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (387,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,423);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,423);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,423);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (389,424);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (502,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (525,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (135,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (39,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (205,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (395,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (132,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,426);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,427);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (340,428);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,429);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (587,430);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,431);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (396,432);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (397,433);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (447,434);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (340,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (52,436);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,436);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,437);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,437);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,437);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,438);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (389,441);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,442);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,443);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (502,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (329,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (192,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (558,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (239,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (436,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (248,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (446,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (565,445);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (155,446);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (414,447);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,448);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,448);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,448);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,450);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (411,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (417,452);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (420,453);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,454);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (586,455);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,455);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (100,455);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,456);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (425,457);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,458);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,459);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,459);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,459);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (428,460);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (430,461);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (306,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (324,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (411,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (383,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (97,463);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,463);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,463);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,464);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (441,465);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,467);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,467);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,468);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,468);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,469);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (418,469);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (562,469);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (429,469);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (443,470);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,471);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,471);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,472);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,473);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,473);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,473);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (119,474);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (596,475);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (584,476);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (386,477);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,477);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,477);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (515,477);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (395,477);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (52,478);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,478);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (449,479);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (450,480);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,481);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,481);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,481);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,481);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,481);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (498,482);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (453,483);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (454,484);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,485);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (424,485);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,486);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,487);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,488);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,488);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,488);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,489);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,489);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,490);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,491);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,492);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (458,493);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,494);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,495);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,495);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,495);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (183,496);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (462,497);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,498);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (466,499);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (64,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,500);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,501);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,501);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,502);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,503);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (173,504);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (470,505);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (471,506);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,507);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,507);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (474,508);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,509);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (477,510);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (306,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (324,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (411,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (383,511);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,512);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,513);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,514);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,515);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (480,516);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (525,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (253,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,517);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,518);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,519);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (484,520);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,521);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,522);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,522);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,522);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (491,523);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (228,523);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,523);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,524);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,525);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,526);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (607,526);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,527);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,528);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,529);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (498,530);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,531);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,531);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,531);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (142,532);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,533);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (28,534);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,534);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,534);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,535);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (501,536);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,537);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,538);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,539);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (89,540);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (504,541);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,542);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,542);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (505,543);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (506,544);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (508,545);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,546);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,546);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (511,547);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,548);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,548);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (117,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (207,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (350,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (502,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (392,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (174,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (469,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (395,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (132,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (284,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (515,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (50,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (135,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (18,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (186,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (217,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (525,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (101,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (607,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (28,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (609,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (39,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (239,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (205,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (424,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (583,549);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,550);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (516,550);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (517,551);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (519,552);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (89,552);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,553);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (315,554);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,554);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,554);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (191,554);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (158,554);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,555);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (101,555);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,556);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (69,557);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (324,557);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,558);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,559);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,559);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (539,560);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (73,560);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,561);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (224,562);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,562);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,563);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,563);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,564);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,564);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,564);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,565);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,565);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,565);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,565);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,566);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (540,567);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,568);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (543,569);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (54,570);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,570);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (544,571);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (139,572);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (547,573);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (185,574);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,575);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (551,576);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (224,577);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,577);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (5,577);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,578);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (76,579);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,580);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,581);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,582);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,583);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (88,584);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (555,585);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,586);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (68,586);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (442,586);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,586);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,587);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,587);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,587);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (365,588);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,589);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (559,590);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (560,591);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,592);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,592);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (7,593);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (565,594);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (566,595);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (293,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,596);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,597);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,598);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (350,599);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,599);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (303,600);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (467,601);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (570,602);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,603);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,604);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (126,605);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,606);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,607);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (573,608);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,609);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,610);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (204,610);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (572,610);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,611);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (254,612);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (574,613);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,614);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,614);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,614);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (229,615);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (577,616);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (582,617);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (584,618);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (585,619);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,620);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,621);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,622);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (591,623);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (590,624);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,625);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (592,626);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,627);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (594,628);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,629);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,629);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,629);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (257,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,630);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,631);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (42,631);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,631);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,631);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,631);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (140,632);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (597,633);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (589,634);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (225,634);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,634);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (600,635);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (599,636);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,636);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,637);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,637);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,638);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (451,638);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (602,639);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,639);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,640);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (386,641);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,641);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (515,641);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (395,641);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (332,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (135,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (340,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (495,642);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,643);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,643);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (552,644);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,644);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,644);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,645);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (545,646);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,646);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (355,646);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (612,647);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (314,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (61,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (535,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (476,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (261,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (484,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (522,648);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (377,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (563,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (599,649);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,650);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (613,651);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (614,652);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,653);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (392,654);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,654);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (186,654);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (27,654);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (611,655);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (203,656);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (20,657);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,658);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (16,658);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (163,658);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (514,659);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (609,659);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (521,660);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (371,660);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (127,661);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,662);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,662);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,662);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (595,663);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,664);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (28,665);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (39,665);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,665);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,665);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (164,665);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (286,666);


COMMIT;

