fill_help_tables.sql

开启mysql的远程连接的方法 mysql-noinstall-5.1.6-alpha-win32.zip

insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (63,21,"BLOB DATA TYPE","A BLOB is a binary large object that can hold a variable amount of\ndata. The four BLOB types are TINYBLOB, BLOB, MEDIUMBLOB, and LONGBLOB.\nThese differ only in the maximum length of the values they can hold.\nThe four TEXT types are TINYTEXT, TEXT, MEDIUMTEXT, and LONGTEXT. These\ncorrespond to the four BLOB types and have the same maximum lengths and\nstorage requirements. See [storage-requirements]. No lettercase\nconversion for TEXT or BLOB columns takes place during storage or\nretrieval.\n","","blob");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (64,33,"BOUNDARY","Boundary(g)\n\nReturns a geometry that is the closure of the combinatorial boundary of\nthe geometry value g.\n","","general-geometry-property-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (65,9,"CREATE USER","Syntax:\nCREATE USER user [IDENTIFIED BY [PASSWORD] 'password']\n    [, user [IDENTIFIED BY [PASSWORD] 'password']] ...\n\nThe CREATE USER statement creates new MySQL accounts. To use it, you\nmust have the global CREATE USER privilege or the INSERT privilege for\nthe mysql database. For each account, CREATE USER creates a new row in\nthe mysql.user table that has no privileges. An error occurs if the\naccount already exists. Each account is named using the same format as\nfor the GRANT statement; for example, 'jeffrey'@'localhost'. The user\nand host parts of the account name correspond to the User and Host\ncolumn values of the user table row for the account.\n\nThe account can be given a password with the optional IDENTIFIED BY\nclause. The user value and the password are given the same way as for\nthe GRANT statement. In particular, to specify the password in plain\ntext, omit the PASSWORD keyword. To specify the password as the hashed\nvalue as returned by the PASSWORD() function, include the PASSWORD\nkeyword. See [grant].\n","","create-user");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (66,23,"POINT","Point(x,y)\n\nConstructs a WKB Point using its coordinates.\n","","gis-mysql-specific-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (67,16,"CURRENT_USER","Syntax:\nCURRENT_USER, CURRENT_USER()\n\nReturns the username and hostname combination for the MySQL account\nthat the server used to authenticate the current client. This account\ndetermines your access privileges. Within a stored routine that is\ndefined with the SQL SECURITY DEFINER characteristic, CURRENT_USER()\nreturns the creator of the routine. The return value is a string in the\nutf8 character set.\n\nThe value of CURRENT_USER() can differ from the value of USER().\n","mysql> SELECT USER();\n        -> 'davida@localhost'\nmysql> SELECT * FROM mysql.user;\nERROR 1044: Access denied for user ''@'localhost' to\ndatabase 'mysql'\nmysql> SELECT CURRENT_USER();\n        -> '@localhost'\n","information-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (68,34,"LCASE","Syntax:\nLCASE(str)\n\nLCASE() is a synonym for LOWER().\n","","string-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (69,18,"<=","Syntax:\n<=\n\nLess than or equal:\n","mysql> SELECT 0.1 <= 2;\n        -> 1\n","comparison-operators");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (70,26,"UPDATE","Syntax:\nSingle-table syntax:\n\nUPDATE [LOW_PRIORITY] [IGNORE] tbl_name\n    SET col_name1=expr1 [, col_name2=expr2 ...]\n    [WHERE where_condition]\n    [ORDER BY ...]\n    [LIMIT row_count]\n\nMultiple-table syntax:\n\nUPDATE [LOW_PRIORITY] [IGNORE] table_references\n    SET col_name1=expr1 [, col_name2=expr2 ...]\n    [WHERE where_condition]\n\nFor the single-table syntax, the UPDATE statement updates columns of\nexisting rows in tbl_name with new values. The SET clause indicates\nwhich columns to modify and the values they should be given. The WHERE\nclause, if given, specifies the conditions that identify which rows to\nupdate. With no WHERE clause, all rows are updated. If the ORDER BY\nclause is specified, the rows are updated in the order that is\nspecified. The LIMIT clause places a limit on the number of rows that\ncan be updated.\n\nFor the multiple-table syntax, UPDATE updates rows in each table named\nin table_references that satisfy the conditions. In this case, ORDER BY\nand LIMIT cannot be used.\n\nwhere_condition is an expression that evaluates to true for each row to\nbe updated. It is specified as described in [select].\n\nThe UPDATE statement supports the following modifiers:\n\no If you use the LOW_PRIORITY keyword, execution of the UPDATE is\n  delayed until no other clients are reading from the table.\n\no If you use the IGNORE keyword, the update statement does not abort\n  even if errors occur during the update. Rows for which duplicate-key\n  conflicts occur are not updated. Rows for which columns are updated\n  to values that would cause data conversion errors are updated to the\n  closet valid values instead.\n","","update");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (71,36,"CASE STATEMENT","Syntax:\nCASE case_value\n    WHEN when_value THEN statement_list\n    [WHEN when_value THEN statement_list] ...\n    [ELSE statement_list]\nEND CASE\n\nOr:\n\nCASE\n    WHEN search_condition THEN statement_list\n    [WHEN search_condition THEN statement_list] ...\n    [ELSE statement_list]\nEND CASE\n\nThe CASE statement for stored routines implements a complex conditional\nconstruct. If a search_condition evaluates to true, the corresponding\nSQL statement list is executed. If no search condition matches, the\nstatement list in the ELSE clause is executed. Each statement_list\nconsists of one or more statements.\n\nNote: The syntax of the CASE statement shown here for use inside stored\nroutines differs slightly from that of the SQL CASE expression\ndescribed in [control-flow-functions]. The CASE statement cannot have\nan ELSE NULL clause, and it is terminated with END CASE instead of END.\n","","case-statement");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (72,26,"EXECUTE STATEMENT","Syntax:\nEXECUTE stmt_name [USING @var_name [, @var_name] ...]\n\nAfter preparing a statement, you execute it with an EXECUTE statement\nthat refers to the prepared statement name. If the prepared statement\ncontains any parameter markers, you must supply a USING clause that\nlists user variables containing the values to be bound to the\nparameters. Parameter values can be supplied only by user variables,\nand the USING clause must name exactly as many variables as the number\nof parameter markers in the statement.\n\nYou can execute a given prepared statement multiple times, passing\ndifferent variables to it or setting the variables to different values\nbefore each execution.\n","","sqlps");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (73,37,"DROP INDEX","Syntax:\nDROP INDEX index_name ON tbl_name\n\nDROP INDEX drops the index named index_name from the table tbl_name.\nThis statement is mapped to an ALTER TABLE statement to drop the index.\nSee [alter-table].\n","","drop-index");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (74,34,"MATCH AGAINST","Syntax:\n\nMATCH (col1,col2,...) AGAINST (expr [IN BOOLEAN MODE | WITH QUERY\nEXPANSION])\n\nMySQL has support for full-text indexing and searching. A full-text\nindex in MySQL is an index of type FULLTEXT. FULLTEXT indexes can be\nused only with MyISAM tables. They can be created for CHAR, VARCHAR, or\nTEXT columns with CREATE TABLE or added later using ALTER TABLE or\nCREATE INDEX. For large datasets, it is much faster to load your data\ninto a table that has no FULLTEXT index and then create the index after\nthat, than to load data into a table that has an existing FULLTEXT\nindex.\n","mysql> SELECT id, body, MATCH (title,body) AGAINST\n    -> ('Security implications of running MySQL as root') AS score\n    -> FROM articles WHERE MATCH (title,body) AGAINST\n    -> ('Security implications of running MySQL as root');\n+----+-------------------------------------+-----------------+\n| id | body                                | score           |\n+----+-------------------------------------+-----------------+\n|  4 | 1. Never run mysqld as root. 2. ... | 1.5219271183014 |\n|  6 | When configured properly, MySQL ... | 1.3114095926285 |\n+----+-------------------------------------+-----------------+\n2 rows in set (0.00 sec)\n","fulltext-search");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (75,4,"ABS","Syntax:\nABS(X)\n\nReturns the absolute value of X.\n","mysql> SELECT ABS(2);\n        -> 2\nmysql> SELECT ABS(-32);\n        -> 32\n","mathematical-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (76,30,"POLYFROMWKB","PolyFromWKB(wkb[,srid]), PolygonFromWKB(wkb[,srid])\n\nConstructs a POLYGON value using its WKB representation and SRID.\n","","gis-wkb-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (77,34,"NOT LIKE","Syntax:\nexpr NOT LIKE pat [ESCAPE 'escape_char']\n\nThis is the same as NOT (expr LIKE pat [ESCAPE 'escape_char']).\n","","string-comparison-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (78,34,"SPACE","Syntax:\nSPACE(N)\n\nReturns a string consisting of N space characters.\n","mysql> SELECT SPACE(6);\n        -> '      '\n","string-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (79,6,"MBR DEFINITION","Its MBR (Minimum Bounding Rectangle), or Envelope. This is the bounding\ngeometry, formed by the minimum and maximum (X,Y) coordinates:\n","((MINX MINY, MAXX MINY, MAXX MAXY, MINX MAXY, MINX MINY))\n","gis-class-geometry");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (80,23,"GEOMETRYCOLLECTION","GeometryCollection(g1,g2,...)\n\nConstructs a WKB GeometryCollection. If any argument is not a\nwell-formed WKB representation of a geometry, the return value is NULL.\n","","gis-mysql-specific-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (81,4,"*","Syntax:\n*\n\nMultiplication:\n","mysql> SELECT 3*5;\n        -> 15\nmysql> SELECT 18014398509481984*18014398509481984.0;\n        -> 324518553658426726783156020576256.0\nmysql> SELECT 18014398509481984*18014398509481984;\n        -> 0\n","arithmetic-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (82,21,"TIMESTAMP","TIMESTAMP[(M)]\n\nA timestamp. The range is '1970-01-01 00:00:00' to partway through the\nyear 2037.\n\nA TIMESTAMP column is useful for recording the date and time of an\nINSERT or UPDATE operation. By default, the first TIMESTAMP column in a\ntable is automatically set to the date and time of the most recent\noperation if you do not assign it a value yourself. You can also set\nany TIMESTAMP column to the current date and time by assigning it a\nNULL value. Variations on automatic initialization and update\nproperties are described in [timestamp-4-1].\n\nA TIMESTAMP value is returned as a string in the format 'YYYY-MM-DD\nHH:MM:SS' whose display width is fixed at 19 characters. To obtain the\nvalue as a number, you should add +0 to the timestamp column.\n\nNote: The TIMESTAMP format that was used prior to MySQL 4.1 is not\nsupported in MySQL 5.1; see MySQL 3.23, 4.0, 4.1 Reference Manual for\ninformation regarding the old format.\n","","date-and-time-type-overview");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (83,11,"DES_DECRYPT","Syntax:\nDES_DECRYPT(crypt_str[,key_str])\n\nDecrypts a string encrypted with DES_ENCRYPT(). If an error occurs,\nthis function returns NULL.\n\nNote that this function works only if MySQL has been configured with\nSSL support. See [secure-connections].\n\nIf no key_str argument is given, DES_DECRYPT() examines the first byte\nof the encrypted string to determine the DES key number that was used\nto encrypt the original string, and then reads the key from the DES key\nfile to decrypt the message. For this to work, the user must have the\nSUPER privilege. The key file can be specified with the --des-key-file\nserver option.\n\nIf you pass this function a key_str argument, that string is used as\nthe key for decrypting the message.\n\nIf the crypt_str argument does not appear to be an encrypted string,\nMySQL returns the given crypt_str.\n","","encryption-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (84,12,"ENDPOINT","EndPoint(ls)\n\nReturns the Point that is the endpoint of the LineString value ls.\n","mysql> SET @ls = 'LineString(1 1,2 2,3 3)';\nmysql> SELECT AsText(EndPoint(GeomFromText(@ls)));\n+-------------------------------------+\n| AsText(EndPoint(GeomFromText(@ls))) |\n+-------------------------------------+\n| POINT(3 3)                          |\n+-------------------------------------+\n","linestring-property-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (85,26,"CACHE INDEX","Syntax:\nCACHE INDEX\n  tbl_index_list [, tbl_index_list] ...\n  IN key_cache_name\n\ntbl_index_list:\n  tbl_name [[INDEX|KEY] (index_name[, index_name] ...)]\n\nThe CACHE INDEX statement assigns table indexes to a specific key\ncache. It is used only for MyISAM tables.\n\nThe following statement assigns indexes from the tables t1, t2, and t3\nto the key cache named hot_cache:\n\nmysql> CACHE INDEX t1, t2, t3 IN hot_cache;\n+---------+--------------------+----------+----------+\n| Table   | Op                 | Msg_type | Msg_text |\n+---------+--------------------+----------+----------+\n| test.t1 | assign_to_keycache | status   | OK       |\n| test.t2 | assign_to_keycache | status   | OK       |\n| test.t3 | assign_to_keycache | status   | OK       |\n+---------+--------------------+----------+----------+\n","","cache-index");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (86,11,"COMPRESS","Syntax:\nCOMPRESS(string_to_compress)\n\nCompresses a string and returns the result as a binary string. This\nfunction requires MySQL to have been compiled with a compression\nlibrary such as zlib. Otherwise, the return value is always NULL. The\ncompressed string can be uncompressed with UNCOMPRESS().\n","mysql> SELECT LENGTH(COMPRESS(REPEAT('a',1000)));\n        -> 21\nmysql> SELECT LENGTH(COMPRESS(''));\n        -> 0\nmysql> SELECT LENGTH(COMPRESS('a'));\n        -> 13\nmysql> SELECT LENGTH(COMPRESS(REPEAT('a',16)));\n        -> 15\n","encryption-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (87,26,"INSERT","Syntax:\nINSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name [(col_name,...)]\n    VALUES ({expr | DEFAULT},...),(...),...\n    [ ON DUPLICATE KEY UPDATE col_name=expr, ... ]\n\nOr:\n\nINSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name\n    SET col_name={expr | DEFAULT}, ...\n    [ ON DUPLICATE KEY UPDATE col_name=expr, ... ]\n\nOr:\n\nINSERT [LOW_PRIORITY | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name [(col_name,...)]\n    SELECT ...\n    [ ON DUPLICATE KEY UPDATE col_name=expr, ... ]\n\nINSERT inserts new rows into an existing table. The INSERT ... VALUES\nand INSERT ... SET forms of the statement insert rows based on\nexplicitly specified values. The INSERT ... SELECT form inserts rows\nselected from another table or tables. INSERT ... SELECT is discussed\nfurther in [insert-select].\n","","insert");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (88,15,"COUNT","Syntax:\nCOUNT(expr)\n\nReturns a count of the number of non-NULL values in the rows retrieved\nby a SELECT statement.\n\nCOUNT() returns 0 if there were no matching rows.\n","mysql> SELECT student.student_name,COUNT(*)\n    ->        FROM student,course\n    ->        WHERE student.student_id=course.student_id\n    ->        GROUP BY student_name;\n","group-by-functions");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (89,26,"HANDLER","Syntax:\nHANDLER tbl_name OPEN [ AS alias ]\nHANDLER tbl_name READ index_name { = | >= | <= | < } (value1,value2,...)\n    [ WHERE where_condition ] [LIMIT ... ]\nHANDLER tbl_name READ index_name { FIRST | NEXT | PREV | LAST }\n    [ WHERE where_condition ] [LIMIT ... ]\nHANDLER tbl_name READ { FIRST | NEXT }\n    [ WHERE where_condition ] [LIMIT ... ]\nHANDLER tbl_name CLOSE\n\nThe HANDLER statement provides direct access to table storage engine\ninterfaces. It is available for MyISAM and InnoDB tables.\n","","handler");
insert into help_topic (help_topic_id,help_category_id,name,description,example,url) values (90,3,"MLINEFROMTEXT","MLineFromText(wkt[,srid]), MultiLineStringFromText(wkt[,srid])\n\nConstructs a MULTILINESTRING value using its WKT representation and\nSRID.\n","","gis-wkt-functions");
insert into help_topic (help_topic_id,help_catego