INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (389,32,'NOW','Syntax:\nNOW()\n\nReturns the current date and time as a value in \'YYYY-MM-DD HH:MM:SS\'\nor YYYYMMDDHHMMSS.uuuuuu format, depending on whether the function is\nused in a string or numeric context. The value is expressed in the\ncurrent time zone.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (390,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.5/en/engines-table.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/show-engines.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-engines.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (391,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.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (392,23,'YEAR DATA TYPE','YEAR[(2|4)]\n\nA year in two-digit or four-digit format. The default is four-digit\nformat. YEAR(2) or YEAR(4) differ in display format, but have the same\nrange of values. In four-digit format, values display as 1901 to 2155,\nand 0000. In two-digit format, values display as 70 to 69, representing\nyears from 1970 to 2069. MySQL displays YEAR values in YYYY or YY\nformat, but permits assignment of values to YEAR columns using either\nstrings or numbers.\n\n*Note*: The YEAR(2) data type has certain issues that you should\nconsider before choosing to use it. As of MySQL 5.5.27, YEAR(2) is\ndeprecated. For more information, see\nhttp://dev.mysql.com/doc/refman/5.5/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.5/en/year.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/date-and-time-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (393,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.5/en/group-by-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (394,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.5/en/string-functions.html\n\n','mysql> SELECT REPEAT(\'MySQL\', 3);\n        -> \'MySQLMySQLMySQL\'\n','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (395,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (396,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.5/en/spatial-relation-functions-mysql-specific.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/spatial-relation-functions-mysql-specific.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (397,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.5/en/drop-event.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/drop-event.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (398,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.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (399,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.5, 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.5/en/load-index.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/load-index.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (400,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.5/en/union.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/union.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (401,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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (402,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.5/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.5/en/show-create-database.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (403,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.5/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.5/en/show-index.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-index.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (404,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.5/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.5/en/logical-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (405,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.5/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (406,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.5/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.5/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\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.5/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, 1 warning (0.01 sec)\n\nmysql> SHOW WARNINGS//\n+-------+------+---------------------------------------+\n| Level | Code | Message                               |\n+-------+------+---------------------------------------+\n| Error | 1062 | Duplicate entry \'1\' for key \'PRIMARY\' |\n+-------+------+---------------------------------------+\n1 row in set (0.00 sec)\n\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.5/en/declare-handler.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (407,23,'TIME','TIME\n\nA time. The range is \'-838:59:59\' to \'838:59:59\'. MySQL displays TIME\nvalues in \'HH:MM:SS\' format, but permits assignment of values to TIME\ncolumns using either strings or numbers.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/date-and-time-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (408,17,'SYSTEM_USER','Syntax:\nSYSTEM_USER()\n\nSYSTEM_USER() is a synonym for USER().\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/information-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (409,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.5/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (410,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.5:\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 if there are any FOREIGN KEY\n  constraints from other tables that reference the table. Foreign key\n  constraints between columns of the 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.5/en/truncate-table.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/truncate-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (411,2,'AREA','Area(poly)\n\nReturns a double-precision number indicating the area of the Polygon or\nMultiPolygon value poly, as measured in its spatial reference system.\nThe result is 0 for arguments of dimension 0 or 1.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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 Area(GeomFromText(@poly));\n+---------------------------+\n| Area(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 Area(GeomFromText(@mpoly));\n+----------------------------+\n| Area(GeomFromText(@mpoly)) |\n+----------------------------+\n|                          8 |\n+----------------------------+\n','http://dev.mysql.com/doc/refman/5.5/en/gis-polygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (412,8,'START SLAVE','Syntax:\nSTART SLAVE [thread_types]\n\nSTART SLAVE [SQL_THREAD] UNTIL\n    MASTER_LOG_FILE = \'log_name\', MASTER_LOG_POS = log_pos\n\nSTART SLAVE [SQL_THREAD] UNTIL\n    RELAY_LOG_FILE = \'log_name\', RELAY_LOG_POS = log_pos\n\nthread_types:\n    [thread_type [, thread_type] ... ]\n\nthread_type: IO_THREAD | SQL_THREAD\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\nURL: http://dev.mysql.com/doc/refman/5.5/en/start-slave.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/start-slave.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (413,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.5/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.5/en/explain-extended.html.\n\nSHOW WARNINGS displays information about the conditions resulting from\nthe most recent statement in the current session that generated\nmessages. It shows nothing if the most recent statement used a table\nand generated no messages. (That is, statements that use a table but\ngenerate no messages clear the message list.) Statements that do not\nuse tables and do not generate messages have no effect on the message\nlist.\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 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].\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/show-warnings.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-warnings.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (414,10,'DROP USER','Syntax:\nDROP USER 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. An error occurs for accounts that do not exist. To use this\nstatement, you must have the global CREATE USER privilege or the DELETE\nprivilege for the mysql database.\n\nEach account name uses the format described in\nhttp://dev.mysql.com/doc/refman/5.5/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.5/en/drop-user.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/drop-user.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (415,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (416,37,'ISEMPTY','IsEmpty(g)\n\nThis function is a placeholder that returns 0 for any valid geometry\nvalue, 1 for any invalid geometry value or NULL.\n\nMySQL does not support GIS EMPTY values such as POINT EMPTY.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (417,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.5/en/show-function-status.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-function-status.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (418,38,'LTRIM','Syntax:\nLTRIM(str)\n\nReturns the string str with leading space characters removed.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/string-functions.html\n\n','mysql> SELECT LTRIM(\'  barbar\');\n        -> \'barbar\'\n','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (419,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.5/en/spatial-relation-functions-mysql-specific.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/spatial-relation-functions-mysql-specific.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (420,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.5/en/insert-on-duplicate.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (421,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.5/en/call.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/call.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (422,12,'ENCODE','Syntax:\nENCODE(str,pass_str)\n\nEncrypt str using pass_str as the password. The result is a binary\nstring of the same length as str. To decrypt the result, use DECODE().\n\nThe ENCODE() function should no longer be used. If you still need to\nuse ENCODE(), a salt value must be used with it to reduce risk. For\nexample:\n\nENCODE(\'plaintext\', 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.5/en/encryption-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (423,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (424,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\nIt is possible to use FRAC_SECOND in place of MICROSECOND, but\nFRAC_SECOND is deprecated. FRAC_SECOND was removed in MySQL 5.5.3.\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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (425,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.5/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.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (426,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 AUTHORS\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 CONTRIBUTORS\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\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.5/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/show.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (427,27,'SHOW VARIABLES','Syntax:\nSHOW [GLOBAL | SESSION] VARIABLES\n    [LIKE \'pattern\' | WHERE expr]\n\nSHOW VARIABLES shows the values of MySQL system variables. This\ninformation also can be obtained using the mysqladmin variables\ncommand. The LIKE clause, if present, indicates which variable names to\nmatch. The WHERE clause can be given to select rows using more general\nconditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.5/en/extended-show.html. This\nstatement does not require any privilege. It requires only the ability\nto connect to the server.\n\nWith the GLOBAL modifier, SHOW VARIABLES displays the values that are\nused for new connections to MySQL. As of MySQL 5.5.3, if a variable has\nno global value, no value is displayed. Before 5.5.3, the session value\nis displayed. With SESSION, SHOW VARIABLES displays the values that are\nin effect for the current connection. If no modifier is present, the\ndefault is SESSION. LOCAL is a synonym for SESSION.\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.5/en/show-variables.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-variables.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (428,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.5/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.5/en/binlog.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/binlog.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (429,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.5/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.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (430,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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (431,28,'SELECT','Syntax:\nSELECT\n    [ALL | DISTINCT | DISTINCTROW ]\n      [HIGH_PRIORITY]\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    [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.5/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 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.5/en/expressions.html, and\n  http://dev.mysql.com/doc/refman/5.5/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.5/en/select.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/select.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (432,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.5/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.5/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (433,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.5/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.5/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (434,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.5/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (435,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 {NDB | NDBCLUSTER} STATUS\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.5/en/innodb-monitors.html.\n\nSHOW ENGINE INNODB MUTEX displays InnoDB mutex and rw-lock statistics.\nStatement output has the following columns:\n\no Type\n\n  Always InnoDB.\n\no Name\n\n  The source file where the mutex is implemented, and the line number\n  in the file where the mutex is created. The line number is specific\n  to your version of MySQL.\n\no Status\n\n  The mutex status. This field displays several values if UNIV_DEBUG\n  was defined at MySQL compilation time (for example, in include/univ.i\n  in the InnoDB part of the MySQL source tree). If UNIV_DEBUG was not\n  defined, the statement displays only the os_waits value. In the\n  latter case (without UNIV_DEBUG), the information on which the output\n  is based is insufficient to distinguish regular mutexes and mutexes\n  that protect rw-locks (which permit multiple readers or a single\n  writer). Consequently, the output may appear to contain multiple rows\n  for the same mutex.\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.5 timing is disabled and this\n    value is always 0.\n\nAs of MySQL 5.5, SHOW ENGINE INNODB MUTEX skips the mutexes and\nrw-locks of buffer pool blocks, as the amount of output can be\noverwhelming on systems with a large buffer pool. (There is one mutex\nand one rw-lock in each 16K buffer pool block, and there are 65,536\nblocks per gigabyte.) SHOW ENGINE INNODB MUTEX also does not list any\nmutexes or rw-locks that have never been waited on (os_waits=0). Thus,\nSHOW ENGINE INNODB MUTEX only displays information about mutexes and\nrw-locks outside of the buffer pool that have caused at least one\nOS-level wait.\n\nSHOW ENGINE INNODB MUTEX information can be used to diagnose system\nproblems. For example, large values of spin_waits and spin_rounds may\nindicate scalability problems.\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.row_size\nStatus: 76\n*************************** 4. row ***************************\n  Type: performance_schema\n  Name: events_waits_history.row_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).row_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.row_size,\n  mutex_instances.row_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 row_size is the size of the internal record used by the\n  implementation, such as the size of a row in a table. row_size values\n  cannot be changed.\n\no row_count is the number of internal records, such as the number of\n  rows in a table. row_count values can be changed using Performance\n  Schema configuration options.\n\no For a table, tbl_name.memory is the product of row_size and\n  row_count. For the Performance Schema as a whole,\n  performance_schema.memory is the sum of all the memory used (the sum\n  of all other memory values).\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.row_count corresponds to\nperformance_schema_events_waits_history_long_size. In other cases, the\nrelationship is more complex. For example,\nevents_waits_history.row_count corresponds to\nperformance_schema_events_waits_history_size (the number of rows per\nthread) multiplied by performance_schema_max_thread_instances ( the\nnumber of threads).\n\nIf the server has the NDBCLUSTER storage engine enabled, SHOW ENGINE\nNDB STATUS displays cluster status information such as the number of\nconnected data nodes, the cluster connectstring, and cluster binary log\nepochs, as well as counts of various Cluster API objects created by the\nMySQL Server when connected to the cluster. Sample output from this\nstatement is shown here:\n\nmysql> SHOW ENGINE NDB STATUS;\n+------------+-----------------------+--------------------------------------------------+\n| Type       | Name                  | Status                                           |\n+------------+-----------------------+--------------------------------------------------+\n| ndbcluster | connection            | cluster_node_id=7,\n  connected_host=192.168.0.103, connected_port=1186, number_of_data_nodes=4,\n  number_of_ready_data_nodes=3, connect_count=0                                         |\n| ndbcluster | NdbTransaction        | created=6, free=0, sizeof=212                    |\n| ndbcluster | NdbOperation          | created=8, free=8, sizeof=660                    |\n| ndbcluster | NdbIndexScanOperation | created=1, free=1, sizeof=744                    |\n| ndbcluster | NdbIndexOperation     | created=0, free=0, sizeof=664                    |\n| ndbcluster | NdbRecAttr            | created=1285, free=1285, sizeof=60               |\n| ndbcluster | NdbApiSignal          | created=16, free=16, sizeof=136                  |\n| ndbcluster | NdbLabel              | created=0, free=0, sizeof=196                    |\n| ndbcluster | NdbBranch             | created=0, free=0, sizeof=24                     |\n| ndbcluster | NdbSubroutine         | created=0, free=0, sizeof=68                     |\n| ndbcluster | NdbCall               | created=0, free=0, sizeof=16                     |\n| ndbcluster | NdbBlob               | created=1, free=1, sizeof=264                    |\n| ndbcluster | NdbReceiver           | created=4, free=0, sizeof=68                     |\n| ndbcluster | binlog                | latest_epoch=155467, latest_trans_epoch=148126,\n  latest_received_binlog_epoch=0, latest_handled_binlog_epoch=0,\n  latest_applied_binlog_epoch=0                                                         |\n+------------+-----------------------+--------------------------------------------------+\n\nThe rows with connection and binlog in the Name column were added to\nthe output of this statement in MySQL 5.1. The Status column in each of\nthese rows provides information about the MySQL server\'s connection to\nthe cluster and about the cluster binary log\'s status, respectively.\nThe Status information is in the form of comma-delimited set of\nname/value pairs.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/show-engine.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-engine.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (436,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.5/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (437,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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (438,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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (439,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.5/en/time-zone-support.html. This\nfunction returns NULL if the arguments are invalid.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (440,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (441,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.5/en/cast-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/cast-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (442,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.5/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (443,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.5/en/date-and-time-functions.html\n\n','mysql> SELECT PERIOD_DIFF(200802,200703);\n        -> 11\n','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (444,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.5/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.5/en/group-by-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (445,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (446,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.5/en/type-conversion.html, but\napplied to all the arguments.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (447,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.5/en/date-and-time-functions.html\n\n','mysql> SELECT QUARTER(\'2008-04-01\');\n        -> 2\n','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (448,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.5/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.5/en/mysql-server-side-help.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/mysql-server-side-help.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (449,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.5/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (450,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 that holds the lock.\nOtherwise, it returns NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (451,4,'POLYFROMTEXT','PolyFromText(wkt[,srid]), PolygonFromText(wkt[,srid])\n\nConstructs a Polygon value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (452,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.5/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\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (453,3,'CEIL','Syntax:\nCEIL(X)\n\nCEIL() is a synonym for CEILING().\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/mathematical-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (454,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.5/en/string-functions.html\n\n','mysql> SELECT LENGTH(\'text\');\n        -> 4\n','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (455,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.5/en/alter-event.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/alter-event.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (456,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.5/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (457,19,'|','Syntax:\n|\n\nBitwise OR:\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/bit-functions.html\n\n','mysql> SELECT 29 | 15;\n        -> 31\n','http://dev.mysql.com/doc/refman/5.5/en/bit-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (458,4,'GEOMFROMTEXT','GeomFromText(wkt[,srid]), GeometryFromText(wkt[,srid])\n\nConstructs a geometry value of any type using its WKT representation\nand SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-wkt-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/gis-wkt-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (459,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.5/en/miscellaneous-functions.html\n\n','mysql> SELECT UUID_SHORT();\n        -> 92395783831158784\n','http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (460,32,'DATEDIFF','Syntax:\nDATEDIFF(expr1,expr2)\n\nDATEDIFF() returns expr1 - expr2 expressed as a value in days from one\ndate 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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (461,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.5/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.5/en/drop-procedure.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/drop-procedure.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (462,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.5/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 change 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.5/en/install-plugin.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/install-plugin.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (463,28,'LOAD DATA','Syntax:\nLOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE \'file_name\'\n    [REPLACE | IGNORE]\n    INTO TABLE tbl_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.5/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.5/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.5/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\nThe character set indicated by the character_set_database system\nvariable is used to interpret the information in the file. SET NAMES\nand the setting of character_set_client do not affect interpretation of\ninput. If the contents of the input file use a character set that\ndiffers from the default, it is usually preferable to specify the\ncharacter set of the file by using the CHARACTER SET clause. A\ncharacter 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,\nor 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.5/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.5/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 all. Also, to use LOAD DATA INFILE on server files, you must have\nthe FILE privilege. See\nhttp://dev.mysql.com/doc/refman/5.5/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.\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.5/en/load-data.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/load-data.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (464,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.5/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.5/en/declare-cursor.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/declare-cursor.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (465,32,'LOCALTIME','Syntax:\nLOCALTIME, LOCALTIME()\n\nLOCALTIME and LOCALTIME() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (466,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\nAs of MySQL 5.5.3, the return value is a nonbinary string in the\nconnection character set. Before 5.5.3, the return value is a binary\nstring; see the notes at the beginning of this section about using the\nvalue as a nonbinary string.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/encryption-functions.html\n\n','mysql> SELECT SHA1(\'abc\');\n        -> \'a9993e364706816aba3e25717850c26c9cd0d89d\'\n','http://dev.mysql.com/doc/refman/5.5/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (467,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.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (468,12,'PASSWORD','Syntax:\nPASSWORD(str)\n\nReturns a hashed password string calculated from the cleartext password\nstr. The return value is a nonbinary string in the connection character\nset (a binary string before MySQL 5.5.3), or NULL if the argument is\nNULL. This function is the SQL interface to the algorithm used by the\nserver to encrypt MySQL passwords for storage in the mysql.user grant\ntable.\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.5/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.5/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (469,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.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (470,37,'DIMENSION','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.5/en/gis-class-geometry.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html\n\n','mysql> SELECT Dimension(GeomFromText(\'LineString(1 1,2 2)\'));\n+------------------------------------------------+\n| Dimension(GeomFromText(\'LineString(1 1,2 2)\')) |\n+------------------------------------------------+\n|                                              1 |\n+------------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (471,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.5/en/numeric-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/numeric-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (472,31,'EQUALS','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.5/en/spatial-relation-functions-mbr.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/spatial-relation-functions-mbr.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (473,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\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.5/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\nURL: http://dev.mysql.com/doc/refman/5.5/en/xa-statements.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/xa-statements.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (474,2,'CENTROID','Centroid(mpoly)\n\nReturns the mathematical centroid for the MultiPolygon value mpoly as a\nPoint. The result is not guaranteed to be on the MultiPolygon.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-multipolygon-property-functions.html\n\n','mysql> SET @poly =\n    -> GeomFromText(\'POLYGON((0 0,10 0,10 10,0 10,0 0),(5 5,7 5,7 7,5 7,5 5))\');\nmysql> SELECT GeometryType(@poly),AsText(Centroid(@poly));\n+---------------------+--------------------------------------------+\n| GeometryType(@poly) | AsText(Centroid(@poly))                    |\n+---------------------+--------------------------------------------+\n| POLYGON             | POINT(4.958333333333333 4.958333333333333) |\n+---------------------+--------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.5/en/gis-multipolygon-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (475,38,'OCTET_LENGTH','Syntax:\nOCTET_LENGTH(str)\n\nOCTET_LENGTH() is a synonym for LENGTH().\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/string-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (476,32,'UTC_TIMESTAMP','Syntax:\nUTC_TIMESTAMP, UTC_TIMESTAMP()\n\nReturns the current UTC date and time as a value in \'YYYY-MM-DD\nHH:MM:SS\' or YYYYMMDDHHMMSS.uuuuuu format, depending on whether the\nfunction is used in a string or numeric context.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (477,12,'AES_ENCRYPT','Syntax:\nAES_ENCRYPT(str,key_str)\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. These functions implement AES with a 128-bit key length, but\nyou can extend them to 256 bits by modifying the source. The key length\nis a trade off between performance and 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 plaintext 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\nURL: http://dev.mysql.com/doc/refman/5.5/en/encryption-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/encryption-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (478,3,'+','Syntax:\n+\n\nAddition:\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/arithmetic-functions.html\n\n','mysql> SELECT 3+5;\n        -> 8\n','http://dev.mysql.com/doc/refman/5.5/en/arithmetic-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (479,14,'INET_NTOA','Syntax:\nINET_NTOA(expr)\n\nGiven a numeric IPv4 network address in network byte order, returns the\ndotted-quad representation of the address as a string. INET_NTOA()\nreturns NULL if it does not understand its argument.\n\nAs of MySQL 5.5.3, the return value is a nonbinary string in the\nconnection character set. Before 5.5.3, the return value is a binary\nstring.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html\n\n','mysql> SELECT INET_NTOA(167773449);\n        -> \'10.0.5.9\'\n','http://dev.mysql.com/doc/refman/5.5/en/miscellaneous-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (480,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.5/en/date-and-time-functions.html\n\n','mysql> SELECT DAYOFWEEK(\'2007-02-03\');\n        -> 7\n','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (481,3,'CEILING','Syntax:\nCEILING(X)\n\nReturns the smallest integer value not less than X.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (482,33,'LINEFROMWKB','LineFromWKB(wkb[,srid]), LineStringFromWKB(wkb[,srid])\n\nConstructs a LineString value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (483,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.5/en/show-processlist.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-processlist.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (484,37,'GEOMETRYTYPE','GeometryType(g)\n\nReturns a binary string indicating the name of the geometry type of\nwhich the geometry instance g is a member. The name corresponds to one\nof the instantiable Geometry subclasses.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html\n\n','mysql> SELECT GeometryType(GeomFromText(\'POINT(1 1)\'));\n+------------------------------------------+\n| GeometryType(GeomFromText(\'POINT(1 1)\')) |\n+------------------------------------------+\n| POINT                                    |\n+------------------------------------------+\n','http://dev.mysql.com/doc/refman/5.5/en/gis-general-property-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (485,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\none 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. (When you select from the view, you select in effect using\nthe SELECT statement.) select_statement can select from base tables or\nother views.\n\nThe view definition is "frozen" at creation time, so 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,\nspecify the name as db_name.view_name when you create it:\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. They can also be expressions that use functions,\nconstant values, operators, and so forth.\n\nViews must have unique column names with no duplicates, just like base\ntables. By default, the names of the columns retrieved by the SELECT\nstatement are used for the view column names. To define explicit names\nfor the view columns, the optional column_list clause can be given as a\nlist of comma-separated identifiers. The number of names in column_list\nmust be the same as the number of columns retrieved by the SELECT\nstatement.\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\nproper 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. The following\nexample defines a view that selects two columns from another table, as\nwell 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 The SELECT statement cannot contain a subquery in the FROM clause.\n\no The SELECT statement cannot refer to system or user variables.\n\no Within a stored program, the definition 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. However,\n  after a view has been created, it is possible to drop a table or view\n  that the definition refers to. In this case, use of the view results\n  in an error. To check a view definition for problems of this kind,\n  use the CHECK TABLE statement.\n\no The definition cannot refer to a TEMPORARY table, and you cannot\n  create a TEMPORARY view.\n\no Any tables named in the view definition must exist at definition\n  time.\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 that you get\nfrom the 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 and INVOKER. These indicate that the\nrequired privileges must be held by the user who defined or invoked the\nview, respectively. The default SQL SECURITY value is DEFINER.\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 actually exist, a warning\n  is 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.5/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.5/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\nView privileges are checked 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.5/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\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.5/en/view-updatability.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/create-view.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/create-view.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (486,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (487,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\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.5/en/signal.html#signal-condition-inf\normation-items. Some signal values cause statement termination; see\nhttp://dev.mysql.com/doc/refman/5.5/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.5/en/signal.html#signal-condition-inf\normation-items.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/signal.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (488,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.5/en/savepoint.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/savepoint.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (489,33,'MPOINTFROMWKB','MPointFromWKB(wkb[,srid]), MultiPointFromWKB(wkb[,srid])\n\nConstructs a MultiPoint value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/gis-wkb-functions.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/gis-wkb-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (490,40,'ALTER TABLE','Syntax:\nALTER [ONLINE | OFFLINE] [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  | 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  | 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  | 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  | ADD PARTITION (partition_definition)\n  | DROP PARTITION partition_names\n  | TRUNCATE PARTITION {partition_names | ALL}\n  | COALESCE PARTITION number\n  | REORGANIZE PARTITION [partition_names INTO (partition_definitions)]\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  | PARTITION BY partitioning_expression\n  | REMOVE 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, merging, and splitting\npartitions, and for performing partitioning maintenance. It is possible\nfor an ALTER TABLE statement to contain a PARTITION BY or REMOVE\nPARTITIONING clause in an addition to other alter specifications, but\nthe PARTITION BY or REMOVE PARTITIONING clause must be specified last\nafter any other specifications. The ADD PARTITION, DROP PARTITION,\nCOALESCE PARTITION, REORGANIZE PARTITION, ANALYZE PARTITION, CHECK\nPARTITION, and REPAIR PARTITION options cannot be combined with other\nalter specifications in a single ALTER TABLE, since the options just\nlisted act on individual partitions. For a list of partition options\nand a description of each, see [HELP CREATE TABLE]. For additional\ninformation, see\nhttp://dev.mysql.com/doc/refman/5.5/en/alter-table-partition-operations\n.html.\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.5/en/alter-table-problems.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/alter-table.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/alter-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (491,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.5/en/statement-labels.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/statement-labels.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (492,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.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (493,20,'>','Syntax:\n>\n\nGreater than:\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/comparison-operators.html\n\n','mysql> SELECT 2 > 2;\n        -> 0\n','http://dev.mysql.com/doc/refman/5.5/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (494,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.\n\nFor more information on how the analysis works within InnoDB, see\nhttp://dev.mysql.com/doc/refman/5.5/en/innodb-statistics-estimation.htm\nl. Also see\nhttp://dev.mysql.com/doc/refman/5.5/en/innodb-analyze-table-complexity.\nhtml and\nhttp://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html.\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.5/en/partitioning-maintenance.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/analyze-table.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/analyze-table.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (495,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.5/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.5/en/string-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (496,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.5/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.5/en/create-table-foreign-keys.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (497,40,'ALTER TABLESPACE','Syntax:\nALTER TABLESPACE tablespace_name\n    {ADD|DROP} DATAFILE \'file_name\'\n    [INITIAL_SIZE [=] size]\n    [WAIT]\n    ENGINE [=] engine_name\n\nThis statement can be used either to add a new data file, or to drop a\ndata file from a tablespace.\n\nThe ADD DATAFILE variant enables you to specify an initial size using\nan INITIAL_SIZE clause, where size is measured in bytes; the default\nvalue is 134217728 (128 MB). Prior to MySQL Cluster NDB 7.2.14, this\nvalue was required to be specified using digits (Bug #13116514, Bug\n#16104705, Bug #62858); in MySQL Cluster NDB 7.2.14 and later, you may\noptionally follow size with a one-letter abbreviation for an order of\nmagnitude, similar to those used in my.cnf. Generally, this is one of\nthe letters M (megabytes) or G (gigabytes).\n\n*Note*: All MySQL Cluster Disk Data objects share the same namespace.\nThis means that each Disk Data object must be uniquely named (and not\nmerely each Disk Data object of a given type). For example, you cannot\nhave a tablespace and an data file with the same name, or an undo log\nfile and a tablespace with the same name.\n\nOn 32-bit systems, the maximum supported value for INITIAL_SIZE is\n4294967296 (4 GB). (Bug #29186)\n\nINITIAL_SIZE is rounded, explicitly, as for CREATE TABLESPACE.\n\nOnce a data file has been created, its size cannot be changed; however,\nyou can add more data files to the tablespace using additional ALTER\nTABLESPACE ... ADD DATAFILE statements.\n\nUsing DROP DATAFILE with ALTER TABLESPACE drops the data file\n\'file_name\' from the tablespace. You cannot drop a data file from a\ntablespace which is in use by any table; in other words, the data file\nmust be empty (no extents used). See\nhttp://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-disk-data-objects.\nhtml. In addition, any data file to be dropped must previously have\nbeen added to the tablespace with CREATE TABLESPACE or ALTER\nTABLESPACE.\n\nBoth ALTER TABLESPACE ... ADD DATAFILE and ALTER TABLESPACE ... DROP\nDATAFILE require an ENGINE clause which specifies the storage engine\nused by the tablespace. Currently, the only accepted values for\nengine_name are NDB and NDBCLUSTER.\n\nWAIT is parsed but otherwise ignored, and so has no effect in MySQL\n5.5. It is intended for future expansion.\n\nWhen ALTER TABLESPACE ... ADD DATAFILE is used with ENGINE = NDB, a\ndata file is created on each Cluster data node. You can verify that the\ndata files were created and obtain information about them by querying\nthe INFORMATION_SCHEMA.FILES table. For example, the following query\nshows all data files belonging to the tablespace named newts:\n\nmysql> SELECT LOGFILE_GROUP_NAME, FILE_NAME, EXTRA\n    -> FROM INFORMATION_SCHEMA.FILES\n    -> WHERE TABLESPACE_NAME = \'newts\' AND FILE_TYPE = \'DATAFILE\';\n+--------------------+--------------+----------------+\n| LOGFILE_GROUP_NAME | FILE_NAME    | EXTRA          |\n+--------------------+--------------+----------------+\n| lg_3               | newdata.dat  | CLUSTER_NODE=3 |\n| lg_3               | newdata.dat  | CLUSTER_NODE=4 |\n| lg_3               | newdata2.dat | CLUSTER_NODE=3 |\n| lg_3               | newdata2.dat | CLUSTER_NODE=4 |\n+--------------------+--------------+----------------+\n2 rows in set (0.03 sec)\n\nSee http://dev.mysql.com/doc/refman/5.5/en/files-table.html.\n\nALTER TABLESPACE is useful only with Disk Data storage for MySQL\nCluster. See\nhttp://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-disk-data.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/alter-tablespace.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/alter-tablespace.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (498,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.5/en/limits-frm-file.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (499,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.5/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.5/en/string-comparison-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (500,28,'INSERT DELAYED','Syntax:\nINSERT DELAYED ...\n\nThe DELAYED option for the INSERT statement is a MySQL extension to\nstandard SQL that is very useful if you have clients that cannot or\nneed not wait for the INSERT to complete. This is a common situation\nwhen you use MySQL for logging and you also periodically run SELECT and\nUPDATE statements that take a long time to complete.\n\nWhen a client uses INSERT DELAYED, it gets an okay from the server at\nonce, and the row is queued to be inserted when the table is not in use\nby any other thread.\n\nAnother major benefit of using INSERT DELAYED is that inserts from many\nclients are bundled together and written in one block. This is much\nfaster than performing many separate inserts.\n\nNote that INSERT DELAYED is slower than a normal INSERT if the table is\nnot otherwise in use. There is also the additional overhead for the\nserver to handle a separate thread for each table for which there are\ndelayed rows. This means that you should use INSERT DELAYED only when\nyou are really sure that you need it.\n\nThe queued rows are held only in memory until they are inserted into\nthe table. This means that if you terminate mysqld forcibly (for\nexample, with kill -9) or if mysqld dies unexpectedly, any queued rows\nthat have not been written to disk are lost.\n\nThere are some constraints on the use of DELAYED:\n\no INSERT DELAYED works only with MyISAM, MEMORY, ARCHIVE, and BLACKHOLE\n  tables. For engines that do not support DELAYED, an error occurs.\n\no An error occurs for INSERT DELAYED if used with a table that has been\n  locked with LOCK TABLES because the insert must be handled by a\n  separate thread, not by the session that holds the lock.\n\no For MyISAM tables, if there are no free blocks in the middle of the\n  data file, concurrent SELECT and INSERT statements are supported.\n  Under these circumstances, you very seldom need to use INSERT DELAYED\n  with MyISAM.\n\no INSERT DELAYED should be used only for INSERT statements that specify\n  value lists. The server ignores DELAYED for INSERT ... SELECT or\n  INSERT ... ON DUPLICATE KEY UPDATE statements.\n\no Because the INSERT DELAYED statement returns immediately, before the\n  rows are inserted, you cannot use LAST_INSERT_ID() to get the\n  AUTO_INCREMENT value that the statement might generate.\n\no DELAYED rows are not visible to SELECT statements until they actually\n  have been inserted.\n\no Prior to MySQL 5.5.7, INSERT DELAYED was treated as a normal INSERT\n  if the statement inserted multiple rows, binary logging was enabled,\n  and the global logging format was statement-based (that is, whenever\n  binlog_format was set to STATEMENT). Beginning with MySQL 5.5.7,\n  INSERT DELAYED is always handled as a simple INSERT (that is, without\n  the DELAYED option) whenever the value of binlog_format is STATEMENT\n  or MIXED. (In the latter case, the statement no longer triggers a\n  switch to row-based logging, and so is logged using the\n  statement-based format.)\n\n  This does not apply when using row-based binary logging mode\n  (binlog_format set to ROW), in which INSERT DELAYED statements are\n  always executed using the DELAYED option as specified, and logged as\n  row-update events.\n\no DELAYED is ignored on slave replication servers, so that INSERT\n  DELAYED is treated as a normal INSERT on slaves. This is because\n  DELAYED could cause the slave to have different data than the master.\n\no Pending INSERT DELAYED statements are lost if a table is write locked\n  and ALTER TABLE is used to modify the table structure.\n\no INSERT DELAYED is not supported for views.\n\no INSERT DELAYED is not supported for partitioned tables.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/insert-delayed.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/insert-delayed.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (501,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.5/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.5/en/show-procedure-code.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (502,23,'MEDIUMTEXT','MEDIUMTEXT [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 16,777,215 (224 - 1) characters.\nThe effective maximum length is less if the value contains multibyte\ncharacters. Each MEDIUMTEXT value is stored using a 3-byte length\nprefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/string-type-overview.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (503,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, then NULL is returned.\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.5/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.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (504,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.5/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.5/en/show-collation.html\n\n','','http://dev.mysql.com/doc/refman/5.5/en/show-collation.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (505,20,'!=','Syntax:\n<>, !=\n\nNot equal:\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (506,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.5/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.5/en/while.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (507,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.5/en/locale-support.html).\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html\n\n','mysql> SELECT DAYNAME(\'2007-02-03\');\n        -> \'Saturday\'\n','http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (508,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.5/en/mathematical-functions.html\n\n','mysql> SELECT RADIANS(90);\n        -> 1.5707963267949\n','http://dev.mysql.com/doc/refman/5.5/en/mathematical-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (509,17,'COLLATION','Syntax:\nCOLLATION(str)\n\nReturns the collation of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.5/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.5/en/information-functions.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (510,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.5/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.5/en/comparison-operators.html');
INSERT INTO help_topic (help_topic_id,help_category_id,name,description,example,url) VALUES (511,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.5/en/server-system-variables.html.\n\nURL: http://dev.mysql.com/doc/refman/5.5/en/information-functions.html\n\n','mysql> SELECT VERSION();\n        -> \'5.5.42-standard\'\n','http://dev.mysql.com/doc/refman/5.5/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,'REPEAT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (3,'SERIALIZABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (4,'REPLACE');
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,'STARTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (9,'MASTER_SSL_CA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (10,'NCHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (11,'ONLY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (12,'COLUMNS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (13,'COMPLETION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (14,'WORK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (15,'DATETIME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (16,'MODE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (17,'OPEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (18,'INTEGER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (19,'ESCAPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (20,'VALUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (21,'MASTER_SSL_VERIFY_SERVER_CERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (22,'SQL_BIG_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (23,'DROP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (24,'GEOMETRYCOLLECTIONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (25,'EVENTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (26,'MONTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (27,'PROFILES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (28,'DUPLICATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (29,'REPLICATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (30,'UNLOCK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (31,'INNODB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (32,'YEAR_MONTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (33,'SUBJECT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (34,'PREPARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (35,'LOCK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (36,'NDB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (37,'CHECK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (38,'FULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (39,'INT4');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (40,'BY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (41,'NO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (42,'MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (43,'PARTITION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (44,'DATA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (45,'DAY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (46,'SHARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (47,'REAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (48,'SEPARATOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (49,'MESSAGE_TEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (50,'MASTER_HEARTBEAT_PERIOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (51,'DELETE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (52,'ON');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (53,'COLUMN_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (54,'CONNECTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (55,'CLOSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (56,'X509');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (57,'USE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (58,'SUBCLASS_ORIGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (59,'WHERE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (60,'PRIVILEGES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (61,'SPATIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (62,'EVENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (63,'SUPER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (64,'SQL_BUFFER_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (65,'IGNORE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (66,'SHA2');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (67,'QUICK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (68,'SIGNED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (69,'OFFLINE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (70,'SECURITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (71,'AUTOEXTEND_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (72,'NDBCLUSTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (73,'POLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (74,'FALSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (75,'LEVEL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (76,'FORCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (77,'BINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (78,'TO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (79,'CHANGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (80,'CURRENT_USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (81,'HOUR_MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (82,'UPDATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (83,'PRESERVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (84,'TABLE_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (85,'INTO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (86,'FEDERATED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (87,'VARYING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (88,'MAX_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (89,'HOUR_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (90,'VARIABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (91,'ROLLBACK');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (92,'PROCEDURE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (93,'TIMESTAMP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (94,'IMPORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (95,'AGAINST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (96,'CHECKSUM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (97,'COUNT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (98,'INSERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (99,'LONGBINARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (100,'THEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (101,'ENGINES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (102,'HANDLER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (103,'PORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (104,'DAY_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (105,'EXISTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (106,'MUTEX');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (107,'HELP_DATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (108,'RELEASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (109,'BOOLEAN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (110,'MOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (111,'DEFAULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (112,'TYPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (113,'NO_WRITE_TO_BINLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (114,'OPTIMIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (115,'SQLSTATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (116,'RESET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (117,'CLASS_ORIGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (118,'INSTALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (119,'ITERATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (120,'DO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (121,'BIGINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (122,'SET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (123,'ISSUER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (124,'DATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (125,'STATUS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (126,'FULLTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (127,'COMMENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (128,'MASTER_CONNECT_RETRY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (129,'INNER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (130,'RELAYLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (131,'STOP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (132,'MASTER_LOG_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (133,'MRG_MYISAM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (134,'PRECISION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (135,'REQUIRE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (136,'TRAILING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (137,'PARTITIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (138,'LONG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (139,'OPTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (140,'REORGANIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (141,'ELSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (142,'DEALLOCATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (143,'IO_THREAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (144,'CASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (145,'CIPHER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (146,'CONTINUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (147,'FROM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (148,'READ');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (149,'LEFT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (150,'ELSEIF');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (151,'MINUTE_SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (152,'COMPACT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (153,'DEC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (154,'FOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (155,'WARNINGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (156,'MIN_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (157,'STRING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (158,'CONDITION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (159,'ENCLOSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (160,'FUNCTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (161,'AGGREGATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (162,'FIELDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (163,'INT3');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (164,'ARCHIVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (165,'AVG_ROW_LENGTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (166,'ADD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (167,'KILL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (168,'FLOAT4');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (169,'TABLESPACE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (170,'VIEW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (171,'REPEATABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (172,'INFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (173,'HELP_VERSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (174,'ORDER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (175,'USING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (176,'CONSTRAINT_CATALOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (177,'MIDDLEINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (178,'GRANT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (179,'UNSIGNED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (180,'DECIMAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (181,'GEOMETRYFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (182,'INDEXES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (183,'FOREIGN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (184,'CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (185,'HOSTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (186,'MYSQL_ERRNO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (187,'COMMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (188,'SCHEMAS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (189,'LEADING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (190,'SNAPSHOT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (191,'CONSTRAINT_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (192,'DECLARE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (193,'LOAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (194,'SQL_CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (195,'CONVERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (196,'DYNAMIC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (197,'COLLATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (198,'POLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (199,'BYTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (200,'ENVELOPE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (201,'GLOBAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (202,'LINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (203,'WHEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (204,'HAVING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (205,'AS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (206,'STARTING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (207,'RELOAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (208,'AUTOCOMMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (209,'REVOKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (210,'GRANTS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (211,'OUTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (212,'CURSOR_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (213,'FLOOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (214,'EXPLAIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (215,'WITH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (216,'AFTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (217,'STD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (218,'CSV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (219,'DISABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (220,'UNINSTALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (221,'OUTFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (222,'LOW_PRIORITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (223,'FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (224,'NODEGROUP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (225,'SCHEMA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (226,'SONAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (227,'POW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (228,'DUAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (229,'INDEX');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (230,'MULTIPOINTFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (231,'MULTIPOINTFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (232,'DEFINER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (233,'MASTER_BIND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (234,'REMOVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (235,'EXTENDED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (236,'MULTILINESTRINGFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (237,'CROSS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (238,'CONTRIBUTORS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (239,'NATIONAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (240,'GROUP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (241,'SHA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (242,'ONLINE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (243,'UNDO');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (244,'IGNORE_SERVER_IDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (245,'ZEROFILL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (246,'CLIENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (247,'MASTER_PASSWORD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (248,'OWNER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (249,'RELAY_LOG_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (250,'TRUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (251,'CHARACTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (252,'MASTER_USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (253,'SCHEMA_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (254,'TABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (255,'ENGINE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (256,'INSERT_METHOD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (257,'CASCADE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (258,'RELAY_LOG_POS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (259,'SQL_CALC_FOUND_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (260,'UNION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (261,'MYISAM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (262,'LEAVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (263,'MODIFY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (264,'MATCH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (265,'MASTER_LOG_POS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (266,'DISTINCTROW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (267,'DESC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (268,'TIME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (269,'NUMERIC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (270,'EXPANSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (271,'CODE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (272,'CURSOR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (273,'GEOMETRYCOLLECTIONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (274,'AREA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (275,'CHAIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (276,'LOGFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (277,'FLUSH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (278,'CREATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (279,'DESCRIBE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (280,'EXTENT_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (281,'MAX_UPDATES_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (282,'INT2');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (283,'PROCESSLIST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (284,'ENDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (285,'LOGS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (286,'RECOVER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (287,'DISCARD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (288,'HEAP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (289,'SOUNDS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (290,'BETWEEN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (291,'MULTILINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (292,'REPAIR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (293,'PACK_KEYS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (294,'FAST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (295,'VALUES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (296,'CALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (297,'LOOP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (298,'VARCHARACTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (299,'BEFORE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (300,'TRUNCATE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (301,'SHOW');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (302,'ALL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (303,'REDUNDANT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (304,'USER_RESOURCES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (305,'PARTIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (306,'BINLOG');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (307,'END');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (308,'SECOND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (309,'AND');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (310,'FLOAT8');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (311,'PREV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (312,'HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (313,'SELECT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (314,'DATABASES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (315,'OR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (316,'IDENTIFIED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (317,'WRAPPER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (318,'MASTER_SSL_CIPHER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (319,'SQL_SLAVE_SKIP_COUNTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (320,'BOOL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (321,'BOTH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (322,'YEAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (323,'MASTER_PORT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (324,'CONCURRENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (325,'HELP');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (326,'UNIQUE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (327,'TRIGGERS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (328,'PROCESS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (329,'OPTIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (330,'RESIGNAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (331,'CONSISTENT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (332,'MASTER_SSL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (333,'DATE_ADD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (334,'MAX_CONNECTIONS_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (335,'LIKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (336,'PLUGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (337,'FETCH');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (338,'IN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (339,'COLUMN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (340,'DUMPFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (341,'USAGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (342,'EXECUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (343,'MEMORY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (344,'CEIL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (345,'QUERY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (346,'MASTER_HOST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (347,'LINES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (348,'SQL_THREAD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (349,'SERVER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (350,'MAX_QUERIES_PER_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (351,'MASTER_SSL_CERT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (352,'MULTIPOLYGONFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (353,'TRANSACTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (354,'DAY_MINUTE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (355,'DATE_SUB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (356,'STDDEV');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (357,'REBUILD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (358,'GEOMETRYFROMWKB');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (359,'INT1');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (360,'RENAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (361,'PARSER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (362,'RIGHT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (363,'ALTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (364,'MAX_ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (365,'SOCKET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (366,'STRAIGHT_JOIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (367,'NATURAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (368,'VARIABLES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (369,'ESCAPED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (370,'SHA1');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (371,'KEY_BLOCK_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (372,'PASSWORD');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (373,'OFFSET');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (374,'CHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (375,'NEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (376,'ERRORS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (377,'SQL_LOG_BIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (378,'TEMPORARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (379,'COMMITTED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (380,'SQL_SMALL_RESULT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (381,'UPGRADE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (382,'XA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (383,'BEGIN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (384,'DELAY_KEY_WRITE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (385,'PROFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (386,'MEDIUM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (387,'INTERVAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (388,'CENTROID');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (389,'SSL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (390,'DAY_HOUR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (391,'NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (392,'REFERENCES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (393,'AES_ENCRYPT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (394,'STORAGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (395,'ISOLATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (396,'CEILING');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (397,'EVERY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (398,'INT8');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (399,'AUTHORS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (400,'RESTRICT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (401,'UNCOMMITTED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (402,'LINESTRINGFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (403,'IS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (404,'NOT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (405,'ANALYSE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (406,'DATAFILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (407,'DES_KEY_FILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (408,'SIGNAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (409,'COMPRESSED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (410,'START');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (411,'PLUGINS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (412,'SAVEPOINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (413,'IF');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (414,'ROWS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (415,'PRIMARY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (416,'PURGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (417,'LAST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (418,'USER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (419,'EXIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (420,'KEYS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (421,'LIMIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (422,'KEY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (423,'MERGE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (424,'UNTIL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (425,'SQL_NO_CACHE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (426,'DELAYED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (427,'CONSTRAINT_SCHEMA');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (428,'ANALYZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (429,'CONSTRAINT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (430,'SERIAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (431,'ACTION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (432,'WRITE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (433,'INITIAL_SIZE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (434,'SESSION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (435,'DATABASE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (436,'NULL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (437,'POWER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (438,'USE_FRM');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (439,'TERMINATED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (440,'SLAVE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (441,'NVARCHAR');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (442,'ASC');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (443,'RETURN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (444,'OPTIONALLY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (445,'ENABLE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (446,'DIRECTORY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (447,'MAX_USER_CONNECTIONS');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (448,'WHILE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (449,'LOCAL');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (450,'AES_DECRYPT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (451,'DISTINCT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (452,'MASTER_SSL_KEY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (453,'NONE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (454,'TABLES');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (455,'<>');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (456,'RLIKE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (457,'TRIGGER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (458,'COLLATION');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (459,'SHUTDOWN');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (460,'HIGH_PRIORITY');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (461,'BTREE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (462,'FIRST');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (463,'COALESCE');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (464,'WAIT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (465,'CATALOG_NAME');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (466,'MASTER');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (467,'FIXED');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (468,'MULTIPOLYGONFROMTEXT');
INSERT INTO help_keyword (help_keyword_id,name) VALUES (469,'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 (431,0);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,1);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (124,2);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,3);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,4);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,4);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,4);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,5);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,6);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,6);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,7);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,8);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,9);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (222,10);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,11);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (265,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,12);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,13);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,13);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,14);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,15);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,16);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,16);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (13,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,17);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (255,18);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,18);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (197,19);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (374,20);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,21);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,22);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (372,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (397,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (6,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (211,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (215,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (461,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (49,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (143,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (348,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (123,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (414,23);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (309,24);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,25);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,25);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (92,25);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,26);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (45,27);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,28);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,29);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,30);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,31);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,32);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,33);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (23,34);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (372,34);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,34);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,35);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,35);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,36);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,37);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,37);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,37);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (265,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,38);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (255,39);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (295,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,40);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,41);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,41);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,42);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,43);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,43);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,44);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,45);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,46);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (405,47);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,47);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,48);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,49);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,49);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,50);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,51);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,52);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,53);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,53);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (94,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,54);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (31,55);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,55);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,56);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (33,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,57);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,58);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,58);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,59);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,59);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,59);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (103,60);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,60);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,60);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,61);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,61);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (397,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (187,62);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,63);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,64);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,65);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (288,66);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,67);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,67);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,67);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,68);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (49,69);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,69);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,69);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,70);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,71);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,72);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (51,73);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (246,73);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (201,74);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,75);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,76);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,77);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (488,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,78);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,79);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,79);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,80);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,81);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,82);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,82);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,82);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,82);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,83);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,83);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,84);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,84);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,85);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,85);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,85);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,85);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,86);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,87);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,88);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,89);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (319,90);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,91);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (488,91);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,91);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (227,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (166,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (501,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (461,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (177,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (100,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,92);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (347,93);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (56,93);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,94);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,94);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,95);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (207,96);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,96);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (292,97);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (223,97);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (413,97);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (105,98);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,98);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (500,98);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (165,98);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (391,99);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (47,100);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,100);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (20,100);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,101);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,101);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,102);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,103);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,104);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (397,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (348,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (6,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,105);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,106);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,106);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (60,107);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,108);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (488,108);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,108);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,109);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (266,109);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (63,110);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (342,110);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (354,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (374,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,111);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,112);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,113);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,113);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (313,113);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,113);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (313,114);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,114);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,115);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,115);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (273,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (316,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (144,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (82,116);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,117);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,117);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (462,118);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (68,119);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,120);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,120);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (69,120);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (506,120);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (117,121);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (179,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (319,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (252,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (98,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (243,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,122);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,123);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (381,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (71,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,124);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (417,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (35,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (177,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (326,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (115,125);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,126);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,126);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,126);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,127);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,128);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,129);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,130);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,131);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,132);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,133);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (405,134);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,135);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,136);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,137);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (391,138);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,139);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,139);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,140);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (47,141);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,141);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (372,142);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,143);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (412,143);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (47,144);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,144);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,145);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,146);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,147);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,148);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,148);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,148);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,148);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,149);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (20,150);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,151);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,152);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,153);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (344,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (464,154);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,155);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (413,155);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,156);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,157);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (344,158);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,159);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (290,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (417,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (271,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (166,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (461,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (204,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (211,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (370,160);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,161);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,162);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,162);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (136,163);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,164);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,165);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,165);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,166);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,166);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,166);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,166);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (94,167);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (338,168);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,169);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,169);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (215,169);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,169);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (485,170);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,170);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (88,170);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,171);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,172);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,172);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (101,173);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,174);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,175);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (48,175);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,175);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,176);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,176);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (136,177);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,178);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,178);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (405,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (255,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (266,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (338,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (317,179);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (86,180);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,180);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,180);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (458,181);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,182);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,183);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (57,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (82,184);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (328,185);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,185);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,186);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,187);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,187);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,188);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (89,188);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,189);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,190);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,190);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,191);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,191);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,192);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (344,192);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (464,192);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (354,192);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,193);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,193);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,194);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,195);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (441,195);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,196);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,197);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,197);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,197);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (451,198);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (492,199);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (128,200);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (319,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (98,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (427,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (326,201);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (482,202);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (47,203);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,203);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,204);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,205);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,205);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,205);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,206);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,207);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,208);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,209);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,210);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (350,210);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,211);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,212);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,212);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (117,213);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,214);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,215);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,216);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (380,217);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,218);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,218);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,219);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,219);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,219);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (159,220);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,221);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,222);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,223);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,224);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (348,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,225);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,226);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (387,227);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (152,228);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (399,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (49,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (57,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (403,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,229);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (489,230);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (220,231);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,232);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,232);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,233);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,234);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,235);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,235);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (150,236);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,237);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,238);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (4,238);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,239);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (222,239);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (278,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (367,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (123,240);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (466,241);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (49,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,242);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,243);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,244);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (405,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (255,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (266,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (338,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (317,245);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,246);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,247);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,248);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,249);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (201,250);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (179,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (222,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,251);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,252);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,253);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,253);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (61,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (313,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (410,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (151,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (207,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (115,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,254);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (435,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (215,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,255);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,256);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,257);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,257);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,257);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,257);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,258);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,259);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,260);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,261);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (168,262);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,263);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,264);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,265);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,266);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,267);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,267);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,267);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (407,268);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (195,268);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,268);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,269);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,270);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (290,271);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (501,271);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (464,272);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (376,273);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (411,274);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,275);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,276);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (278,276);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (367,276);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (123,276);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,277);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (82,277);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (485,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (55,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (166,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (151,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (360,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (295,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (278,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (15,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (204,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (187,278);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,279);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,280);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,281);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (125,282);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,283);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,283);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,284);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,285);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,285);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,285);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,286);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,287);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,288);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (442,289);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (79,290);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (308,291);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,292);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,292);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,293);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,294);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,295);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,295);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (421,296);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (181,297);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,298);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,299);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (410,300);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,300);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (103,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (290,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (179,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (292,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (417,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (4,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (151,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (7,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (326,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (115,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (12,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (265,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (427,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (45,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (17,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (328,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (187,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,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 (435,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (89,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (501,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (249,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (504,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 (403,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (92,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (35,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (204,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (177,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (413,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (350,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (483,301);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (273,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (134,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,302);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,303);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,304);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,305);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,306);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (428,306);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (34,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (47,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (176,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (20,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (181,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (124,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (506,307);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,308);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (79,309);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (170,309);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (405,310);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,311);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,312);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (165,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (138,313);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (89,314);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (75,315);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,316);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,316);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (295,316);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,317);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,318);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (98,319);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (62,320);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (266,320);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (486,321);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,322);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,323);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,324);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,324);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (448,325);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (64,325);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,326);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (17,327);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,327);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,328);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,329);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,329);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,330);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,331);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,331);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,332);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,333);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,334);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,335);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (442,335);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,336);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (159,336);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (462,336);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (200,337);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,338);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,338);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,338);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,338);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,339);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,340);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,341);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (48,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,342);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,343);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (453,344);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (299,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (94,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (82,345);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,346);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,347);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,347);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,348);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (412,348);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,349);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,349);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (6,349);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,350);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,351);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (67,352);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,353);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,353);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,354);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,355);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (212,356);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,357);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (78,358);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (266,359);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,360);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (61,360);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (365,360);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,360);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,361);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,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 (497,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (227,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (88,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (193,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (367,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (370,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,363);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,364);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,365);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,366);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,366);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (0,367);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,368);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (427,368);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,369);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (466,370);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,371);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (243,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (295,372);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,373);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (492,374);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (122,374);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,375);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (292,376);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,376);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (252,377);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,378);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,379);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,380);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,381);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,381);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,382);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (176,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,383);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,384);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (249,385);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (216,386);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,387);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,387);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (474,388);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,389);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (196,390);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,391);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,392);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,392);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,392);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (477,393);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (390,394);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,395);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (481,396);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,397);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (317,398);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (7,399);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,399);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,400);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,400);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,400);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,401);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (283,402);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (298,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (109,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (232,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (192,403);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (298,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (109,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (404,404);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (100,405);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,406);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,406);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,407);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,408);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,409);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (327,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (412,410);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (22,411);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (488,412);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (245,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (397,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (6,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (388,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (20,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (269,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (348,413);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,414);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,415);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,416);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,417);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,418);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (365,418);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (414,418);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (295,418);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (406,419);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,420);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (403,420);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,420);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (219,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (30,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (66,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (46,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,421);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (38,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,422);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,423);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (124,424);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,425);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (260,426);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,426);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (500,426);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,427);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,427);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,428);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,428);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,429);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,429);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,430);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (374,430);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,431);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,431);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,432);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (473,432);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,433);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,433);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (319,434);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (230,434);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (427,434);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (326,434);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (240,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (330,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (402,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (348,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,435);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (298,436);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (496,436);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (192,436);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (247,437);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,438);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,439);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (328,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (273,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (118,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (282,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (412,440);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (141,441);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,442);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,442);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (251,443);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,444);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (455,445);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (300,445);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,445);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,446);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (112,446);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,447);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (506,448);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (236,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (175,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (321,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (313,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (463,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (494,449);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (253,450);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (259,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (54,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (444,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (393,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (223,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (400,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (432,451);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,452);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,453);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (323,454);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,454);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (161,454);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (24,454);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (505,455);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (19,456);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (426,457);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (15,457);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (143,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 (504,458);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (107,459);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (431,460);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (307,460);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (111,461);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (59,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,462);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (490,463);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (104,464);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (497,464);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (487,465);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (194,465);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (25,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (35,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (147,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (349,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (144,466);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (359,467);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,467);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (353,468);
INSERT INTO help_relation (help_topic_id,help_keyword_id) VALUES (238,469);


COMMIT;

