-- phpMyAdmin SQL Dump
-- version 2.10.3
-- http://www.phpmyadmin.net
-- 
-- 主機: localhost
-- 建立日期: Nov 11, 2014, 03:19 AM
-- 伺服器版本: 5.0.51
-- PHP 版本: 5.2.6

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";

-- 
-- 資料庫: `for_fortrend`
-- 
CREATE DATABASE `for_fortrend` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
USE `for_fortrend`;

-- --------------------------------------------------------

-- 
-- 資料表格式： `about_art`
-- 

CREATE TABLE `about_art` (
  `id` int(11) NOT NULL,
  `content` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '關於我們',
  `show` varchar(11) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `about_art`
-- 

INSERT INTO `about_art` VALUES (1, '投射式電容觸控面板被蘋果Apple炒起來後， 已成為日常生活中的人機介面，Win 8將在2012年10月推出後， 中大尺寸觸控面板市場需求每年會有數倍的成長， 據Display Search預估一年約有千億美元的需求量。', '1');
INSERT INTO `about_art` VALUES (2, '投射式電容觸控面板中以OGS成本最低，品質最好，是未來市場的主流。微軟於2012年7月併購一家生產OGS廠商 Perceptive Pixel，韓國政府也在今年投入700億韓圜推OGS，顯示大家看好OGS。', '');
INSERT INTO `about_art` VALUES (3, '富創得的OGS觸控面板結構及製程獨特，沒有尺寸限制，成本比他廠低， 愈大尺寸競爭力愈強 ，玻璃強度強， 不必使用氫氟酸二次強化製程，已量產多年， 技術純熟， 並獲國際專利四十餘項。', '');

-- --------------------------------------------------------

-- 
-- 資料表格式： `about_history`
-- 

CREATE TABLE `about_history` (
  `id` int(11) NOT NULL,
  `year` varchar(30) collate utf8_unicode_ci NOT NULL COMMENT '年分',
  `content` varchar(30) collate utf8_unicode_ci NOT NULL COMMENT '歷年紀事',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `about_history`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `about_info`
-- 

CREATE TABLE `about_info` (
  `id` int(11) NOT NULL,
  `time` varchar(30) collate utf8_unicode_ci NOT NULL COMMENT '成立時間',
  `add` varchar(30) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `about_info`
-- 

INSERT INTO `about_info` VALUES (1, '2005年5月', '台灣 新北市 林口工四路20號');

-- --------------------------------------------------------

-- 
-- 資料表格式： `admin_user`
-- 

CREATE TABLE `admin_user` (
  `id` int(10) NOT NULL,
  `loginuser` varchar(50) collate utf8_unicode_ci default NULL,
  `loginid` varchar(30) collate utf8_unicode_ci default NULL,
  `loginpw` varchar(30) collate utf8_unicode_ci default NULL,
  `loginpv` varchar(10) collate utf8_unicode_ci default NULL,
  `loginip` char(15) collate utf8_unicode_ci default NULL,
  `logindate` datetime default NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `admin_user`
-- 

INSERT INTO `admin_user` VALUES (1, 'User', 'admin', '!#%&admin&%#!', '99', '', NULL);

-- --------------------------------------------------------

-- 
-- 資料表格式： `contact_info`
-- 

CREATE TABLE `contact_info` (
  `id` int(11) NOT NULL,
  `add` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '地址',
  `add_en` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '英文地址',
  `tel` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '電話',
  `fax` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '傳真',
  `mail` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '信箱',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `contact_info`
-- 

INSERT INTO `contact_info` VALUES (1, '244 新北市林口區工四路20號', '.', '02-2601-5678', '02-2601-3075', 'service@touchpanelpro.com');

-- --------------------------------------------------------

-- 
-- 資料表格式： `contact_info2`
-- 

CREATE TABLE `contact_info2` (
  `id` int(11) NOT NULL auto_increment,
  `add` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '地址',
  `add_en` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '英文地址',
  `tel` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '電話',
  `fax` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '傳真',
  `mail` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '信箱',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=7 ;

-- 
-- 列出以下資料庫的數據： `contact_info2`
-- 

INSERT INTO `contact_info2` VALUES (1, '美國-聯絡人 胡大文 Darwin Hu', 'Business Development, Sillcon Valley, 761 Harry Road, San Jose, CA 95120', '+1-408-421-8887', '', 'darwin_hu@tochpanelpro.com');
INSERT INTO `contact_info2` VALUES (2, '韓國-聯絡人 Chuns Kim', '#420, Dong Yang Trebelle park, 272, Shi Min Dae Ro, Dong An-Gu,   An Yang-city, Gyung Gi-province R.O.Korea ', '+82-31-382-0624', '', 'ademtech@hotmail.com');
INSERT INTO `contact_info2` VALUES (3, '韓國-聯絡人 Seok Bon, Koo', 'Flat 405, GS Hangang Eclat, 16-85, Hangangro3-Ga, Yongsan-Gu, Seoul, Korea 140-791', '+82 2 711 0323', '', 'vonkoo@hotmail.com');

-- --------------------------------------------------------

-- 
-- 資料表格式： `download_drdl`
-- 

CREATE TABLE `download_drdl` (
  `drdl_id` int(20) NOT NULL,
  `drdl_title` varchar(500) collate utf8_unicode_ci NOT NULL,
  `drdl_content` varchar(500) collate utf8_unicode_ci NOT NULL,
  `drdl_pic` varchar(500) collate utf8_unicode_ci NOT NULL,
  `drdl_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `drdl_purview` varchar(10) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`drdl_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `download_drdl`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `download_techdl`
-- 

CREATE TABLE `download_techdl` (
  `techdl_id` int(200) NOT NULL,
  `techdl_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_version` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_os` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_description` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_proposal` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_spec` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_protocal` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_driver` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_guide` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_fw` varchar(500) collate utf8_unicode_ci NOT NULL,
  `techdl_purview` varchar(10) collate utf8_unicode_ci NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `download_techdl`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `download_techdl_list`
-- 

CREATE TABLE `download_techdl_list` (
  `techdl_list_id` int(255) NOT NULL,
  `techdl_list_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`techdl_list_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `download_techdl_list`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `download_videodl`
-- 

CREATE TABLE `download_videodl` (
  `videodl_id` int(20) NOT NULL,
  `videodl_title` varchar(500) collate utf8_unicode_ci NOT NULL,
  `videodl_content` varchar(500) collate utf8_unicode_ci NOT NULL,
  `videodl_pic` varchar(500) collate utf8_unicode_ci NOT NULL,
  `videodl_link` varchar(500) collate utf8_unicode_ci NOT NULL,
  `videodl_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `videodl_purview` varchar(20) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`videodl_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `download_videodl`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `index_footer`
-- 

CREATE TABLE `index_footer` (
  `id` int(10) NOT NULL,
  `tel` varchar(255) collate utf8_unicode_ci default NULL,
  `fax` varchar(255) collate utf8_unicode_ci default NULL,
  `mail` varchar(255) collate utf8_unicode_ci default NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `index_footer`
-- 

INSERT INTO `index_footer` VALUES (1, '+886-2-2601-5678', '+886-2-2601-3075 ', 'service@touchpanelpro.com');

-- --------------------------------------------------------

-- 
-- 資料表格式： `index_info`
-- 

CREATE TABLE `index_info` (
  `id` int(11) NOT NULL auto_increment,
  `show` varchar(11) collate utf8_unicode_ci default NULL,
  `title` varchar(255) collate utf8_unicode_ci default NULL,
  `content` varchar(255) collate utf8_unicode_ci default NULL,
  `edit_date` datetime default NULL,
  `add_date` datetime default NULL,
  `youtube` varchar(255) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=3 ;

-- 
-- 列出以下資料庫的數據： `index_info`
-- 

INSERT INTO `index_info` VALUES (1, '1', '獨創性技術', '富創得科技採用Cell製程，玻璃利用率高、玻璃強度強，22"觸控面板可通過1kg/1M的落球測試。製程中所使用的耐高溫材料可耐500度高溫，不碳化、不導電。獨特的多層ITO導電層，無架橋及小絕緣點的創新設計，不會氧化，抗ESD也強。 有高硬度抗刮表面、不需與LCD全面貼合。獲得40項國際專利，10點以上觸控已通過Windows 8認證。', '2014-09-17 15:19:50', '2013-09-26 12:10:37', 'http://www.youtube.com/embed/654NNMtUZB8?wmode=tra');

-- --------------------------------------------------------

-- 
-- 資料表格式： `industry_list`
-- 

CREATE TABLE `industry_list` (
  `id` int(11) NOT NULL,
  `title` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '標題',
  `index_content` varchar(140) collate utf8_unicode_ci NOT NULL,
  `from` varchar(8) collate utf8_unicode_ci NOT NULL COMMENT '出處',
  `content` varchar(5000) collate utf8_unicode_ci NOT NULL COMMENT '內容',
  `date` date NOT NULL COMMENT '時間',
  `show` varchar(11) collate utf8_unicode_ci NOT NULL COMMENT '首頁顯示',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `industry_list`
-- 

INSERT INTO `industry_list` VALUES (1, '從供過於求到供不應求 觸控產業的風險和機遇', '', 'J.P.Morg', 'After prolonged oversupply and margin decline, we now expect over-supply in the touch panel industry to reverse on the back of the launch of Windows 8 along with low-cost tablet PCs.Our analysis suggests the demand from touch-on-PC and ever-growing tablet would outstrip realistic mid/large-size touch panel supply.This would likely create tight supply in 4Q12 onwards especially for One-Glass-Solution ("OGS") capacity.We believe TPK stands out in this trend.Other touch panel makers could also see spill-over effect in 2H12. <br />\r\n<br />\r\n<a href="./templates/index/img/packeg/20120718_JPMorgan.pdf" target="_blank"><img src="./templates/index/img/packeg/20120718_JPMorgan.png" align="left" /></a>', '2012-07-18', '0');
INSERT INTO `industry_list` VALUES (10, '電磁波對人體的危害', '電磁波對人體的危害', '本文摘錄', '電磁波輻射能量較低，不會使物質發生游離現象，也不會直接破壞環境物質，但在到處充滿電子訊用品器材的現代生活，其電磁干擾特性卻不可掉以輕心，因為它隨時可能使人面臨危害的境地。電磁波的危害長時間使用電腦之後，會感到身體疲勞、眼睛疲倦、肩痛、頭痛、想睡、不安，這些都是受了電磁波的影響。電磁波還會使人的免疫機能下降、人體中的鈣質減少，並引致異常生產、流產、視覺障礙、阻礙細胞分裂如癌、白血病、腦腫瘤...等。此外，電磁波會散發出一種擾亂人體狀態的正離子。<br>\r\n<br>\r\n經實驗研究和調查觀察結果表明，電磁輻射對健康的危害是多方面的、複雜的，主要危害表現如下：<br>\r\n<br>\r\n１. 對中樞神經系統的危害<br>\r\n<br>\r\n神經系統對電磁輻射的作用很敏感，受其低強度反複作用後，中樞神經系統機能發生改變，出現神經衰弱症候群，主要表現有頭痛、頭暈、無力、記憶力減退、睡眠障礙（失眠、多夢或嗜睡）、白天打瞌睡、易激動、多汗、心悸、胸悶、脫髮等，尤其是入睡困難、無力、多汗和記憶力減退更為突出，這些均說明大腦是抑制過程佔優勢。所以受害者除有上述症候群外，還表現有短時間記憶力減退、視覺運動反應時值明顯延長、手腦協調動作差、表現對數字劃記速度減慢、出現錯誤較多。<br>\r\n<br>\r\n２. 對機體免疫功能的危害<br>\r\n<br>\r\n使身體抵抗力下降，動物實驗和對人群受輻射作用的研究和調查表明，人體的白血球吞噬細菌的百分率和吞噬的細菌數均下降。此外受電磁輻射長期作用的人，其抗體形成受到明顯抑制。<br>\r\n<br>\r\n３.對心血管系統的影響<br>\r\n<br>\r\n受電磁輻射作用的人，常發生血液動力學失調，血管通透性和張力降低．由於植物神經調節功能受到影響，人們多以心動過緩症狀出現，少數呈現心動過速．受害者出現血壓波動，開始升高，後又回復至正常，最後出現血壓偏低；心電圖出現RT波的電壓下降，這是迷走神經的過敏反應，也是心肌營養障礙的結果；P?Q間的延長，P波加寬，說明房室傳導不良。此外，長期受電磁輻射作用的人，其心血管系統的疾病，會更早更易促使其發生和發展。<br>\r\n<br>\r\n４.對血液系統的影響<br>\r\n<br>\r\n在電磁輻射的作用下，周圍血像可出現白血球不穩定，主要是下降傾向，白血球減少，紅血球的生成受到抑制，出現網狀紅血球減少。對操縱雷達的人健康調查結果表明，多數人出現白血球降低。此外，當無線電波和放射線同時作用人體時，對血液系統的作用較單一因素作用可產生更明顯的傷害。<br>\r\n<br>\r\n５.對生殖系統和遺傳的影響<br>\r\n<br>\r\n長期接觸超短波發生器的人，可出現男人性機能下降，陽萎；女人出現月經周期紊亂。由於睪丸的血液循環不良，對電磁輻射非常敏感，精子生成受到抑制而影響生育；使卵細胞出現變性，破壞了排卵過程，而使女性失去生育能力。 <br>\r\n<br>\r\n高強度的電磁輻射可以產生遺傳效應，使睪丸染色體出現畸變和有絲分裂異常。妊娠婦女在早期或在妊娠前，接受了短波透熱療法，結果使其子代出現先天性出生缺陷（畸形嬰兒）。<br>\r\n<br>\r\n６.對視覺系統的影響<br>\r\n<br>\r\n眼組織含有大量的水份，易吸收電磁輻射功率，而且眼的血流量少，故在電磁輻射作用下，眼球的溫度易升高。溫度升高是造成產生白內障的主要條件，溫度上升導玫眼晶狀體蛋白質凝固，多數學者認為，較低強度的微波長期作用，可以加速晶狀體的衰老和混濁，並有可能使有色視野縮小和暗適應時間延長，造成某些視覺障礙。此外，長期低強度電磁輻射的作用，可促使視覺疲勞，眼感到不舒適和眼感乾燥等現象。<br>\r\n<br>\r\n７.電磁輻射的致癌和致癌作用<br>\r\n<br>\r\n大部份實驗動物經微波作用後，可以使癌的發生率上升．一些微波生物學家的實驗表明，電磁輻射會促使人體內的（遺傳基因），微粒細胞染色體發生突變和有絲分裂異常，而使某些組織出現病理性增生過程，使正常細胞變為癌細胞。美國駐國外一大使館人員長期受到微波竊聽所發射的高度電磁輻射的作用，造成大使館人員白血球數上升，癌發生率較正常人為高。又如受高功率遠程微波雷達影響下的地區，經調查，當地癌患者急增。微波對人體組織的致熱效應，不僅可以用來進行理療，還可以用來治療癌症，使癌組織中心溫度上升，而破壞了癌細胞的增生。<br>\r\n<br>\r\n除上述的電磁輻射對健康的危害外，它還對內分泌系統、聽覺、物質代謝、組織器官形態改變，產生不良影響。<br>\r\n<br>\r\n(本文摘錄自科技圖書出版 環境科學基本叢書 之 環境物理 環境醫學)', '2013-10-03', '0');
INSERT INTO `industry_list` VALUES (4, '兩岸觸控技術那裏走?', '', 'CTIMES', '由CTIMES與中國會多展覽集團、中華觸摸屏網共同主辦的「掌握觸控新變革 – OGS vs. In-cell」技術論壇，昨(5/9)日在深圳會展中心圓滿落幕。這場活動是《2013中國（深圳）國際觸控面板技術展覽會》的開幕論壇，其議程主要由CTIMES規劃，並由CTIMES總編輯歐敏銓擔任主持人，其中多數講師來自台灣，共吸引了超過350名相關從業者的參與，全場不僅座無虛席，連走道也站滿了觀眾。</p>\r\n整場活動圍繞著「觸控技術往那裏走」這個大議題在談，講師專家一致認同的是：OGS將在今年起發光發熱，但現階段仍面臨良率與產能的瓶頸，下階段則要面對來自On-cell和In-cell的面板整合觸控功能的重大挑戰。</p>\r\n針對OGS的的良率問題，富創得吳明發董事長表示，先強後切的大片製程，看似能得到較大的產能，但事實上良率太低，強度又不佳，所以不是很好的生產作法。他認為先切後強的小片製程才能滿足消費市場的使用需求，理由是小片製程看似產能較低，但因良率高，整體而言會更有競爭力。此外，他也強調小片製程的進入門檻較低，中小型觸控業者可以透過結盟的方式來擴充產能、做大市場。</p>\r\n來自台灣（台積電家族）的敦泰科技，這些年在中國的觸控IC市場攻城略地，已站上一哥的地位，並獲得了Intel的投資，其發展倍受注目。敦泰科技莫良華副總經理表示，在觸控市場，M型化的趨勢也很明顯，高階與低階市場各有一片天，看不到中間市場。</p>\r\n在技術上，他強調身為IC公司，必須廣泛支援各種類型的觸控面板，但他分析指出，單層自電容技術是現階段市場看好的主流技術。他以該公司日前推出的自容兩點技術為例，雖然在性能及功能不是最好的選擇，但因成本能做到最低、可靠性高，也能滿足薄度需求，因此上月的出貨量一舉衝到三千萬片，成績斐然。</p>\r\n就功能面來說，莫良華指出今年觸控IC的四大發展重點，包括支援懸浮觸控、近接感應、觸控筆，以及手套觸控等功能。其中手套觸控的需求在中國北方特別強烈，由於該地近冬季後氣候寒冷，人們平時多戴著手套，但現在為了接聽電話而需脫下手套，是非常不方便的動作，因此誰能先做好「手套觸控」功能，就有機會搶佔這市場的商機。</p>\r\n整場活動中可以感受到在地業者渴望掌握市場商機的強烈企圖心，不論是問答時間或休息及會後時間，都積極求問可落實為自己業務環節的門徑。很顯然地，在技術面台灣業者仍擁有領先的優勢，若能與大陸在地企業緊密接軌，將可打開更大的市場腹地。CTIMES將繼續扮演此一「開門」、「接軌」的媒介角色。</p>\r\n<img src="C:\\AppServ\\www\\packeg\\20130510.jpg">\r\n', '2013-05-10', '0');
INSERT INTO `industry_list` VALUES (5, '宸鴻 要搶iPhone 6訂單', '宸鴻 要搶iPhone 6訂單 F-TPK宸鴻（3673）的六面強化單片觸控（TOL）獲蘋果認證通過，有機會用在今年旗艦機種5.5吋的iPhone 6，加上12.9吋iPad的新貼合業務，蘋果大單挹注，可望帶動TPK今年重返榮耀，但TPK昨（14）日不對單一客戶與訂單..', '聯合理財網', '<p style="text-indent:2em;">\r\n	F-TPK宸鴻（3673）的六面強化單片觸控（TOL）獲蘋果認證通過，有機會用在今年旗艦機種5.5吋的iPhone 6，加上12.9吋iPad的新貼合業務，蘋果大單挹注，可望帶動TPK今年重返榮耀，但TPK昨（14）日不對單一客戶與訂單置評。\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	NPD DisplaySearch副總裁謝勤益昨日發布報告表示，iPhone 6今年將推兩款，即4.7吋與5.5吋，同時，也將發表12.9吋的新iPad。其中iPhone 6的備貨規模，將遠超過iPhone 5s與5c，蘋果非常看好大螢幕iPhone 6商機。\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p>\r\n	<img src="/kindeditor/php/../../images/image/20140326/20140326013745_91735.jpg" alt="" /> \r\n</p>\r\n<p style="text-indent:2em;">\r\n	<img src="C:\\AppServ\\www\\packeg\\20140115.jpg" /> \r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	供應鏈人士表示，4.7吋iPhone將延用內嵌觸控（in-cell），由於4吋的iPhone 5已發表兩年多，仍然無法解決觸控邊緣不靈敏的問題，4.7吋螢幕進一步放大，不靈敏的問題會更嚴重，因此，4.7吋將是內嵌觸控的極限，螢幕無法再長大。<span style="line-height:1.5;">至於5.5吋的旗艦版iPhone，勢必要採用其他觸控技術，目前，TPK的TOL已獲得蘋果認證通過，呼聲頗高，另外一種可能的觸控技術備案，將是薄膜觸控（GF2）。</span><span style="line-height:1.5;">若5.5吋的iPhone採用TOL，則TPK通吃5.5吋版本的前段觸控感應器，以及後段的觸控貼合業務。若是採用GF2，TPK也勢必要承接GF2後段的觸控貼合訂單，此舉將使得TPK在今年重回iPhone供應鏈的懷抱。</span>\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	GF2的薄膜觸控感應器一直是由日本寫真供應，TPK與日本寫真已組成策略聯盟，共同發展奈米銀線（SNW）新一代薄膜觸控，若蘋果採用SNW來生產GF2，則TPK將通吃GF2觸控的前段與後段訂單。\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	在iPhone 4之前，TPK一直是iPhone觸控供應商，iPhone過去也占TPK營收高達40%的比重，隨著TPK有機會重回iPhone 6的供應鏈，可望大舉帶動TPK今年業績爆發。<span style="line-height:1.5;">另外，12.9吋iPad也將在今年發表，由於TPK是iPad Air與iPad mini 2的供應商，隨著12.9吋iPad上市，TPK可望擴大供應蘋果的平板用觸控產品。</span>\r\n</p>', '2014-01-15', '0');
INSERT INTO `industry_list` VALUES (6, '不做In-cell iPhone 5S轉向OGS?', '', 'CTIMES', '蘋果iPhone 5上市兩個多月以來，供貨不順的消息頻傳，主要原因還是出在In-cell良率不足，進而影響產能。就在消費者苦等不到iPhone 5的同時，市場已傳出蘋果打算在明年上半年推出iPhone 5S。</p>\r\n這不僅違背了蘋果以往一年只推一款手機的行銷策略，若消息屬實，也將會影響到iPhone 5的銷售狀況。對此，中華科技大學機電光工程研究所教授林彥瑞猜測，這也許只是市場傳言，但卻也代表In-cell目前仍面臨許多挑戰，技術瓶頸短期內不能解決、良率也沒辦法有效提升等因素，將迫使蘋果轉向投入其他技術的技術研發。在技術相對成熟的OGS成為首選，也因此，不少人推測，iPhone 5S將捨棄In-cell，改採OGS。</p>\r\n「OGS要勝過In-cell的機率很高，」林彥瑞指出，In-cell在中、大尺寸面板上有發展上的限制。然而，在主打觸控的Windows 8上市之後，未來在9.7吋-10吋的筆電或all in one電腦等產品都將導入觸控，以目前的In-cell技術來看，尚無法負擔。</p>\r\n相較於In-cell，OGS在許多方面擁有優勢，富創得科技董事長吳明發表示，其touch層和玻璃一體成形，免去貼合的動作，不僅降低成本，也不會有因高溫而產生氣泡的狀況；除此之外，以品牌廠商的角度來看，OGS技術成熟，不會有一家獨大、壟斷市場的憂慮。同時，林彥瑞強調，OGS客製化容易，能夠做到少量多樣化產品。</p>\r\n值得注意的是，儘管OGS大片製程的強度上較為不足，因此在小片製程較為有利，但台灣仍有友達、奇美電、Cando、勝華等面板廠專注在大片製程上。林彥瑞表示，這是過去歷史的包袱所產生。早期因在大尺寸面板上的落後，使的一些面板廠不得不轉型作觸控，然而既有設備還未折舊，即使強度不足，業者仍只能繼續做下去。</p>', '2012-11-28', '0');
INSERT INTO `industry_list` VALUES (7, '面板太髒 無菌化觸控面板有解', '', 'CTIMES', '<p>\r\n	隨著現代人人手一支智慧型手機、平板電腦，觸控面板已經蔚為主流。但有一個驚人的新醫學新聞：根據英國「每日郵報」報導英國消費者團體「<a href="http://www.dailymail.co.uk/news/article-2423051/How-smartphones-tablets-harbour-thousands-germs-TOILET-SEAT.html">Which？</a>」隨機測試三十支智慧手機與三十部平板電腦的細菌含量，發現有些智慧手機與平板電腦的觸控螢幕，細菌比馬桶座還要高出30倍以上。把臉貼在這樣一個細菌的溫床上，比無線電訊號輻射SAR還要更致命。\r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	為此，觸控業者想出為觸控面板加值的作法，也就是讓這些行動面板「無菌化」。富創得日前表示，該公司發展出一項新製程，透過在觸控面板上預鍍製一層藍寶石的膜層，在經過紫外線或日光燈照射後，會產生”氫氧自由離子基(OH-)”，可有效破壞細菌胞膜，亦可固化病毒蛋白，抑制病毒活動能力，且可將細菌還原成CO<sub>2</sub>和H<sub>2</sub>O。\r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	富創得表示，此技術的殺菌能力達99.99%，還可以有效分解空氣難聞異味。但這一膜層除了無菌化的功用外，還能有效吸收UV紫外光。眼睛中的視網膜若過度接收UV紫外光，會使得眼睛的功能衰退，水晶體產生白內障，未老先衰，而不論LCD顯示器會產生UV紫外光，而藍寶石的特性亦能吸收UV紫外光，有助於防制這一個危險因素。\r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	加上藍寶石的鍍膜層還有一個好處，就是增加了屏幕表面硬度，大大降低了受環境灰塵中硬顆粒磨蝕的機會，保持屏幕的無刮痕狀態。藍寶石的高水滴角特性，也讓髒污不易黏著於表面，容易擦拭保潔。\r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n看起來，觸控面板除了朝更輕薄、低成本和大尺寸發展外，還可從其他差異化的角度切入。當然，這些賣點不能讓消費者感到太「高貴」，否則，消費者大可從更實惠的方式來達成同樣的目的，例如多擦拭面板，以及貼一片好一點的保護膜即可。\r\n<p>\r\n	<br />\r\n<img src="templates/index/img/packeg/20131011.jpg" align="left" /> \r\n</p>', '2013-10-11', '0');
INSERT INTO `industry_list` VALUES (8, '2013年全球觸控模組營收估增逾4成', '', '精實新聞', '市場研究機構NPD DisplaySearch研究總監謝忠利指出，2013年全球觸控（面板）模組出貨數量與金額均將較去年持續強勁成長。其中，全球觸控模組今年出貨量上看15.74億片（台）、年成長率估達19%，主要係觸控手機出貨穩定增加，並且平板電腦出貨大幅攀升所帶動。預估2013年全球觸控模組出貨金額（營收）更將達到341億美元、年增率上看41%。主要動能來自於投射電容觸控技術應用擴大（單價較高）、智慧型手機螢幕大尺寸化，以及平板電腦市場強勁成長。\r\n</p>\r\n就個別應用來看，據估計，2012年全球觸控手機出貨量約達9.7億支，滲透率約59%。預估2013出貨量將達11.26億支、年增估16%，滲透率估達62%，2014年到2015年全球觸控手機出貨量可能分別達到12.9億支、14.6億支，年增估分別達15%、13%。\r\n</p>\r\n目前應用於手機之觸控技術包含In-Cell、On-Cell、包含OGS單片玻璃與GF1薄膜結構等投射電容觸控解決方案、電阻式及其他技術等等。\r\n</p>\r\n其中，In-Cell技術目前主要係由JDI提供，Apple為現階段最大客戶。但受限於良率、雜訊、iPhone成長趨緩、缺乏其他廠牌採用等等因素影響，預估2013、2014年In-Cell觸控技術在手機觸控面板市場比重可能都在13%附近。\r\n</p>\r\nOn-Cell則由群創（3481）從2013年首季開始供應TOD產品，並且彩晶（6116）、華映（2475）也展開相關業務，預估2013年、2014年On-Cell在手機觸控市場比重可能分別達17%、20%。\r\n</p>\r\n至於OGS/Film薄膜結構投射電容觸控技術2013年與2014年比重可能仍有5成以上。電阻式產品比重今明兩年則估約10%-12% 。\r\n</p>\r\n平板電腦應用方面，根據NPD DisplaySearch預測，2013年全球平板電腦出貨規模上看2.3億台、年成長率估達41%，2014年、2015年全球平板電腦出貨量規模分別將達2.9億台、3.5億台，年增率分別估達26%、19%。由於平板電腦100%都係採用觸控螢幕，隨著平板電腦市場擴大、對於觸控模組需求同步提升。不過，值得注意的是，近來平板電腦螢幕呈現小尺寸化趨勢（從早期10吋規格、漸漸走向7-8吋），這並不利於平板電腦觸控模組營收表現。</p>\r\n而目前應用於平板電腦主要觸控技術包括GF2薄膜結構與OGS單片玻璃等投射電容觸控技術、On-Cell技術等等。其中，GF2係由日廠供應、iPad mini與新款iPad採用，已經對台廠GG雙層玻璃結構觸控供應鏈造成衝擊。OGS則由Google Nexus 7和Amazon Kindle Fire等非蘋果廠牌所採用。\r\n</p>\r\n至於觸控筆記型電腦2012年出貨量估僅445萬台，原本預估，2013年預期將成長至3000萬台以上、年增估達7倍、滲透率可望達到18%，但近來已下修。接下來2014年、2015年全球觸控筆電出貨量及滲透率又將如何發展？關鍵在於觸控模組成本。目前被認為最適合筆電的觸控技術為OGS單片玻璃技術（考量重量、厚度、成本等因素），但廠商正持續推出低價OGS解決方案，例如群創推出InnoTouch，以及TPK宸鴻（3673）今年第三季將推的低成本OGS方案。\r\n</p>\r\n根據NPD DisplaySearch調查與預測，全球觸控（面板）模組出貨規模（包含數量與金額）係從2009年開始顯著成長。預估從2013年全球觸控面板模組出貨數量與金額（營收）年增率可望分別維持19%、41%水準，但2014年全球觸控模組出貨量與營收年成長率可能分別降至16%、15%，2015年全球觸控模組出貨量與金額年增則可能進一步縮減至14%、11%。\r\n</p>', '2013-08-16', '0');
INSERT INTO `industry_list` VALUES (9, 'OGS為觸控NB成本最平衡解決方案', '', '精實新聞', '市場研究機構NPD DisplaySearch在Touch Sensor Market and Evolution Report報告指出，筆記型電腦的觸控感應線路結構目前以SITO蝕刻方式的OGS（one glass solution，單片式觸控方案）為主，2012年出貨比重約達78%，預計2013年比重將提高到84%。雖然OGS並非成本最低的觸控面板方案，但卻是最平衡的方案。所謂「平衡」指的是供應鏈、製程、靈敏度、規格、厚度、重量與成本的綜合性考量。這些才是品牌廠採購時所有的考慮關鍵，而不只是僅考慮模組價格。\r\n</p>\r\n回到觸控介面來看，NPD DisplaySearch表示，其實談行動裝置使用的觸控技術已經不太具有意義，因為投射式電容已經幾乎獲得全面勝利，即使是面板內嵌式in-cell與on-cell，也已經從早期的各種技術原理（如光學式photo-sensing），到如今僅剩下電容式。所以，討論觸控技術主要的關鍵是在觸控感應線路結構。\r\n</p>\r\n相較於應用在手機的觸控結構多樣化，筆記型電腦所使用的觸控感應線路結構相當收斂。主要是因為10吋等級以上的觸控面板至少40美元到70美元（尚不含全貼合），加上Windows 8較嚴格的規格要求，能夠跨入門檻的供應商自然就少。NPD DisplaySearch評估，若再考慮全貼合，那麼觸控模組廠就需具備充足的營運現金、以備先購買液晶面板，並且還要有良好的貼合良率，否則在資金壓力與良率損失賠償下，很可能帶來營運周轉上的困境。 \r\n</p>\r\n根據NPD DisplaySearch觀察，薄膜式G/F/F觸控面板雖然在2012年時曾佔觸控NB約13%的出貨比重，但預計2013年在OGS放量衝擊下，薄膜觸控G/F/F技術滲透率可能降到7%左右。 \r\n</p>\r\n主要原因有二，一方面薄膜電容觸控模組廠多半從電阻式起家，主要客戶來自手機等較小尺寸應用，而且生產線規模、無塵室、線路蝕刻設備均需要升級，才能邁入筆記型電腦的尺寸應用。二方面ITO本身易脆的特性、加上薄膜具伸展性，若無一定的經驗、技術能力掌握，感應線路可能容易在製程中斷裂，造成良率損失。 \r\n</p>\r\n有些模組廠提出G1F的結構，可以減少一層ITO薄膜與OCA/OCR光學膠的使用。NPD DisplaySearch說明，G1F將線路分別置於兩種阻抗值不易匹配的載板（表面玻璃與薄膜）上，除了不容易調整靈敏度外，生產上也未必容易整合。因此，有些廠商的看法是，如果不是直接將X-Y線路都置於表面玻璃成為OGS觸控面板，不然就是把X-Y線路都放在ITO薄膜、使成為G/F/F觸控面板，材料成本將可在較為流暢的製程與出貨量下被補償，所以不需要個別置於表面玻璃與薄膜。 \r\n</p>\r\n基本上，觸控模組面積越大、成本越高。因此，不論是OGS、G/F/F或是G1F，觸控模組廠提出方案的考量原因並不單純只是技術與價格問題，往往也跟廠商設備、熟悉的材料、製程有關。例如：OGS的大片製程（sheet type）考驗模組廠表面玻璃加工與二次強化的能力，但對G/F/F的模組廠來說，其表面玻璃與感應線路無關，因此可以外包給表面玻璃加工廠。反過來說，如果OGS模組廠能夠突破製程瓶頸，那麼反而具備整合供應鏈、縮短時間、降低成本等優勢。 \r\n</p>\r\n綜上，雖然不同觸控結構技術之間存有價差，但各種架構下的觸控模組成本、目前都還未降到讓品牌廠願意全面導入觸控介面。NPD DisplaySearch指出，14吋與15吋等級產品約占所有筆記型電腦總出貨量70%以上，特別是一些具有出貨量份額的低價機種。然而，觸控模組卻是面積越大、成本越高。因此，就產生了終端售價與可接受成本之間的矛盾。 \r\n</p>\r\n而若是沒有觸控介面，微軟的Windows 8和Windows 7對使用者來說，就沒有顯著差異，也就談不上升級的動機，那麼Windows最終仍將會困守在傳統的筆記型電腦框架裡。 \r\n</p>\r\n不過，新推出的SSG（strengthened sensor glass）技術，其低成本可能是低階機種導入觸控模組、提高觸控滲透率的關鍵之一。NPD DisplaySearch統計自2012年末到2013年6月，Microsoft約經過了2次要求規格的修正，修正之處並不是在於對觸控效能的妥協，而主要是跟觸控模組與整機的機構設計有關。 \r\n</p>\r\n以往全平面（edge-to-edge）的表面玻璃設計雖然美觀、有質感，但是較低良率的玻璃加工製程（包含成形、強化與鍍膜），也造成觸控模組成本難以下降的主因。若Microsoft能夠接受非全平面的設計，並且放寬外露感應線路引線區（ink or border）的寬度要求，那麼觸控模組廠與系統廠就可以一塊類似強化過、單純矩形切割的感應線路玻璃，加以覆蓋外框（bezel），來取代全平面的表面玻璃設計，以明顯降低成本。這就是所謂的SSG。 \r\n</p>\r\nNPD DisplaySearch強調，SSG的導入意義並不是要取代OGS，相反地，SSG與OGS相輔相成。而SSG也讓液晶面板廠有更多的機會將原本的面板生產線轉移到觸控領域。OGS小片製程（piece type）無強度的妥協，適用於高階機種，OGS大片製程（sheet type）具備規模與效率，適合中高階機種。而SSG雖無OGS的全平面設計，但是其低成本優勢可能是低階機種導入觸控模組、提高觸控滲透率的關鍵。\r\n</p>', '2013-06-21', '0');
INSERT INTO `industry_list` VALUES (11, '杨维俊与台湾富创得科技股份有限公司洽谈项目', '', '天水網', '<p>\r\n	天天天水网上海电【记者 辛闻】1月9日晚，中共天水市委副书记、市长杨维俊一行在上海与台湾富创得科技股份有限公司董事长吴明发洽谈OGS触摸屏生产线建设项目。天水市副市长雷鸣、市政府秘书长逯克宗以及市工信委、天水天光半导体有限责任公司负责人一同参加洽谈。\r\n</p>\r\n<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140113_TSRB_01.jpg" align="center" /> \r\n</p>\r\n<br />\r\n<p>\r\n	台湾富创得科技股份有限公司成立于1998年，是专业研发和生产国际型触摸屏的高科技企业。OGS触摸屏生产线建设项目是显示与控制系统融为一体的高科技产业，系列产品在工业、农业、国防、军事、民用等各个领域应用广泛、前景广阔。台湾富创得科技股份有限公司与天水天光半导体有限责任公司合作建设的OGS触摸屏项目，一期计划投资4亿元人民币，其中设备投资2.79亿元人民币。项目建成后，预计年产值可达9亿多元，实现利税约2亿元。\r\n</p>\r\n<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140113_TSRB_02.jpg" align="center" /> \r\n</p>\r\n<br />\r\n<p>\r\n	双方就OGS触摸屏项目实施进行了深入洽谈。杨维俊在听取吴明发对台湾富创得科技股份有限公司及OGS触摸屏项目情况的介绍后表示，欢迎台湾富创得科技股份有限公司来天水投资发展，我们将落实各项优惠政策，全力支持项目建设。希望富创得公司与天水天光公司、投资方加强合作，尽快启动实施项目，利用现有的标准化厂房，尽量缩短项目建设周期，促进项目早日建成投产。\r\n</p>\r\n<br />\r\n<p>\r\n	雷鸣向客商介绍了天水经济技术开发区优惠政策以及科技孵化大厦、标准化厂房建设等方面的情况。\r\n</p>', '2014-01-13', '0');
INSERT INTO `industry_list` VALUES (12, 'iPhone 6 還是不太可能全面採用藍寶石水晶玻璃', 'Apple 蘋果公司對藍寶石水晶玻璃這個新材質倍感興趣已是眾多皆知的事，除了在 iPhone 相機與 Touch ID 上使用此一材質外，更與極特先進（GT Advanced）簽下一筆供應約，再加上近日曝光的相關設備..', 'TechNews', 'Apple 蘋果公司對藍寶石水晶玻璃這個新材質倍感興趣已是眾多皆知的事，除了在 iPhone 相機與 Touch ID 上使用此一材質外，更與極特先進（GT Advanced）簽下一筆供應約，再加上近日曝光的相關設備來看，全部顯示蘋果有意在 iPhone 上使用藍寶石水晶玻璃來做為面板的保護玻璃，不過總整體設備規格與時程來看，要在 2014 年的 iPhone 上出現藍寶石水晶玻璃面板，恐怕可能性還是不大。<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140207_iphone6_01.jpg" align="center" /> \r\n</p>\r\n<br />\r\n根據 9to5Mac 的報導，蘋果最近在其設立於美國亞歷桑納州的工廠中已開使積極準備藍寶石水晶玻璃的生產相關動作，而且一如各界對蘋果此舉的猜測，蘋果的確打算透過極特先進的設備，把藍寶石水晶玻璃用在 iPhone 的面板上。<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140207_iphone6_02.jpg" align="center" /> \r\n</p>\r\n<br />\r\n最大的證據在於，極特先進最近引進了由 Intego 生產的 Sirius 藍寶石水晶玻璃面板的檢測工具組件，從描述來看，這是為了檢測藍寶石水晶玻璃的品質是否能符合於觸控面板所需的自動化檢驗機具，而不是用來做為鏡頭保護或是 Touch ID 這種小尺寸玻璃所需要的測試流程。<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140207_iphone6_03.jpg" align="center" /> \r\n</p>\r\n<br />\r\nIntego Sirius機具的尺寸不小，可以同時容納多組面板同時檢測以加快速度。而從取得的文件來看，極特先進正是為與蘋果合作所需才引進這類的檢測工具，整個證據看來，蘋果的確是有打算把藍寶石水晶玻璃做為面板的玻璃。<br />\r\n<br />\r\n根據報導，蘋果夥同極特先進已購置了 518 套藍寶石晶爐，產量預計到每年可生產 1.03 億至 1.16 億片 5 吋大小的顯示玻璃，且後續還有 420 套晶爐訂單，每年可再增加 8,400 萬到 9,400 萬片的玻璃，看似足以供應蘋果 iPhone 所需才對。<br />\r\n<br />\r\n不過情況真有如此樂觀？在詢問過了解藍寶石相關產業的人士後，了解到極特先進與蘋果簽下的並非是設備採購合約，應該是一筆有供貨保證的採購合約，數量多寡目前不詳。不過就極特先進採用的機型來看，應是 120 公斤等級以上的藍寶石長晶爐，在良率高的狀況下，單一晶爐就需要耗時20~30天才能長成晶球，然後才能進行鑽取、切割、加工等流程。&nbsp;<br />\r\n<p>\r\n	<img src="templates/index/img/packeg/20140207_iphone6_04.jpg" align="center" /> \r\n</p>\r\n<br />\r\n以 518 套晶爐來看，就算蘋果採用了極特先進併購自 Twin Ceeks 研發的「氫離子加速器」可以避免原材料的無謂浪費與切割厚度太薄所造成的碎裂，也仍不敷 iPhone 使用。而 90 公斤的晶爐雖然的長晶速度雖可以提高一倍，只要兩週即可長晶完成，但晶體尺寸較小，如果要鑽取可以製作的新一代 iPhone 使用的 5 吋的螢幕尺寸，並不符合成本效益。<br />\r\n<br />\r\n也就是 9to5Mac 對晶爐生產量恐怕過於高估，目前看來，由於藍寶石水晶玻璃的長晶速度有其限制，在晶爐若過度加快提伸速率，就容易導致產生的原石出現汽泡、龜裂或變質，因此除非極特先進在這方便有著技術有所突破，不然在 2014 年的 iPhone 是不太可能全面採用藍寶石水晶玻璃面板的，當然，若是只提供部分機型率先採用自然可行，只是不太符合蘋果的風格而已。<br />', '2014-02-07', '1');
INSERT INTO `industry_list` VALUES (36, '變化中的觸控面板行業', '', 'KDB Daew', '<br />\r\n<b>Touchscreen market to grow twofold by 2016</b><br />\r\n<span style="line-height:1.5;">We remain optimistic about the growth of touchscreens for use in smartphones and\r\ntablet PCs. This year, we project shipments of smartphones and tablet PCs to reach\r\n1.1bn units (+32% YoY), with shipment area expanding 39% YoY to 8,580km2. The\r\nsmartphone- and tablet PC-use touchscreen market is forecast to jump 31% YoY to\r\nUS$16.4bn, or W18tr. Traditional PC manufacturers are likely to adopt touchscreens full\r\nswing starting this year. Indeed, Intel made touchscreens a required specification for all\r\n3rd generation Ultrabooks (to be released this year). We project the touchscreen market\r\nto grow at a CAGR of 104% until end-2016, as 40% of laptop computers (89mn units)\r\nand 39% of desktop computers (56mn units) are expected to adopt touchscreens. </span><br />\r\n<br />\r\n<b>Changing rules: Large players entering the touchscreen market</b><br />\r\n<span style="line-height:1.5;"> Up to this point, only small-to-medium enterprises have engaged in the touchscreen\r\nbusiness. Touchscreens for smartphones and tablet PCs require customization, as: 1)\r\ntheir cover glass designs are unique, 2) they must feature cutouts for cameras and\r\nspeakers, and 3) they must accommodate various bezel colors and logos. Indeed, this\r\nneed to produce multiple items in small volumes made the touchscreen business optimal\r\nfor small manufacturers. However, the market has recently experienced changes. Large\r\npanel makers, as well as LCD color filter producers, are entering the market due to: 1)\r\ntheir desire to find new growth drivers amid the LCD industry slowdown, 2) a surge in\r\n10-inch-or-larger touchscreen demand, and 3) ongoing standardization efforts for\r\ntouchscreens. In particular, standardization would be positive for big players with large\r\nproduction facilities, since it would enable the mass production of standardized products\r\nto bring down cost significantly. </span> <br />\r\n<br />\r\n<b>Overweight; Top picks are Samsung SDI, ELK, and Melfas</b><br />\r\n<span style="line-height:1.5;"> Although the smartphone- and tablet PC-use touchscreen market is likely to grow, fierce\r\ncompetition should hamper margin improvement. We take note of potential growth for\r\nlarge-sized touchscreens (larger than laptop panels). In addition, we believe PDP lines\r\ncould be converted to produce touchscreens. We maintain our Overweight rating on the\r\ndisplay sector, and select as our top picks Samsung SDI, which is seeing its loss-making\r\nunits turn around rapidly; ELK, which is a supplier for global PC makers; and Melfas,\r\nwhich is likely to expand its customer base and achieve ASP increases on larger TSPs.</span> <br />\r\n<br />\r\n<a href="./templates/index/img/packeg/20130603_KDB.pdf" target="_blank"><img src="./templates/index/img/packeg/20130603_KDB.png" align="left" /></a>', '2013-06-03', '0');
INSERT INTO `industry_list` VALUES (14, '高科技巨擘攜手富創得 共創觸控面板新商機', '日本Sharp佐佐木社長和中國京東方王總經理親自來台北，專程與OGS觸控面板全球一線製造廠富創得科技，於11/1日簽訂合作協議。', 'DIGITIME', '日本Sharp佐佐木社長和中國京東方王總經理親自來台北，專程與OGS觸控面板全球一線製造廠富創得科技，於11/1日簽訂合作協議。<br />\r\n<br />\r\n<br />\r\nSharp株式會社將提出最先進的IGZO，這是一款先進的高清晰、節電省能的Full HD產品LCD，交給富創得與京東方團隊，加裝背光模組與先進的OGS電容式觸控成為模組，提供給NB筆記型電腦與AIO及智慧型終端機組裝市場。<br />\r\n<br />\r\n<br />\r\n此一舉措將提升台灣的整體供應面到一個新階段，因為Sharp初期將提供13吋屏每月50萬組，6個月後可大幅增加到每月100萬組，進而將大尺寸24吋屏幕也加進供應的項目內。Sharp此舉一方面為台灣電腦產業界帶進一波強大助力，加上富創得的OGS觸控功能，可以擺脫低價產品的微利紅海競價市場，在緊接而來的雲端時代有充份的競爭力。<br />\r\n<br />\r\n<br />\r\n佐佐木社長之所以選擇富創得作為全球重要合作夥伴，因為富創得與京東方的合作夥伴團隊中，京東方在LCD panel組成上有強而有力的工程能力，加上富創得OGS觸控面板的優異競爭力，富創得水鑽石表面鍍膜的秘密武器，抗UV反射、抗菌自潔的優異能力，可以推升整體競爭力。<br />\r\n<br />\r\n<br />\r\n富創得將與搭檔京東方合作，將此IGZO OC組裝背光與OGS觸控面板，攜手進軍全球市場。在台灣目前低迷的氛圍當中，三巨頭合作注入一股強而有力的新力量，以新產品組合開創新機。<br />\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<img src="/kindeditor/php/../../images/image/20140326/20140326014425_40407.jpg" alt="" /> \r\n</p>', '2013-11-05', '0');
INSERT INTO `industry_list` VALUES (15, 'OGS觸控面板富創得 技術領先', '單片玻璃方案（OGS）觸控面板商機後市看漲。在貼合良率提升以及Windows 8新作業系統帶動的市場需求逐漸浮現下，OGS觸控面板商機可望在下半年爆發，不論大、中、小螢幕尺寸的行動裝置均將大量導入。', '工商時報', '單片玻璃方案（OGS）觸控面板商機後市看漲。在貼合良率提升以及Windows 8新作業系統帶動的市場需求逐漸浮現下，OGS觸控面板商機可望在下半年爆發，不論大、中、小螢幕尺寸的行動裝置均將大量導入。富創得科技領先同業開發出獨特OGS技術、材料及設備，受同業和國際知名大廠肯定，爭相爭取授權及技術轉移。<br />\r\n<br />\r\n<br />\r\n富創得生產成本只有其他觸控面板廠的1/4，而且生產設備的建置成本只有其他廠的1/10。因此全中國第一家使用富創得技術及設備的OGS觸控面板製造廠，今年7月已經在山東濟南開幕量產。Fortrend富創得是目前全球唯一將OGS＋Sapphire treatment結合起來，整合加工與生產的領導者。而且尺寸愈大的OGS觸控面板，價格成本愈有競爭力。在只有同業1/4的成本架構下，生產具有高效率觸控/抗菌/抗UV/抗污染/抗輻射的產品，並且在製程中無鹵/免氟，貼緊RoHS的標準與HSF的潮流趨勢，使用者用得安心；生產者有高度競爭力，發揚台灣創新精神，為國內3C業進步做支撐。<br />\r\n<br />\r\n<br />\r\n藍寶石Sapphire被覆，是在玻璃表面沉積一層Sapphire的材質，不單是運用藍寶石的高硬度可以防蝕與抗刮、耐磨擦，更因為藍寶石的濾光特性，將UV紫外線阻隔，防止對使用者眼睛視網膜的傷害。<br />\r\n<br />\r\n<br />\r\n該公司從素玻璃開始直到TP成品完善的一條龍生產設備規劃與設置，軟硬體技術皆已整合，且藍寶石可以coating被覆在玻璃、塑膠和金屬上，產品運用涵蓋IT、建築、汽車和家電等產品上，電容式觸控面板也從兩片玻璃交接的方式，進展到單片玻璃OGS式，全力投入OGS投射式電容觸控面板研發、開發到生產的Fortrend富創得科技，不但成功推出一系列大尺寸OGS觸控面板，是為這個範疇的領導者；更進一步開發出的製程，將這個產業推到新境界。<br />', '2013-08-28', '0');
INSERT INTO `industry_list` VALUES (16, '富創得科技獨特技術、解決3C產品對視覺不良影響的方法', '僅只不過幾年以前，教育界擔心學生的書包越來越重，脊柱彎曲、身形佝僂，未老先衰。再這樣下去，台灣只會更是東亞病夫，在全球的健康評比上，比飢餓非洲的人民還不如。', '工商時報', '僅只不過幾年以前，教育界擔心學生的書包越來越重，脊柱彎曲、身形佝僂，未老先衰。再這樣下去，台灣只會更是東亞病夫，在全球的健康評比上，比飢餓非洲的人民還不如。因此寄望能有一個小電腦，擁有超群的記憶容量，國文、英文、物理化學加生物，還有一本好算術，全都放在手持電腦 + 閱讀器裡，手指一撥，就出現在顯示屏，每天上學甩掉那沉重8公斤書包，快樂捏著個1公斤智慧電腦。<br />\r\n<br />\r\n<br />\r\n這個「夢」已經實現了，價格也符合「摩爾定律」；雖不說價廉物美，但是倒真的幾乎人人買得起。台灣各家發展出來的小平板、超薄筆電，性能不輸蘋果、新力，價格平易近人。時髦一點用iPad，實用一點用台灣的品牌。加上智慧型手機，屏幕一日大於一日，功能早就超越PDA，性能簡直是到了無所不能的地步，通話是最基本的功能，上網、發簡訊、打卡、照相PO網、e mail、打電動 …. 人生不可一日無之，不可一時離手，如果電池儲量不足，預備一個Power Bank隨時支援。<br />\r\n<br />\r\n<br />\r\n只見MRT捷運上，有一半人低頭用手指撥弄智慧型手機，走在路上有人邊走還邊低頭撥弄，餐廳裡的情侶，面對面；可是低著頭，各玩各的手上「智慧玩具」。已經有了一個新名詞：低頭族。這也不過是近一年的事，但是影響卻迅速且有傷害。報章雜誌；醫師都大聲呼籲：整天低頭盯螢幕；近視性白內障激增。不再是老年人的眼睛有飛蚊症、白內障，這低頭族們年紀輕輕，近視度數激增，白內障爆發；已經不只是「視茫茫」，簡直要「盲」了。原因呢？ 緊盯著螢光屏幕，眼球疲勞，最糟糕的是螢光屏幕發的光線會傷害到視神經。這在幾家國內大醫院的名眼科醫師，都做出了醫學統計報告。如果再這樣下去，有相當一部分人會到近乎於「瞎」的地步，已經不是東亞病夫，要成東亞盲夫了。<br />\r\n<br />\r\n<br />\r\n大小螢光屏幕的光源現在都是運用白光LED，這白光LED是以氮化鎵藍光LED藉著激發螢光粉，產生次生黃光，混合後以白光型式進入我們的眼睛。有部分使用UV LED 紫外光作為螢光粉光源，這不可避免的一部分紫外光線，也是造成眼睛傷害的重大原因。有眼科醫師建議，加戴個偏光濾色眼鏡，遮濾一部分紫外光與藍光。<br />\r\n<br />\r\n<br />\r\n其實這個紫外光與藍光的問題，不一定需要眼鏡族加裝濾色偏光片；可以在螢光屏幕端直接解決。使得螢光屏本身無害，去除掉使用者的潛在傷害危機，將傷害視神精的UV紫外光濾除。<br />\r\n<br />\r\n<br />\r\n富創得FORTREND擁有一項新技術，在螢光屏幕的玻璃板上加一層鍍膜，永久性的藍寶石Sapphire膜層。Sapphire藍寶石的特性是硬度大、剛性耐磨，可以保護屏幕玻璃耐刮。藍寶石鍍膜後，表面水滴角特性改變，髒污一擦即除。最重要的是可以過濾阻絕大部分UV光，只有波長較長的藍光，可以透出。使得螢光屏幕顯色柔和，也大幅減少對眼睛視神經的傷害。<br />\r\n<br />\r\n<br />\r\n解決一個問題，揚湯止沸；不如釜底抽薪。走到現階段；手持式電腦3C產品這麼發達，用途還在與日俱增，不可能丟下來不用。與其要求加戴一副眼鏡，不如在螢光屏幕端解決。我們歡迎富創得的解決之道，期待每一個新螢光屏幕，無論尺寸大小，都能夠有藍寶石鍍膜，都能有柔和的光輸出。12<br />', '2013-08-12', '0');
INSERT INTO `industry_list` VALUES (17, '富創得 獨占OGS市場', '富創得科技董事長吳明發表示，OGS（One glass solution）近年在業界的興起值得關注。OGS的技術特點主要是在保護玻璃上直接形成ITO導電膜及傳感器的技術， 一塊玻璃同時能起到保護玻璃和觸摸傳感器的雙重作用。由於其透光性、輕薄度在GF之上，產品的良率、研發投入又較o', '工商時報', '富創得科技董事長吳明發表示，OGS（One glass solution）近年在業界的興起值得關注。OGS的技術特點主要是在保護玻璃上直接形成ITO導電膜及傳感器的技術， 一塊玻璃同時能起到保護玻璃和觸摸傳感器的雙重作用。由於其透光性、輕薄度在GF之上，產品的良率、研發投入又較on、in-cell有優勢。<br />\r\n<br />\r\n<br />\r\n富創得科技開發出獨特的技術、材料及設備，品質領先業界，也是目前唯一可生產各種顏色邊框的OGS製造商，TP售價更是傳統製程所生產出的相同產品的成本。 世界各知名大廠除了紛紛下單，也爭取授權生產，目前已有多家取得授權。<br />\r\n<br />\r\n<br />\r\n該公司製程與一般採用薄膜製程的觸控廠商不同的是，其生產製程先將玻璃切割，再進行導電層的電鍍，採用奈米化工技術，可直接在面板上進行各種加工， 因為該公司玻璃強度是別人的3倍，也因為玻璃強度超高，TP和LCD不必全面貼合，這對系統廠又能節省每吋1至2美元的費用。同時獨創專利導電層是多層結構， 不必架橋，沒有架構的缺陷，製程簡單，設備成熟，設廠4個月就可完成，6個月就可量產，良率可達80％。<br />\r\n<br />\r\n<br />\r\n另外貼合的問題，目前業界除了用玻璃貼玻璃，也有用玻璃或塑膠貼1層或2層PET，除了良率低外，延遲性氣泡是永無解的問題。因為貼合要用OCA膠， OCA的材料是PVA，PVA在溫度37度以上烤會產生氣泡，氣泡會造成觸控失靈。LCD溫度達42度，因此TP使用後氣泡會逐漸產生，觸控功能也就慢慢消失。 目前國內外大廠自己生產ITO PET、OCA和控制IC，除了材料成本居高不下外，仍然無法解決ITO阻抗在通電後升高的問題，對OCA膠的延遲性氣泡也無解， 加上貼合良率也提高不起來，所以台灣、南韓和大陸多家TP廠紛紛改用富創得OGS製程。<br />', '2013-08-06', '0');
INSERT INTO `industry_list` VALUES (18, '華碩平板大單，友達勝華分食', '單片式觸控面板（One Glass Solution）需求今年起飛，勝華（2384）、友達（2409）單片式觸控面板開始供貨給華碩新款10.1吋變形平板電腦， 而友達也是主要的平板面板供應商之一。其中勝華單片式觸控在去年量產，今年隨著中大尺寸單片式觸控陸續出貨，營收比重可望由現在', '工商時報', '單片式觸控面板（One Glass Solution）需求今年起飛，勝華（2384）、友達（2409）單片式觸控面板開始供貨給華碩新款10.1吋變形平板電腦， 而友達也是主要的平板面板供應商之一。其中勝華單片式觸控在去年量產，今年隨著中大尺寸單片式觸控陸續出貨，營收比重可望由現在的10％，提升到25％的水準。<br />\r\n<br />\r\n<br />\r\n在輕薄化的趨勢之下，蘋果iPhone 5將率先採用內嵌式觸控，今年多家手機、平板電腦廠商也將改為單片式觸控面板。其中，華碩最新的10.1吋就改用單片式觸控面板， 由勝華和友達分食訂單，其中友達還同時供應10.1吋LCD面板。<br />\r\n<br />\r\n<br />\r\n友達在今年開始供應厚度約0.7毫米的單片玻璃，相較於一般雙片玻璃觸控厚度1.1毫米，厚度縮減了大約40％；此外，友達還開發出厚度在0.55毫米以下的單片玻璃觸控， 預計下半年供貨。隨著Windows 8將於下半年上市，還將進一步帶動Ultrabook和筆電搭配單片玻璃觸控的需求上揚，友達也和許多品牌廠商合作，預計在明年第1季， 大尺寸筆電也將會導入單片玻璃觸控。<br />\r\n<br />\r\n<br />\r\n勝華單片式觸控在去年量產，供應宏達電智慧型手機和日系平板電腦品牌之用，今年進一步打入華碩平板電腦供應鏈，第2季量產出貨。 今年第1季勝華單片式觸控占營收比重不到10％，隨著客戶新產品上市，勝華預估第4季單片式觸控所占營收比重可望提升到20～25％。<br />\r\n<br />\r\n<br />\r\n看好單片式觸控面板世代交替趨勢，由新加坡商Creative創新科技所發起成立的Creative漢之派橫縱聯盟已經投入卡位，聯盟中網羅了晶片開發商、 方案設計商、ID設計商、應用軟體開發商、關鍵零組件設計研發製造商等等，集聚一起提供完整的觸控應用產業服務。<br />\r\n<br />\r\n<br />\r\n另外，也有小型設計業者爭取單片式觸控面板商機，如富創得科技從2005年開始投入單片觸控面板的設計開發、製作生產，應用小片製程所生產玻璃強化結構完整的單片投射式電容觸控面板， 在國際間握有超過40多項的相關專利技術。富創得也宣布具備量產能力，未來將導入消費性平板電腦品牌廠商。<br />\r\n<br />', '2012-05-29', '0');
INSERT INTO `industry_list` VALUES (19, '富創得科技成為新加坡漢之派聯盟成員', '觸控面板廠富創得科技宣布，正式成為Creative漢之派橫縱聯盟成員企業；不僅是此聯盟目前唯一的觸控面板合作廠商，也是唯一一家來自台灣的企業。', 'Digitime', '觸控面板廠富創得科技宣布，正式成為Creative漢之派橫縱聯盟成員企業；不僅是此聯盟目前唯一的觸控面板合作廠商，也是唯一一家來自台灣的企業。', '2012-05-28', '0');
INSERT INTO `industry_list` VALUES (20, 'Microsoft 發布基本觸控手勢操控規範，舊平板也能感受到 Windows 8 魅力', '隨著科技不斷發展，新的數碼觸控螢幕也開始支援越來越多的觸控點，有的甚至已經支援 10 個手指觸控。 而 Windows 8 系統在將來也有可能被裝進多種設備中，現在能夠支援 Windows 7 的觸控 PC 也是可以使用的， 那麼如何確保在不同的設備之間提供一個相對統一的基本觸控', 'Engadget', '隨著科技不斷發展，新的數碼觸控螢幕也開始支援越來越多的觸控點，有的甚至已經支援 10 個手指觸控。 而 Windows 8 系統在將來也有可能被裝進多種設備中，現在能夠支援 Windows 7 的觸控 PC 也是可以使用的， 那麼如何確保在不同的設備之間提供一個相對統一的基本觸控操作體驗呢？Microsoft 給出了答案， 這次給出了單點和兩點觸控手勢規範，也就是說最基本的操作在兩點觸控下已經能夠完成了；其中包括向下滑動進行選擇， 從下邊緣向上滑動調出應用程序設定選單，從右邊緣向內螢幕滑動調出系統設定選單；而放大和縮小，旋轉等手勢對於那些支持 Windows 7 的舊平板來說， 也是可以輕鬆實現的，而用戶也基本上能夠快速上手。同時還加入了一個 20 像素的螢幕邊緣緩衝區，以讓那些老 Windows 7 設備的邊緣觸控不那麼敏感，防止錯按。<br />\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<img src="/kindeditor/php/../../images/image/20140326/20140326020228_45477.jpg" alt="" />\r\n</p>\r\n<br />\r\n硬件和軟件完美融合才能帶來最佳體驗，Microsoft 正在和硬件生產商合作，確保觸控螢幕能夠和觸控手勢完美匹配， 從而確保 Windows 8 的各項使用體驗能夠更加完美。跳轉影片中你可以看到演示，裡面談到了不同的觸控螢幕硬件差異對 Windows 8 實際操作帶來的影響。當然現在的應用越來越復雜， 用戶的要求也趨於多樣化，Microsoft 希望未來的 Windows 8 新設備能夠至少支援五點觸控，這樣你就可以在你的平板上彈奏一首鋼琴曲了。<br />', '2012-04-01', '0');
INSERT INTO `industry_list` VALUES (21, '分析師：Windows 8將為觸控面板市場帶來革命性需求', '不過，大多數使用者會存在的使用情境可能介於「輸入內容」與「消費內容」之間，只是使用頻率、停留時間和使用傾向各不相同而已， 而不是往兩端集中。因此，品牌可以依據不同的產品規格、成本、市場定位等因素來決定觸控螢幕的支援與否。', '電子工程專輯', '不過，大多數使用者會存在的使用情境可能介於「輸入內容」與「消費內容」之間，只是使用頻率、停留時間和使用傾向各不相同而已， 而不是往兩端集中。因此，品牌可以依據不同的產品規格、成本、市場定位等因素來決定觸控螢幕的支援與否。 Windows 8的介面設計就可以同時滿足「輸入內容」與「消費內容」的需要，使用者在兩種介面模式的切換也很容易； 這正是Windows 8與Windows 7在觸控操作上最根本的不同。Windows 7雖然支援觸控，但並沒有為這樣的操作方式在介面予以優化。<br />\r\n<br />\r\n<br />\r\nNPD DisplaySearch 顯示技術研究總監謝忠利表示：「我們可以想像情境如下──上班族在通勤、或是拜訪客戶的路途中攜帶一台平板電腦， 在過程中他以觸控螢幕操作的方式在Metro介面中瀏覽網頁；也以這樣的方式為客戶做簡報。 之後，他回到辦公室並需要以文書處理軟體為剛剛的拜訪做記錄。」<br />\r\n<br />\r\n<br />\r\n在上述情景的上半段中，使用者需要以觸控螢幕來操作；而在下半段中，他只要透過USB埠來外接滑鼠與鍵盤，同時將介面切換到Aero介面， 即能以他熟悉的工作環境來做文書處理。在這兩種不同的使用情境中，使用者僅需要攜帶一台平板電腦，並以使用情境與需要來切換操作方式和介面。<br />\r\n<br />\r\n<br />\r\n謝忠利接著表示：「從以上案例的分析可以看出微軟和Apple在平板電腦策略上的差異，對Apple來說，平板電腦是智慧型手機向上的延伸(也使用同樣的iOS)； 但對微軟來說，平板電腦則是筆記型電腦的另一種不同需要、不同類型的機種設計(form factor)，也因此，微軟以較具市場優勢的Windows 8向下延伸， 而不是以Windows Phone向上延伸；Windows 8裡兼具Aero與Metro介面的設計目的，也正是企圖打造一套作業系統，以無縫連接使用者經常變換的使用情境， 使用者將不需要為不同的使用情境而攜帶太多的終端設備。」<br />\r\n<br />\r\n<br />\r\nNPD DisplaySearch 表示，為了使觸控功能在Metro介面下使用起來更加直觀，除了簡化外，微軟也設計了一些與Windows 7系統中不同的觸控手勢。 Windows 8系統中有7個主要的手勢，而Windows 7中至少有九個。其中，縮放(Zoom)功能被保留了下來，旋轉(Rotate)功能得到了改進。 值得一提的是，Windows 8新增了「自側邊滑入(swipe from edge)」的功能，此一類手勢通常與作業系統與程式有關。 微軟針對從四個螢幕側邊滑入作了一些保留和定義；左右側邊主要保留給作業系統相關的功能，上下側邊則為應用功能表或者功能鍵。 正因為「自側邊滑入」將會是經常使用的觸控手勢，Windows 8對這手勢也自然有較嚴格的規範要求，響應準確度(edge accuracy)約為1mm。很明顯，這個功能是為觸控而設計，尤其是在平板電腦上。<br />\r\n<br />\r\n<br />\r\n除了這些系統預先設定的觸控手勢之外，Windows 8也允許應用開發商創建他們自己的多點觸控手勢。 但是，微軟仍然建議開發者應該遵循一些基本原則以提高用戶的使用經驗；比如讓使用者選擇起來簡單、統一、明確、直接，而不需要複雜的組合等。 為了達到Windows 8的規範要求，5個以上的多點偵測是必需的，通常這會是互感電容(mutual sensing)技術，另外，較高的回應率(≧100 Hz)也是必不可少的。 這些規範要求雖然提高了的控制晶片設計的難度，但技術上的門檻也讓晶片商有機會創造更高的銷售，特別是平板電腦或是筆記型電腦所需的控制晶片，成本往往將近是手機的5~10倍。<br />\r\n<br />\r\n<br />\r\n依照微軟的規劃，Windows 8可以同時支援傳統的X86架構與新的ARM架構。X86是一般筆記型電腦或是桌上型電腦的基本架構，針對的是比較要求效能、工作為主的市場定位； 而新的ARM架構則有機會在未來以較低的市場均價來挑戰iPad或是Android為系統的平板電腦。 預計X86版本的Windows 8有機會在2012年第三季問世，而ARM版本則會晚幾個月。2010年蘋果通過iPad讓平板電腦變得家喻戶曉，時隔兩年， 有著更高觸控要求的Windows 8系統將讓微軟有機會重新定義平板電腦與筆記型電腦，觸控產業由此將會迎來新的市場前景。<br />', '2012-01-19', '0');
INSERT INTO `industry_list` VALUES (22, 'Ultrabook輕薄化趨勢壓境 帶動晶片式觸控竄出頭', '微軟Win8系統平台蓄勢待發，並將觸控帶入大尺寸產品，業界指出，目前各大NB品牌正積極醞釀推出導入觸控功能的Ultrabook新機， 尺寸約在11.6~15.6吋，由於Ultrabook機型設計講究重量輕、薄型化，使得2012年單片玻璃觸控技術(One Glass Solutio', 'DIGITIME', '微軟Win8系統平台蓄勢待發，並將觸控帶入大尺寸產品，業界指出，目前各大NB品牌正積極醞釀推出導入觸控功能的Ultrabook新機， 尺寸約在11.6~15.6吋，由於Ultrabook機型設計講究重量輕、薄型化，使得2012年單片玻璃觸控技術(One Glass Solution；OGS) 將竄出成為新寵，預計在Win8帶領下，觸控Ultrabook大軍將於第3季全面壓境。<br />\r\n<br />\r\n<br />\r\n業界指出，受到平板電腦效應帶動，薄型筆電Ultrabook未來在機型設計對於觸控螢幕的支援與需求將提升，而Win8也將打造全新、適合觸控的Metro介面， 成為促成機型設計演變的主要原因之一，目前NB上蓋主要採取掀蓋式設計，然而若直接將觸控功能置於螢幕上將不符合人體工學，在觸控趨勢的引領下， NB外觀設計將出現重大革新。 市場預期，惠普(HP)、日系品牌可望推出反轉式設計，而華碩可望採取滑蓋式設計，藉由各家品牌發展具創意的機型設計演變，讓使用者可依照使用情境，發揮可攜性的特性。<br />\r\n<br />\r\n<br />\r\n儘管目前主流的觸控模組結構都是外掛式的，但不論感應器採用的是玻璃(G/G)或是薄膜(G/F/F)，其基本結構除了增加厚度、重量外，由於貼合次數增加，因此也降低良率，相較於外掛式技術， OGS受限於製程影響，硬度不如傳統外掛式GG技術，然而目前Ultrabook對於硬度要求的規格不如其他手持式裝置，由於Ultrabook對於機型輕薄的要求，搭配目前投射式電容觸控技術的輕薄化發展的趨勢， 可望帶動觸控廠2012年力推的OGS技術加速導入市場。<br />\r\n<br />\r\n<br />\r\n據指出，目前多家觸控廠商正陸續送樣進行Win8認證作業，由於Win8對於觸控功能的規格要求不高，主要在於能達到同時5點觸控的技術，這對於玻璃投射式觸控技術並不成問題， 因此觸控相關供應鏈廠商早已配合品牌廠的新機推出計畫，預計將在下半年陸續推出11.6~15.6吋的觸控Ultrabook問世。<br />\r\n<br />\r\n<br />\r\n業界認為，Ultrabook將藉由輕薄與可攜性切入市場，並以不同的機型設計演變，以融合觸控螢幕功能，隨著觸控Ultrabook將引領NB應用更加輕薄化，並可能將衝擊高階平板電腦， 並迫使無鍵盤、ARM核心的平板電腦往價位較低、尺寸較小的區隔定位發展。<br />', '2012-03-28', '0');
INSERT INTO `industry_list` VALUES (23, 'iPad、Windows 8平板　潛在用戶的關鍵考量點', '蘋果(Apple)已在3月16日推出新iPad，還在首賣週末完成3天賣出300萬台的新紀錄。 微軟(Microsoft)則預計在秋季以Windows on ARM(WOA)平板正式跨入平板市場。 對許多還沒採購的消費者而言，考量的重點在於是否要現在購入iPad，或者要等10月就可', 'DIGITIME', '蘋果(Apple)已在3月16日推出新iPad，還在首賣週末完成3天賣出300萬台的新紀錄。 微軟(Microsoft)則預計在秋季以Windows on ARM(WOA)平板正式跨入平板市場。 對許多還沒採購的消費者而言，考量的重點在於是否要現在購入iPad，或者要等10月就可能推出的Windows 8平板。<br />\r\n<br />\r\n<br />\r\n根據InformationWeek報導，目前若把雙方的功能逐條拿來比較並不公平，因為iPad已經有實品上市，而WOA平板則還沒。 Windows 8平板的實際性能得看硬體商如諾基亞(Nokia)、聯想(Lenovo)、華碩等廠商如何布署微軟的規格而定。 但即便如此，若就現已知的事實來比較，還是可以看到初步概況。首先從價格來看，新iPad售價從最低的499美元起跳， 基本款是16GB容量、Wi-Fi上網；最頂級版本則是829美元、64GB容量、有Wi-Fi與4G連線。<br />\r\n<br />\r\n<br />\r\nWindows 8平板目前還不知道售價，但若從Windows Phone來觀察，則可預期微軟與諾基亞的價格會訂得十分有競爭力， 諾基亞低階Windows Phone(即Lumia 710)目前若與T-Mobile綁約已是免費。 微軟似乎展現出願意賠錢來搶市佔率的決心，平板極有可能也是如此作法。也因此屆時Windows 8平板的價格不見得會輸iPad。 就介面而言，iPad採用是用戶已經相當熟悉的iOS平台；相較之下，Windows 8平板則跟目前市面上的平板很不一樣， 主要會採微軟的Metro觸控介面，而其概念主要延伸自Windows Phone 7。<br />\r\n<br />\r\n<br />\r\n就螢幕尺寸而言，新iPad採9.7吋，跟舊款版本一樣。Windows 8平板會支援多種螢幕尺寸，但初期外界預估應該會以較大螢幕為主， 以最近NVIDIA公開展示過的原型就至少會是10吋以上。微軟在部落格提到，Windows 8的主流螢幕尺寸會介於10.1~12吋之間。<br />\r\n<br />\r\n<br />\r\n微軟打算採大尺寸為主，顯然希望讓WOA平板兼容媒體消費與生產力，不過就實際而言，10.1吋與9.7吋差異並不大。 從螢幕解析度來看，新iPad最大特色是採用所謂的視網膜顯示器(Retina Display)，解析度2,048x1,536，像素密度264 ppi。 微軟則已經表示Windows 8平板會支援好幾種螢幕解析度，最高甚至會打平或超越視網膜顯示器，比如10.1吋的平板解析度最高可支援2,560x1,440， 像素密度291 ppi。<br />\r\n<br />\r\n<br />\r\nWindows 8在規格上或許可打敗iPad，但iPad的重點從來不是規格，而是整合力，因此微軟與硬體合作夥伴要如何在畫質上打敗視網膜顯示器可能還得費一番思量。 就處理器方面，iPad採蘋果自家的A5X晶片，規格為2核心、時脈1GHz。微軟則找3家晶片商來生產WOA平板處理器，包括NVIDIA、德州儀器(TI)，以及高通(Qualcomm)。<br />\r\n<br />\r\n<br />\r\n新iPad最近曾傳出會過熱，背後主因之一便是A5X比前一代的A5更大。 Windows 8平板所用的3家廠商之前在Android陣營都已經有過經驗，這對WOA平板是一大優勢。NVIDIA的Kal-El 4核心架構更廣受注目。 就開機時間而言，蘋果沒有公布實際數據，但一般外界測量，新iPad開機介於21~30秒間，會比iPad 2稍慢幾秒。 相較之下，之前Windows平板會失敗的主因之一便是開機時間跟PC差不多，都較慢。 但Windows 8官方版的開機速度已經降至8秒。雖說實際上相差10秒或許差異不大，但用戶多半會把開機速度跟系統性能劃上等號， 微軟加快開機速度，將有助於洗刷開機太慢的惡名。<br />\r\n<br />\r\n<br />\r\n就應用面而言，iPad專用的應用已經超過20萬個，這還不包括把iPhone應用放大的版本。 Windows 8平板的作法會模仿蘋果，用戶必須直接從Windows Store下載，或微軟直接出貨預裝在裡面，其中最引人注意的是Office 15觸控版。 WOA平板會預裝出貨；對於商業用戶，Office 365也有可能會是選配之一。 Windows 8平板能否成功，應用即可能扮演關鍵，比如USA Today便已經承諾會在Windows 8平台上開發應用。 只是微軟若要追上iPad的生態體系規模，仍需要一段時間的發展。 Windows 8會有更多細節會陸續公布，外界普遍預期產品會在10月上市，屆時應該許多人都已經買了iPad，但微軟與合作夥伴認為應該還是會有不少人會等著進行比較之後才採購。 但不管如何，看來這次的假期旺季會有更多選擇。<br />', '2012-03-27', '0');
INSERT INTO `industry_list` VALUES (25, 'Creative 在中國發表全新”漢之派”平板電腦', '', 'VR-ZONE', 'Creative在中國大陸市場發表了一款名為”漢之派”的平板電腦，將採用Creative ZMS-40處理器。 Creative”漢之派”瞄準中國大陸廣大的平板電腦用戶，其建立與Android 4.X Ice Cream Sandwich作業系統上， 擁有豐富的媒體功能以及中文App平台。”漢之派”將主電子書包市場，並期望能夠建立橫向以及縱向的合作聯盟。<br />\r\n<br />\r\n<br />\r\n擁有4顆核心的ZMS-40將會是”漢之派”所使用的處理器，為ARM Cortex-A9架構，核心時脈為1.5GHz。 相較於前一代的ZMS-20，全新的ZMS-40擁有更好的處理能力，同時其功耗部分也降低了約50%。 支援了H.264、VC1、WebM (VP8)和HEVC(H.265)等編碼，同時也支援2560 x 1600 (WQXGA)解析度。<br />\r\n<br />\r\n<br />\r\n“漢之派”平板電腦重量僅僅只有480g，厚度部分為7.4mm。 售價以及發售時間並沒有在新聞稿內提至，同時此台平板電腦估計將只會在中國大陸販售。<br />', '2012-02-15', '0');
INSERT INTO `industry_list` VALUES (27, '蘋果內嵌式觸控 有影了', '蘋果投入內嵌式（in cell）觸控面板開發已經不是秘密，不過近期傳出蘋果將派員與面板合作伙伴LGD、 TMD（Toshiba Mobile Display）、夏普於今年中展開試做，顯示內嵌式觸控面板將應用在蘋果下一代的新產品中。 而包括友達（2409）、三星今年也都將推出AMO', '工商時報', '蘋果投入內嵌式（in cell）觸控面板開發已經不是秘密，不過近期傳出蘋果將派員與面板合作伙伴LGD、 TMD（Toshiba Mobile Display）、夏普於今年中展開試做，顯示內嵌式觸控面板將應用在蘋果下一代的新產品中。 而包括友達（2409）、三星今年也都將推出AMOLED搭配on cell觸控面板，今年可望掀起一波面板輕薄化大戰。<br />\r\n<br />\r\n<br />\r\n蘋果iPhone正式開啟了多點式觸控面板應用的序幕，不過蘋果不滿意止於此，過去兩年的時間，蘋果投入in cell內嵌式觸控面板的開發， 並且申請了多項專利。不過由於內嵌式觸控面板一直有雜訊偏多造成觸控操作干擾的問題，而生產良率更是只有30％至40％的水準， 也讓量產性備受質疑。但是近期傳出蘋果有意在今年導入內嵌式觸控面板，今年中還將派駐研發人員到LGD、TMD、夏普等面板合作伙伴， 開始試做內嵌式觸控面板，希望應用在下一代的iPhone和iPod touch上。<br />\r\n<br />\r\n<br />\r\n內嵌式觸控面板開始量產，也將直接衝擊傳統觸控面板廠商。但宸鴻表示，不論是內嵌式還是單片玻璃解決方案，都少不了貼合製程（lamination）， 目前宸鴻在後段貼合的良率仍是業界之首，公司仍會隨著觸控產業成長。<br />\r\n<br />\r\n<br />\r\n先前LGD就已經宣布今年將配合客戶在年中開始量產內嵌式觸控面板，生產項目更是涵蓋小尺寸和中尺寸。 至於三星今年則是計畫推出AMOLED面板搭配自己製作的on cell觸控面板。友達法說會上也宣布in cell觸控面板完成開發， 下半年將導入客戶，而AMOLED會搭配on cell觸控，在上半年開始量產。奇美電也壓寶在on cell觸控面板，被內部視為是今年的秘密武器。<br />\r\n<br />\r\n<br />\r\n現在外掛式觸控面板結構上共有保護玻璃、觸控感應玻璃和TFT面板3層，不論是內嵌式還是單片式觸控，都少一片觸控感應玻璃， 可以減薄約0.3~0.4毫米的厚度。今年智慧型手機比外型設計更比輕薄。<br />', '2012-02-10', '0');
INSERT INTO `industry_list` VALUES (28, '控商機 花落誰家？黃金十年開始登峰', '觸控市場熱度早已觸發，目前，電阻式是2吋觸控面板最具價格競爭力的解決方案，但投射式電容受歡迎程度快速增加，已有主流姿態，並挾平板風潮從小尺寸進展至中大尺寸。 光學觸控的應用則被限制在AIO電腦，待解決的問題仍然不少。 AIO電腦與平板電腦成為後進驅動力，智慧型手機也吹起大螢幕風，', 'CTimes', '觸控市場熱度早已觸發，目前，電阻式是2吋觸控面板最具價格競爭力的解決方案，但投射式電容受歡迎程度快速增加，已有主流姿態，並挾平板風潮從小尺寸進展至中大尺寸。 光學觸控的應用則被限制在AIO電腦，待解決的問題仍然不少。 AIO電腦與平板電腦成為後進驅動力，智慧型手機也吹起大螢幕風，觸控面板的尺寸開始加大， 這波商機熱度目前才剛起頭，三年內投射式電容將是主流，預估持續十年不是問題。<br />\r\n<br />\r\n<br />\r\n應用面：手機帶頭跑　PC是成長大宗： 根據DisplaySearch分析報告指出，全球有三分之二觸控面板出貨是應用於手機， 2011年手機觸控面板出貨量預計達8億6千8百萬片，年增長率為68%。 而資策會MIC則認為，觸控手機開始從高階機種向下滲透，期待功能型手機的外型突破來驅動消費者換機，國際品牌廠商寄望透過經典機種拉抬獲利，觸控機種有助於創造差異化， 觸控面板取代鍵盤介面，逐漸滲透中階機種。 擁有20年觸控經驗的宇辰光電董事長王貴璟表示，雖然各家分析機構對於應用趨勢的解讀有著不盡相同的數字預估，但是對於PC搭載觸控面板的趨勢相當有共識。 平板電腦將以超高速成長帶動觸控產業革命，觸控技術載小筆電與平板電腦應用將在2010年後快速成長，總體PC觸控市場將擴大兩倍，現在開始，PC就將成為目前市場上觸控技術增長最迅速的領域。 由於平板電腦與智慧型手機成為高獲利品項，面板廠商在低迷景氣中，也開始學習不再以面板面積與切割效益作為思索點。過去面板廠評估6代、7代線時，都是以TV產業角度切入， 由於TV面板規格幾乎已是公規，著重的是面積以及切割效率。但這兩年智慧型手機等高獲利產品竄起，相同的面積卻擁有更高的毛利率，雖然智慧型手機面板客製化程度高、 產品週期縮短至2、3個月甚至更短，但相同的面積卻擁有更高的毛利率，顯示傳統的投資評估標的已經不見得持續沿用。DisplaySearch資深分析師Shawn Lee表示，LCD TV產能使用率從73%降至64%， 更多IT應用產品在6代線出現，除了PC螢幕以及小筆電面板之外，平板電腦等中尺寸面板合計增加了10％。5代線的面板也打破過往LCD螢幕獨大狀態，使用領域則更加彈性多元，更多小筆電、 平板電腦等中小尺寸面板將投產至此。<br />\r\n<br />\r\n<br />\r\n技術面：投射式電容壯大 競爭仍激烈：分析2010觸控面板產值，投射電容已成為領先技術。 自2007年Apple採用此技術以來，投射電容市場呈現爆炸性增長，后繼者紛紛跟進。縱然觸控技術百花齊放，但各分析機構均有共識－未來三年，投射式電容與電阻式技術仍然是觸控界的主流。 DisplaySearch預測－今年將是投射式電容繼續大鳴大放的年度，2011投射電容將占有70%觸控產值。不僅如此，投射式電容也將藉由iPad擴展至中尺寸，故營收年成長率比出或年成長率更高。 2011年使用於平板電腦投射電容式觸控面板產值將超過10億美元。如以以面板尺寸區分之，十二吋以下為兩者技術共存競爭，電阻式市場雖然仍大，但在三吋以上有被投射式電容吃掉市佔的趨勢。 現階段來說，除了電阻式，投射式電容以及光學式觸控外，其他的觸控技術老實說生存空間已經不大，現在投射式電容和電組正在搶奪智慧型手機市場，這是最大的一塊餅， 而在大尺寸方面，光學觸控則有其優勢，但值得注意的是投射式電容也開始朝大尺寸發展。至於on-cell技術，則逐步轉向較小尺寸應用如手機與數碼相機等。 宇辰光電董事長王貴璟表示，投射式電容固然短期內不會退燒，但競爭態勢非常火熱。首先，Apple以iPad訂出了很高的競爭門檻，硬體規格很高，但是價格策略卻走低價路線，這對於傳統PC產業帶來了很大的跨入障礙。 此外，真實多點觸控應用技術與控制IC的能力發展依存度高。目前，大家看到有餅可吃，投入者相當眾多，技術層次和商業模式都還沒有一定的準則，競爭規模大。 觸控業者正朝製程改善及材料替代的方向發展，到時候擁有高穿透率、低功耗、多點觸控與較佳手勢識別觸控技術將會居於領先地位。MIC資深分析師兼副組長謝佩芬說，「貼合技術」是最大的勝出關鍵。 因為現在Glass Sensor以及貼合製程的成本下降不易，導致價格居高不下，其他業者很難和Apple競爭，所以市場新進者若要吸引客戶，必須推出具有價格優勢的產品。目前技術層次來說，OGS技術可降低材料成本， 減少貼合製程道數，縮小與Film Type之間的價差。不過Film Type廠商當然也希望提高自己的滲透率，也一直在簡化自身結構，推出G/F產品。目前，Glass Sensor觸控面板供應商主要為宸虹與勝華，而Film Type則有洋華、介面與日本寫真。 2010年，Glass Sensor與Film Type的比例約為6比4，預估今年比例會互有消長來到7:3。<br />\r\n<br />\r\n<br />\r\n看台灣：找到自己的微笑曲線 ： 面對TFT面板廠商垂直整合的大動作，原先都是以簡單水平分工方式運作的觸控面板廠商，被迫積極向上游進行垂直整合。 在韓國市場，觸控模組出貨量成長幅度很大，這是其強大的手機品牌業者奧援而能得利；中國市場是後起之秀，建構投射式電容產業鏈的速度甚至比傳統電磁式觸控技術更快。 至於台灣觸控業者，也正在嘗試建立完整的價值產業鏈。DisplaySearch表示，台灣本身具備的條件包括系統製造，觸控模組，ITO Glass，ITO光罩，Cover Lense都是台灣廠商的能力範圍。 不過，台灣業者目前仍然缺乏ITO Film和ACF相關資源，這兩者主要資源仍然掌握在日本廠商手中。此外，觸控控制IC大廠Atmel，Synaptic以及Cypress也仍大權在握。 台灣談觸控產業，通常會將產業鏈以是否打入Apple供應商作為區分標準。Apple供應鏈部分，奇美電子的價值鏈整併動作很大，Cover Lense面板與系統製造都囊括在內。 非Apple供應鏈：則以Tier1的智慧型手機與非蘋果平板客戶作為利基，2011年產能將轉為投射式電容與電阻式技術五五分的產能分配。傳統的TFT-LCD面板廠商無不希望能在觸控找到新的機會而在控制IC， 台灣本土業者得到好訂單的機會恐怕要到2012年。 台灣觸控產業的機會，在於作業系統對於觸控功能的支持－無論是iOS、Android、Windows8、還是MeeGo，無論是傳統PC作業系統或是行動作業系統，無不納入觸控功能，市場肯定迅速成長。 iPhone第一代到第五代仍然方興未艾，顯然看得出觸控產業不怕找不到舞台；而且中大尺寸應用不斷沿伸，正處於新興爆發期，觸控產業的黃金十年還在攀上頂峰的路上，此話並不為過。 台灣觸控產業的機會，在於作業系統對於觸控功能的支持－無論是iOS、Android、Windows8、還是MeeGo，無論是傳統PC作業系統或是行動作業系統，無不納入觸控功能，市場肯定迅速成長。 iPhone第一代到第五代仍然方興未艾，顯然看得出觸控產業不怕找不到舞台；而且中大尺寸應用不斷沿伸，正處於新興爆發期，觸控產業的黃金十年還在攀上頂峰的路上，此話並不為過。 如何在觸控的黃金十年創造屬於自己的黃金時代？王貴璟說，台灣觸控業者應該設法迅速找到屬於自己的「微笑曲線」。 在研發階段，要特別留意智財權的發展，才能在鯊魚滿佈的專利戰中擁有全球競爭力；而在地域性行銷階段，則要擺脫代工思維、強調品牌與服務，才能甩開低毛利、增加產品的附加價值。<br />', '2011-09-29', '0');
INSERT INTO `industry_list` VALUES (29, '電容觸控強出頭 電阻式快Hold不住了', '2011年觸控面板整體市場規模已經達到12億片出貨，超過130億美元。今年預計將創下出貨量比去年增加60％， 金額比去年增加90％的大幅成長紀錄，而且未來還將繼續成長，預計2011年到2017年出貨量的年平均成長率將達到16.5％。', 'CTimes', '2011年觸控面板整體市場規模已經達到12億片出貨，超過130億美元。今年預計將創下出貨量比去年增加60％， 金額比去年增加90％的大幅成長紀錄，而且未來還將繼續成長，預計2011年到2017年出貨量的年平均成長率將達到16.5％。<br />\r\n<br />\r\n<br />\r\n根據DisplaySearch的2011年觸控面板市場調查報告指出，2011年電容式觸控已超過電阻式，且電容式也將成為未來的主流。 據了解，DisplaySearch過去曾預測電阻式雖然在電容式大軍壓境下會相形失色，但仍將維持一定的市場佔有比重持續發展。 然而目前DisplaySearch已經修正這樣的看法，並認為觸控面板將從電阻式向電容式逐漸過渡。未來電容式有可能逐漸消失。<br />\r\n<br />\r\n<br />\r\n電容式的構造分為兩種，一種是採用ITO薄膜作為基板，另一種則採用ITO玻璃作為基板，目前業界則正在開發一體型的新構造， 這是觸控感測器直接安裝在已普遍用於電容式的保護玻璃上，可以省去作為基板的薄膜或玻璃，可以實現薄型輕量化並降低成本。 這種構造目前已開始在部分智慧手機上採用，然而在切割強化玻璃等製作過程中，仍有諸多挑戰需要解決。 未來將觀察面板廠商的開發情況才知道能否真正普及。<br />\r\n<br />\r\n<br />\r\n在電阻式觸控逐漸被取代之際，電容式在智慧手機的應用已成為王道。目前電容式觸控面板還持續向遊戲機領域滲透， 例如任天堂3DS及微軟Kinect等都是其中的代表。在其他的應用方面，例如筆記型電腦、AIO個人電腦及車載顯示器等， 往後對於觸控面板的需求也將增加。<br />', '2011-09-29', '0');
INSERT INTO `industry_list` VALUES (30, '創新科技推出漢之派平板電腦', '玻璃投射式電容觸控面板是所有觸控面板中的主流,單片玻璃投射式具有價格上的優勢,更可滿足終端產品輕薄短小 的外觀需求。不管是國際手機或平板電腦大廠都紛紛導入使用。國內外觸控面板廠,無不投入單片玻璃投射式電容 觸控面板開發,單片玻璃投射式電容觸控面板是所有觸控面板中主流的主流。', 'IT產業趨勢研究', '玻璃投射式電容觸控面板是所有觸控面板中的主流,單片玻璃投射式具有價格上的優勢,更可滿足終端產品輕薄短小 的外觀需求。不管是國際手機或平板電腦大廠都紛紛導入使用。國內外觸控面板廠,無不投入單片玻璃投射式電容 觸控面板開發,單片玻璃投射式電容觸控面板是所有觸控面板中主流的主流。<br />\r\n<br />\r\n<br />\r\n單片玻璃觸控OGS(One/Single glass solution亦可稱為Touch on Lens),指的是將觸控玻璃(Touch Sensor)與外層 的保護玻璃(Cover Glass)結合在一片玻璃上,使觸控模組結構由2片玻璃簡化成1片玻璃,亦即在原本保護玻璃內層 鍍上多層導電層,可減少玻璃材料使用,簡化觸控模組貼合製程進而提升生產良率,最重要的是除了降低成本外,外型 還可以更輕薄短小,為觸控面板必然要走的方向。單片玻璃觸控面板不管是材料、軟體或硬體製造技術,都比雙玻璃 觸控貼合基版(G/G Type)及玻璃與薄膜觸控貼合基版(G/F Type)高。單片玻璃觸控能大量穩定供貨者,僅有使用半 導體設備及擁有多項製程專利的富創得科技。<br />\r\n<br />\r\n<br />\r\n黑色邊框區(Black Matrix)單片玻璃投射式電容觸控面板的導電層,必須要以高溫濺鍍方式,直接濺鍍在可視區及黑 色邊框區;而黑色邊框區在經過高溫濺鍍製程後會碳化,碳化會造成導電,因而導致導電層短路。而且FPC是貼合在黑 色邊框區,黑色邊框區會因碳化剝落,因此FPC亦會隨之剝落或造成Bonding區透光,因此黑色邊框區選材是非常困難, 但也是最重要的。<br />\r\n<br />\r\n<br />\r\n材料-玻璃：玻璃是觸控面板主要基材,強度當然重要,基本上要有450mpa以上的強度才夠。Soda-lime玻璃是觸控面 板的最主要玻璃,必須經過強化,而且必須是六面強化才可以達到450mpa強度,因此玻璃強化後不可再切割或研磨,因 為強化後再切割或研磨就不是六面強化,問題更大是切割或研磨會破壞玻璃結晶構造,強度幾乎被摧殘無餘。因此玻 璃切割及研磨後再強化是唯一的選擇,但是用切割或研磨後再強化的玻璃去濺鍍、曝光、顯影、蝕刻的技術是非常 高的,好在國內半導體工業非常進步,引用一下就有解決了。<br />\r\n<br />\r\n<br />\r\n電性－ITO電性：投射電容觸控是靠充電及電容變化原理而達到觸控效果,因此電性是主導觸控品質最重要的關 鍵,ITO導電層的線阻抗以及電容值必須維持在平均10KΩ及10pF以下才能達到報點率每秒兩百以上,不然觸控 靈敏度不夠。ITO在通電後才開始老化,阻值及容值會因老化而變化很大,因此ITO濺鍍在玻璃上必須結晶,因ITO結晶 也是抗老化的最佳方法。不過ITO結晶必須仰賴高溫濺鍍,黃光製程要達到這個目標不難,其它製程就不可能達<br />\r\n<br />\r\n<br />\r\n電性－電氣干擾：由於電容式觸控面板是利用電容值的改變，才使觸控有反應，因此任何干擾皆會影響觸控的功能 。干擾分為外在與內在,外在干擾是由大氣環境所產生。內在干擾是系統的Power、LCM 與主板所產生,因此觸控面 板防干擾能力必須非常強,多片式觸控面板可做抗干擾層,但單片就沒辦法,好在是先進的導電與軟體設計及製程能 力可以解決電源的物理雜訊問題。/p&gt;<br />\r\n<br />\r\n<br />\r\n材料選擇－表面處理技術：觸控面板應用越來越廣,觸控面板不同表面處理及顏色變化需求就因應而產生,表面處理 必須靠自動化噴塗與鍍膜設備及專業技術調整光學L、a*、b*值,而L、a*、b*值的調整,可獲得所期望的光學效果及 顏色。因表面處理加工環境,會明顯地影響玻璃光學特質,因此最佳的方式是在無塵室中,以一條龍的噴塗或鍍膜製 程,進行如AS防污易潔、AG防炫光、AR防反射等表面處理,透過適當地表面加工處理,可增加產品附加價值與提升市 場競爭銷售優勢。<br />', '2011-08-24', '0');
INSERT INTO `industry_list` VALUES (31, '2011年玻璃式投射電容觸控面板佔整體平板裝置用觸控面板出 貨量61.9%', '2011年平板裝置(Tablet Device)用觸控面板市場最重要發展，在於玻璃式投射電容觸控面板市佔率高於預期；另 外，即使山寨業者也加速採用投射式電容觸控面板，使電阻式觸控面板侷限於極低階產品市場。', 'Techup科技', '2011年平板裝置(Tablet Device)用觸控面板市場最重要發展，在於玻璃式投射電容觸控面板市佔率高於預期；另 外，即使山寨業者也加速採用投射式電容觸控面板，使電阻式觸控面板侷限於極低階產品市場。<br />\r\n<br />\r\n<br />\r\nDIGITIMES Research分析師楊仁杰分析，由於蘋果(Apple)以外作業系統業者在將其作業系統從尺寸較小的手機應 用擴大到尺寸較大的平板裝置應用時，遭受部分技術上的困難，使蘋果以外平板裝置上市時程有所延誤；再加上蘋 果以外業者仍有多數，係與台灣NB代工業者合作採ODM方式生產，而這些台灣NB代工業者在選擇觸控面板供應商時 ，亦多優先選擇其TFT LCD面板供應廠及其關係企業，因此多會採用玻璃式投射電容觸控面板，也促使玻璃式投射 電容觸控面板市佔率高於預期。<br />\r\n<br />\r\n<br />\r\n儘管2011年下半蘋果以外平板裝置業者將急起直追，預估2011年iPad佔一般平板裝置比重仍將達62.5%；不過楊仁 杰也說明，除一般平板裝置外，美國邦諾(Barnes &amp; Noble)亦推出採用Google Android作業系統及TFT LCD面板搭 配觸控面板，以電子閱讀功能為主的平板裝置，而全球最大電子書閱讀器業者亞馬遜(Amazon)未來亦可望跟進推出 類似產品。若將此類產品加入非iPad平板裝置出貨量，則2011年iPad將只佔整體平板裝置出貨量53.0%，非iPad平 板裝置市佔率將逼近5成大關。<br />\r\n<br />\r\n<br />\r\n整體而言，若不計以電子閱讀功能為主的平板裝置，玻璃式投射電容觸控面板將佔整體平板裝置用觸控面板71.9% ，但由於電子書閱讀器業者對成本要求較嚴，多將採用薄膜式投射電容觸控面板，因此楊仁杰預估，玻璃式投射電 容觸控面板將佔平板裝置用觸控面板出貨量61.9%。<br />', '2011-05-16', '0');
INSERT INTO `industry_list` VALUES (33, 'iPhone 5將採In-cell觸控? 專家說可能性不高', '在觸控領域中，各項技術皆有其優點與缺點，沒有任何單一技術可以涵括所有的優點。例如投射式電容技術，在大尺寸的應用有其設計與成本上的困難點；而傳統的類比電阻式與表面電容式，在多點觸控方面未能滿足市場需求；電磁式與光學影像式儘管在大尺寸上擁有成本優勢，但目前尚無法轉移到小尺寸面板的應用', 'CTimes', '在觸控領域中，各項技術皆有其優點與缺點，沒有任何單一技術可以涵括所有的優點。例如投射式電容技術，在大尺寸的應用有其設計與成本上的困難點；而傳統的類比電阻式與表面電容式，在多點觸控方面未能滿足市場需求；電磁式與光學影像式儘管在大尺寸上擁有成本優勢，但目前尚無法轉移到小尺寸面板的應用；而市場公認未來最具成本效應及技術領先性的內嵌式（in Cell）觸控技術，也因為訊號處理技術上的門檻，難以成為實際產品化的主流技術。<br />\r\n<br />\r\n然而專家認為，多點觸控在人機介面的發展趨勢上，扮演了關鍵角色，未來的產品應用勢必會越來越普及。而為了展現較佳的光學表現及更低的成本結構，內嵌式觸技術勢必被市場不斷推升，成為未來的主流技術。<br />\r\n<br />\r\n就需求面來看，包括蘋果的iPad等行動裝置，預估高達九成以上都將採用投射式電容技術，因此透光率佳的投射式電容觸控面板，儼然站穩高階智慧手機與十吋平板裝置的應用主流地位。<br />\r\n<br />\r\n只不過在此同時，市場傳出iPhone 5的觸控面板將採用內嵌式技術的消息，這對於投射式電容的業者來說是個不利因素，但專家認為，內嵌式技術由於良率問題及觸控面板反應度降低，整體來看，目前對於高階行動裝置的滲透率依然不高，且此技術仍需面對晶片整合的挑戰，因此認定蘋果突然轉換觸控技術的可能性並不大，短期內，內嵌式技術對現有觸控廠商的威脅仍低。<br />', '2011-03-16', '0');
INSERT INTO `industry_list` VALUES (34, '日震波及iPad 2：觸控玻璃,電池芯和電子羅盤', '日本東北大地震所引發的限電措施，也影響到iPad 2五大關鍵零組件供貨短缺。目前市場看法認為，其中有三大零組件，必須完全仰賴日本，這三大零組件分別是觸控玻璃面板、電池芯和電子羅盤（compass），其他兩項NAND Flash和DRAM則可從其他廠商取得替代來源。', 'CTimes', '日本東北大地震所引發的限電措施，也影響到iPad 2五大關鍵零組件供貨短缺。目前市場看法認為，其中有三大零組件，必須完全仰賴日本，這三大零組件分別是觸控玻璃面板、電池芯和電子羅盤（compass），其他兩項NAND Flash和DRAM則可從其他廠商取得替代來源。<br />\r\n<br />\r\n市調機構iSuppli最新的拆解報告認為，iPad 2其中有五大元件與日本電子產業有密切連帶關係：東芝（Toshiba）供應NAND Flash、爾必達（Elpida）供應DRAM記憶體、AKM Semiconductor提供電子羅盤、旭硝子（Asahi Glass）供應觸控玻璃、而蘋果日本分公司則是提供超薄型電池芯。<br />\r\n<br />\r\n儘管東芝製造NAND Flash的工廠因為停產檢查和物流受到阻礙，供貨可能受到影響，不過南韓三星電子和美國美光科技（Micron）都可以提供NAND Falsh元件，因此對於iPad 2來說影響並不大。同樣地，DRAM也可以從三星電子那邊取得替代來源。<br />\r\n<br />\r\n倒是觸控玻璃、超薄電池和電子羅盤這三大元件供貨情況，可能會直接受到日本震災直接波及，因為這些元件都沒有其他替代來源，只有日本廠商可以提供。日本旭硝子應該是獨家供應iPad 2觸控螢幕玻璃材質的廠商。iPad 2玻璃材質在延展性和耐受度的物理特性，比第一代iPad還要來得好，這可能是旭硝子研發的Dragontrai玻璃材質技術。不過iSuppli指出在上週的震災中，旭硝子至少有兩個工廠可能受損，受到央及程度可能達到1/3的生產規模。<br />\r\n<br />\r\n另外，AKM Semiconductor雖然表示生產電子羅盤的廠房並未受到震災波及，但是iSuppli指出供貨狀況仍因為物流尚未恢復正常，短期之內還是會影響正常出貨。儘管包括Yamaha、愛知製鋼（Aichi Steel）、Alps和意法半導體（STM）都已生產製造電子羅盤，但是iSuppli指出，由於電子調校問題較為複雜，加上電子羅盤元件對於電磁干擾相當敏感，並且iPad 2的電子羅盤是緊密地與加速度計和陀螺儀元件共同運作，因此牽一髮動全身，很不容易被取代。<br />\r\n<br />\r\n同時，iPad 2的鋰離子聚合物電池也是在日本製造，目前相關物流供貨也受到阻礙。iSuppli表示，雖然電池內標明的是「中國製造」，不過這應該是指電池組，iSuppli確認電池芯是由蘋果在日本的協力製造廠商所供應，因為這種先進超薄型電池芯技術的製造能力，只有日本才有。<br />', '2011-03-21', '0');

-- --------------------------------------------------------

-- 
-- 資料表格式： `invest_info`
-- 

CREATE TABLE `invest_info` (
  `id` int(11) NOT NULL,
  `title` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '文章標題',
  `content` varchar(1000) collate utf8_unicode_ci NOT NULL COMMENT '文章內文',
  `youtube` varchar(255) collate utf8_unicode_ci NOT NULL COMMENT '影片網址',
  `youtu_con` varchar(255) collate utf8_unicode_ci NOT NULL COMMENT '影片說明',
  `message` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '右上訊息',
  `link` varchar(255) collate utf8_unicode_ci NOT NULL COMMENT '訊息連結',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `invest_info`
-- 

INSERT INTO `invest_info` VALUES (1, '富創得即將裝運設備出給大陸第一家授權廠商', '富創得科技用600多天開發出獨特的技術、材料及設備，創造了OGS TP的奇蹟，品質冠全球，也是全球唯一可生產各種顏色邊框的OGS製造商，TP售價更是傳統製程所生產出的相同產品的成本。世界各大廠紛紛下單，甚至於國際前十的知名大廠向富創得爭取授權生產，目前已有多家取得授權。智慧型資訊用品改變大家的生活習慣，智慧型資訊產品的人機介面是TP，TP的市場需求擴展快，全球年需求量已達20億以上。但是TP價格居高不下，TP的價格必須突破。\r\n\r\n傳統製程是沿用LCD製程，生產技術老舊，良率非常低，材料大量浪費，設備投資更是幾百億起跳，但產能又低，這種設備生產7吋以下的成本尚可，但對10吋以上的成本就太高了。一條五代線的27吋用產能是20萬片，每一片玻璃成本就達100多美元。富創得的設備價格約為5代線的七分之一，而月產能是50萬片，售價低於五代線生產的玻璃成本。', 'http://www.youtube.com/embed/2MTW5i8NhSk', '傳統製程的玻璃尺寸固定，玻璃必需先強化後再進行各種製程，製程完成後再切割，因此造成玻璃大量浪費，增加成本及破壞玻璃強度。', '', '');

-- --------------------------------------------------------

-- 
-- 資料表格式： `member`
-- 

CREATE TABLE `member` (
  `member_id` int(20) NOT NULL auto_increment,
  `member_user` varchar(10) collate utf8_unicode_ci NOT NULL,
  `member_password` varchar(20) collate utf8_unicode_ci NOT NULL,
  `member_name` varchar(30) collate utf8_unicode_ci NOT NULL,
  `member_com` varchar(20) collate utf8_unicode_ci NOT NULL,
  `member_url` varchar(100) collate utf8_unicode_ci NOT NULL,
  `member_pro` varchar(200) collate utf8_unicode_ci NOT NULL,
  `member_title` varchar(200) collate utf8_unicode_ci NOT NULL,
  `member_mail` varchar(200) collate utf8_unicode_ci NOT NULL,
  `member_tel` varchar(200) collate utf8_unicode_ci NOT NULL,
  `member_add` varchar(300) collate utf8_unicode_ci NOT NULL,
  `member_city` varchar(100) collate utf8_unicode_ci NOT NULL,
  `member_cou` varchar(1000) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`member_id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=20 ;

-- 
-- 列出以下資料庫的數據： `member`
-- 

INSERT INTO `member` VALUES (1, 'dsfdsff', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd', 'asd');
INSERT INTO `member` VALUES (2, 'abcdabcd', 'abcdabcd', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (3, 'abcdabcda', 'abcdabcda', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (4, 'abcdabcdad', 'abcdabcdad', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (5, 'asdfasdf', 'asdfasdf', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (6, 'edcrfv', 'edcrfv', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (7, 'edcrfvd', 'edcrfvd', 'abcd', 'abcd', 'abcd', 'abcd', 'abcd', 'withurs@gmail.com', '124567980', 'sdfsdfsdf', 'sdfsdfsdf', 'sdfsdfsdf');
INSERT INTO `member` VALUES (8, 'samtsou', 'samtsou025678', 'Sam Tsou', 'Abcon Technology Inc', '', 'Etching in-line controller', 'Technologist', 'tsousam121@gmail.com', '0937108668', 'No. 57, Ln. 422, Sec. 2,  Zhongshan E. Rd.', 'Zhongli City, Taoyuan County', 'Taiwan, R.O.C.');
INSERT INTO `member` VALUES (9, 'AndrewWu', '26015678', 'AndrewWu', '富創得', 'www.touchpanelpro.com', 'OGS', 'Engineer', 'andrew_wu@touchpanelpro.com', '26015678', '林口工四路20號', 'New Taipei', 'Taiwan');
INSERT INTO `member` VALUES (10, 'admike', 'adminmin', '楊福涼', '富創得', 'www.touchpanelpro.com', 'TP', 'MIS', 'mike_yang@touchpanelpro.com', '02-2601-5678', '林口區工四路20號', 'Taipei', 'Taiwan');
INSERT INTO `member` VALUES (11, '', '', '', '', '', '', '', '', '', '', '', '');
INSERT INTO `member` VALUES (12, 'hqqwhj', 'hqqwhj', '许杰', '新东产业集聚区', 'www.xdq.gov.cn', '', '', 'hqqwhjxmb@163.com', '18537332103', '新乡市引黄西路46号', '河南省新乡市', '');
INSERT INTO `member` VALUES (13, 'kqpcno@nyz', 'wD0iOY', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com', 'kqpcno@nyzcwa.com');
INSERT INTO `member` VALUES (14, 'jrsfwx@ptp', 'lXht4t', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com', 'jrsfwx@ptpjcb.com');
INSERT INTO `member` VALUES (15, 'gigi01', 'gggg01', '陳志豪', '宏達國際電子', '無', 'mobile phone', '工程師', 'leo06022001@gmail.com', '0930582450', '無', '台北', '臺灣');
INSERT INTO `member` VALUES (16, 'newjob', '27486081', '陳建勳', '永喬科技有限公司', 'www.new-job.com.tw', 'touch 設備耗材', '總經理', 'steven@new-job.com.tw', '0917533740', '台中市豐原區圓環北路二段72號', '台中', '台灣');
INSERT INTO `member` VALUES (17, 'matt', 'xHH7uv', 'matt', 'SvDyKIFhSeIoNqO', 'http://www.QS3PE5ZGdxC9IoVKTAPT2DBYpPkMKqfz.com', 'hzRWidceiyaUaSs', 'JlXQfPoVewdirGy', 'barny182@hotmail.com', '66685538570', 'KmTcHEkH', 'New York', 'rFpoZVLXCfhTjIhNLTw');
INSERT INTO `member` VALUES (18, 'minchee_98', 'kanasai', 'LUM MIN CHEE', '--', '--', '--', '--', 'minchee_98@msn.com', '0169501711', '--', 'pahang', 'malaysia');
INSERT INTO `member` VALUES (19, 'dinky1999', 'jimmyzai2mikoyan', 'jimmy', '黃到時', '家裏', '我家', '', 'dinky1999@hotmail.com', '0102088128', '', '馬來西亞', '吉隆坡');

-- --------------------------------------------------------

-- 
-- 資料表格式： `news_list`
-- 

CREATE TABLE `news_list` (
  `id` int(11) NOT NULL,
  `title` varchar(50) collate utf8_unicode_ci NOT NULL COMMENT '標題',
  `index_content` varchar(140) collate utf8_unicode_ci NOT NULL,
  `from` varchar(30) collate utf8_unicode_ci NOT NULL COMMENT '出處',
  `content` varchar(5000) collate utf8_unicode_ci NOT NULL COMMENT '內容',
  `date` varchar(30) collate utf8_unicode_ci NOT NULL COMMENT '時間',
  `show` varchar(11) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `news_list`
-- 

INSERT INTO `news_list` VALUES (1, '高科技巨擘攜手富創得 共創觸控面板新商機', '面板新商機..', 'DIGITIMES', '<p>\r\n	日本Sharp佐佐木社長和中國京東方王總經理親自來台北，專程與OGS觸控面板全球一線製造廠富創得科技，於11/1日簽訂合作協議。\r\n</p>\r\n<p>\r\n	<span style="font-size:12px;line-height:1.5;">Sharp株式會社將提出最先進的IGZO，這是一款先進的高清晰、節電省能的Full HD產品LCD，交給富創得與京東方團隊，加裝背光模組與先進的OGS電容式觸控成為模組，提供給NB筆記型電腦與AIO及智慧型終端機組裝市場。</span> \r\n</p>\r\n<p>\r\n	<span style="font-size:12px;line-height:1.5;">此一舉措將提升台灣的整體供應面到一個新階段，因為Sharp初期將提供13吋屏每月50萬組，6個月後可大幅增加到每月100萬組，進而將大尺寸24吋屏幕也加進供應的項目內。Sharp此舉一方面為台灣電腦產業界帶進一波強大助力，加上富創得的OGS觸控功能，可以擺脫低價產品的微利紅海競價市場，在緊接而來的雲端時代有充份的競爭力。</span> \r\n</p>\r\n<p>\r\n	<span style="font-size:12px;line-height:1.5;">佐佐木社長之所以選擇富創得作為全球重要合作夥伴，因為富創得與京東方的合作夥伴團隊中，京東方在LCD panel組成上有強而有力的工程能力，加上富創得OGS觸控面板的優異競爭力，富創得水鑽石表面鍍膜的秘密武器，抗UV反射、抗菌自潔的優異能力，可以推升整體競爭力。</span> \r\n</p>\r\n<p>\r\n	<span style="font-size:12px;line-height:1.5;">富創得將與搭檔京東方合作，將此IGZO OC組裝背光與OGS觸控面板，攜手進軍全球市場。在台灣目前低迷的氛圍當中，三巨頭合作注入一股強而有力的新力量，以新產品組合開創新機。</span> \r\n</p>\r\n<img src="templates/index/img/packeg/20131105.jpg" align="left" />\r\n<p>\r\n	<br />\r\n</p>\r\n', '2013-11-05', '0');
INSERT INTO `news_list` VALUES (2, '水鑽石鍍膜玻璃 抑菌力比未鍍膜強四倍', '水鑽石鍍膜玻璃 抑菌力比未鍍膜強四倍 水鑽石鍍膜玻璃在任何環境或室內都具「抑菌效果」，其抑菌能力比未鍍膜強四倍多，經由台灣財團法人食品工業發展研究所(Food Industry Research and Development)測試後證實，並發給檢測報告書。', 'DIGITIMES', '富創得水鑽石鍍膜玻璃在任何環境或室內都具「抑菌效果」，其抑菌能力比未鍍膜強四倍多，經由台灣財團法人食品工業發展研究所(Food Industry Research and Development)測試後證實，並發給檢測報告書。<br />\r\n<br />\r\n富創得(FORTREND)研發出抑菌「水鑽石」鍍膜，可以防範細菌與病毒滋生。「水鑽石」鍍膜使用範圍很廣，可加在任何玻璃、金屬及塑膠上。<br />\r\n<br />\r\n應用層面涵蓋著生活中的各種物品，像是抗菌玻璃餐具、飲用水處理，家裡常見到的家電用品如空氣清淨機、冷氣機，細菌易滋生的浴室中各項設備像是馬桶、浴室扶手、浴室磁磚、水龍頭，現代人最常使用3C產品像是電腦鍵盤、手機、平板電腦，以及建築玻璃、房子外牆材料、保護貼玻璃…等。<br />\r\n<br />\r\n富創得「水鑽石」由台灣財團法人食品工業發展研究所(Food Industry Research and Development)測試後證實，並發給檢測報告書。<br />\r\n<br />\r\n最新的人機介面都為觸控屏，想必未來的生活中，人體接觸的頻率會向上攀升。公共衛生專家指出：觸控屏上的細菌數比馬桶座還高出30倍。若不解決細菌、病毒群落的問題，人們都將暴露在危險當中，由此可知抑菌效果已成為觸控產品的新指標。台灣若要進入高階產品產製，一定需要具有高附加價值，富創得水鑽石鍍膜，就成為觸控產業的新希望，市場致勝就看「水鑽石」。<br />\r\n<br />\r\n<a href="./templates/index/img/packeg/20140311_Std.jpg"><img src="./templates/index/img/packeg/20140311_Sml.jpg" align="left" /></a>', '2014-03-11', '0');
INSERT INTO `news_list` VALUES (3, '富創得OGS觸控面板通過Win8認證', '', 'DIGITIMES', '富創得科技與意法半導體和聯陽半導體攜手合作，成功獲得Windows 8認證。富創得科技董事長吳明發表示，意法半導體和聯陽半導體的觸控IC，在搭配富創得各種尺寸的OGS觸控面板之後已成功陸續通過Windows 8認證，為未來筆記型電腦觸控市場添加有力生力軍。<br />\r\n<br />\r\n該兩家IC搭配富創得的OGS觸控面板擁有幾項優勢：舉凡報點速度非常快、報點精確、滑動與縮放非常滑順，其觸控功能遠遠超越Windows 8所要求的規格，並已成功進入國際大廠供應鏈。<br />\r\n<br />\r\n富創得與意法、聯陽聯手，OGS觸控面板通過Win 8認證。<br />\r\n<br />\r\n吳董事長更進一步說明，富創得的OGS因其製程和材料特殊，品質非常穩定，所有產品均含有抗反射、抗汙和抗金屬刮傷的表面處理。例如：筆記型電腦、一體機和顯示器在玩遊戲時都是10個手指同時操控觸控畫面，而且畫面是平躺的，因此抗反射是絕對必要的，以免傷害眼睛。<br />\r\n<br />\r\n此外，金屬物品像是戒指及手錶等在操作觸控面板的同時，非常容易刮傷觸控面板，如果加保護膜不但價格昂貴，又會降低觸控性能。故抗刮功能亦成為另一項影響觸控面板的關鍵。此外，操控觸控畫面時，手指上的油脂非常容易沾汙觸控面板，又不易擦拭乾淨，因此，抗汙處理也不能沒有。<br />\r\n<br />\r\n富創得把這些問題，列入表面處理標準製程。品質優良，又幾乎免費贈送給客戶，非常受客戶喜愛。富創得髙品質的OGS觸控面板在搭配意法半導體、聯陽半導體優越的IC之下，更是如魚得水。吳董事長樂觀表示，今年富創得在觸控面板的出貨量一定能超越預期，並維持穩定成長。<br />\r\n<br />\r\n<img src="templates/index/img/packeg/20130425.jpg" align="left" />', '2013-04-25', '0');
INSERT INTO `news_list` VALUES (4, '富創得科技OGS售價為他人的成本', 'OGS成本..', 'DIGITIMES', '富創得科技用600多天開發出獨特的技術、材料及設備，創造了OGS TP的奇蹟，品質冠全球，也是全球唯一可生產各種顏色邊框的OGS製造商，TP售價更是傳統製程所生產出的相同產品的成本。世界各大廠紛紛下單，甚至於國際前十的知名大廠向富創得爭取授權生產，目前已有多家取得授權。<br>\r\n<br>\r\n智慧型資訊用品改變大家的生活習慣，智慧型資訊產品的人機介面是TP，TP的市場需求擴展快，全球年需求量已達20億以上。但是TP價格居高不下，TP的價格必須突破。<br>\r\n<br>\r\n傳統製程是沿用LCD製程，生產技術老舊， 良率非常低，材料大量浪費，設備投資更是幾百億起跳，但產能又低，這種設備生產7吋以下的成本尚可，但對10吋以上的成本就太高了。一條五代線的27吋月產能是20萬片，每一片玻璃成本就達100多美元。富創得的設備價格約為五代線的七分之一，而月產能是50萬片，售價低於五代線生產的玻璃成本。<br>\r\n<br>\r\n傳統製程的玻璃尺寸固定，玻璃必需先強化後再進行各種製程，製程完成後再切割，因此造成玻璃大量浪費，增加成本及破壞玻璃強度。因而必須使用化骨水的氫氟酸做二度強化。<br>\r\n<br>\r\n實際上玻璃強化必須把玻璃浸泡在高溫硝酸鉀裡，玻璃表面的鈉離子和硝酸鉀的鉀離子交換，在冷卻後因收縮比不同而增加玻璃強度。但製程做完的玻璃不耐高溫，也不能釋出鈉離子和鉀離子交換，因此只有浸泡在常溫的化骨水裡，僅能把因切割損傷裂開部分腐蝕掉，同時因化學反應產生的六氟化矽粉末殘留在眼睛看不見的玻璃微小細縫裡，而造成玻璃強度加強的假像。六氟化矽非常不隱定，碰到潮溼就會還原成化骨水，溼潤的手操作TP，碰到六氟化矽就會把六氟化矽還原成化骨水，而1.5公克化骨水就可以殺死一個人。<br>\r\n<br>\r\n化學反應式如下：<br>\r\n<br>\r\nSiO<sub>2</sub>(玻璃)+6HF(氫氟酸)→H<sub>2</sub>[SiF<sub>6</sub>](不穩定的六氟化矽)＋2H<sub>2</sub>O<br>\r\n<br>\r\nH<sub>2</sub>[SiF<sub>6</sub>](不穩定的六氟化矽)+2H<sub>2</sub>O(水) →6HF(氫氟酸)+SiO<sub>2</sub><br>\r\n<br>\r\n富創得製程是先把玻璃切割研磨好後再強化，製程走完後也無需再切割，也就沒有化骨水製程問題。富創得玻璃強度是別人的3倍，也因為玻璃強度超高，富創得的TP和LCD不必全面貼合，這對系統廠又能節省每吋1~2美元的費用。<br>\r\n<br>\r\n傳統OGS的邊框是光阻劑做成的，顏色只有黑色，富創得是用印的，各種顏色都可以做，經高溫不碳化，也不變色。印的邊框厚度是導電層的200~600倍厚，富創得獨特設備做的導電層可以爬高800倍。<br>\r\n<br>\r\n傳統OGS製程的導電層是單層加架橋，不但有侵犯他人專利的疑慮，架橋非常難做，良率很低。1片10吋的TP有1,100個架橋，24吋的TP有6,650個架橋。做架橋要先做小絕緣點，再做架橋，兩者的尺寸都比頭髮小非常多，人眼看不到。其製程複雜，任何一個小絕緣點或架橋都不能斷，斷了整片TP就報廢了，良率只有36%，愈大尺寸架橋愈多，良率也就愈低，架橋基本架構的缺陷是無法改善的死胡同，有很多人誓言可在幾年內把良率提高到80%，這是緣木求魚。<br>\r\n<br>\r\n富創得專利導電層是多層結構，不必架橋，沒有架構的缺陷，製程簡單，設備成熟，設廠4個月就可完成，6個月就可量產，良率可達80%。<br>\r\n<br>\r\n有些業者用ITO PET取代ITO玻璃，ITO是銦錫氧化物，導電靠錫，錫和銦分子的排列方式構成ITO的導電係數，ITO在通電後錫和銦分子會不斷重新排列而改變導電係數及阻抗。觸控的敏感度是靠電容和電阻相乘的值的大小，愈小愈好 ，且必須穩定不變，否則會觸控不良。尺寸愈大電阻變化要求愈嚴格。<br>\r\n<br>\r\n要維持錫和銦分子在通電後不重新排列，就必須用高溫濺鍍把ITO結晶化。PET ITO不能高溫濺鍍，沒有結晶通電後阻抗會不斷升高。雖然回火可加速ITO老化，但是回火是低溫，也無法使ITO晶化，通電後的變化是一樣的。同時ITO PET價格居高不下，適合大尺寸的低阻抗ITO PET髙逹每平方公尺60美元。因此有人用ITO玻璃貼ITO PET以降低成本，但是一個ITO有結晶，一個沒有，通電後兩者阻抗相差遂漸增大，導致機子死當。<br>\r\n<br>\r\n另外是貼合，有人用玻璃貼玻璃，也有人用玻璃或塑膠貼1層或2層PET，除了良率低外，延遲性氣泡是永無解的問題。因為貼合要用OCA膠，OCA的材料是PVA，PVA在溫度37度以上烤會產生氣泡，氣泡會造成觸控失靈。LCD溫度達42度，因此TP使用後氣泡會遂漸產生，觸控功能也就慢慢消失。<br>\r\n<br>\r\n某國際大廠自己生產ITO PET、OCA和控制IC，除了材料成本居高不下外，他們仍然也無法解決ITO阻抗在通電後升高的問題，對OCA膠的延遲性氣泡也無解，加上貼合良率也提高不起來，不得不關廠。尚有很多家公司在這一塊領域奮鬥，10吋以下TP及山寨機需求規格低，仍有市場外，10吋以上是全單覆沒，因此台灣、南韓和大陸等多家TP廠紛紛改用富創得的OGS製程。<br>\r\n<br>\r\n觸控剛剛才萌芽，懂的人少之又少，大多數廠商都使用錯誤的設備、技術和材料，以至於虧損累累。富創得以獨特眼光開發自己的技術、材料和設備，所生產的TP品質高，成本也親民多了，銷售價格為五代線做出來的成本。富創得的TP不但是供不應求，登門要求授權生產的廠商更是絡繹不絕。<br>\r\n<br>', '2013-04-10', '0');
INSERT INTO `news_list` VALUES (7, '台湾高科技OGS触摸屏电子产品项目落户天水市', '天水天光半导体有限责任公司和台湾富创得科技股份有限公司就OGS触摸屏高科技电子产品项目举行签约仪式，这标志该项目正式落户天水市。省科技厅副厅长巨有谦、台湾富创得科技股份有限公司董事长吴明发出席签约仪式', '天水网', '<p>\r\n	天天天水网讯（记者 令文慧）12月19日，天水天光半导体有限责任公司和台湾富创得科技股份有限公司就OGS触摸屏高科技电子产品项目举行签约仪式，这标志该项目正式落户天水市。省科技厅副厅长巨有谦、台湾富创得科技股份有限公司董事长吴明发出席签约仪式。\r\n</p>\r\n<br \\=""> <img src="./templates/index/img/packeg/20140326_TSRB_01.png" align="center" /> <br \\="">\r\n<p>\r\n	台湾富创得科技股份有限公司成立于1998年，是专业研发及生产的国际型触摸屏的高科技企业，拥有成熟的OGS触摸屏生产与制造的全过程技术等多项自主知识产权的全球注册专利。系列产品在工业、农业、国防、军事、民用等各个领域应用广泛，前景广阔。本次与天水天光半导体有限责任公司签署的合作项目，将先期投资4亿元人民币，其中设备投资2.79亿元人民币。项目建成后，预计年产值可达9亿多元，实现利税近2亿元。\r\n</p>\r\n<br \\=""> <img src="./templates/index/img/packeg/20140326_TSRB_02.png" align="center" /> <br \\="">', '2014-03-26', '0');
INSERT INTO `news_list` VALUES (6, '富創得OGS觸摸屏和設備供不應求', '', 'DIGITIMES', 'Apple新機將使用六面強化OGS效應發酵，富創得OGS觸摸屏和設備供不應求。<br />\r\n<br />\r\n富創得科技董事長吳明發表示，富創得科技在投入觸摸屏生產前先評估全世界觸摸屏各種製造技術，發現以半導體製程的小片製程所製造出來的單片玻璃觸摸屏，成本最低，品質最好，設備也最便宜。因此在2007年就投入大筆資金，從零做起，開發出獨特技術、材料、設備和專利。<br />\r\n<br />\r\n富創得六面強化的OGS已經量產4年，行銷海內外，使用在汽車、飛機、工業設備、醫療機器和IT產業。富創得從2年前開始授權他廠以富創得的技術、材料、設備和專利生產，目前合作廠商分布在歐亞各國。<br />\r\n<br />\r\nApple決定使用六面強化OGS觸摸屏是非常明智的決定，因為成本和品質都優於其他任何一種觸摸屏，連in cell和on cell都比不上。而且六面強化的OGS使用的玻璃，是先切割研磨強化後再進行導電層等製程，製程完成後玻璃不必再切割，因此玻璃維持原本六面強化的強度，其強度是一般的三倍多。<br />\r\n<br />\r\n很多人用大片玻璃強化後來做OGS，做完後再切割，切割將使玻璃強度破壞殆盡，再使用氰氟酸(俗稱化骨水)腐蝕崩裂的玻璃，號稱二度強化，其實這不但不能增加玻璃強度，甚至會有氰氟酸殘留在玻璃破碎細縫裡，而造成消費者中毒時有所聞。<br />\r\n<br />\r\n最近造訪富創得的各國訪客絡繹不絕，大家都來尋求技術授權，尤其富創得在數個月前又發表水鑽石技術，可以使觸摸屏的細菌抑制率達百分之九十九，又可吸收藍光、紫外線、電磁波，且兼有自潔易潔功能。因此從世界各地的訪客大量湧至，尋求六面強化加水鑽石OGS的製造技術，大家都認同這將是觸摸屏的主流。<br />\r\n富創得已開始量產出貨水鑽石OGS，南韓、大陸和印度也將在今年陸續量產。<br />', '2014-01-28', '0');
INSERT INTO `news_list` VALUES (9, '楊維俊與臺灣富創得 科技股份有限公司洽談專案', '1月9日晚，中共天水市委副書記、市長楊維俊一行在上海與臺灣富創得科技股份有限公司董事長吳明發洽談OGS觸摸屏生產線建設項目。天水市副市長雷鳴、市政府秘書長逯克宗以及市工信委、天水天光半導體有限責任公司負責人一同參加洽談。', '天水网', '<p>1月9日晚，中共天水市委副書記、市長楊維俊一行在上海與臺灣富創得科技股份有限公司董事長吳明發洽談<span>OGS</span>觸摸屏生產線建設項目。天水市副市長雷鳴、市政府秘書長逯克宗以及市工信委、天水天光半導體有限責任公司負責人一同參加洽談。</p> \r\n</br>\r\n\r\n<p>臺灣富創得科技股份有限公司成立於1998年，是專業研發和生產國際型觸摸屏的高科技企業。OGS觸摸屏生產線建設專案是顯示與控制系統融為一體的高科技產業，系列產品在工業、農業、國防、軍事、民用等各個領域應用廣泛、前景廣闊。臺灣富創得科技股份有限公司與天水天光半導體有限責任公司合作建設的OGS觸摸屏專案，一期計畫投資4億元人民幣，其中設備投資2.79億元人民幣。項目建成後，預計年產值可達9億多元，實現利稅約2億元。</p>\r\n</br>\r\n<p>雙方就OGS觸摸屏項目實施進行了深入洽談。楊維俊在聽取吳明發對臺灣富創得科技股份有限公司及OGS觸摸屏專案情況的介紹後表示，歡迎臺灣富創得科技股份有限公司來天水投資發展，我們將落實各項優惠政策，全力支援專案建設。希望富創得公司與天水天光公司、投資方加強合作，儘快啟動實施項目，利用現有的標準化廠房，儘量縮短項目建設週期，促進項目早日建成投產。</p>\r\n</br>\r\n\r\n<p>雷鳴向客商介紹了天水經濟技術開發區優惠政策以及科技孵化大廈、標準化廠房建設等方面的情況。\r\n</p>', '2014-01-13', '0');
INSERT INTO `news_list` VALUES (18, 'OGS抗干擾更上一層樓', 'OGS領導製造商富創得科技的23.1吋大尺寸觸控面板，已經通過歐盟的CE認證，是為全球第一的大尺寸觸控面板新標竿，並且將此規範納入全系列產品的標準規格..', 'DIGITIMES', 'OGS領導製造商富創得科技的23.1吋大尺寸觸控面板，已經通過歐盟的CE認證，是為全球第一的大尺寸觸控面板新標竿，並且將此規範納入全系列產品的標準規格。<br />\r\n<br />\r\n現今電子設備已充斥在我們的日常生活中，一般常有的經驗就是當我們在講手機靠近電腦、或開車時電話來電都會聽到吵雜刺耳的聲音，這都是電子設備間電磁波的相互干擾。<br />\r\n<br />\r\n搭乘飛機禁止使用行動裝置也是怕干擾到精密的飛航儀器，除此之外，電磁波對於人體的影響更甚，會對中樞神經系統及自體免疫功能造成危害，甚至對心血管系統及血液系統產生影響導致白血球不穩定。多數學者認為，較低強度的微波長期作用，會加速眼睛晶狀體的衰老和混濁，並有可能使有色視野縮小和暗適應時間延長，造成視覺障礙。<br />\r\n<br />\r\n投射式電容觸控面板為達到高規的CE標準，需完全通過電磁干擾(EMI)及抗電磁干擾(EMS)兩大部分共14個測項。<br />\r\n<br />\r\n電磁干擾(EMI)的部分需通過：<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Conduction(傳導干擾)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Radiation(輻射干擾)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Harmonic(電源諧波干擾測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Voltage Fluctuation &amp; Flicker(電壓變動與閃爍干擾測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Disturbance Power(干擾功率)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Click(喀嚦率)<br />\r\n<br />\r\n抗電磁干擾(EMS)的部分需通過:<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ ESD(靜電放電耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ RS(輻射耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ EFT(電性快速突波耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Surge(雷擊耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ CS(傳導耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ PMF(電源頻率磁場耐受測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Dip(電壓下降瞬斷測試)<br />\r\n&nbsp;&nbsp;&nbsp;&nbsp;‧ Harmonics and Interharmonics(諧波與諧間波耐受測試)<br />\r\n<br />\r\n其中輻射耐受測試為對電子產品，做外加高頻電磁波干擾，而傳導耐受測試則是在電源端直接加入150K-80MHz的干擾源，而裝置在干擾下，必須正常使用不能有任何異常。<br />\r\n<br />\r\n能通過此嚴苛的測試後，不但產品更加穩定，對使用者也有保障。OGS在輕、薄的趨勢下更是挑戰，尤其是在20吋以上的觸控面板，更是一般小廠所無法跨越的門檻。<br />\r\n<br />\r\n若留意富創得科技近來所研發推廣之產品，不難發覺已朝向更環保、健康、生活化的方向邁進，足以見其經營團隊在觸控業界如此大者恆大的環境下，尋求產品定位與世界脈絡接軌的企圖心。<br />', '2014-04-01', '0');
INSERT INTO `news_list` VALUES (11, '富創得 獨占OGS市場', '富創得科技董事長吳明發表示，OGS（One glass solution）近年在業界的興起值得關注。OGS的技術特點主要是在保護玻璃上直接形成ITO導電膜及傳感器的技術，一塊玻璃同時能起到保護玻璃和觸摸傳感器的雙重作用。由於其透光性、輕薄度在GF之上，產品的良率、研發投入又較on', '工商時報', '富創得科技董事長吳明發表示，OGS（One glass solution）近年在業界的興起值得關注。OGS的技術特點主要是在保護玻璃上直接形成ITO導電膜及傳感器的技術，一塊玻璃同時能起到保護玻璃和觸摸傳感器的雙重作用。由於其透光性、輕薄度在GF之上，產品的良率、研發投入又較on、in-cell有優勢。<br />\r\n<br />\r\n富創得科技開發出獨特的技術、材料及設備，品質領先業界，也是目前唯一可生產各種顏色邊框的OGS製造商，TP售價更是傳統製程所生產出的相同產品的成本。世界各知名大廠除了紛紛下單，也爭取授權生產，目前已有多家取得授權。<br />\r\n<br />\r\n該公司製程與一般採用薄膜製程的觸控廠商不同的是，其生產製程先將玻璃切割，再進行導電層的電鍍，採用奈米化工技術，可直接在面板上進行各種加工，因為該公司玻璃強度是別人的3倍，也因為玻璃強度超高，TP和LCD不必全面貼合，這對系統廠又能節省每吋1至2美元的費用。同時獨創專利導電層是多層結構，不必架橋，沒有架構的缺陷，製程簡單，設備成熟，設廠4個月就可完成，6個月就可量產，良率可達80％。<br />\r\n<br />\r\n另外貼合的問題，目前業界除了用玻璃貼玻璃，也有用玻璃或塑膠貼1層或2層PET，除了良率低外，延遲性氣泡是永無解的問題。因為貼合要用OCA膠，OCA的材料是PVA，PVA在溫度37度以上烤會產生氣泡，氣泡會造成觸控失靈。LCD溫度達42度，因此TP使用後氣泡會逐漸產生，觸控功能也就慢慢消失。目前國內外大廠自己生產ITO PET、OCA和控制IC，除了材料成本居高不下外，仍然無法解決ITO阻抗在通電後升高的問題，對OCA膠的延遲性氣泡也無解，加上貼合良率也提高不起來，所以台灣、南韓和大陸多家TP廠紛紛改用富創得OGS製程。<br />', '2013-08-06', '0');
INSERT INTO `news_list` VALUES (12, '富創得科技OGS觸控面板成功整廠輸出', 'FORTREND富創得科技Turn-Key整廠輸出，在山東濟南創下一個成功的案例。  山東是一個新近努力擠進信息產業供應鏈的地方。從前山東以有泰山為地標，孔老夫子誕生在曲阜為驕傲，作為北京的「菜園子」是經濟主軸，路上有許多歷史的知名地名「臨淄」、「即墨」齊魯故地是懷念。冬春種麥、', 'DIGITIMES', 'FORTREND富創得科技Turn-Key整廠輸出，在山東濟南創下一個成功的案例。<br />\r\n<br />\r\n山東是一個新近努力擠進信息產業供應鏈的地方。從前山東以有泰山為地標，孔老夫子誕生在曲阜為驕傲，作為北京的「菜園子」是經濟主軸，路上有許多歷史的知名地名「臨淄」、「即墨」齊魯故地是懷念。冬春種麥、夏種玉米還有大蔥、大白菜，生活自得其樂。<br />\r\n<br />\r\n現在的山東變革大了，有地利之便，處在南韓、日本與上海之間，海運交通便捷，青島港航向國際。山東各市級都加緊建設「高新科技園區」，投入拔尖的訊息產業，在電子產業供應鏈上不缺席。名城濟南市不落人後，積極投入OGS觸控屏幕的開發與生產，在台灣篩選了各個潛在的合作夥伴，評估技術的可行性、生產良率與成本管控的優勢，最後選擇「富創得科技」為合作夥伴與生產設備的提供者。<br />\r\n<br />\r\n<img src="/kindeditor/php/../../images/image/20140326/20140326071824_17498.jpg" alt="" /><br />\r\n<p>\r\n	富創得科技OGS觸控面板成功整廠輸出。\r\n</p>\r\n<p>\r\n	<span style="line-height:1.5;">富創得為山東濟南華芯富創規劃設計了一條完整的OGS生產線，所有設備都是精選自台灣的主力高階設備廠商。這一整套設備共計打盤裝箱了60個40呎貨櫃，浩浩蕩蕩在今年6月初裝船，運抵山東濟南。富創得派出了80位工程師配合設備廠的數十位工程技師，在濟南新建設的工廠中裝機，業於7月初達成使命。</span>\r\n</p>\r\n<br />\r\n7月11日山東濟南華芯富創OGS廠正式開幕，富創得董事長吳明發先生親自率隊在場迎接；山東省級領導與大陸知名電子業主管、日本與南韓相關業者都蒞臨考察參觀，對未來的OGS觸控面板供應鏈添加的新成員予以關注。<br />\r\n<br />\r\n<p>\r\n	這是富創得新增加的一個忠實生產夥伴，也是大陸第一條自主的觸控面板生產線；意義重大。這一個即將投產的案例，更是證明了富創得科技股份有限公司的製程能力、整廠規劃與設備供輸能力，加上工程建設能力；已經成為各方注目的焦點，未來更有愈新愈進的發展。\r\n</p>\r\n<p>\r\n	<br />\r\n</p>', '2013-07-25', '0');
INSERT INTO `news_list` VALUES (13, '繼濟南後富創得再下重慶 四川廣安兩城', '富創得科技的OGS授權、生產繼濟南7月量產之後，在四川廣安及重慶再下兩城，12/3日，由重慶市黃市長親自主持重慶市渝北區政府和富創得科技及清華集團三方合作協議簽約儀式。', '  DIGITIMES', '<p>富創得科技的OGS授權、生產繼濟南7月量產之後，在四川廣安及重慶再下兩城，12/3日，由重慶市黃市長親自主持重慶市渝北區政府和富創得科技及清華集團三方合作協議簽約儀式。</p>\r\n</br>\r\n<p>依據三方合作協議內容中，由重慶市渝北區政府提供6,000平方公尺標準廠房，和180畝的土地，富創得科技提供OGS授權，凌訊科技提供總投資額人民幣60億元，主攻13~27吋觸控面板，其中藍寶石選項將為國內首創。重慶市黃市長致詞中表示，重慶市的IT產業供應鏈很齊全，且大力推廣大尺寸觸控面板在中國發展，提供大量資源，要錢給錢，要人給人，全力配合。</p>\r\n</br>\r\n<p>清華集團梅董事長表示，清華集團是中國高科技業的龍頭，中國許多高科技業都隸屬於清華集團，且願意配合政府政策，與富創得科技配合在中國推動觸控面板產業。富創得科技吳董事長表示，富創得科技的生產成本為他廠的4分之1，機器成本為他廠的10分之1，且生產的觸控面板具有抗菌、抗UV、自潔等功能，在國際間具有強烈的優勢，國際間許多大廠紛紛來談合作，包括水果公司在內。</p>\r\n</br>\r\n<p>富創得科技與重慶市政府及清華集團合作，共同在中國推動OGS觸控面板，注入一股新力量，開創新商機。</p>\r\n</br>\r\n	<img src="http://192.168.0.4/images/image/20140326/20140326072816_18116.jpg" alt="" /> \r\n</p>', '2013-12-11', '0');
INSERT INTO `news_list` VALUES (15, '富創得推出新秘密武器 藍寶石鍍膜', '近幾年，教育界擔心學生的書包越來越重，脊柱彎曲、身形佝僂，未老先衰。再這樣下去，台灣只會更是東亞病夫，在全球的健康評比上，比飢餓非洲的人民還不如。因此寄望能有一個小電腦，擁有超群的記憶容量，國文、英文、物理化學加生物，還有一本好算術，全都放在手持電腦 + 閱讀器裡，手指一撥，就出', 'DIGITIMES', '近幾年，教育界擔心學生的書包越來越重，脊柱彎曲、身形佝僂，未老先衰。再這樣下去，台灣只會更是東亞病夫，在全球的健康評比上，比飢餓非洲的人民還不如。因此寄望能有一個小電腦，擁有超群的記憶容量，國文、英文、物理化學加生物，還有一本好算術，全都放在手持電腦 + 閱讀器裡，手指一撥，就出現在顯示屏，每天上學甩掉那沉重8公斤書包，快樂拎著個1公斤智慧電腦。<br />\r\n<br />\r\n<br />\r\n若非使用顯示屏幕不可 &nbsp;那就減少降低它的風險<br />\r\n<br />\r\n這個「夢」已經實現了，價格也符合「摩爾定律」；雖不說價廉物美，但是倒真的幾乎人人買得起。台灣各家發展出來的小平板、超薄筆記型電腦，性能不輸蘋果、新力，價格平易近人。時髦一點用iPad，實用一點用台灣的品牌。加上智慧型手機，屏幕一日大於一日，功能早就超越PDA，性能簡直是到了無所不能的地步，通話是最基本的功能，上網、發簡訊、打卡、照相PO網、E-mail、打電動等。人生不可一日無之，不可一時離手，如果電池儲量不足，預備一個Power Bank隨時支援。<br />\r\n<br />\r\n<img src="/kindeditor/php/../../images/image/20140326/20140326073407_91848.jpg" alt="" /><br />\r\n富創得FORTREND擁有一項新技術，在觸控面板上加一層鍍膜，永久性的藍寶石Sapphire膜層，解決3C產品對視覺不良影響的方法。<br />\r\n<br />\r\n只見MRT捷運上，有一半人低頭用手指撥弄智慧型手機，走在路上有人邊走還邊低頭撥弄，餐廳裡的情侶，面對面；可是低著頭，各玩各的手上「智慧玩具」。已經有了一個新名詞：低頭族。這也不過是近1年的事，但是影響卻迅速且有傷害。 連各大報章雜誌和醫師都大聲呼籲：整天低頭盯螢幕；近視性白內障激增。<br />\r\n<br />\r\n不僅是老年人的眼睛有飛蚊症、白內障，這低頭族們年紀輕輕，近視度數激增，白內障爆發；已經不只是「視茫茫」，簡直要「盲」了。原因呢？ 緊盯著螢光屏幕，眼球疲勞，最糟糕的是螢光屏幕發出的光線會傷害到視神經。這在幾家國內大醫院的名眼科醫師，都做出了醫學統計報告。如果再這樣下去，有相當一部分人會到近乎於「瞎」的地步，已經不是東亞病夫，要成東亞盲夫了。<br />\r\n<br />\r\n大小螢光屏幕的光源現在都是運用白光LED，這白光LED是以氮化鎵藍光LED藉著激發螢光粉，產生次生黃光，混合後以白光型式進入我們的眼睛。有部分使用UV LED 紫外光作為螢光粉光源，這不可避免的一部分紫外光線，也是造成眼睛傷害的重大原因。有眼科醫師建議，加戴個偏光濾色眼鏡，遮濾一部分紫外光與藍光。 其實這個紫外光與藍光的問題，不一定需要眼鏡族加裝濾色偏光片；可以在螢光屏幕端直接解決。使得螢光屏本身無害，去除掉使用者的潛在傷害危機，將傷害視神精的UV紫外光濾除。<br />\r\n<br />\r\n觸控面板上加一層鍍膜，永久性藍寶石Sapphire膜層&nbsp;<br />\r\n<br />\r\nSapphire藍寶石的特性是硬度大、剛性耐磨，可以保護屏幕玻璃耐刮。藍寶石鍍膜後，表面水滴角特性改變，髒污一擦即除。最重要的是可以過濾阻絕大部分UV光，只有波長較長的藍光，可以透出。使得螢光屏幕顯色柔和，也大幅減少對眼睛視神經的傷害。<br />\r\n<br />\r\n解決一個問題，揚湯止沸；不如釜底抽薪。走到現階段；手持式電腦3C產品這麼發達，用途還在與日俱增，不可能丟下來不用。與其要求加戴一副眼鏡，不如在螢光屏幕端解決。我們歡迎富創得的解決之道，期待每一個新螢光屏幕，無論尺寸大小，都能夠有藍寶石鍍膜，都能有柔和的光輸出。<br />\r\n<br />', '2013-08-22', '0');
INSERT INTO `news_list` VALUES (16, 'OGS觸控面板富創得 技術領先', '單片玻璃方案（OGS）觸控面板商機後市看漲。在貼合良率提升以及Windows 8新作業系統帶動的市場需求逐漸浮現下，OGS觸控面板商機可望在下半年爆發，不論大、中、小螢幕尺寸的行動裝置均將大量導入。富創得科技領先同業開發出獨特OGS技術、材料及設備，受同業和國際知名大廠肯定，爭相', '工商時報', '<p>\r\n	<img src="/kindeditor/php/../../images/image/20140326/20140326073608_51278.jpg" alt="" /> \r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n</p>\r\n<p style="text-indent:2em;">\r\n	單片玻璃方案（OGS）觸控面板商機後市看漲。在貼合良率提升以及Windows 8新作業系統帶動的市場需求逐漸浮現下，OGS觸控面板商機可望在下半年爆發，不論大、中、小螢幕尺寸的行動裝置均將大量導入。富創得科技領先同業開發出獨特OGS技術、材料及設備，受同業和國際知名大廠肯定，爭相爭取授權及技術轉移。\r\n</p>\r\n<p style="text-indent:2em;">\r\n	<br />\r\n富創得生產成本只有其他觸控面板廠的1/4，而且生產設備的建置成本只有其他廠的1/10。因此全中國第一家使用富創得技術及設備的OGS觸控面板製造廠，今年7月已經在山東濟南開幕量產。Fortrend富創得是目前全球唯一將OGS＋Sapphire treatment結合起來，整合加工與生產的領導者。而且尺寸愈大的OGS觸控面板，價格成本愈有競爭力。在只有同業1/4的成本架構下，生產具有高效率觸控/抗菌/抗UV/抗污染/抗輻射的產品，並且在製程中無鹵/免氟，貼緊RoHS的標準與HSF的潮流趨勢，使用者用得安心；生產者有高度競爭力，發揚台灣創新精神，為國內3C業進步做支撐。<br />\r\n<br />\r\n藍寶石Sapphire被覆，是在玻璃表面沉積一層Sapphire的材質，不單是運用藍寶石的高硬度可以防蝕與抗刮、耐磨擦，更因為藍寶石的濾光特性，將UV紫外線阻隔，防止對使用者眼睛視網膜的傷害。<br />\r\n<br />\r\n該公司從素玻璃開始直到TP成品完善的一條龍生產設備規劃與設置，軟硬體技術皆已整合，且藍寶石可以coating被覆在玻璃、塑膠和金屬上，產品運用涵蓋IT、建築、汽車和家電等產品上，電容式觸控面板也從兩片玻璃交接的方式，進展到單片玻璃OGS式，全力投入OGS投射式電容觸控面板研發、開發到生產的Fortrend富創得科技，不但成功推出一系列大尺寸OGS觸控面板，是為這個範疇的領導者；更進一步開發出的製程，將這個產業推到新境界。\r\n</p>', '2013-08-28', '0');
INSERT INTO `news_list` VALUES (17, '触控面板上镀层蓝宝石膜层 可分解细菌!', '在触控面板上预镀製一层蓝宝石的膜层：在经过紫外线或日光灯照射后，会产生”氢氧自由离子基(OH-)”，可有效破坏细菌胞膜，亦可固化病毒蛋白，抑制病毒活动能力，且可将细菌还原成CO2, H2O。杀菌能力达99.99%，还可以有效分解空气难闻异味。', 'CTimes ', '<p class="MsoNormal">\r\n	【导读】：在触控面板上预镀製一层蓝宝石的膜层：在经过紫外线或日光灯照射后，会产生”氢氧自由离子基(OH-)”，可有效破坏细菌胞膜，亦可固化病毒蛋白，抑制病毒活动能力，且可将细菌还原成CO2, H2O。杀菌能力达99.99%，还可以有效分解空气难闻异味。<br />\r\n&nbsp; &nbsp; 北京时间10月11日消息，中国触摸屏网讯， 随着现代人人手一支智慧型手机、平板电脑，触控面板已经蔚为主流。但有一个惊人的新医学新闻：根据英国「每日邮报」报导英国消费者团体「Which？」随机测试三十支智慧手机与三十部平板电脑的细菌含量，发现有些智慧手机与平板电脑的触控萤幕，细菌比马桶座还要高出30倍以上。把脸贴在这样一个细菌的温床上，比无线电讯号辐射SAR还要更致命!<br />\r\n<br />\r\n<img src="/kindeditor/php/../../images/image/20140326/20140326073950_82092.jpg" alt="" /><br />\r\n图示: 富创得在触控面板上预镀製一层蓝宝石的膜层，可以有效分解空气难闻异味。<br />\r\n<br />\r\n&nbsp; &nbsp; 富创得先进的製程，在触控面板上预镀製一层蓝宝石的膜层：在经过紫外线或日光灯照射后，会产生”氢氧自由离子基(OH-)”，可有效破坏细菌胞膜，亦可固化病毒蛋白，抑制病毒活动能力，且可将细菌还原成CO2, H2O。杀菌能力达99.99%，还可以有效分解空气难闻异味。<br />\r\n<br />\r\n&nbsp; &nbsp; 此外在环境中无时无刻存在的UV紫外光，且LCD也会产生UV紫外光，轰击我们的视网膜，刺激视神经；使得眼睛的功能衰退，水晶体产生白内障，未老先衰，危机重重。<br />\r\n<br />\r\n&nbsp; &nbsp; 蓝宝石的特性亦能吸收UV紫外光，防制这一个危险因素；使用者的眼睛得以不受伤害。富创得蓝宝石镀膜层也增加了屏幕表面硬度，大大降低了受环境灰尘中硬颗粒磨蚀的机会，保持屏幕的无刮痕状态。蓝宝石的高水滴角特性，也让髒污不易黏着于表面，容易擦拭保洁。最重要的是；富创得蓝宝石镀膜製程有Cost Effective的成本优势，惠而不费。<br />\r\n<br />\r\n&nbsp; &nbsp; 资讯业界推动新产品，需要有先进的优势、防范问题于未然的洞烛先机，富创得在这裡为众家屏幕的生产者提供了一个高附加价值的机会与方桉。\r\n</p>\r\n<p class="MsoNormal">\r\n	<span></span> \r\n</p>', '2013-10-11', '0');
INSERT INTO `news_list` VALUES (19, '富創得水鑽石抑菌力高達98.9%', '位在新竹市的財團法人食品工業發展研究所，在4月28日的測試報告顯示，富創得水鑽石的抑菌能力出乎意料的高。', 'DIGITIMES', '<p style="text-align:center;">\r\n	<br />\r\n</p>\r\n<div style="text-align:left;">\r\n	<span style="line-height:1.5;">位在新竹市的財團法人食品工業發展研究所，在4月28日的測試報告顯示，富創得水鑽石的抑菌能力出乎意料的高。</span> \r\n</div>\r\n<div style="text-align:left;">\r\n	<br />\r\n</div>\r\n<div style="text-align:left;">\r\n	<span style="line-height:1.5;">在經過富創得水鑽石鍍膜加工後的玻璃片上，接種載入每平方公分10,300株的大腸桿菌，就在一般普通日光燈照明下，經過24小時，進入檢測發現平均每平方公分只有80.6菌株存活。而對照組的普通玻璃面，同樣接種了相等數量的菌株，也在同樣環境下，平均每平方公分上還有7,310個菌株存活。比較起來，富創得水鑽石膜層的抑菌力高達98.9%。</span> \r\n</div>\r\n<div style="text-align:left;">\r\n	<br />\r\n</div>\r\n<div style="text-align:left;">\r\n	<span style="line-height:1.5;">兩相對比之下，富創得水鑽石驚人的抑菌力表現出來，可運用在各種各樣的生活用品上。用在食器上，不論是碗、盤、杯盞，可以抑制細菌孳生，即便是清洗過程中漏網之菌株，也無法在水鑽石膜層上存活。</span> \r\n</div>\r\n<div style="text-align:left;">\r\n	<br />\r\n</div>\r\n<div style="text-align:left;">\r\n	<span style="line-height:1.5;">使用在冰箱玻璃層架上，鍍在浴室的器具上，即使是潮濕環境，防霉抗菌，增益生活安全。建築室內、外玻璃加鍍富創得水鑽石，則可以發揮抑菌效果之外，還有過濾紫外線、電磁波，消除環境中臭味，易潔加上自潔的多重功效。</span> \r\n</div>\r\n<div style="text-align:left;">\r\n	<br />\r\n</div>\r\n<div style="text-align:left;">\r\n	<span style="line-height:1.5;">從所得到的食品工業發展研究所正式檢測報告，可以看到這富創得水鑽石膜層的抑菌功效卓著。</span> \r\n</div>\r\n<p>\r\n	<br />\r\n</p>\r\n<p style="text-align:center;">\r\n	<img src="/images/image/20140509/20140509005607_49284.jpg" alt="" /><span style="line-height:1.5;">&nbsp;</span> \r\n</p>\r\n<p style="text-align:center;">\r\n	<span style="line-height:1.5;">食品工業發展研究所正式檢測報告。</span> \r\n</p>', '2014-05-08', '1');
INSERT INTO `news_list` VALUES (20, '2014 觸控．面板暨光學膜製程、設備、材料展覽會', '', '富創得', '<p style="text-align:center;">\r\n	<span style="font-size:18px;"><br />\r\n</span> \r\n</p>\r\n<p style="text-align:center;">\r\n	<span style="font-size:18px;"></span> \r\n</p>\r\n<p style="text-align:center;">\r\n	<img src="/images/image/20140820/20140820015013_91790.png" alt="" /> \r\n</p>\r\n<p style="text-align:center;">\r\n	<strong><br />\r\n</strong> \r\n</p>\r\n<blockquote>\r\n	<blockquote>\r\n		<blockquote>\r\n			<blockquote>\r\n				<blockquote>\r\n					<blockquote>\r\n						<p style="text-align:left;">\r\n							<strong><span style="font-family:''Microsoft YaHei'';font-size:18px;color:#006600;">公司名稱： 富創得科技股份有限公司&nbsp;</span></strong> \r\n						</p>\r\n					</blockquote>\r\n				</blockquote>\r\n			</blockquote>\r\n		</blockquote>\r\n	</blockquote>\r\n	<blockquote>\r\n		<blockquote>\r\n			<blockquote>\r\n				<blockquote>\r\n					<blockquote>\r\n						<p style="text-align:left;">\r\n							<strong><span style="font-family:''Microsoft YaHei'';font-size:18px;color:#006600;"><strong>攤位號碼： K1022&nbsp;</strong></span></strong> \r\n						</p>\r\n					</blockquote>\r\n				</blockquote>\r\n			</blockquote>\r\n		</blockquote>\r\n	</blockquote>\r\n</blockquote>\r\n<p style="text-align:center;">\r\n	<strong></strong> \r\n</p>\r\n<blockquote>\r\n	<blockquote>\r\n		<blockquote>\r\n			<blockquote>\r\n				<blockquote>\r\n					<blockquote>\r\n						<blockquote>\r\n							<blockquote>\r\n								<p style="text-align:center;">\r\n									<br />\r\n								</p>\r\n							</blockquote>\r\n						</blockquote>\r\n					</blockquote>\r\n				</blockquote>\r\n			</blockquote>\r\n		</blockquote>\r\n	</blockquote>\r\n</blockquote>\r\n<p style="text-align:center;">\r\n	<span style="font-size:14px;"></span> \r\n</p>\r\n<p style="text-align:center;">\r\n	<span style="font-family:''Microsoft YaHei'';font-size:16px;">富創得將於2014/08/27-29於台北世貿南港展覽館1樓參與展出，</span><span style="line-height:1.5;font-family:''Microsoft YaHei'';font-size:16px;">我們竭誠歡迎您前來參觀 !</span> \r\n</p>\r\n<div style="text-align:center;">\r\n	<span style="line-height:1.5;font-family:''Microsoft YaHei'';font-size:16px;"></span><span style="line-height:1.5;font-family:''Microsoft YaHei'';font-size:16px;">敬請參觀者上網預先登錄: http://www.touchtaiwan.com/visitorReg.asp&nbsp;</span> \r\n</div>\r\n<span> \r\n<div style="text-align:center;">\r\n	<span style="line-height:1.5;font-family:''Microsoft YaHei'';font-size:16px;">為減少您現場換證的等待時間，歡迎使用線上參觀者預先登錄!</span> \r\n</div>\r\n</span> \r\n<p>\r\n	<br />\r\n</p>\r\n<p style="text-align:center;">\r\n	<br />\r\n</p>\r\n<p style="text-align:center;">\r\n	<br />\r\n</p>', '2014-08-20', '0');

-- --------------------------------------------------------

-- 
-- 資料表格式： `ogs_four`
-- 

CREATE TABLE `ogs_four` (
  `ogs_id` int(10) NOT NULL,
  `ogs_content` longtext collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`ogs_id`),
  FULLTEXT KEY `ogs_content` (`ogs_content`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `ogs_four`
-- 

INSERT INTO `ogs_four` VALUES (1, '<div style="padding-left:10%;padding-right:10%"><br><br><br><br>\r\n<br><br><br><br><br><br><b><span style="font-size:30px;line-height:2;color: #1C19FF; ">富創得觸控屏的專利</span></b><br />\r\n<br />\r\n\r\n<div align="center">\r\n	<img src="/webroot/templates/index/img/ogs/ogs5_bg-1-1.png" width="800" height="500" alt="" align="center"/><br> \r\n</div>\r\n<ul style="padding-right: 0px; padding-left: 0px; margin: 0px; list-style: none; border: 0px; outline: 0px; font-size: 20px; color: rgb(0, 0, 0); font-family: sans-serif, 微軟正黑體; line-height: 16px; background-color: rgb(244, 244, 244);">\r\n	<li class="mb20" style="margin: 0px 0px 20px; padding: 0px; border: 0px; outline: 0px; list-style: disc;">\r\n	<p style="margin: 0px; padding: 0px; border: 0px; outline: 0px; line-height: 1.2em;">已獲頒領專利證書計23件，專利待領證總計2件，審查中有19件。</p>\r\n	</li>\r\n	<li class="mb20 " style="margin: 0px 0px 20px; padding: 0px; border: 0px; outline: 0px; list-style: disc;">\r\n	<p style="margin: 0px; padding: 0px; border: 0px; outline: 0px; line-height: 1.2em;">富創得擁有OGS觸控屏最基礎的疊層構造與製作方法發明專利，有簡化製程、提升良率及降低成本的優勢。</p>\r\n	</li>\r\n</ul>\r\n</div>');

-- --------------------------------------------------------

-- 
-- 資料表格式： `ogs_one`
-- 

CREATE TABLE `ogs_one` (
  `ogs_id` int(10) NOT NULL auto_increment,
  `ogs_title` varchar(500) collate utf8_unicode_ci default NULL,
  `ogs_content` longtext collate utf8_unicode_ci,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`ogs_id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=10 ;

-- 
-- 列出以下資料庫的數據： `ogs_one`
-- 

INSERT INTO `ogs_one` VALUES (1, 'OGS疊構與製程 ', '<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2">1.何謂OGS</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">將觸控玻璃(Touch Sensor)的觸控功能與保護玻璃(Cover Glass)的保護功能集結成一塊玻璃的產品，稱為One glass solution，簡稱OGS，亦即在一般的保護玻璃內側鍍上ITO導電層，使該單片玻璃不僅具備保護玻璃的強度、安全性，同時也兼具觸控功能。       由於目前以玻璃基材為主的投射式電容觸控面板，多採用2片玻璃結構，亦即1片觸控玻璃加上1片保護玻璃，為簡化材料、製程，提升生產效率以及降低成本，同時減少1片玻璃的使用，也可以使終端產品設計更輕、更薄，使面板透光度更高，因此幾乎所有的觸控面板廠都著手開發單片玻璃解決方案。</span><br />\r\n<b><span style="font-size:30px;line-height:2">2.OGS疊構</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">富創得OGS疊構與製程已獲得美國及其他多國多項發明專利，為採用Cell製程，玻璃利用率高、玻璃強度強，27"觸控面板可通過1kg/1M的落球測試。製程中所使用的耐高溫材料可耐500度高溫，不碳化、不導電。獨特的多層ITO導電層，無架橋及小絕緣點的創新設計，不會氧化，抗ESD也強。有高硬度抗刮表面、不需與LCD全面貼合，擁有10點以上觸控功能，並已通過Windows 8認證</span> \r\n\r\n</div>\r\n\r\n    <br />\r\n    <div align="center">\r\n<div style="padding-left:10%;padding-right:10%>\r\n\r\n  <div align="center">\r\n    <b><span style="font-size:26px;font-weight:bold;line-height:2;">富創得專利層ITO疊構</span></b><br> \r\n  </div>\r\n\r\n</div>\r\n\r\n\r\n  <div style="padding-left:10%;padding-right:10%>\r\n\r\n  <span style="font-size:16px;line-height:1.5;">富創得採用為多層ITO疊構，無架橋及小絕緣點的創新設計，不會有氧化情況，良率可高達80%以上，且抗ESD夠強，可支援10指觸控，已有多項產品通過Windows 8認證。</span> \r\n\r\n  </div>\r\n\r\n    <br />\r\n\r\n<div align="center">\r\n<img src="/images/image/20140416/20140416081101_123.gif" width="650" height="211" alt="" align="middle"/> \r\n</div>\r\n\r\n    <br />\r\n\r\n<div align="center">\r\n<img src="/images/image/20140416/20140416081101_456.gif" width="650" height="211" alt="" align="middle"/> \r\n</div>\r\n<p>\r\n    <br />\r\n</p>\r\n\r\n    <br />\r\n\r\n\r\n    <br />\r\n\r\n    <div align="center">\r\n\r\n    <b><span style="font-size:26px;font-weight:bold;line-height:2;">富創得專利</span></b><b><span style="font-size:26px;font-weight:bold;line-height:2;">OGS</span></b><b><span style="font-size:26px;font-weight:bold;line-height:2;">疊構<br></span></b><b></b> \r\n\r\n<div style="padding-left:10%;padding-right:10%>\r\n<span style="font-size:16px;line-height:1.5">富創得獨創OGS疊構已獲得多項國際專利，且多種專利材料，例如防蝕刻膠、絕緣層、玻璃邊框油墨、水鑽石表面處理。</span> \r\n<p>\r\n</div>\r\n    <br />\r\n</p>\r\n</div>\r\n\r\n  <div align="center">\r\n    <img src="/images/image/20140416/20140416093006_78933.png"width="800" height="350" alt="" align="center" /> \r\n  </div>\r\n\r\n\r\n    <br />\r\n\r\n<div style="text-align:center;">\r\n    <img src="/images/image/20140710/20140710083025_60553.png" width="800" height="500" alt="" /><br />\r\n</div>\r\n\r\n\r\n\r\n    <br />\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<div align="left">\r\n<b><span style="font-size:30px;line-height:2">3.OGS製程優勢\r\n</div>\r\n</span></b><br />\r\n</p>\r\n</div>\r\n\r\n    <br />\r\n\r\n<div align="center">\r\n\r\n    <b><span style="font-size:26px;font-weight:bold;line-height:2;">富創得</span></b><b><span style="font-size:26px;font-weight:bold;line-height:2;">CELL</span></b><b><span style="font-size:26px;font-weight:bold;line-height:2;">製程</span><br></b><b></b> \r\n\r\n\r\n<span style="font-size:16px;line-height:1.5">富創得OGS製程採用的是CELL/單片製程，與他廠所使用的SHEET製程其優劣比較如下：</span> \r\n<p>\r\n    <br />\r\n</p>\r\n</div>\r\n\r\n    <br />\r\n\r\n\r\n  <div align="center">\r\n    <img src="/images/image/20140416/20140416083026_87978.png" width="800" height="187" alt="" align="center" /> \r\n  </div>\r\n\r\n\r\n    <br />\r\n\r\n\r\n    <br />\r\n\r\n<div align="center">\r\n\r\n    <b><span style="font-size:26px;font-weight:bold;line-height:2;">富創得獨創的濺鍍技術 </span><br><span></span></b> \r\n\r\n</div>\r\n    <div align="center">\r\n\r\n    <span style="font-size:16px;line-height:1.5">富創得獨創的濺鍍技術，能讓</span><span style="font-size:16px;line-height:1.5">ITO</span><span style="font-size:16px;line-height:1.5;">線路爬上高達</span><span style="font-size:16px;line-height:1.5">24um</span><span style="font-size:16px;line-height:1.5">的斷差的邊框油墨，無線路斷線問題。</span><span></span> \r\n\r\n</div>\r\n<p>\r\n    <br />\r\n</p>\r\n\r\n    <div align="center">\r\n    <img src="/images/image/20140417/20140417024102_16083.png" width="800" height="187" alt="" align="center"/> \r\n\r\n\r\n\r\n    <br />\r\n\r\n\r\n    <span style="font-size:16px;line-height:1.5;">它廠濺鍍技術，會受限於邊框油墨的厚度，導至於ITO斷線。</span> \r\n\r\n    </div>\r\n\r\n\r\n    <br />\r\n<div style="padding-left:10%;padding-right:10%">\r\n<div align="left">\r\n<b><span style="font-size:30px;line-height:2">4.富創得OGS與其他觸控製程的比較</span></b><br />\r\n</div>\r\n\r\n</div>\r\n<div align="center">\r\n<p>\r\n    <img src="http://192.168.0.4/images/image/20140328/20140328050407_64450.png" width="700" height="214" alt="" /> \r\n</p>\r\n\r\n\r\n    <span style="font-size:16px;line-height:1.5;">LCD加OGS或In-Cell . On-Cell的厚度相同。</span></div> \r\n\r\n<div align="center">\r\n<img src="/images/image/20140328/20140328050407_55812.png" width="265" height="214" alt="" /> \r\n<img src="/images/image/20140328/20140328050407_88112.png" width="265" height="214" alt="" /> \r\n<img src="/images/image/20140328/20140328050407_55112.png" width="265" height="214" alt="" /> <br /></div>\r\n<br />\r\n\r\n    <br />\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2">5.富創得OGS優勢</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">富創得的OGS成本比他廠低，觸控模組售價是別人的成本。</span><br />\r\n<span style="font-size:16px;line-height:1.5">富創得OGS製程無架橋，製程良率高。</span><br />\r\n<span style="font-size:16px;line-height:1.5">我們的製程可做任何尺寸，尺寸愈大，競爭力愈強。</span><br />\r\n<span style="font-size:16px;line-height:1.5">玻璃是先切割再研磨C角R角後，接著高溫強化處理，強化後不再切割研磨,因此強度都在500MPA或800MPA以上。強化後玻璃靜壓擊破點為80Kg，比大片製程高3倍多</span><br />\r\n<span style="font-size:16px;line-height:1.5">我們不必使用化骨水做二度強化，因1.5克的化骨水可殺死一個人。</span><br /> \r\n</p>\r\n</div>', 0);

-- --------------------------------------------------------

-- 
-- 資料表格式： `ogs_three`
-- 

CREATE TABLE `ogs_three` (
  `ogs_id` int(20) NOT NULL auto_increment,
  `ogs_title` varchar(200) collate utf8_unicode_ci NOT NULL,
  `ogs_link` varchar(200) collate utf8_unicode_ci NOT NULL,
  `ogs_content` longtext collate utf8_unicode_ci NOT NULL,
  `ogs_img` varchar(300) collate utf8_unicode_ci NOT NULL,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`ogs_id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=9 ;

-- 
-- 列出以下資料庫的數據： `ogs_three`
-- 

INSERT INTO `ogs_three` VALUES (7, '獨創性技術 Terry', '', '<div style="padding-left:10%;padding-right:10%">\r\n<p class="MsoNormal">\r\n	<span style="font-size:18px;line-height:1.5;"> 富創得OGS，因搭配自行研發的特定材料，不僅製程簡化，良率高，更能彰顯富創得OGS品質與價格的優勢，包含奈米級水鑽石鍍膜、邊框油墨、耐酸油墨、絕緣光學材料等，極具優異性：</span> \r\n</p>\r\n<b><span style="font-size:26px;line-height:2">邊框油墨：</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">在OGS製程中，一般邊框油墨會遭遇FPC在熱壓作業三個月後，壓合區有油墨透明的情況。因此只能選擇設備昂貴的黃光製程，但是富創得所開發出的邊框油墨，使用於簡便印刷製程，不但不會有油墨透明化狀況且能夠承受高溫製程，在ITO濺鍍時不會碳化和剝落現象。</span><br />\r\n<div align="center">\r\n<img src="/images/image/20140416/20140416083221_62437.png" width="400" height="303" alt="" align="center"/><br> \r\n</div><br>\r\n<b><span style="font-size:26px;line-height:2">絕緣光學材料：</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">富創得自行研發的絕緣光學材料，使富創得的OGS製程無需傳統架橋製程，大幅提升良率，除了改善光學特性外，具備極佳絕緣特性與耐高溫性，即使在ITO濺鍍的高溫製程下，仍保有高光穿透率優點。</span> \r\n</p>\r\n<b><span style="font-size:26px;line-height:2">水鑽石鍍膜：</span></b><br />\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">奈米級材料，具有抗菌 、抗藍光 、抗UV、抗刮、抗汙易潔、抗霧、抗電磁波、自潔、除臭等九大功能，勝過於價格昂貴的Sapphire藍寶石玻璃。</span> \r\n</p>\r\n<div align="center">\r\n<img src="/webroot/templates/index/img/ogs/ogs4_bg.png" width="400" height="303" alt="" align="center"/><br> \r\n</div><br>\r\n<b><span style="font-size:16px;line-height:1">註一：</span></b>\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">高階手機玻璃保護採用藍寶石Sapphire，只借助其表面硬度，但是它沒有富創得水鑽石的抗菌易潔….等功能。<br /></span> \r\n</p>\r\n<b><span style="font-size:16px;line-height:1">註二：</span></b>\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">Apple曾經意圖將藍寶石加在i Phone上，所以投資5.78億美元於美國GTAT藍寶石製造商上。<br /></span> \r\n</p>\r\n<b><span style="font-size:16px;line-height:1">註三：</span></b>\r\n<br />\r\n<span style="font-size:16px;line-height:1.5">由於藍寶石成本高昂、生產速率低、良率低、加工困難，根本無法支持i Phone手機的需求量。於日前Apple所投資的美國GTAT藍寶石製造商已宣告破產。</span> \r\n</p>\r\n\r\n</div>\r\n\r\n', '', 0);

-- --------------------------------------------------------

-- 
-- 資料表格式： `ogs_two`
-- 

CREATE TABLE `ogs_two` (
  `ogs_id` int(10) NOT NULL auto_increment,
  `ogs_title` varchar(500) collate utf8_unicode_ci default NULL,
  `ogs_content` longtext collate utf8_unicode_ci,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`ogs_id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=7 ;

-- 
-- 列出以下資料庫的數據： `ogs_two`
-- 

INSERT INTO `ogs_two` VALUES (1, '', '<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2;color: #0f0f75">1.生活上常出現的問題</span></b><br />\r\n<br />\r\n\r\n<b><span style="font-size:20px;line-height:2;color: #5c5cf5">ａ.細菌</span></b><br />\r\n<img style="float:right;margin:10px" src="/images/image/20141020/20141020001.png" width="150" height="150" alt="" align="center"/><br> \r\n</div>\r\n<div style="padding-left:10%;padding-right:10%">\r\n<span style="font-size:16px;line-height:1.5"><span style="font-size:18px;color: #3937FF; ">你知道每天使用的手機/平板電腦有多少細菌嗎?</span><br>\r\n一般馬桶座的金黃色葡萄球菌只有不到20個，但滑一次智慧型手機或平板電腦，就會沾上600個金黃色葡萄球菌（staphylococcus aureus），它會產生可導致上吐下瀉的毒素。Which也發現了像沙門氏桿菌（salmonella）與大腸桿菌（E. coli）等感染性細菌。<br>\r\n<span style="font-size:18px;color: #ff2424; ">「智慧型手機或平板電腦藏匿的細菌，竟然比馬桶座多30倍以上!!! 」</span></span><br />\r\n</div></div><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:20px;line-height:2;color: #5c5cf5">ｂ.藍光和UV光</span></b><br />\r\n<img style="float:left;margin:10px" src="/images/image/20141020/20141020002.png" width="150" height="150" alt="" align="center"/><br> \r\n</div>\r\n<div style="padding-left:10%;padding-right:10%">\r\n<span style="font-size:16px;line-height:1.5"> LCD是用白光LED做背光，LED白光是由藍光轉白光。所以會產生藍光和UV光，轟擊我們的視網膜、刺激視神經，世界各國眼科醫師證明，藍光易使眼睛起黃斑病變、紫外線則會造成白內障，易讓視力減退。 </span><br />\r\n</div><br><br><br><br><br><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:20px;line-height:2;color: #5c5cf5">ｃ.刮傷</span></b></div><br />\r\n<div style="padding-left:10%;padding-right:10%">\r\n<span style="font-size:16px;line-height:1.5">觸控螢幕已成為日常生活的人機介面，使用或存放的時候，容易與硬物互相摩擦而刮傷，如戒指等硬物。</span><br />\r\n</div><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:20px;line-height:2;color: #5c5cf5">ｄ.髒污及霧氣</span></b><br />\r\n<img style="float:right;margin:10px" src="/images/image/20141020/20141020003.png" width="150" height="150" alt="" align="center"/><br> \r\n</div>\r\n<div style="padding-left:10%;padding-right:10%">\r\n<span style="font-size:16px;line-height:1.5">大氣中的有機物、無機物、灰塵和人的指紋容易沾污在觸控面板上；同時空氣中的水氣，會在觸控面板表面形成霧氣。</span><br />\r\n</div><br><br><br><br><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:20px;line-height:2;color: #5c5cf5">ｅ.電磁波</span></b></div><br />\r\n<div style="padding-left:10%;padding-right:10%">\r\n<span style="font-size:16px;line-height:1.5">眾所皆知，電子產品的電磁波干擾，一直是刻不容緩急需解決的課題。</span><br />\r\n</div><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:20px;line-height:2">富創得科技為了解決在生活中所遭遇的各種問題，研發出</span></b><span style="font-size:16px;line-height:1.5">一安定性高的水性奈米溶膠溶液-水鑽石，其奈米粒徑≦5nm，完全不含其它添加劑，如：Binder、分散劑、塑劑等。經噴塗、烘烤燒結後 ，在基材表面形成水鑽石無機膜，表面光亮、易潔、自潔、抗菌、抗UV、抗藍光、抗刮、抗污、抗電磁波等功能。</span><br />\r\n</div><br>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2;color: #0f0f75">2.水鑽石功能</span></b><br />\r\n<br />\r\n<img src="/images/image/20141020/20141020004.png" width="581" height="362" alt="" align="center"/><br>\r\n<img src="/images/image/20141020/20141020005.png" width="581" height="362" alt="" align="center"/><br>  \r\n</div>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2;color: #0f0f75">3.富創得產品特性如下</span></b><br />\r\n<br />\r\n<img src="/images/image/20141020/20141020006.png" width="800" height="400" alt="" align="center"/><br>\r\n<span style="font-size:16px;line-height:2;color: #FA0300">註：水鑽石不斷氧化還原，所以是永久性</span>\r\n</div>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<b><span style="font-size:30px;line-height:2;color: #0f0f75">4.水鑽石應用</span></b><br />\r\n<br />\r\n<img src="/images/image/20141020/20141020007.png" width="800" height="550" alt="" align="center"/><br> \r\n</div>\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n\r\n<b><span style="font-size:30px;line-height:2;color: #0f0f75">5.產業應用</span></b><br />\r\n<br />\r\n<div align="center">\r\n<img src="/images/image/20141020/20141020009.png" width="800" height="400" alt="" /><br> \r\n', 1);

-- --------------------------------------------------------

-- 
-- 資料表格式： `prod_aio`
-- 

CREATE TABLE `prod_aio` (
  `aio_id` int(20) NOT NULL,
  `aio_img` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_explan` longtext collate utf8_unicode_ci NOT NULL,
  `aio_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_size` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_outline` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_active` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_glass` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_interface` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_os` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_pcb` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_win8` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_green` varchar(500) collate utf8_unicode_ci NOT NULL,
  `aio_main` varchar(500) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`aio_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `prod_aio`
-- 

INSERT INTO `prod_aio` VALUES (1, '', '', '<div style="margin-top:-5%">\r\n<div style="padding-left:15%">\r\n\r\n<p style="font-size:20px;line-height:3.5">\r\n<b>富創得Liquid Diamond水鑽石膜的優勢：</b>\r\n</p>\r\n</div>\r\n<div style="font-size:18px;padding-left:25%;line-height:1.5">\r\n<p>＊	富創得水鑽石有高硬度、抑菌、自潔、易潔、除臭功能。</p>\r\n<p>＊	富創得水鑽石特性經過SGS、食品檢驗局的正式驗證。</p>\r\n<p>＊	富創得所提供生產設備有大量生產的能力。</p>\r\n<p>＊	富創得水鑽石膜的性價比高，對產品的附加價值大。</p>\r\n<p>＊	大面積尺寸製作易，面對市場需求反應快。</p>\r\n</div>\r\n<p style="padding-left:15%;font-size:20px;line-height:3"><b>* 請參看Website產品介紹</b></p>\r\n\r\n<p style="padding-left:28%">\r\n	<img src="/images/image/20140820/20140820020012_95558.png" width="400" height="317" alt="" />\r\n</p>\r\n\r\n<p style="font-size:20px;padding-left:15%;line-height:3.5">\r\n<b>為何選擇富創得Liquid Diamond水鑽石整廠生產設備？</b>\r\n</p>\r\n\r\n<div style="font-size:18px;padding-left:25%;line-height:1.5">\r\n<p>˙ 富創得在水鑽石膜製作上有多年經驗。</p>\r\n<p>˙ 富創得提供水鑽石液材料與技術。 </p>\r\n<p>˙ 富創得提供生產設備。</p>\r\n<p>˙ 富創得為合作夥伴提供完整的教育訓練。</p>\r\n<p>˙ 富創得繼續提供合作夥伴後續新研發的產品與技術。</p>\r\n</div>\r\n<p style="padding-left:25%;padding-top:50px;padding-bottom:50px">\r\n	<img src="/images/image/20140820/20140820020158_11098.png" width="500" height="282" alt="" />\r\n</p>\r\n\r\n<div style="padding-left:20%;line-height:1.5">\r\n<b>\r\n<p>台灣新北市林口區工四路20號</p>\r\n<p>   TEL :  +886-2-26015678</p>\r\n<p>   FAX :  +886-2-26013075</p>\r\n<p>   service@touchpanelpro.com</p></b>\r\n</div>\r\n</div>', '1', '3', '1', '1', '1', '1', '1', '0', '0', '0', '0');
INSERT INTO `prod_aio` VALUES (2, '', '', '<div align="center">\r\n	<a href="./templates/index/img/packeg/20140820_LDOP.ppt" target="_blank"><img src="./templates/index/img/packeg/20140820_LDOP.png" /> </a> \r\n</div>', '1', '3', '1', '1', '1', '1', '1', '0', '0', '0', '0');

-- --------------------------------------------------------

-- 
-- 資料表格式： `prod_ipc`
-- 

CREATE TABLE `prod_ipc` (
  `ipc_id` int(20) NOT NULL,
  `ipc_img` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_explan` longtext collate utf8_unicode_ci NOT NULL,
  `ipc_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_size` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_outline` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_active` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_glass` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_interface` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_os` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_pcb` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_win8` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_green` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ipc_main` varchar(500) collate utf8_unicode_ci NOT NULL,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`ipc_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `prod_ipc`
-- 

INSERT INTO `prod_ipc` VALUES (2, '', '', '<div style="margin-top:-5%">\r\n<div style="padding-left:20%">\r\n\r\n<p style="font-size:20px;line-height:3.5">\r\n<b>富創得OGS投射式電容觸控面板的優勢：</b>\r\n</p>\r\n</div>\r\n<div style="font-size:18px;padding-left:28%;line-height:1.5">\r\n<p>＊	單片式投線	六面化強，無氫氟酸二次強化問題</p>\r\n<p>＊	富創得專利	疊構無架橋，高良率 + 高產率</p>\r\n<p>＊	產品特性	報點精準、反應速度快，作業壽命長</p>\r\n<p>＊	生產成本	有強競爭力，越是大尺寸越有優勢</p>\r\n<p>＊	研發速度	新尺寸製作易，面對市場需求反應快</p>\r\n</div>\r\n<p style="padding-left:20%;font-size:20px;line-height:3"><b>* 請參看Website產品介紹</b></p>\r\n\r\n<p style="padding-left:28%">\r\n	<img src="/images/image/20140818/20140818040106_60809.png" width="400" height="264" alt="" style="padding-top:40px;padding-bottom:50px"/> \r\n</p>\r\n\r\n<p style="font-size:20px;padding-left:20%;line-height:3.5">\r\n<b>為何選擇富創得OGS整廠生產設備？</b>\r\n</p>\r\n\r\n<div style="font-size:18px;padding-left:25%;line-height:1.5">\r\n<p>˙ 富創得有完整的研發團隊、在投射電容觸控面板的研發經驗豐富。</p>\r\n<p>˙ 富創得有一系列的專利，涵蓋了OGS疊構設計、製程等等範疇。</p>\r\n<p>˙ 富創得為合作夥伴提供完整的教育訓練。</p>\r\n<p>˙ 富創得團隊提供軟體、韌體及硬體的全套技術規劃。</p>\r\n<p>˙ 富創得能支援到最新的觸控面板控制IC方案。</p>\r\n<p>˙ 富創得繼續提供合作夥伴後續新研發的產品與技術。</p>\r\n</div>\r\n<p style="padding-left:25%">\r\n	<img src="/images/image/20140818/20140818061351_76621.png" width="500" height="282" alt="" style="padding-top:50px;padding-bottom:50px"/> \r\n</p>\r\n\r\n<div style="padding-left:20%;line-height:1.5">\r\n<b>\r\n<p>台灣新北市林口區工四路20號</p>\r\n<p>   TEL :  +886-2-26015678</p>\r\n<p>   FAX :  +886-2-26013075</p>\r\n<p>   service@touchpanelpro.com</p></b>\r\n</div>\r\n</div>', '', '', '', '', '', '', '', '0', '0', '0', '0', 0);
INSERT INTO `prod_ipc` VALUES (3, '', '', '<div align="center">\r\n	<a href="./templates/index/img/packeg/20140327_303.pdf" target="_blank"> <img src="./templates/index/img/packeg/20140327_303.png" align="middle" /> </a> \r\n</div>', '', '', '', '', '', '', '', '0', '0', '0', '0', 0);

-- --------------------------------------------------------

-- 
-- 資料表格式： `prod_monitor`
-- 

CREATE TABLE `prod_monitor` (
  `monitor_id` int(20) NOT NULL,
  `monitor_img` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_explan` longtext collate utf8_unicode_ci NOT NULL,
  `monitor_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_size` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_outline` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_active` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_glass` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_interface` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_os` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_pcb` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_win8` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_green` varchar(500) collate utf8_unicode_ci NOT NULL,
  `monitor_main` varchar(500) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`monitor_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `prod_monitor`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `prod_tablet`
-- 

CREATE TABLE `prod_tablet` (
  `tablet_id` int(20) NOT NULL,
  `tablet_img` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_file` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_explan` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_model` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_size` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_outline` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_active` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_glass` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_interface` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_os` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_pcb` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_win8` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_green` longtext collate utf8_unicode_ci NOT NULL,
  `tablet_main` longtext collate utf8_unicode_ci NOT NULL,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`tablet_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `prod_tablet`
-- 

INSERT INTO `prod_tablet` VALUES (3, '', '', '<img src="/images/image/20141110/2014111001154.png" width="240" height="150" alt="" />\r\n<img src="/images/image/20141110/2014111001155.png" width="240" height="150" alt="" />\r\n<img src="/images/image/20141110/2014111001156.png" width="240" height="150" alt="" />\r\n<img src="/images/image/20141110/2014111001157.png" width="240" height="150" alt="" />\r\n\r\n\r\n\r\n<div style="padding-left:10%;padding-right:10%">\r\n<br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 3C家電產品:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">ITE產品、電腦、手機、平板、筆記型電腦、AIO</span><br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 傢電用品:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">空氣清淨機、冷暖氣空調機、除濕機、電風扇</span><br><br>\r\n\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 生活用品:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">室內照明燈、燈罩、燈管</span><br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 衛浴設備:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">浴盆、馬桶、浴缸、浴室扶手、浴室磁磚</span><br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 建築材料:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">隔音牆、隧道壁、房子外面牆壁、建築玻璃、玻璃帷幕</span><br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 交通號誌:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">路燈、紅綠燈</span><br><br>\r\n\r\n<span style="font-size:28px;line-height:1;color: #D20000"><b> 醫療用品:</b></span><br>\r\n<span style="font-size:20px;line-height:2;color: ">口罩、手套、手術器材、無菌衣</span><br><br>\r\n</div>', '', '', '', '', '', '', '', '', '', '', '0', 1);

-- --------------------------------------------------------

-- 
-- 資料表格式： `prod_ultra`
-- 

CREATE TABLE `prod_ultra` (
  `ultra_id` int(20) NOT NULL,
  `ultra_img` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_file` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_explan` longtext collate utf8_unicode_ci NOT NULL,
  `ultra_model` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_size` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_outline` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_active` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_glass` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_interface` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_os` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_pcb` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_win8` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_green` varchar(500) collate utf8_unicode_ci NOT NULL,
  `ultra_main` varchar(500) collate utf8_unicode_ci NOT NULL,
  `sortnum` int(11) default '1',
  PRIMARY KEY  (`ultra_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `prod_ultra`
-- 

INSERT INTO `prod_ultra` VALUES (2, '', '', '<p style="text-align:center;">\r\n	<img src="/images/image/20140409/20140409100158_39487.jpg" alt="" /> \r\n</p>\r\n<p style="text-align:center;">\r\n	<strong><b><span><br />\r\n</span></b></strong> \r\n</p>\r\n<p style="text-align:center;">\r\n	<strong><b><span>富創得秉持精益求精的態度，持續研發、提高生產良率及擴大產能已以達成客戶需求。</span></b></strong> \r\n</p>\r\n<p style="text-align:center;">\r\n	<br />\r\n</p>\r\n<p class="MsoNormal" style="text-align:center;">\r\n	<strong><b><span>富創得為客戶提供</span><span>OGS(One Glass Solution) 1.5</span></b></strong><strong><b><span>吋至</span><span>27</span></b></strong><strong><b><span>吋各種大小尺寸觸控面板；</span></b></strong> \r\n</p>\r\n<p class="MsoNormal" style="text-align:center;">\r\n	<strong><b><span><br />\r\n</span></b></strong>\r\n</p>\r\n<p class="MsoNormal" style="text-align:center;">\r\n	<strong><b><span>專業的研發團隊也能協助配合開發不同尺寸的客製化需求。</span></b></strong><span></span> \r\n</p>\r\n<p class="MsoNormal" style="text-align:center;">\r\n	<strong><b><span><br />\r\n</span></b></strong>\r\n</p>\r\n<p class="MsoNormal" style="text-align:center;"', '', '', '', '', '', '', '', '0', '0', '0', '0', 1);

-- --------------------------------------------------------

-- 
-- 資料表格式： `product_intro`
-- 

CREATE TABLE `product_intro` (
  `id` int(11) NOT NULL auto_increment,
  `ptitle` varchar(500) default NULL,
  `pname` varchar(50) default NULL,
  `intro1` varchar(500) default NULL,
  `intro2` varchar(500) default NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 AUTO_INCREMENT=6 ;

-- 
-- 列出以下資料庫的數據： `product_intro`
-- 

INSERT INTO `product_intro` VALUES (1, '攜帶性應用系列', 'tablet', '<ul>\r\n<li><span>*</span>快速反應</li>\r\n<li><span>*</span>精準定位</li>\r\n<li><span>*</span>直覺性操作</li>\r\n</ul>', '<p>\r\n"輕薄短小"!這是消費者心<br/>中的真實想法，投射式電容觸控<br/>解決方案可立即滿足這個慾望，因\r\n<br/>\r\n未攜帶型電子商品再也不需要鍵盤與滑鼠了!<br/>富創得攜帶式應用系列觸控面板讓觸控電子商品<br/>擁有更自由的ID產品設計想像空間。\r\n</p>');
INSERT INTO `product_intro` VALUES (2, '', 'aio', '<ul>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n</ul>', '<p>請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字</p>');
INSERT INTO `product_intro` VALUES (3, 'test應用', 'ipc', '<ul>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n</ul>', '<p>請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字</p>');
INSERT INTO `product_intro` VALUES (4, '', 'monitor', '<ul>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n</ul>', '<p>請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字</p>');
INSERT INTO `product_intro` VALUES (5, '', 'ultra', '<ul>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n<li><span>*</span>請輸入文字</li>\r\n</ul>', '<p>請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字<br/>\r\n請輸入文字</p>');

-- --------------------------------------------------------

-- 
-- 資料表格式： `quality_info`
-- 

CREATE TABLE `quality_info` (
  `id` int(11) NOT NULL,
  `content` varchar(1000) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `quality_info`
-- 

INSERT INTO `quality_info` VALUES (1, '<ul>\r\n	<li class="p10 fb" style="font-size:15px;font-weight:600;">\r\n		富創得科技精益求精，訴求嚴格的品質把關，精心規劃製作生產程序， 符合各項品質管理標準。目標是生產高品質、低成本的觸控產品，嚴謹 的監管工作與彈性的問題解決能力是我們達成『效率與品質』的關鍵。\r\n	</li>\r\n	<li class="p10 fb" style="font-size:15px;font-weight:600;">\r\n		從供應商管理、生產品質管理一直到售後服務管理，富創得科技層層進 行監督、稽核與改善。我們的承諾是要確保客戶的滿意度，提供最新穎 的觸控技術、最嚴謹的客戶服務以及最領先的市場優勢。\r\n	</li>\r\n<li class="p10 fb" style="font-size:15px;font-weight:600;">\r\n		對於無有害物質原材料，環境友善的生產作業製程控管；富創得都符合ISO-14000與QC-080000的標準，取得了TUV審驗的合格證明。\r\n	</li>\r\n</ul>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<img alt="" src="\\webroot\\templates\\index\\img\\qual\\quality.png" style="width:492px;height:269px;" />\r\n</p>\r\n<p>\r\n	<br />\r\n</p>');

-- --------------------------------------------------------

-- 
-- 資料表格式： `recruit_art`
-- 

CREATE TABLE `recruit_art` (
  `id` int(11) NOT NULL,
  `content` varchar(8000) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `recruit_art`
-- 

INSERT INTO `recruit_art` VALUES (1, '<p>\r\n	<b><span style="color:#008080;font-size:22px;">如果您..</span></b> \r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<b><span style="color:#008080;font-size:22px;">有熱情、有活力</span></b> \r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<b><span style="color:#008080;font-size:22px;">有夢想、有創意</span></b> \r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<b><span style="color:#008080;font-size:22px;">有企圖、具拼勁</span></b> \r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<b><span style="color:#008080;font-size:22px;">歡迎志同道合的您</span></b> \r\n</p>\r\n<p>\r\n	<br />\r\n</p>\r\n<p>\r\n	<b><span style="color:#008080;font-size:22px;">加入我們的團隊..</span></b> \r\n</p>');

-- --------------------------------------------------------

-- 
-- 資料表格式： `recruit_welfare`
-- 

CREATE TABLE `recruit_welfare` (
  `id` int(11) NOT NULL,
  `welfare` varchar(1000) collate utf8_unicode_ci NOT NULL,
  `slogan` varchar(1000) collate utf8_unicode_ci NOT NULL,
  `web` varchar(1000) collate utf8_unicode_ci NOT NULL,
  `web_link` varchar(1000) collate utf8_unicode_ci NOT NULL,
  `warning` varchar(1000) collate utf8_unicode_ci NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

-- 
-- 列出以下資料庫的數據： `recruit_welfare`
-- 

INSERT INTO `recruit_welfare` VALUES (1, '週休二日/特休年假/員工停車位/勞健保/生育津貼/年終獎金...等多項福利', '歡迎優秀朋友一起加入富創得科技股份有限公司的工作行列', '...富創得科技104人力銀行 招募網頁...', 'http://www.104.com.tw/jobbank/custjob/index.php?r=cust&j=3c7042255a6c3e2030683b1d1d1d1d5f2443a363189j99&jobsource=checkc', '禁用童工:員工聘僱政策中明確宣示禁用童工及任何可能造成雇用童工的行為皆不被允許');

-- --------------------------------------------------------

-- 
-- 資料表格式： `roadmap_info`
-- 

CREATE TABLE `roadmap_info` (
  `id` int(11) NOT NULL auto_increment,
  `c_subject` varchar(200) character set utf8 collate utf8_unicode_ci NOT NULL,
  `e_subject` varchar(200) character set utf8 collate utf8_unicode_ci NOT NULL,
  `content` text NOT NULL,
  `years` varchar(20) character set utf8 collate utf8_unicode_ci NOT NULL,
  `wtime` int(11) NOT NULL,
  `catid` int(11) NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 AUTO_INCREMENT=4 ;

-- 
-- 列出以下資料庫的數據： `roadmap_info`
-- 

INSERT INTO `roadmap_info` VALUES (1, '水鑽石', 'Liquid Diamond', '<p>\r\n	水鑽石是富創得所研發的復合材，為一安定性高的水性奈米溶膠溶液，水鑽石奈米粒徑≦5nm，完全不含其它添加劑，如：Binder、分散劑、塑劑等。水鑽石經照光後被激發形成之電子電洞對，將附近分子(H<sub>2</sub>O、O<sub>2</sub>)游離形成正、負離子或自由基(OH<sup>-</sup>、OH*…)。\r\n</p>\r\n<br />\r\n<p>\r\n	&nbsp;&nbsp;&nbsp;&nbsp;	水鑽石 + hv → h<sup>+</sup> + e<sup>-</sup> \r\n</p>\r\n<p>\r\n	&nbsp;&nbsp;&nbsp;&nbsp;	OH<sup>-</sup> + h<sup>+</sup> → OH*\r\n</p>\r\n<p>\r\n	&nbsp;&nbsp;&nbsp;&nbsp;	O<sub>2ads</sub> + e<sup>-</sup> → O<sub>2<sup>-</sup>ads</sub> \r\n</p>\r\n<br />\r\n<p>\r\n	污染物質遇上氫氧自由基即被分解，形成中間產物，或是無害的水及二氧化碳，因此可以達到除污及滅菌的目標。\r\n</p>\r\n<br />\r\n<p>\r\n	&nbsp;&nbsp;&nbsp;&nbsp;	OH* + pollutant + O<sub>2</sub>→ products (CO<sub>2</sub>, H<sub>2</sub>O...)\r\n</p>\r\n<br />\r\n<p>\r\n	水鑽石經噴塗、烘烤燒結後 ，在基材表面形成水鑽石無機膜，表面光亮且具有抑菌、抗UV、抗刮、除汙/霧、防電磁波等五大功能。\r\n</p>', '2013', 0, 2013);
INSERT INTO `roadmap_info` VALUES (2, '藍寶石', 'Coating', '藍寶石Coating在OGS上，硬度達9H可抗刮、過濾紫外線。\r\n永久性水滴接觸角85度可抗汙易潔。<br>\r\n外面有人用AS含氟，水滴接觸角在沒陽光底下100~115度僅能撐2週、85~100度\r\n僅能維持1個月，3個月後就不再有抗汙功能了。', '2014', 0, 2014);
INSERT INTO `roadmap_info` VALUES (3, 'OGS ', 'Research', '富創得的OGS TP在研發後已經量產2年多，\r\n技術、材料及設備成熟完備。\r\n', '2015', 0, 2015);
-- 
-- 資料庫: `mysql`
-- 
CREATE DATABASE `mysql` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
USE `mysql`;

-- --------------------------------------------------------

-- 
-- 資料表格式： `columns_priv`
-- 

CREATE TABLE `columns_priv` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `Db` char(64) collate utf8_bin NOT NULL default '',
  `User` char(16) collate utf8_bin NOT NULL default '',
  `Table_name` char(64) collate utf8_bin NOT NULL default '',
  `Column_name` char(64) collate utf8_bin NOT NULL default '',
  `Timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',
  PRIMARY KEY  (`Host`,`Db`,`User`,`Table_name`,`Column_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Column privileges';

-- 
-- 列出以下資料庫的數據： `columns_priv`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `db`
-- 

CREATE TABLE `db` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `Db` char(64) collate utf8_bin NOT NULL default '',
  `User` char(16) collate utf8_bin NOT NULL default '',
  `Select_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Insert_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Update_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Delete_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Drop_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Grant_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `References_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Index_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_tmp_table_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Lock_tables_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Show_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Execute_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  PRIMARY KEY  (`Host`,`Db`,`User`),
  KEY `User` (`User`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Database privileges';

-- 
-- 列出以下資料庫的數據： `db`
-- 

INSERT INTO `db` VALUES (0x25, 0x74657374, '', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'N', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'N', 'N');
INSERT INTO `db` VALUES (0x25, 0x746573745c5f25, '', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'N', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'N', 'N');

-- --------------------------------------------------------

-- 
-- 資料表格式： `func`
-- 

CREATE TABLE `func` (
  `name` char(64) collate utf8_bin NOT NULL default '',
  `ret` tinyint(1) NOT NULL default '0',
  `dl` char(128) collate utf8_bin NOT NULL default '',
  `type` enum('function','aggregate') character set utf8 NOT NULL,
  PRIMARY KEY  (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='User defined functions';

-- 
-- 列出以下資料庫的數據： `func`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `help_category`
-- 

CREATE TABLE `help_category` (
  `help_category_id` smallint(5) unsigned NOT NULL,
  `name` char(64) NOT NULL,
  `parent_category_id` smallint(5) unsigned default NULL,
  `url` char(128) NOT NULL,
  PRIMARY KEY  (`help_category_id`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='help categories';

-- 
-- 列出以下資料庫的數據： `help_category`
-- 

INSERT INTO `help_category` VALUES (1, 'Geographic', 0, '');
INSERT INTO `help_category` VALUES (2, 'Polygon properties', 30, '');
INSERT INTO `help_category` VALUES (3, 'WKT', 30, '');
INSERT INTO `help_category` VALUES (4, 'Numeric Functions', 34, '');
INSERT INTO `help_category` VALUES (5, 'MBR', 30, '');
INSERT INTO `help_category` VALUES (6, 'Control flow functions', 34, '');
INSERT INTO `help_category` VALUES (7, 'Transactions', 31, '');
INSERT INTO `help_category` VALUES (8, 'Account Management', 31, '');
INSERT INTO `help_category` VALUES (9, 'Point properties', 30, '');
INSERT INTO `help_category` VALUES (10, 'Encryption Functions', 34, '');
INSERT INTO `help_category` VALUES (11, 'LineString properties', 30, '');
INSERT INTO `help_category` VALUES (12, 'Logical operators', 34, '');
INSERT INTO `help_category` VALUES (13, 'Miscellaneous Functions', 34, '');
INSERT INTO `help_category` VALUES (14, 'Functions and Modifiers for Use with GROUP BY', 31, '');
INSERT INTO `help_category` VALUES (15, 'Information Functions', 34, '');
INSERT INTO `help_category` VALUES (16, 'Storage Engines', 31, '');
INSERT INTO `help_category` VALUES (17, 'Comparison operators', 34, '');
INSERT INTO `help_category` VALUES (18, 'Bit Functions', 34, '');
INSERT INTO `help_category` VALUES (19, 'Table Maintenance', 31, '');
INSERT INTO `help_category` VALUES (20, 'Data Types', 31, '');
INSERT INTO `help_category` VALUES (21, 'Triggers', 31, '');
INSERT INTO `help_category` VALUES (22, 'Geometry constructors', 30, '');
INSERT INTO `help_category` VALUES (23, 'GeometryCollection properties', 1, '');
INSERT INTO `help_category` VALUES (24, 'Administration', 31, '');
INSERT INTO `help_category` VALUES (25, 'Data Manipulation', 31, '');
INSERT INTO `help_category` VALUES (26, 'Geometry relations', 30, '');
INSERT INTO `help_category` VALUES (27, 'Language Structure', 31, '');
INSERT INTO `help_category` VALUES (28, 'Date and Time Functions', 34, '');
INSERT INTO `help_category` VALUES (29, 'WKB', 30, '');
INSERT INTO `help_category` VALUES (30, 'Geographic Features', 31, '');
INSERT INTO `help_category` VALUES (31, 'Contents', 0, '');
INSERT INTO `help_category` VALUES (32, 'Geometry properties', 30, '');
INSERT INTO `help_category` VALUES (33, 'String Functions', 34, '');
INSERT INTO `help_category` VALUES (34, 'Functions', 31, '');
INSERT INTO `help_category` VALUES (35, 'Stored Routines', 31, '');
INSERT INTO `help_category` VALUES (36, 'Data Definition', 31, '');

-- --------------------------------------------------------

-- 
-- 資料表格式： `help_keyword`
-- 

CREATE TABLE `help_keyword` (
  `help_keyword_id` int(10) unsigned NOT NULL,
  `name` char(64) NOT NULL,
  PRIMARY KEY  (`help_keyword_id`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='help keywords';

-- 
-- 列出以下資料庫的數據： `help_keyword`
-- 

INSERT INTO `help_keyword` VALUES (0, 'JOIN');
INSERT INTO `help_keyword` VALUES (1, 'REPEAT');
INSERT INTO `help_keyword` VALUES (2, 'SERIALIZABLE');
INSERT INTO `help_keyword` VALUES (3, 'REPLACE');
INSERT INTO `help_keyword` VALUES (4, 'RETURNS');
INSERT INTO `help_keyword` VALUES (5, 'MASTER_SSL_CA');
INSERT INTO `help_keyword` VALUES (6, 'NCHAR');
INSERT INTO `help_keyword` VALUES (7, 'COLUMNS');
INSERT INTO `help_keyword` VALUES (8, 'WORK');
INSERT INTO `help_keyword` VALUES (9, 'DATETIME');
INSERT INTO `help_keyword` VALUES (10, 'MODE');
INSERT INTO `help_keyword` VALUES (11, 'OPEN');
INSERT INTO `help_keyword` VALUES (12, 'INTEGER');
INSERT INTO `help_keyword` VALUES (13, 'ESCAPE');
INSERT INTO `help_keyword` VALUES (14, 'VALUE');
INSERT INTO `help_keyword` VALUES (15, 'GEOMETRYCOLLECTIONFROMWKB');
INSERT INTO `help_keyword` VALUES (16, 'SQL_BIG_RESULT');
INSERT INTO `help_keyword` VALUES (17, 'DROP');
INSERT INTO `help_keyword` VALUES (18, 'EVENTS');
INSERT INTO `help_keyword` VALUES (19, 'MONTH');
INSERT INTO `help_keyword` VALUES (20, 'INFO');
INSERT INTO `help_keyword` VALUES (21, 'PROFILES');
INSERT INTO `help_keyword` VALUES (22, 'DUPLICATE');
INSERT INTO `help_keyword` VALUES (23, 'REPLICATION');
INSERT INTO `help_keyword` VALUES (24, 'INNODB');
INSERT INTO `help_keyword` VALUES (25, 'YEAR_MONTH');
INSERT INTO `help_keyword` VALUES (26, 'SUBJECT');
INSERT INTO `help_keyword` VALUES (27, 'PREPARE');
INSERT INTO `help_keyword` VALUES (28, 'LOCK');
INSERT INTO `help_keyword` VALUES (29, 'NDB');
INSERT INTO `help_keyword` VALUES (30, 'CHECK');
INSERT INTO `help_keyword` VALUES (31, 'FULL');
INSERT INTO `help_keyword` VALUES (32, 'INT4');
INSERT INTO `help_keyword` VALUES (33, 'BY');
INSERT INTO `help_keyword` VALUES (34, 'NO');
INSERT INTO `help_keyword` VALUES (35, 'MINUTE');
INSERT INTO `help_keyword` VALUES (36, 'DATA');
INSERT INTO `help_keyword` VALUES (37, 'DAY');
INSERT INTO `help_keyword` VALUES (38, 'SHARE');
INSERT INTO `help_keyword` VALUES (39, 'REAL');
INSERT INTO `help_keyword` VALUES (40, 'SEPARATOR');
INSERT INTO `help_keyword` VALUES (41, 'DELETE');
INSERT INTO `help_keyword` VALUES (42, 'ON');
INSERT INTO `help_keyword` VALUES (43, 'CONNECTION');
INSERT INTO `help_keyword` VALUES (44, 'CLOSE');
INSERT INTO `help_keyword` VALUES (45, 'X509');
INSERT INTO `help_keyword` VALUES (46, 'USE');
INSERT INTO `help_keyword` VALUES (47, 'WHERE');
INSERT INTO `help_keyword` VALUES (48, 'PRIVILEGES');
INSERT INTO `help_keyword` VALUES (49, 'SPATIAL');
INSERT INTO `help_keyword` VALUES (50, 'SUPER');
INSERT INTO `help_keyword` VALUES (51, 'SQL_BUFFER_RESULT');
INSERT INTO `help_keyword` VALUES (52, 'IGNORE');
INSERT INTO `help_keyword` VALUES (53, 'QUICK');
INSERT INTO `help_keyword` VALUES (54, 'SIGNED');
INSERT INTO `help_keyword` VALUES (55, 'SECURITY');
INSERT INTO `help_keyword` VALUES (56, 'POLYGONFROMWKB');
INSERT INTO `help_keyword` VALUES (57, 'NDBCLUSTER');
INSERT INTO `help_keyword` VALUES (58, 'FALSE');
INSERT INTO `help_keyword` VALUES (59, 'LEVEL');
INSERT INTO `help_keyword` VALUES (60, 'FORCE');
INSERT INTO `help_keyword` VALUES (61, 'BINARY');
INSERT INTO `help_keyword` VALUES (62, 'TO');
INSERT INTO `help_keyword` VALUES (63, 'CHANGE');
INSERT INTO `help_keyword` VALUES (64, 'HOUR_MINUTE');
INSERT INTO `help_keyword` VALUES (65, 'UPDATE');
INSERT INTO `help_keyword` VALUES (66, 'INTO');
INSERT INTO `help_keyword` VALUES (67, 'FEDERATED');
INSERT INTO `help_keyword` VALUES (68, 'VARYING');
INSERT INTO `help_keyword` VALUES (69, 'HOUR_SECOND');
INSERT INTO `help_keyword` VALUES (70, 'VARIABLE');
INSERT INTO `help_keyword` VALUES (71, 'ROLLBACK');
INSERT INTO `help_keyword` VALUES (72, 'PROCEDURE');
INSERT INTO `help_keyword` VALUES (73, 'RTREE');
INSERT INTO `help_keyword` VALUES (74, 'TIMESTAMP');
INSERT INTO `help_keyword` VALUES (75, 'IMPORT');
INSERT INTO `help_keyword` VALUES (76, 'AGAINST');
INSERT INTO `help_keyword` VALUES (77, 'CHECKSUM');
INSERT INTO `help_keyword` VALUES (78, 'COUNT');
INSERT INTO `help_keyword` VALUES (79, 'LONGBINARY');
INSERT INTO `help_keyword` VALUES (80, 'THEN');
INSERT INTO `help_keyword` VALUES (81, 'INSERT');
INSERT INTO `help_keyword` VALUES (82, 'ENGINES');
INSERT INTO `help_keyword` VALUES (83, 'HANDLER');
INSERT INTO `help_keyword` VALUES (84, 'DAY_SECOND');
INSERT INTO `help_keyword` VALUES (85, 'EXISTS');
INSERT INTO `help_keyword` VALUES (86, 'MUTEX');
INSERT INTO `help_keyword` VALUES (87, 'RELEASE');
INSERT INTO `help_keyword` VALUES (88, 'BOOLEAN');
INSERT INTO `help_keyword` VALUES (89, 'MOD');
INSERT INTO `help_keyword` VALUES (90, 'DEFAULT');
INSERT INTO `help_keyword` VALUES (91, 'TYPE');
INSERT INTO `help_keyword` VALUES (92, 'NO_WRITE_TO_BINLOG');
INSERT INTO `help_keyword` VALUES (93, 'OPTIMIZE');
INSERT INTO `help_keyword` VALUES (94, 'RESET');
INSERT INTO `help_keyword` VALUES (95, 'ITERATE');
INSERT INTO `help_keyword` VALUES (96, 'DO');
INSERT INTO `help_keyword` VALUES (97, 'BIGINT');
INSERT INTO `help_keyword` VALUES (98, 'SET');
INSERT INTO `help_keyword` VALUES (99, 'ISSUER');
INSERT INTO `help_keyword` VALUES (100, 'DATE');
INSERT INTO `help_keyword` VALUES (101, 'STATUS');
INSERT INTO `help_keyword` VALUES (102, 'FULLTEXT');
INSERT INTO `help_keyword` VALUES (103, 'COMMENT');
INSERT INTO `help_keyword` VALUES (104, 'MASTER_CONNECT_RETRY');
INSERT INTO `help_keyword` VALUES (105, 'INNER');
INSERT INTO `help_keyword` VALUES (106, 'STOP');
INSERT INTO `help_keyword` VALUES (107, 'MASTER_LOG_FILE');
INSERT INTO `help_keyword` VALUES (108, 'MRG_MYISAM');
INSERT INTO `help_keyword` VALUES (109, 'PRECISION');
INSERT INTO `help_keyword` VALUES (110, 'REQUIRE');
INSERT INTO `help_keyword` VALUES (111, 'TRAILING');
INSERT INTO `help_keyword` VALUES (112, 'LONG');
INSERT INTO `help_keyword` VALUES (113, 'OPTION');
INSERT INTO `help_keyword` VALUES (114, 'ELSE');
INSERT INTO `help_keyword` VALUES (115, 'DEALLOCATE');
INSERT INTO `help_keyword` VALUES (116, 'IO_THREAD');
INSERT INTO `help_keyword` VALUES (117, 'CASE');
INSERT INTO `help_keyword` VALUES (118, 'CIPHER');
INSERT INTO `help_keyword` VALUES (119, 'CONTINUE');
INSERT INTO `help_keyword` VALUES (120, 'FROM');
INSERT INTO `help_keyword` VALUES (121, 'READ');
INSERT INTO `help_keyword` VALUES (122, 'LEFT');
INSERT INTO `help_keyword` VALUES (123, 'ELSEIF');
INSERT INTO `help_keyword` VALUES (124, 'MINUTE_SECOND');
INSERT INTO `help_keyword` VALUES (125, 'COMPACT');
INSERT INTO `help_keyword` VALUES (126, 'RESTORE');
INSERT INTO `help_keyword` VALUES (127, 'DEC');
INSERT INTO `help_keyword` VALUES (128, 'FOR');
INSERT INTO `help_keyword` VALUES (129, 'WARNINGS');
INSERT INTO `help_keyword` VALUES (130, 'MIN_ROWS');
INSERT INTO `help_keyword` VALUES (131, 'STRING');
INSERT INTO `help_keyword` VALUES (132, 'CONDITION');
INSERT INTO `help_keyword` VALUES (133, 'FUNCTION');
INSERT INTO `help_keyword` VALUES (134, 'ENCLOSED');
INSERT INTO `help_keyword` VALUES (135, 'AGGREGATE');
INSERT INTO `help_keyword` VALUES (136, 'FIELDS');
INSERT INTO `help_keyword` VALUES (137, 'INT3');
INSERT INTO `help_keyword` VALUES (138, 'ARCHIVE');
INSERT INTO `help_keyword` VALUES (139, 'ADD');
INSERT INTO `help_keyword` VALUES (140, 'AVG_ROW_LENGTH');
INSERT INTO `help_keyword` VALUES (141, 'KILL');
INSERT INTO `help_keyword` VALUES (142, 'FLOAT4');
INSERT INTO `help_keyword` VALUES (143, 'VIEW');
INSERT INTO `help_keyword` VALUES (144, 'REPEATABLE');
INSERT INTO `help_keyword` VALUES (145, 'INFILE');
INSERT INTO `help_keyword` VALUES (146, 'ORDER');
INSERT INTO `help_keyword` VALUES (147, 'USING');
INSERT INTO `help_keyword` VALUES (148, 'MIDDLEINT');
INSERT INTO `help_keyword` VALUES (149, 'GRANT');
INSERT INTO `help_keyword` VALUES (150, 'UNSIGNED');
INSERT INTO `help_keyword` VALUES (151, 'DECIMAL');
INSERT INTO `help_keyword` VALUES (152, 'GEOMETRYFROMTEXT');
INSERT INTO `help_keyword` VALUES (153, 'INDEXES');
INSERT INTO `help_keyword` VALUES (154, 'FOREIGN');
INSERT INTO `help_keyword` VALUES (155, 'CACHE');
INSERT INTO `help_keyword` VALUES (156, 'HOSTS');
INSERT INTO `help_keyword` VALUES (157, 'COMMIT');
INSERT INTO `help_keyword` VALUES (158, 'SCHEMAS');
INSERT INTO `help_keyword` VALUES (159, 'LEADING');
INSERT INTO `help_keyword` VALUES (160, 'SNAPSHOT');
INSERT INTO `help_keyword` VALUES (161, 'DECLARE');
INSERT INTO `help_keyword` VALUES (162, 'LOAD');
INSERT INTO `help_keyword` VALUES (163, 'SQL_CACHE');
INSERT INTO `help_keyword` VALUES (164, 'CONVERT');
INSERT INTO `help_keyword` VALUES (165, 'DYNAMIC');
INSERT INTO `help_keyword` VALUES (166, 'POLYGONFROMTEXT');
INSERT INTO `help_keyword` VALUES (167, 'COLLATE');
INSERT INTO `help_keyword` VALUES (168, 'BYTE');
INSERT INTO `help_keyword` VALUES (169, 'LINESTRINGFROMWKB');
INSERT INTO `help_keyword` VALUES (170, 'GLOBAL');
INSERT INTO `help_keyword` VALUES (171, 'BERKELEYDB');
INSERT INTO `help_keyword` VALUES (172, 'WHEN');
INSERT INTO `help_keyword` VALUES (173, 'HAVING');
INSERT INTO `help_keyword` VALUES (174, 'AS');
INSERT INTO `help_keyword` VALUES (175, 'STARTING');
INSERT INTO `help_keyword` VALUES (176, 'RELOAD');
INSERT INTO `help_keyword` VALUES (177, 'AUTOCOMMIT');
INSERT INTO `help_keyword` VALUES (178, 'REVOKE');
INSERT INTO `help_keyword` VALUES (179, 'GRANTS');
INSERT INTO `help_keyword` VALUES (180, 'OUTER');
INSERT INTO `help_keyword` VALUES (181, 'FLOOR');
INSERT INTO `help_keyword` VALUES (182, 'WITH');
INSERT INTO `help_keyword` VALUES (183, 'STD');
INSERT INTO `help_keyword` VALUES (184, 'AFTER');
INSERT INTO `help_keyword` VALUES (185, 'CSV');
INSERT INTO `help_keyword` VALUES (186, 'DISABLE');
INSERT INTO `help_keyword` VALUES (187, 'OUTFILE');
INSERT INTO `help_keyword` VALUES (188, 'LOW_PRIORITY');
INSERT INTO `help_keyword` VALUES (189, 'FILE');
INSERT INTO `help_keyword` VALUES (190, 'BDB');
INSERT INTO `help_keyword` VALUES (191, 'SCHEMA');
INSERT INTO `help_keyword` VALUES (192, 'SONAME');
INSERT INTO `help_keyword` VALUES (193, 'POW');
INSERT INTO `help_keyword` VALUES (194, 'MULTIPOINTFROMWKB');
INSERT INTO `help_keyword` VALUES (195, 'INDEX');
INSERT INTO `help_keyword` VALUES (196, 'DUAL');
INSERT INTO `help_keyword` VALUES (197, 'MULTIPOINTFROMTEXT');
INSERT INTO `help_keyword` VALUES (198, 'BACKUP');
INSERT INTO `help_keyword` VALUES (199, 'MULTILINESTRINGFROMWKB');
INSERT INTO `help_keyword` VALUES (200, 'EXTENDED');
INSERT INTO `help_keyword` VALUES (201, 'CROSS');
INSERT INTO `help_keyword` VALUES (202, 'NATIONAL');
INSERT INTO `help_keyword` VALUES (203, 'GROUP');
INSERT INTO `help_keyword` VALUES (204, 'SHA');
INSERT INTO `help_keyword` VALUES (205, 'UNDO');
INSERT INTO `help_keyword` VALUES (206, 'ZEROFILL');
INSERT INTO `help_keyword` VALUES (207, 'CLIENT');
INSERT INTO `help_keyword` VALUES (208, 'MASTER_PASSWORD');
INSERT INTO `help_keyword` VALUES (209, 'RELAY_LOG_FILE');
INSERT INTO `help_keyword` VALUES (210, 'TRUE');
INSERT INTO `help_keyword` VALUES (211, 'CHARACTER');
INSERT INTO `help_keyword` VALUES (212, 'MASTER_USER');
INSERT INTO `help_keyword` VALUES (213, 'TABLE');
INSERT INTO `help_keyword` VALUES (214, 'ENGINE');
INSERT INTO `help_keyword` VALUES (215, 'INSERT_METHOD');
INSERT INTO `help_keyword` VALUES (216, 'CASCADE');
INSERT INTO `help_keyword` VALUES (217, 'RELAY_LOG_POS');
INSERT INTO `help_keyword` VALUES (218, 'SQL_CALC_FOUND_ROWS');
INSERT INTO `help_keyword` VALUES (219, 'UNION');
INSERT INTO `help_keyword` VALUES (220, 'MYISAM');
INSERT INTO `help_keyword` VALUES (221, 'LEAVE');
INSERT INTO `help_keyword` VALUES (222, 'MODIFY');
INSERT INTO `help_keyword` VALUES (223, 'MATCH');
INSERT INTO `help_keyword` VALUES (224, 'MASTER_LOG_POS');
INSERT INTO `help_keyword` VALUES (225, 'DESC');
INSERT INTO `help_keyword` VALUES (226, 'DISTINCTROW');
INSERT INTO `help_keyword` VALUES (227, 'TIME');
INSERT INTO `help_keyword` VALUES (228, 'NUMERIC');
INSERT INTO `help_keyword` VALUES (229, 'EXPANSION');
INSERT INTO `help_keyword` VALUES (230, 'CURSOR');
INSERT INTO `help_keyword` VALUES (231, 'CODE');
INSERT INTO `help_keyword` VALUES (232, 'GEOMETRYCOLLECTIONFROMTEXT');
INSERT INTO `help_keyword` VALUES (233, 'CHAIN');
INSERT INTO `help_keyword` VALUES (234, 'FLUSH');
INSERT INTO `help_keyword` VALUES (235, 'CREATE');
INSERT INTO `help_keyword` VALUES (236, 'DESCRIBE');
INSERT INTO `help_keyword` VALUES (237, 'MAX_UPDATES_PER_HOUR');
INSERT INTO `help_keyword` VALUES (238, 'INT2');
INSERT INTO `help_keyword` VALUES (239, 'PROCESSLIST');
INSERT INTO `help_keyword` VALUES (240, 'LOGS');
INSERT INTO `help_keyword` VALUES (241, 'HEAP');
INSERT INTO `help_keyword` VALUES (242, 'SOUNDS');
INSERT INTO `help_keyword` VALUES (243, 'BETWEEN');
INSERT INTO `help_keyword` VALUES (244, 'MULTILINESTRINGFROMTEXT');
INSERT INTO `help_keyword` VALUES (245, 'REPAIR');
INSERT INTO `help_keyword` VALUES (246, 'PACK_KEYS');
INSERT INTO `help_keyword` VALUES (247, 'CALL');
INSERT INTO `help_keyword` VALUES (248, 'FAST');
INSERT INTO `help_keyword` VALUES (249, 'VALUES');
INSERT INTO `help_keyword` VALUES (250, 'LOOP');
INSERT INTO `help_keyword` VALUES (251, 'VARCHARACTER');
INSERT INTO `help_keyword` VALUES (252, 'BEFORE');
INSERT INTO `help_keyword` VALUES (253, 'TRUNCATE');
INSERT INTO `help_keyword` VALUES (254, 'SHOW');
INSERT INTO `help_keyword` VALUES (255, 'REDUNDANT');
INSERT INTO `help_keyword` VALUES (256, 'ALL');
INSERT INTO `help_keyword` VALUES (257, 'USER_RESOURCES');
INSERT INTO `help_keyword` VALUES (258, 'PARTIAL');
INSERT INTO `help_keyword` VALUES (259, 'BINLOG');
INSERT INTO `help_keyword` VALUES (260, 'END');
INSERT INTO `help_keyword` VALUES (261, 'SECOND');
INSERT INTO `help_keyword` VALUES (262, 'AND');
INSERT INTO `help_keyword` VALUES (263, 'FLOAT8');
INSERT INTO `help_keyword` VALUES (264, 'PREV');
INSERT INTO `help_keyword` VALUES (265, 'HOUR');
INSERT INTO `help_keyword` VALUES (266, 'SELECT');
INSERT INTO `help_keyword` VALUES (267, 'DATABASES');
INSERT INTO `help_keyword` VALUES (268, 'OR');
INSERT INTO `help_keyword` VALUES (269, 'IDENTIFIED');
INSERT INTO `help_keyword` VALUES (270, 'MASTER_SSL_CIPHER');
INSERT INTO `help_keyword` VALUES (271, 'SQL_SLAVE_SKIP_COUNTER');
INSERT INTO `help_keyword` VALUES (272, 'BOTH');
INSERT INTO `help_keyword` VALUES (273, 'BOOL');
INSERT INTO `help_keyword` VALUES (274, 'YEAR');
INSERT INTO `help_keyword` VALUES (275, 'MASTER_PORT');
INSERT INTO `help_keyword` VALUES (276, 'CONCURRENT');
INSERT INTO `help_keyword` VALUES (277, 'HELP');
INSERT INTO `help_keyword` VALUES (278, 'UNIQUE');
INSERT INTO `help_keyword` VALUES (279, 'TRIGGERS');
INSERT INTO `help_keyword` VALUES (280, 'PROCESS');
INSERT INTO `help_keyword` VALUES (281, 'CONSISTENT');
INSERT INTO `help_keyword` VALUES (282, 'MASTER_SSL');
INSERT INTO `help_keyword` VALUES (283, 'DATE_ADD');
INSERT INTO `help_keyword` VALUES (284, 'MAX_CONNECTIONS_PER_HOUR');
INSERT INTO `help_keyword` VALUES (285, 'LIKE');
INSERT INTO `help_keyword` VALUES (286, 'FETCH');
INSERT INTO `help_keyword` VALUES (287, 'IN');
INSERT INTO `help_keyword` VALUES (288, 'COLUMN');
INSERT INTO `help_keyword` VALUES (289, 'DUMPFILE');
INSERT INTO `help_keyword` VALUES (290, 'USAGE');
INSERT INTO `help_keyword` VALUES (291, 'EXECUTE');
INSERT INTO `help_keyword` VALUES (292, 'MEMORY');
INSERT INTO `help_keyword` VALUES (293, 'CEIL');
INSERT INTO `help_keyword` VALUES (294, 'QUERY');
INSERT INTO `help_keyword` VALUES (295, 'MASTER_HOST');
INSERT INTO `help_keyword` VALUES (296, 'LINES');
INSERT INTO `help_keyword` VALUES (297, 'SQL_THREAD');
INSERT INTO `help_keyword` VALUES (298, 'MAX_QUERIES_PER_HOUR');
INSERT INTO `help_keyword` VALUES (299, 'MULTIPOLYGONFROMWKB');
INSERT INTO `help_keyword` VALUES (300, 'MASTER_SSL_CERT');
INSERT INTO `help_keyword` VALUES (301, 'DAY_MINUTE');
INSERT INTO `help_keyword` VALUES (302, 'TRANSACTION');
INSERT INTO `help_keyword` VALUES (303, 'STDDEV');
INSERT INTO `help_keyword` VALUES (304, 'DATE_SUB');
INSERT INTO `help_keyword` VALUES (305, 'GEOMETRYFROMWKB');
INSERT INTO `help_keyword` VALUES (306, 'INT1');
INSERT INTO `help_keyword` VALUES (307, 'RENAME');
INSERT INTO `help_keyword` VALUES (308, 'ALTER');
INSERT INTO `help_keyword` VALUES (309, 'MAX_ROWS');
INSERT INTO `help_keyword` VALUES (310, 'RIGHT');
INSERT INTO `help_keyword` VALUES (311, 'STRAIGHT_JOIN');
INSERT INTO `help_keyword` VALUES (312, 'NATURAL');
INSERT INTO `help_keyword` VALUES (313, 'VARIABLES');
INSERT INTO `help_keyword` VALUES (314, 'ESCAPED');
INSERT INTO `help_keyword` VALUES (315, 'SHA1');
INSERT INTO `help_keyword` VALUES (316, 'PASSWORD');
INSERT INTO `help_keyword` VALUES (317, 'CHAR');
INSERT INTO `help_keyword` VALUES (318, 'OFFSET');
INSERT INTO `help_keyword` VALUES (319, 'NEXT');
INSERT INTO `help_keyword` VALUES (320, 'SQL_LOG_BIN');
INSERT INTO `help_keyword` VALUES (321, 'ERRORS');
INSERT INTO `help_keyword` VALUES (322, 'TEMPORARY');
INSERT INTO `help_keyword` VALUES (323, 'COMMITTED');
INSERT INTO `help_keyword` VALUES (324, 'SQL_SMALL_RESULT');
INSERT INTO `help_keyword` VALUES (325, 'UPGRADE');
INSERT INTO `help_keyword` VALUES (326, 'DELAY_KEY_WRITE');
INSERT INTO `help_keyword` VALUES (327, 'BEGIN');
INSERT INTO `help_keyword` VALUES (328, 'PROFILE');
INSERT INTO `help_keyword` VALUES (329, 'MEDIUM');
INSERT INTO `help_keyword` VALUES (330, 'INTERVAL');
INSERT INTO `help_keyword` VALUES (331, 'SSL');
INSERT INTO `help_keyword` VALUES (332, 'DAY_HOUR');
INSERT INTO `help_keyword` VALUES (333, 'REFERENCES');
INSERT INTO `help_keyword` VALUES (334, 'AES_ENCRYPT');
INSERT INTO `help_keyword` VALUES (335, 'STORAGE');
INSERT INTO `help_keyword` VALUES (336, 'ISOLATION');
INSERT INTO `help_keyword` VALUES (337, 'CEILING');
INSERT INTO `help_keyword` VALUES (338, 'INT8');
INSERT INTO `help_keyword` VALUES (339, 'RESTRICT');
INSERT INTO `help_keyword` VALUES (340, 'LINESTRINGFROMTEXT');
INSERT INTO `help_keyword` VALUES (341, 'UNCOMMITTED');
INSERT INTO `help_keyword` VALUES (342, 'IS');
INSERT INTO `help_keyword` VALUES (343, 'NOT');
INSERT INTO `help_keyword` VALUES (344, 'ANALYSE');
INSERT INTO `help_keyword` VALUES (345, 'DES_KEY_FILE');
INSERT INTO `help_keyword` VALUES (346, 'COMPRESSED');
INSERT INTO `help_keyword` VALUES (347, 'START');
INSERT INTO `help_keyword` VALUES (348, 'SAVEPOINT');
INSERT INTO `help_keyword` VALUES (349, 'IF');
INSERT INTO `help_keyword` VALUES (350, 'PRIMARY');
INSERT INTO `help_keyword` VALUES (351, 'PURGE');
INSERT INTO `help_keyword` VALUES (352, 'USER');
INSERT INTO `help_keyword` VALUES (353, 'INNOBASE');
INSERT INTO `help_keyword` VALUES (354, 'LAST');
INSERT INTO `help_keyword` VALUES (355, 'EXIT');
INSERT INTO `help_keyword` VALUES (356, 'KEYS');
INSERT INTO `help_keyword` VALUES (357, 'LIMIT');
INSERT INTO `help_keyword` VALUES (358, 'KEY');
INSERT INTO `help_keyword` VALUES (359, 'MERGE');
INSERT INTO `help_keyword` VALUES (360, 'UNTIL');
INSERT INTO `help_keyword` VALUES (361, 'SQL_NO_CACHE');
INSERT INTO `help_keyword` VALUES (362, 'DELAYED');
INSERT INTO `help_keyword` VALUES (363, 'ANALYZE');
INSERT INTO `help_keyword` VALUES (364, 'CONSTRAINT');
INSERT INTO `help_keyword` VALUES (365, 'SERIAL');
INSERT INTO `help_keyword` VALUES (366, 'ACTION');
INSERT INTO `help_keyword` VALUES (367, 'WRITE');
INSERT INTO `help_keyword` VALUES (368, 'SESSION');
INSERT INTO `help_keyword` VALUES (369, 'DATABASE');
INSERT INTO `help_keyword` VALUES (370, 'NULL');
INSERT INTO `help_keyword` VALUES (371, 'POWER');
INSERT INTO `help_keyword` VALUES (372, 'USE_FRM');
INSERT INTO `help_keyword` VALUES (373, 'SLAVE');
INSERT INTO `help_keyword` VALUES (374, 'TERMINATED');
INSERT INTO `help_keyword` VALUES (375, 'NVARCHAR');
INSERT INTO `help_keyword` VALUES (376, 'ASC');
INSERT INTO `help_keyword` VALUES (377, 'ENABLE');
INSERT INTO `help_keyword` VALUES (378, 'OPTIONALLY');
INSERT INTO `help_keyword` VALUES (379, 'DIRECTORY');
INSERT INTO `help_keyword` VALUES (380, 'WHILE');
INSERT INTO `help_keyword` VALUES (381, 'MAX_USER_CONNECTIONS');
INSERT INTO `help_keyword` VALUES (382, 'DISTINCT');
INSERT INTO `help_keyword` VALUES (383, 'AES_DECRYPT');
INSERT INTO `help_keyword` VALUES (384, 'LOCAL');
INSERT INTO `help_keyword` VALUES (385, 'MASTER_SSL_KEY');
INSERT INTO `help_keyword` VALUES (386, 'NONE');
INSERT INTO `help_keyword` VALUES (387, 'TABLES');
INSERT INTO `help_keyword` VALUES (388, '<>');
INSERT INTO `help_keyword` VALUES (389, 'RLIKE');
INSERT INTO `help_keyword` VALUES (390, 'TRIGGER');
INSERT INTO `help_keyword` VALUES (391, 'COLLATION');
INSERT INTO `help_keyword` VALUES (392, 'SHUTDOWN');
INSERT INTO `help_keyword` VALUES (393, 'HIGH_PRIORITY');
INSERT INTO `help_keyword` VALUES (394, 'BTREE');
INSERT INTO `help_keyword` VALUES (395, 'FIRST');
INSERT INTO `help_keyword` VALUES (396, 'TYPES');
INSERT INTO `help_keyword` VALUES (397, 'MASTER');
INSERT INTO `help_keyword` VALUES (398, 'FIXED');
INSERT INTO `help_keyword` VALUES (399, 'MULTIPOLYGONFROMTEXT');
INSERT INTO `help_keyword` VALUES (400, 'ROW_FORMAT');

-- --------------------------------------------------------

-- 
-- 資料表格式： `help_relation`
-- 

CREATE TABLE `help_relation` (
  `help_topic_id` int(10) unsigned NOT NULL,
  `help_keyword_id` int(10) unsigned NOT NULL,
  PRIMARY KEY  (`help_keyword_id`,`help_topic_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='keyword-topic relation';

-- 
-- 列出以下資料庫的數據： `help_relation`
-- 

INSERT INTO `help_relation` VALUES (1, 0);
INSERT INTO `help_relation` VALUES (334, 0);
INSERT INTO `help_relation` VALUES (214, 1);
INSERT INTO `help_relation` VALUES (419, 2);
INSERT INTO `help_relation` VALUES (37, 3);
INSERT INTO `help_relation` VALUES (395, 3);
INSERT INTO `help_relation` VALUES (194, 4);
INSERT INTO `help_relation` VALUES (173, 5);
INSERT INTO `help_relation` VALUES (402, 6);
INSERT INTO `help_relation` VALUES (18, 7);
INSERT INTO `help_relation` VALUES (326, 7);
INSERT INTO `help_relation` VALUES (131, 8);
INSERT INTO `help_relation` VALUES (212, 9);
INSERT INTO `help_relation` VALUES (77, 10);
INSERT INTO `help_relation` VALUES (334, 10);
INSERT INTO `help_relation` VALUES (13, 11);
INSERT INTO `help_relation` VALUES (93, 11);
INSERT INTO `help_relation` VALUES (119, 11);
INSERT INTO `help_relation` VALUES (326, 11);
INSERT INTO `help_relation` VALUES (194, 12);
INSERT INTO `help_relation` VALUES (467, 12);
INSERT INTO `help_relation` VALUES (357, 13);
INSERT INTO `help_relation` VALUES (224, 14);
INSERT INTO `help_relation` VALUES (95, 15);
INSERT INTO `help_relation` VALUES (334, 16);
INSERT INTO `help_relation` VALUES (26, 17);
INSERT INTO `help_relation` VALUES (76, 17);
INSERT INTO `help_relation` VALUES (174, 17);
INSERT INTO `help_relation` VALUES (219, 17);
INSERT INTO `help_relation` VALUES (245, 17);
INSERT INTO `help_relation` VALUES (257, 17);
INSERT INTO `help_relation` VALUES (311, 17);
INSERT INTO `help_relation` VALUES (382, 17);
INSERT INTO `help_relation` VALUES (390, 17);
INSERT INTO `help_relation` VALUES (434, 17);
INSERT INTO `help_relation` VALUES (109, 18);
INSERT INTO `help_relation` VALUES (353, 19);
INSERT INTO `help_relation` VALUES (241, 20);
INSERT INTO `help_relation` VALUES (71, 21);
INSERT INTO `help_relation` VALUES (91, 22);
INSERT INTO `help_relation` VALUES (185, 23);
INSERT INTO `help_relation` VALUES (326, 24);
INSERT INTO `help_relation` VALUES (377, 24);
INSERT INTO `help_relation` VALUES (439, 24);
INSERT INTO `help_relation` VALUES (353, 25);
INSERT INTO `help_relation` VALUES (185, 26);
INSERT INTO `help_relation` VALUES (29, 27);
INSERT INTO `help_relation` VALUES (219, 27);
INSERT INTO `help_relation` VALUES (30, 28);
INSERT INTO `help_relation` VALUES (334, 28);
INSERT INTO `help_relation` VALUES (439, 29);
INSERT INTO `help_relation` VALUES (391, 30);
INSERT INTO `help_relation` VALUES (439, 30);
INSERT INTO `help_relation` VALUES (18, 31);
INSERT INTO `help_relation` VALUES (275, 31);
INSERT INTO `help_relation` VALUES (326, 31);
INSERT INTO `help_relation` VALUES (424, 31);
INSERT INTO `help_relation` VALUES (439, 31);
INSERT INTO `help_relation` VALUES (467, 32);
INSERT INTO `help_relation` VALUES (42, 33);
INSERT INTO `help_relation` VALUES (66, 33);
INSERT INTO `help_relation` VALUES (72, 33);
INSERT INTO `help_relation` VALUES (185, 33);
INSERT INTO `help_relation` VALUES (334, 33);
INSERT INTO `help_relation` VALUES (340, 33);
INSERT INTO `help_relation` VALUES (395, 33);
INSERT INTO `help_relation` VALUES (434, 33);
INSERT INTO `help_relation` VALUES (439, 33);
INSERT INTO `help_relation` VALUES (439, 34);
INSERT INTO `help_relation` VALUES (443, 34);
INSERT INTO `help_relation` VALUES (353, 35);
INSERT INTO `help_relation` VALUES (104, 36);
INSERT INTO `help_relation` VALUES (395, 36);
INSERT INTO `help_relation` VALUES (439, 36);
INSERT INTO `help_relation` VALUES (353, 37);
INSERT INTO `help_relation` VALUES (334, 38);
INSERT INTO `help_relation` VALUES (194, 39);
INSERT INTO `help_relation` VALUES (294, 39);
INSERT INTO `help_relation` VALUES (340, 40);
INSERT INTO `help_relation` VALUES (42, 41);
INSERT INTO `help_relation` VALUES (439, 41);
INSERT INTO `help_relation` VALUES (443, 41);
INSERT INTO `help_relation` VALUES (1, 42);
INSERT INTO `help_relation` VALUES (443, 42);
INSERT INTO `help_relation` VALUES (162, 43);
INSERT INTO `help_relation` VALUES (439, 43);
INSERT INTO `help_relation` VALUES (45, 44);
INSERT INTO `help_relation` VALUES (93, 44);
INSERT INTO `help_relation` VALUES (185, 45);
INSERT INTO `help_relation` VALUES (1, 46);
INSERT INTO `help_relation` VALUES (42, 47);
INSERT INTO `help_relation` VALUES (72, 47);
INSERT INTO `help_relation` VALUES (93, 47);
INSERT INTO `help_relation` VALUES (178, 48);
INSERT INTO `help_relation` VALUES (185, 48);
INSERT INTO `help_relation` VALUES (230, 48);
INSERT INTO `help_relation` VALUES (196, 49);
INSERT INTO `help_relation` VALUES (434, 49);
INSERT INTO `help_relation` VALUES (185, 50);
INSERT INTO `help_relation` VALUES (334, 51);
INSERT INTO `help_relation` VALUES (1, 52);
INSERT INTO `help_relation` VALUES (72, 52);
INSERT INTO `help_relation` VALUES (91, 52);
INSERT INTO `help_relation` VALUES (334, 52);
INSERT INTO `help_relation` VALUES (395, 52);
INSERT INTO `help_relation` VALUES (434, 52);
INSERT INTO `help_relation` VALUES (42, 53);
INSERT INTO `help_relation` VALUES (391, 53);
INSERT INTO `help_relation` VALUES (437, 53);
INSERT INTO `help_relation` VALUES (212, 54);
INSERT INTO `help_relation` VALUES (185, 55);
INSERT INTO `help_relation` VALUES (79, 56);
INSERT INTO `help_relation` VALUES (451, 56);
INSERT INTO `help_relation` VALUES (439, 57);
INSERT INTO `help_relation` VALUES (362, 58);
INSERT INTO `help_relation` VALUES (419, 59);
INSERT INTO `help_relation` VALUES (1, 60);
INSERT INTO `help_relation` VALUES (32, 61);
INSERT INTO `help_relation` VALUES (212, 61);
INSERT INTO `help_relation` VALUES (173, 62);
INSERT INTO `help_relation` VALUES (431, 62);
INSERT INTO `help_relation` VALUES (435, 62);
INSERT INTO `help_relation` VALUES (173, 63);
INSERT INTO `help_relation` VALUES (434, 63);
INSERT INTO `help_relation` VALUES (353, 64);
INSERT INTO `help_relation` VALUES (72, 65);
INSERT INTO `help_relation` VALUES (91, 65);
INSERT INTO `help_relation` VALUES (334, 65);
INSERT INTO `help_relation` VALUES (443, 65);
INSERT INTO `help_relation` VALUES (37, 66);
INSERT INTO `help_relation` VALUES (91, 66);
INSERT INTO `help_relation` VALUES (284, 66);
INSERT INTO `help_relation` VALUES (334, 66);
INSERT INTO `help_relation` VALUES (439, 67);
INSERT INTO `help_relation` VALUES (238, 68);
INSERT INTO `help_relation` VALUES (353, 69);
INSERT INTO `help_relation` VALUES (116, 70);
INSERT INTO `help_relation` VALUES (131, 71);
INSERT INTO `help_relation` VALUES (431, 71);
INSERT INTO `help_relation` VALUES (14, 72);
INSERT INTO `help_relation` VALUES (171, 72);
INSERT INTO `help_relation` VALUES (281, 72);
INSERT INTO `help_relation` VALUES (308, 72);
INSERT INTO `help_relation` VALUES (326, 72);
INSERT INTO `help_relation` VALUES (334, 72);
INSERT INTO `help_relation` VALUES (390, 72);
INSERT INTO `help_relation` VALUES (411, 72);
INSERT INTO `help_relation` VALUES (456, 72);
INSERT INTO `help_relation` VALUES (196, 73);
INSERT INTO `help_relation` VALUES (86, 74);
INSERT INTO `help_relation` VALUES (175, 74);
INSERT INTO `help_relation` VALUES (395, 75);
INSERT INTO `help_relation` VALUES (77, 76);
INSERT INTO `help_relation` VALUES (378, 77);
INSERT INTO `help_relation` VALUES (439, 77);
INSERT INTO `help_relation` VALUES (58, 78);
INSERT INTO `help_relation` VALUES (309, 78);
INSERT INTO `help_relation` VALUES (405, 78);
INSERT INTO `help_relation` VALUES (267, 79);
INSERT INTO `help_relation` VALUES (24, 80);
INSERT INTO `help_relation` VALUES (49, 80);
INSERT INTO `help_relation` VALUES (74, 80);
INSERT INTO `help_relation` VALUES (91, 81);
INSERT INTO `help_relation` VALUES (179, 81);
INSERT INTO `help_relation` VALUES (282, 81);
INSERT INTO `help_relation` VALUES (455, 81);
INSERT INTO `help_relation` VALUES (263, 82);
INSERT INTO `help_relation` VALUES (326, 82);
INSERT INTO `help_relation` VALUES (93, 83);
INSERT INTO `help_relation` VALUES (293, 83);
INSERT INTO `help_relation` VALUES (353, 84);
INSERT INTO `help_relation` VALUES (26, 85);
INSERT INTO `help_relation` VALUES (140, 85);
INSERT INTO `help_relation` VALUES (174, 85);
INSERT INTO `help_relation` VALUES (257, 85);
INSERT INTO `help_relation` VALUES (264, 86);
INSERT INTO `help_relation` VALUES (326, 86);
INSERT INTO `help_relation` VALUES (131, 87);
INSERT INTO `help_relation` VALUES (431, 87);
INSERT INTO `help_relation` VALUES (20, 88);
INSERT INTO `help_relation` VALUES (77, 88);
INSERT INTO `help_relation` VALUES (99, 89);
INSERT INTO `help_relation` VALUES (160, 89);
INSERT INTO `help_relation` VALUES (37, 90);
INSERT INTO `help_relation` VALUES (91, 90);
INSERT INTO `help_relation` VALUES (140, 90);
INSERT INTO `help_relation` VALUES (183, 90);
INSERT INTO `help_relation` VALUES (197, 90);
INSERT INTO `help_relation` VALUES (224, 90);
INSERT INTO `help_relation` VALUES (434, 90);
INSERT INTO `help_relation` VALUES (439, 90);
INSERT INTO `help_relation` VALUES (434, 91);
INSERT INTO `help_relation` VALUES (439, 91);
INSERT INTO `help_relation` VALUES (101, 92);
INSERT INTO `help_relation` VALUES (307, 92);
INSERT INTO `help_relation` VALUES (437, 92);
INSERT INTO `help_relation` VALUES (441, 92);
INSERT INTO `help_relation` VALUES (101, 93);
INSERT INTO `help_relation` VALUES (31, 94);
INSERT INTO `help_relation` VALUES (105, 94);
INSERT INTO `help_relation` VALUES (136, 94);
INSERT INTO `help_relation` VALUES (246, 94);
INSERT INTO `help_relation` VALUES (111, 95);
INSERT INTO `help_relation` VALUES (112, 96);
INSERT INTO `help_relation` VALUES (463, 96);
INSERT INTO `help_relation` VALUES (205, 97);
INSERT INTO `help_relation` VALUES (37, 98);
INSERT INTO `help_relation` VALUES (72, 98);
INSERT INTO `help_relation` VALUES (116, 98);
INSERT INTO `help_relation` VALUES (124, 98);
INSERT INTO `help_relation` VALUES (131, 98);
INSERT INTO `help_relation` VALUES (140, 98);
INSERT INTO `help_relation` VALUES (169, 98);
INSERT INTO `help_relation` VALUES (197, 98);
INSERT INTO `help_relation` VALUES (313, 98);
INSERT INTO `help_relation` VALUES (395, 98);
INSERT INTO `help_relation` VALUES (434, 98);
INSERT INTO `help_relation` VALUES (439, 98);
INSERT INTO `help_relation` VALUES (443, 98);
INSERT INTO `help_relation` VALUES (447, 98);
INSERT INTO `help_relation` VALUES (461, 98);
INSERT INTO `help_relation` VALUES (185, 99);
INSERT INTO `help_relation` VALUES (118, 100);
INSERT INTO `help_relation` VALUES (212, 100);
INSERT INTO `help_relation` VALUES (244, 100);
INSERT INTO `help_relation` VALUES (353, 100);
INSERT INTO `help_relation` VALUES (50, 101);
INSERT INTO `help_relation` VALUES (122, 101);
INSERT INTO `help_relation` VALUES (199, 101);
INSERT INTO `help_relation` VALUES (207, 101);
INSERT INTO `help_relation` VALUES (264, 101);
INSERT INTO `help_relation` VALUES (308, 101);
INSERT INTO `help_relation` VALUES (326, 101);
INSERT INTO `help_relation` VALUES (344, 101);
INSERT INTO `help_relation` VALUES (377, 101);
INSERT INTO `help_relation` VALUES (196, 102);
INSERT INTO `help_relation` VALUES (434, 102);
INSERT INTO `help_relation` VALUES (439, 102);
INSERT INTO `help_relation` VALUES (439, 103);
INSERT INTO `help_relation` VALUES (173, 104);
INSERT INTO `help_relation` VALUES (1, 105);
INSERT INTO `help_relation` VALUES (46, 106);
INSERT INTO `help_relation` VALUES (173, 107);
INSERT INTO `help_relation` VALUES (439, 108);
INSERT INTO `help_relation` VALUES (294, 109);
INSERT INTO `help_relation` VALUES (185, 110);
INSERT INTO `help_relation` VALUES (427, 111);
INSERT INTO `help_relation` VALUES (267, 112);
INSERT INTO `help_relation` VALUES (185, 113);
INSERT INTO `help_relation` VALUES (230, 113);
INSERT INTO `help_relation` VALUES (49, 114);
INSERT INTO `help_relation` VALUES (74, 114);
INSERT INTO `help_relation` VALUES (219, 115);
INSERT INTO `help_relation` VALUES (46, 116);
INSERT INTO `help_relation` VALUES (305, 116);
INSERT INTO `help_relation` VALUES (49, 117);
INSERT INTO `help_relation` VALUES (74, 117);
INSERT INTO `help_relation` VALUES (185, 118);
INSERT INTO `help_relation` VALUES (293, 119);
INSERT INTO `help_relation` VALUES (42, 120);
INSERT INTO `help_relation` VALUES (104, 120);
INSERT INTO `help_relation` VALUES (109, 120);
INSERT INTO `help_relation` VALUES (326, 120);
INSERT INTO `help_relation` VALUES (334, 120);
INSERT INTO `help_relation` VALUES (339, 120);
INSERT INTO `help_relation` VALUES (427, 120);
INSERT INTO `help_relation` VALUES (30, 121);
INSERT INTO `help_relation` VALUES (93, 121);
INSERT INTO `help_relation` VALUES (419, 121);
INSERT INTO `help_relation` VALUES (1, 122);
INSERT INTO `help_relation` VALUES (24, 123);
INSERT INTO `help_relation` VALUES (353, 124);
INSERT INTO `help_relation` VALUES (439, 125);
INSERT INTO `help_relation` VALUES (165, 126);
INSERT INTO `help_relation` VALUES (193, 127);
INSERT INTO `help_relation` VALUES (166, 128);
INSERT INTO `help_relation` VALUES (293, 128);
INSERT INTO `help_relation` VALUES (326, 128);
INSERT INTO `help_relation` VALUES (334, 128);
INSERT INTO `help_relation` VALUES (393, 128);
INSERT INTO `help_relation` VALUES (309, 129);
INSERT INTO `help_relation` VALUES (326, 129);
INSERT INTO `help_relation` VALUES (439, 130);
INSERT INTO `help_relation` VALUES (194, 131);
INSERT INTO `help_relation` VALUES (166, 132);
INSERT INTO `help_relation` VALUES (14, 133);
INSERT INTO `help_relation` VALUES (194, 133);
INSERT INTO `help_relation` VALUES (281, 133);
INSERT INTO `help_relation` VALUES (308, 133);
INSERT INTO `help_relation` VALUES (326, 133);
INSERT INTO `help_relation` VALUES (382, 133);
INSERT INTO `help_relation` VALUES (390, 133);
INSERT INTO `help_relation` VALUES (411, 133);
INSERT INTO `help_relation` VALUES (456, 133);
INSERT INTO `help_relation` VALUES (395, 134);
INSERT INTO `help_relation` VALUES (194, 135);
INSERT INTO `help_relation` VALUES (326, 136);
INSERT INTO `help_relation` VALUES (395, 136);
INSERT INTO `help_relation` VALUES (233, 137);
INSERT INTO `help_relation` VALUES (439, 138);
INSERT INTO `help_relation` VALUES (52, 139);
INSERT INTO `help_relation` VALUES (434, 139);
INSERT INTO `help_relation` VALUES (434, 140);
INSERT INTO `help_relation` VALUES (439, 140);
INSERT INTO `help_relation` VALUES (162, 141);
INSERT INTO `help_relation` VALUES (154, 142);
INSERT INTO `help_relation` VALUES (26, 143);
INSERT INTO `help_relation` VALUES (144, 143);
INSERT INTO `help_relation` VALUES (426, 143);
INSERT INTO `help_relation` VALUES (419, 144);
INSERT INTO `help_relation` VALUES (395, 145);
INSERT INTO `help_relation` VALUES (42, 146);
INSERT INTO `help_relation` VALUES (72, 146);
INSERT INTO `help_relation` VALUES (334, 146);
INSERT INTO `help_relation` VALUES (340, 146);
INSERT INTO `help_relation` VALUES (434, 146);
INSERT INTO `help_relation` VALUES (1, 147);
INSERT INTO `help_relation` VALUES (42, 147);
INSERT INTO `help_relation` VALUES (75, 147);
INSERT INTO `help_relation` VALUES (233, 148);
INSERT INTO `help_relation` VALUES (185, 149);
INSERT INTO `help_relation` VALUES (230, 149);
INSERT INTO `help_relation` VALUES (20, 150);
INSERT INTO `help_relation` VALUES (115, 150);
INSERT INTO `help_relation` VALUES (154, 150);
INSERT INTO `help_relation` VALUES (193, 150);
INSERT INTO `help_relation` VALUES (212, 150);
INSERT INTO `help_relation` VALUES (294, 150);
INSERT INTO `help_relation` VALUES (467, 150);
INSERT INTO `help_relation` VALUES (141, 151);
INSERT INTO `help_relation` VALUES (194, 151);
INSERT INTO `help_relation` VALUES (387, 152);
INSERT INTO `help_relation` VALUES (326, 153);
INSERT INTO `help_relation` VALUES (434, 154);
INSERT INTO `help_relation` VALUES (439, 154);
INSERT INTO `help_relation` VALUES (443, 154);
INSERT INTO `help_relation` VALUES (89, 155);
INSERT INTO `help_relation` VALUES (136, 155);
INSERT INTO `help_relation` VALUES (284, 155);
INSERT INTO `help_relation` VALUES (130, 156);
INSERT INTO `help_relation` VALUES (326, 156);
INSERT INTO `help_relation` VALUES (131, 157);
INSERT INTO `help_relation` VALUES (145, 158);
INSERT INTO `help_relation` VALUES (326, 158);
INSERT INTO `help_relation` VALUES (427, 159);
INSERT INTO `help_relation` VALUES (131, 160);
INSERT INTO `help_relation` VALUES (166, 161);
INSERT INTO `help_relation` VALUES (183, 161);
INSERT INTO `help_relation` VALUES (293, 161);
INSERT INTO `help_relation` VALUES (393, 161);
INSERT INTO `help_relation` VALUES (104, 162);
INSERT INTO `help_relation` VALUES (284, 162);
INSERT INTO `help_relation` VALUES (339, 162);
INSERT INTO `help_relation` VALUES (395, 162);
INSERT INTO `help_relation` VALUES (334, 163);
INSERT INTO `help_relation` VALUES (212, 164);
INSERT INTO `help_relation` VALUES (354, 164);
INSERT INTO `help_relation` VALUES (439, 165);
INSERT INTO `help_relation` VALUES (371, 166);
INSERT INTO `help_relation` VALUES (140, 167);
INSERT INTO `help_relation` VALUES (197, 167);
INSERT INTO `help_relation` VALUES (439, 167);
INSERT INTO `help_relation` VALUES (436, 168);
INSERT INTO `help_relation` VALUES (423, 169);
INSERT INTO `help_relation` VALUES (116, 170);
INSERT INTO `help_relation` VALUES (122, 170);
INSERT INTO `help_relation` VALUES (169, 170);
INSERT INTO `help_relation` VALUES (328, 170);
INSERT INTO `help_relation` VALUES (419, 170);
INSERT INTO `help_relation` VALUES (439, 171);
INSERT INTO `help_relation` VALUES (49, 172);
INSERT INTO `help_relation` VALUES (74, 172);
INSERT INTO `help_relation` VALUES (334, 173);
INSERT INTO `help_relation` VALUES (1, 174);
INSERT INTO `help_relation` VALUES (30, 174);
INSERT INTO `help_relation` VALUES (334, 174);
INSERT INTO `help_relation` VALUES (395, 175);
INSERT INTO `help_relation` VALUES (185, 176);
INSERT INTO `help_relation` VALUES (131, 177);
INSERT INTO `help_relation` VALUES (230, 178);
INSERT INTO `help_relation` VALUES (177, 179);
INSERT INTO `help_relation` VALUES (326, 179);
INSERT INTO `help_relation` VALUES (1, 180);
INSERT INTO `help_relation` VALUES (205, 181);
INSERT INTO `help_relation` VALUES (77, 182);
INSERT INTO `help_relation` VALUES (185, 182);
INSERT INTO `help_relation` VALUES (242, 183);
INSERT INTO `help_relation` VALUES (434, 184);
INSERT INTO `help_relation` VALUES (395, 185);
INSERT INTO `help_relation` VALUES (439, 185);
INSERT INTO `help_relation` VALUES (434, 186);
INSERT INTO `help_relation` VALUES (334, 187);
INSERT INTO `help_relation` VALUES (30, 188);
INSERT INTO `help_relation` VALUES (37, 188);
INSERT INTO `help_relation` VALUES (42, 188);
INSERT INTO `help_relation` VALUES (72, 188);
INSERT INTO `help_relation` VALUES (91, 188);
INSERT INTO `help_relation` VALUES (395, 188);
INSERT INTO `help_relation` VALUES (185, 189);
INSERT INTO `help_relation` VALUES (151, 190);
INSERT INTO `help_relation` VALUES (439, 190);
INSERT INTO `help_relation` VALUES (140, 191);
INSERT INTO `help_relation` VALUES (174, 191);
INSERT INTO `help_relation` VALUES (197, 191);
INSERT INTO `help_relation` VALUES (289, 191);
INSERT INTO `help_relation` VALUES (326, 191);
INSERT INTO `help_relation` VALUES (194, 192);
INSERT INTO `help_relation` VALUES (258, 193);
INSERT INTO `help_relation` VALUES (433, 194);
INSERT INTO `help_relation` VALUES (1, 195);
INSERT INTO `help_relation` VALUES (52, 195);
INSERT INTO `help_relation` VALUES (76, 195);
INSERT INTO `help_relation` VALUES (89, 195);
INSERT INTO `help_relation` VALUES (196, 195);
INSERT INTO `help_relation` VALUES (284, 195);
INSERT INTO `help_relation` VALUES (288, 195);
INSERT INTO `help_relation` VALUES (326, 195);
INSERT INTO `help_relation` VALUES (434, 195);
INSERT INTO `help_relation` VALUES (439, 195);
INSERT INTO `help_relation` VALUES (260, 196);
INSERT INTO `help_relation` VALUES (397, 197);
INSERT INTO `help_relation` VALUES (336, 198);
INSERT INTO `help_relation` VALUES (253, 199);
INSERT INTO `help_relation` VALUES (437, 200);
INSERT INTO `help_relation` VALUES (1, 201);
INSERT INTO `help_relation` VALUES (238, 202);
INSERT INTO `help_relation` VALUES (402, 202);
INSERT INTO `help_relation` VALUES (334, 203);
INSERT INTO `help_relation` VALUES (399, 204);
INSERT INTO `help_relation` VALUES (293, 205);
INSERT INTO `help_relation` VALUES (20, 206);
INSERT INTO `help_relation` VALUES (115, 206);
INSERT INTO `help_relation` VALUES (154, 206);
INSERT INTO `help_relation` VALUES (193, 206);
INSERT INTO `help_relation` VALUES (294, 206);
INSERT INTO `help_relation` VALUES (467, 206);
INSERT INTO `help_relation` VALUES (185, 207);
INSERT INTO `help_relation` VALUES (173, 208);
INSERT INTO `help_relation` VALUES (173, 209);
INSERT INTO `help_relation` VALUES (362, 210);
INSERT INTO `help_relation` VALUES (140, 211);
INSERT INTO `help_relation` VALUES (197, 211);
INSERT INTO `help_relation` VALUES (238, 211);
INSERT INTO `help_relation` VALUES (313, 211);
INSERT INTO `help_relation` VALUES (395, 211);
INSERT INTO `help_relation` VALUES (402, 211);
INSERT INTO `help_relation` VALUES (439, 211);
INSERT INTO `help_relation` VALUES (173, 212);
INSERT INTO `help_relation` VALUES (52, 213);
INSERT INTO `help_relation` VALUES (96, 213);
INSERT INTO `help_relation` VALUES (101, 213);
INSERT INTO `help_relation` VALUES (165, 213);
INSERT INTO `help_relation` VALUES (199, 213);
INSERT INTO `help_relation` VALUES (257, 213);
INSERT INTO `help_relation` VALUES (259, 213);
INSERT INTO `help_relation` VALUES (301, 213);
INSERT INTO `help_relation` VALUES (326, 213);
INSERT INTO `help_relation` VALUES (336, 213);
INSERT INTO `help_relation` VALUES (339, 213);
INSERT INTO `help_relation` VALUES (378, 213);
INSERT INTO `help_relation` VALUES (391, 213);
INSERT INTO `help_relation` VALUES (434, 213);
INSERT INTO `help_relation` VALUES (437, 213);
INSERT INTO `help_relation` VALUES (439, 213);
INSERT INTO `help_relation` VALUES (441, 213);
INSERT INTO `help_relation` VALUES (326, 214);
INSERT INTO `help_relation` VALUES (344, 214);
INSERT INTO `help_relation` VALUES (434, 214);
INSERT INTO `help_relation` VALUES (439, 214);
INSERT INTO `help_relation` VALUES (439, 215);
INSERT INTO `help_relation` VALUES (26, 216);
INSERT INTO `help_relation` VALUES (257, 216);
INSERT INTO `help_relation` VALUES (439, 216);
INSERT INTO `help_relation` VALUES (443, 216);
INSERT INTO `help_relation` VALUES (173, 217);
INSERT INTO `help_relation` VALUES (334, 218);
INSERT INTO `help_relation` VALUES (285, 219);
INSERT INTO `help_relation` VALUES (439, 220);
INSERT INTO `help_relation` VALUES (290, 221);
INSERT INTO `help_relation` VALUES (434, 222);
INSERT INTO `help_relation` VALUES (77, 223);
INSERT INTO `help_relation` VALUES (173, 224);
INSERT INTO `help_relation` VALUES (310, 225);
INSERT INTO `help_relation` VALUES (334, 225);
INSERT INTO `help_relation` VALUES (340, 225);
INSERT INTO `help_relation` VALUES (334, 226);
INSERT INTO `help_relation` VALUES (212, 227);
INSERT INTO `help_relation` VALUES (295, 227);
INSERT INTO `help_relation` VALUES (352, 227);
INSERT INTO `help_relation` VALUES (193, 228);
INSERT INTO `help_relation` VALUES (77, 229);
INSERT INTO `help_relation` VALUES (393, 230);
INSERT INTO `help_relation` VALUES (456, 231);
INSERT INTO `help_relation` VALUES (227, 232);
INSERT INTO `help_relation` VALUES (131, 233);
INSERT INTO `help_relation` VALUES (136, 234);
INSERT INTO `help_relation` VALUES (307, 234);
INSERT INTO `help_relation` VALUES (14, 235);
INSERT INTO `help_relation` VALUES (17, 235);
INSERT INTO `help_relation` VALUES (52, 235);
INSERT INTO `help_relation` VALUES (66, 235);
INSERT INTO `help_relation` VALUES (140, 235);
INSERT INTO `help_relation` VALUES (194, 235);
INSERT INTO `help_relation` VALUES (196, 235);
INSERT INTO `help_relation` VALUES (259, 235);
INSERT INTO `help_relation` VALUES (281, 235);
INSERT INTO `help_relation` VALUES (289, 235);
INSERT INTO `help_relation` VALUES (326, 235);
INSERT INTO `help_relation` VALUES (426, 235);
INSERT INTO `help_relation` VALUES (439, 235);
INSERT INTO `help_relation` VALUES (310, 236);
INSERT INTO `help_relation` VALUES (185, 237);
INSERT INTO `help_relation` VALUES (215, 238);
INSERT INTO `help_relation` VALUES (326, 239);
INSERT INTO `help_relation` VALUES (424, 239);
INSERT INTO `help_relation` VALUES (32, 240);
INSERT INTO `help_relation` VALUES (151, 240);
INSERT INTO `help_relation` VALUES (326, 240);
INSERT INTO `help_relation` VALUES (344, 240);
INSERT INTO `help_relation` VALUES (435, 240);
INSERT INTO `help_relation` VALUES (439, 241);
INSERT INTO `help_relation` VALUES (355, 242);
INSERT INTO `help_relation` VALUES (132, 243);
INSERT INTO `help_relation` VALUES (94, 244);
INSERT INTO `help_relation` VALUES (437, 245);
INSERT INTO `help_relation` VALUES (439, 246);
INSERT INTO `help_relation` VALUES (318, 247);
INSERT INTO `help_relation` VALUES (391, 248);
INSERT INTO `help_relation` VALUES (37, 249);
INSERT INTO `help_relation` VALUES (323, 250);
INSERT INTO `help_relation` VALUES (238, 251);
INSERT INTO `help_relation` VALUES (435, 252);
INSERT INTO `help_relation` VALUES (301, 253);
INSERT INTO `help_relation` VALUES (14, 254);
INSERT INTO `help_relation` VALUES (18, 254);
INSERT INTO `help_relation` VALUES (21, 254);
INSERT INTO `help_relation` VALUES (32, 254);
INSERT INTO `help_relation` VALUES (50, 254);
INSERT INTO `help_relation` VALUES (58, 254);
INSERT INTO `help_relation` VALUES (71, 254);
INSERT INTO `help_relation` VALUES (109, 254);
INSERT INTO `help_relation` VALUES (119, 254);
INSERT INTO `help_relation` VALUES (122, 254);
INSERT INTO `help_relation` VALUES (130, 254);
INSERT INTO `help_relation` VALUES (145, 254);
INSERT INTO `help_relation` VALUES (151, 254);
INSERT INTO `help_relation` VALUES (177, 254);
INSERT INTO `help_relation` VALUES (178, 254);
INSERT INTO `help_relation` VALUES (199, 254);
INSERT INTO `help_relation` VALUES (207, 254);
INSERT INTO `help_relation` VALUES (259, 254);
INSERT INTO `help_relation` VALUES (263, 254);
INSERT INTO `help_relation` VALUES (264, 254);
INSERT INTO `help_relation` VALUES (275, 254);
INSERT INTO `help_relation` VALUES (288, 254);
INSERT INTO `help_relation` VALUES (289, 254);
INSERT INTO `help_relation` VALUES (308, 254);
INSERT INTO `help_relation` VALUES (309, 254);
INSERT INTO `help_relation` VALUES (313, 254);
INSERT INTO `help_relation` VALUES (326, 254);
INSERT INTO `help_relation` VALUES (328, 254);
INSERT INTO `help_relation` VALUES (344, 254);
INSERT INTO `help_relation` VALUES (377, 254);
INSERT INTO `help_relation` VALUES (424, 254);
INSERT INTO `help_relation` VALUES (456, 254);
INSERT INTO `help_relation` VALUES (459, 254);
INSERT INTO `help_relation` VALUES (439, 255);
INSERT INTO `help_relation` VALUES (185, 256);
INSERT INTO `help_relation` VALUES (230, 256);
INSERT INTO `help_relation` VALUES (285, 256);
INSERT INTO `help_relation` VALUES (334, 256);
INSERT INTO `help_relation` VALUES (307, 257);
INSERT INTO `help_relation` VALUES (439, 258);
INSERT INTO `help_relation` VALUES (109, 259);
INSERT INTO `help_relation` VALUES (24, 260);
INSERT INTO `help_relation` VALUES (49, 260);
INSERT INTO `help_relation` VALUES (74, 260);
INSERT INTO `help_relation` VALUES (214, 260);
INSERT INTO `help_relation` VALUES (306, 260);
INSERT INTO `help_relation` VALUES (323, 260);
INSERT INTO `help_relation` VALUES (463, 260);
INSERT INTO `help_relation` VALUES (353, 261);
INSERT INTO `help_relation` VALUES (132, 262);
INSERT INTO `help_relation` VALUES (296, 262);
INSERT INTO `help_relation` VALUES (294, 263);
INSERT INTO `help_relation` VALUES (93, 264);
INSERT INTO `help_relation` VALUES (353, 265);
INSERT INTO `help_relation` VALUES (37, 266);
INSERT INTO `help_relation` VALUES (237, 266);
INSERT INTO `help_relation` VALUES (241, 266);
INSERT INTO `help_relation` VALUES (282, 266);
INSERT INTO `help_relation` VALUES (334, 266);
INSERT INTO `help_relation` VALUES (145, 267);
INSERT INTO `help_relation` VALUES (326, 267);
INSERT INTO `help_relation` VALUES (126, 268);
INSERT INTO `help_relation` VALUES (66, 269);
INSERT INTO `help_relation` VALUES (185, 269);
INSERT INTO `help_relation` VALUES (173, 270);
INSERT INTO `help_relation` VALUES (169, 271);
INSERT INTO `help_relation` VALUES (427, 272);
INSERT INTO `help_relation` VALUES (20, 273);
INSERT INTO `help_relation` VALUES (97, 273);
INSERT INTO `help_relation` VALUES (353, 274);
INSERT INTO `help_relation` VALUES (173, 275);
INSERT INTO `help_relation` VALUES (395, 276);
INSERT INTO `help_relation` VALUES (106, 277);
INSERT INTO `help_relation` VALUES (367, 277);
INSERT INTO `help_relation` VALUES (434, 278);
INSERT INTO `help_relation` VALUES (21, 279);
INSERT INTO `help_relation` VALUES (185, 280);
INSERT INTO `help_relation` VALUES (131, 281);
INSERT INTO `help_relation` VALUES (173, 282);
INSERT INTO `help_relation` VALUES (353, 283);
INSERT INTO `help_relation` VALUES (185, 284);
INSERT INTO `help_relation` VALUES (326, 285);
INSERT INTO `help_relation` VALUES (355, 285);
INSERT INTO `help_relation` VALUES (360, 286);
INSERT INTO `help_relation` VALUES (77, 287);
INSERT INTO `help_relation` VALUES (109, 287);
INSERT INTO `help_relation` VALUES (334, 287);
INSERT INTO `help_relation` VALUES (434, 288);
INSERT INTO `help_relation` VALUES (334, 289);
INSERT INTO `help_relation` VALUES (185, 290);
INSERT INTO `help_relation` VALUES (75, 291);
INSERT INTO `help_relation` VALUES (185, 291);
INSERT INTO `help_relation` VALUES (334, 292);
INSERT INTO `help_relation` VALUES (373, 293);
INSERT INTO `help_relation` VALUES (77, 294);
INSERT INTO `help_relation` VALUES (136, 294);
INSERT INTO `help_relation` VALUES (162, 294);
INSERT INTO `help_relation` VALUES (173, 295);
INSERT INTO `help_relation` VALUES (395, 296);
INSERT INTO `help_relation` VALUES (46, 297);
INSERT INTO `help_relation` VALUES (305, 297);
INSERT INTO `help_relation` VALUES (185, 298);
INSERT INTO `help_relation` VALUES (110, 299);
INSERT INTO `help_relation` VALUES (173, 300);
INSERT INTO `help_relation` VALUES (353, 301);
INSERT INTO `help_relation` VALUES (131, 302);
INSERT INTO `help_relation` VALUES (419, 302);
INSERT INTO `help_relation` VALUES (383, 303);
INSERT INTO `help_relation` VALUES (353, 304);
INSERT INTO `help_relation` VALUES (129, 305);
INSERT INTO `help_relation` VALUES (20, 306);
INSERT INTO `help_relation` VALUES (96, 307);
INSERT INTO `help_relation` VALUES (206, 307);
INSERT INTO `help_relation` VALUES (434, 307);
INSERT INTO `help_relation` VALUES (52, 308);
INSERT INTO `help_relation` VALUES (144, 308);
INSERT INTO `help_relation` VALUES (185, 308);
INSERT INTO `help_relation` VALUES (197, 308);
INSERT INTO `help_relation` VALUES (411, 308);
INSERT INTO `help_relation` VALUES (434, 308);
INSERT INTO `help_relation` VALUES (439, 309);
INSERT INTO `help_relation` VALUES (1, 310);
INSERT INTO `help_relation` VALUES (1, 311);
INSERT INTO `help_relation` VALUES (334, 311);
INSERT INTO `help_relation` VALUES (1, 312);
INSERT INTO `help_relation` VALUES (326, 313);
INSERT INTO `help_relation` VALUES (328, 313);
INSERT INTO `help_relation` VALUES (395, 314);
INSERT INTO `help_relation` VALUES (399, 315);
INSERT INTO `help_relation` VALUES (66, 316);
INSERT INTO `help_relation` VALUES (185, 316);
INSERT INTO `help_relation` VALUES (447, 316);
INSERT INTO `help_relation` VALUES (212, 317);
INSERT INTO `help_relation` VALUES (436, 317);
INSERT INTO `help_relation` VALUES (334, 318);
INSERT INTO `help_relation` VALUES (93, 319);
INSERT INTO `help_relation` VALUES (461, 320);
INSERT INTO `help_relation` VALUES (58, 321);
INSERT INTO `help_relation` VALUES (326, 321);
INSERT INTO `help_relation` VALUES (257, 322);
INSERT INTO `help_relation` VALUES (419, 323);
INSERT INTO `help_relation` VALUES (334, 324);
INSERT INTO `help_relation` VALUES (391, 325);
INSERT INTO `help_relation` VALUES (439, 326);
INSERT INTO `help_relation` VALUES (131, 327);
INSERT INTO `help_relation` VALUES (306, 327);
INSERT INTO `help_relation` VALUES (71, 328);
INSERT INTO `help_relation` VALUES (391, 329);
INSERT INTO `help_relation` VALUES (353, 330);
INSERT INTO `help_relation` VALUES (185, 331);
INSERT INTO `help_relation` VALUES (353, 332);
INSERT INTO `help_relation` VALUES (185, 333);
INSERT INTO `help_relation` VALUES (439, 333);
INSERT INTO `help_relation` VALUES (443, 333);
INSERT INTO `help_relation` VALUES (415, 334);
INSERT INTO `help_relation` VALUES (263, 335);
INSERT INTO `help_relation` VALUES (419, 336);
INSERT INTO `help_relation` VALUES (420, 337);
INSERT INTO `help_relation` VALUES (115, 338);
INSERT INTO `help_relation` VALUES (26, 339);
INSERT INTO `help_relation` VALUES (257, 339);
INSERT INTO `help_relation` VALUES (443, 339);
INSERT INTO `help_relation` VALUES (48, 340);
INSERT INTO `help_relation` VALUES (419, 341);
INSERT INTO `help_relation` VALUES (73, 342);
INSERT INTO `help_relation` VALUES (190, 342);
INSERT INTO `help_relation` VALUES (347, 342);
INSERT INTO `help_relation` VALUES (428, 342);
INSERT INTO `help_relation` VALUES (73, 343);
INSERT INTO `help_relation` VALUES (140, 343);
INSERT INTO `help_relation` VALUES (190, 343);
INSERT INTO `help_relation` VALUES (292, 343);
INSERT INTO `help_relation` VALUES (171, 344);
INSERT INTO `help_relation` VALUES (307, 345);
INSERT INTO `help_relation` VALUES (439, 346);
INSERT INTO `help_relation` VALUES (131, 347);
INSERT INTO `help_relation` VALUES (305, 347);
INSERT INTO `help_relation` VALUES (431, 348);
INSERT INTO `help_relation` VALUES (24, 349);
INSERT INTO `help_relation` VALUES (26, 349);
INSERT INTO `help_relation` VALUES (140, 349);
INSERT INTO `help_relation` VALUES (174, 349);
INSERT INTO `help_relation` VALUES (257, 349);
INSERT INTO `help_relation` VALUES (448, 349);
INSERT INTO `help_relation` VALUES (434, 350);
INSERT INTO `help_relation` VALUES (435, 351);
INSERT INTO `help_relation` VALUES (66, 352);
INSERT INTO `help_relation` VALUES (206, 352);
INSERT INTO `help_relation` VALUES (311, 352);
INSERT INTO `help_relation` VALUES (439, 353);
INSERT INTO `help_relation` VALUES (93, 354);
INSERT INTO `help_relation` VALUES (293, 355);
INSERT INTO `help_relation` VALUES (288, 356);
INSERT INTO `help_relation` VALUES (326, 356);
INSERT INTO `help_relation` VALUES (434, 356);
INSERT INTO `help_relation` VALUES (42, 357);
INSERT INTO `help_relation` VALUES (72, 357);
INSERT INTO `help_relation` VALUES (93, 357);
INSERT INTO `help_relation` VALUES (109, 357);
INSERT INTO `help_relation` VALUES (334, 357);
INSERT INTO `help_relation` VALUES (52, 358);
INSERT INTO `help_relation` VALUES (91, 358);
INSERT INTO `help_relation` VALUES (434, 358);
INSERT INTO `help_relation` VALUES (439, 358);
INSERT INTO `help_relation` VALUES (443, 358);
INSERT INTO `help_relation` VALUES (439, 359);
INSERT INTO `help_relation` VALUES (214, 360);
INSERT INTO `help_relation` VALUES (334, 361);
INSERT INTO `help_relation` VALUES (37, 362);
INSERT INTO `help_relation` VALUES (91, 362);
INSERT INTO `help_relation` VALUES (455, 362);
INSERT INTO `help_relation` VALUES (441, 363);
INSERT INTO `help_relation` VALUES (434, 364);
INSERT INTO `help_relation` VALUES (439, 364);
INSERT INTO `help_relation` VALUES (224, 365);
INSERT INTO `help_relation` VALUES (439, 365);
INSERT INTO `help_relation` VALUES (439, 366);
INSERT INTO `help_relation` VALUES (443, 366);
INSERT INTO `help_relation` VALUES (30, 367);
INSERT INTO `help_relation` VALUES (116, 368);
INSERT INTO `help_relation` VALUES (122, 368);
INSERT INTO `help_relation` VALUES (328, 368);
INSERT INTO `help_relation` VALUES (419, 368);
INSERT INTO `help_relation` VALUES (140, 369);
INSERT INTO `help_relation` VALUES (174, 369);
INSERT INTO `help_relation` VALUES (197, 369);
INSERT INTO `help_relation` VALUES (289, 369);
INSERT INTO `help_relation` VALUES (326, 369);
INSERT INTO `help_relation` VALUES (73, 370);
INSERT INTO `help_relation` VALUES (347, 370);
INSERT INTO `help_relation` VALUES (443, 370);
INSERT INTO `help_relation` VALUES (452, 371);
INSERT INTO `help_relation` VALUES (437, 372);
INSERT INTO `help_relation` VALUES (31, 373);
INSERT INTO `help_relation` VALUES (46, 373);
INSERT INTO `help_relation` VALUES (130, 373);
INSERT INTO `help_relation` VALUES (207, 373);
INSERT INTO `help_relation` VALUES (305, 373);
INSERT INTO `help_relation` VALUES (395, 374);
INSERT INTO `help_relation` VALUES (238, 375);
INSERT INTO `help_relation` VALUES (334, 376);
INSERT INTO `help_relation` VALUES (340, 376);
INSERT INTO `help_relation` VALUES (434, 377);
INSERT INTO `help_relation` VALUES (395, 378);
INSERT INTO `help_relation` VALUES (439, 379);
INSERT INTO `help_relation` VALUES (463, 380);
INSERT INTO `help_relation` VALUES (185, 381);
INSERT INTO `help_relation` VALUES (0, 382);
INSERT INTO `help_relation` VALUES (84, 382);
INSERT INTO `help_relation` VALUES (270, 382);
INSERT INTO `help_relation` VALUES (285, 382);
INSERT INTO `help_relation` VALUES (334, 382);
INSERT INTO `help_relation` VALUES (340, 382);
INSERT INTO `help_relation` VALUES (361, 382);
INSERT INTO `help_relation` VALUES (405, 382);
INSERT INTO `help_relation` VALUES (464, 383);
INSERT INTO `help_relation` VALUES (30, 384);
INSERT INTO `help_relation` VALUES (101, 384);
INSERT INTO `help_relation` VALUES (307, 384);
INSERT INTO `help_relation` VALUES (395, 384);
INSERT INTO `help_relation` VALUES (437, 384);
INSERT INTO `help_relation` VALUES (441, 384);
INSERT INTO `help_relation` VALUES (173, 385);
INSERT INTO `help_relation` VALUES (185, 386);
INSERT INTO `help_relation` VALUES (30, 387);
INSERT INTO `help_relation` VALUES (119, 387);
INSERT INTO `help_relation` VALUES (275, 387);
INSERT INTO `help_relation` VALUES (326, 387);
INSERT INTO `help_relation` VALUES (462, 388);
INSERT INTO `help_relation` VALUES (23, 389);
INSERT INTO `help_relation` VALUES (17, 390);
INSERT INTO `help_relation` VALUES (245, 390);
INSERT INTO `help_relation` VALUES (459, 391);
INSERT INTO `help_relation` VALUES (185, 392);
INSERT INTO `help_relation` VALUES (91, 393);
INSERT INTO `help_relation` VALUES (334, 393);
INSERT INTO `help_relation` VALUES (196, 394);
INSERT INTO `help_relation` VALUES (93, 395);
INSERT INTO `help_relation` VALUES (434, 395);
INSERT INTO `help_relation` VALUES (439, 395);
INSERT INTO `help_relation` VALUES (326, 396);
INSERT INTO `help_relation` VALUES (32, 397);
INSERT INTO `help_relation` VALUES (50, 397);
INSERT INTO `help_relation` VALUES (104, 397);
INSERT INTO `help_relation` VALUES (173, 397);
INSERT INTO `help_relation` VALUES (246, 397);
INSERT INTO `help_relation` VALUES (339, 397);
INSERT INTO `help_relation` VALUES (435, 397);
INSERT INTO `help_relation` VALUES (193, 398);
INSERT INTO `help_relation` VALUES (439, 398);
INSERT INTO `help_relation` VALUES (184, 399);
INSERT INTO `help_relation` VALUES (439, 400);

-- --------------------------------------------------------

-- 
-- 資料表格式： `help_topic`
-- 

CREATE TABLE `help_topic` (
  `help_topic_id` int(10) unsigned NOT NULL,
  `name` char(64) NOT NULL,
  `help_category_id` smallint(5) unsigned NOT NULL,
  `description` text NOT NULL,
  `example` text NOT NULL,
  `url` char(128) NOT NULL,
  PRIMARY KEY  (`help_topic_id`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='help topics';

-- 
-- 列出以下資料庫的數據： `help_topic`
-- 

INSERT INTO `help_topic` VALUES (0, 'MIN', 14, 'Syntax:\nMIN([DISTINCT] expr)\n\nReturns the minimum value of expr. MIN() may take a string argument; in\nsuch cases, it returns the minimum string value. See\nhttp://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html. The DISTINCT\nkeyword can be used to find the minimum of the distinct values of expr,\nhowever, this produces the same result as omitting DISTINCT.\n\nMIN() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', 'mysql> SELECT student_name, MIN(test_score), MAX(test_score)\n    ->        FROM student\n    ->        GROUP BY student_name;\n', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (1, 'JOIN', 25, 'MySQL supports the following JOIN syntaxes for the table_references\npart of SELECT statements and multiple-table DELETE and UPDATE\nstatements:\n\ntable_references:\n    table_reference [, table_reference] ...\n\ntable_reference:\n    table_factor\n  | join_table\n\ntable_factor:\n    tbl_name [[AS] alias] [index_hint)]\n  | ( table_references )\n  | { OJ table_reference LEFT OUTER JOIN table_reference\n        ON conditional_expr }\n\njoin_table:\n    table_reference [INNER | CROSS] JOIN table_factor [join_condition]\n  | table_reference STRAIGHT_JOIN table_factor\n  | table_reference STRAIGHT_JOIN table_factor ON condition\n  | table_reference LEFT [OUTER] JOIN table_reference join_condition\n  | table_reference NATURAL [LEFT [OUTER]] JOIN table_factor\n  | table_reference RIGHT [OUTER] JOIN table_reference join_condition\n  | table_reference NATURAL [RIGHT [OUTER]] JOIN table_factor\n\njoin_condition:\n    ON conditional_expr\n  | USING (column_list)\n\nindex_hint:\n    USE {INDEX|KEY} [FOR JOIN] (index_list)\n  | IGNORE {INDEX|KEY} [FOR JOIN] (index_list)\n  | FORCE {INDEX|KEY} [FOR JOIN] (index_list)\n\nindex_list:\n    index_name [, index_name] ...\n\nA table reference is also known as a join expression.\n\nThe syntax of table_factor is extended in comparison with the SQL\nStandard. The latter accepts only table_reference, not a list of them\ninside a pair of parentheses.\n\nThis is a conservative extension if we consider each comma in a list of\ntable_reference items as equivalent to an inner join. For example:\n\nSELECT * FROM t1 LEFT JOIN (t2, t3, t4)\n                 ON (t2.a=t1.a AND t3.b=t1.b AND t4.c=t1.c)\n\nis equivalent to:\n\nSELECT * FROM t1 LEFT JOIN (t2 CROSS JOIN t3 CROSS JOIN t4)\n                 ON (t2.a=t1.a AND t3.b=t1.b AND t4.c=t1.c)\n\nIn MySQL, CROSS JOIN is a syntactic equivalent to INNER JOIN (they can\nreplace each other). In standard SQL, they are not equivalent. INNER\nJOIN is used with an ON clause, CROSS JOIN is used otherwise.\n\nIn versions of MySQL prior to 5.0.1, parentheses in table_references\nwere just omitted and all join operations were grouped to the left. In\ngeneral, parentheses can be ignored in join expressions containing only\ninner join operations. As of 5.0.1, nested joins are allowed (see\nhttp://dev.mysql.com/doc/refman/5.0/en/nested-joins.html).\n\nFurther changes in join processing were made in 5.0.12 to make MySQL\nmore compliant with standard SQL. These charges are described later in\nthis section.\n\nIndex hints can be specified to affect how the MySQL optimizer makes\nuse of indexes. For more information, see\nhttp://dev.mysql.com/doc/refman/5.0/en/index-hints.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/join.html\n\n', 'SELECT left_tbl.*\n  FROM left_tbl LEFT JOIN right_tbl ON left_tbl.id = right_tbl.id\n  WHERE right_tbl.id IS NULL;\n', 'http://dev.mysql.com/doc/refman/5.0/en/join.html');
INSERT INTO `help_topic` VALUES (2, 'HEX', 33, 'Syntax:\nHEX(N_or_S)\n\nIf N_or_S is a number, returns a string representation of the\nhexadecimal value of N, where N is a longlong (BIGINT) number. This is\nequivalent to CONV(N,10,16).\n\nIf N_or_S is a string, returns a hexadecimal string representation of\nN_or_S where each character in N_or_S is converted to two hexadecimal\ndigits. The inverse of this operation is performed by the UNHEX()\nfunction.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT HEX(255);\n        -> ''FF''\nmysql> SELECT 0x616263;\n        -> ''abc''\nmysql> SELECT HEX(''abc'');\n        -> 616263\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (3, 'REPLACE', 33, 'Syntax:\nREPLACE(str,from_str,to_str)\n\nReturns the string str with all occurrences of the string from_str\nreplaced by the string to_str. REPLACE() performs a case-sensitive\nmatch when searching for from_str.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT REPLACE(''www.mysql.com'', ''w'', ''Ww'');\n        -> ''WwWwWw.mysql.com''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (4, 'CONTAINS', 26, 'Contains(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 completely contains g2. This\ntests the opposite relationship as Within().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (5, 'SRID', 32, 'SRID(g)\n\nReturns an integer indicating the Spatial Reference System ID for the\ngeometry value g.\n\nIn MySQL, the SRID value is just an integer associated with the\ngeometry value. All calculations are done assuming Euclidean (planar)\ngeometry.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html\n\n', 'mysql> SELECT SRID(GeomFromText(''LineString(1 1,2 2)'',101));\n+-----------------------------------------------+\n| SRID(GeomFromText(''LineString(1 1,2 2)'',101)) |\n+-----------------------------------------------+\n|                                           101 |\n+-----------------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (6, 'CURRENT_TIMESTAMP', 28, 'Syntax:\nCURRENT_TIMESTAMP, CURRENT_TIMESTAMP()\n\nCURRENT_TIMESTAMP and CURRENT_TIMESTAMP() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (7, 'VARIANCE', 14, 'Syntax:\nVARIANCE(expr)\n\nReturns the population standard variance of expr. This is an extension\nto standard SQL. As of MySQL 5.0.3, the standard SQL function VAR_POP()\ncan be used instead.\n\nVARIANCE() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (8, 'VAR_SAMP', 14, 'Syntax:\nVAR_SAMP(expr)\n\nReturns the sample variance of expr. That is, the denominator is the\nnumber of rows minus one. This function was added in MySQL 5.0.3.\n\nVAR_SAMP() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (9, 'CONCAT', 33, 'Syntax:\nCONCAT(str1,str2,...)\n\nReturns the string that results from concatenating the arguments. May\nhave one or more arguments. If all arguments are non-binary strings,\nthe result is a non-binary string. If the arguments include any binary\nstrings, the result is a binary string. A numeric argument is converted\nto its equivalent binary string form; if you want to avoid that, you\ncan use an explicit type cast, as in this example:\n\nSELECT CONCAT(CAST(int_col AS CHAR), char_col);\n\nCONCAT() returns NULL if any argument is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT CONCAT(''My'', ''S'', ''QL'');\n        -> ''MySQL''\nmysql> SELECT CONCAT(''My'', NULL, ''QL'');\n        -> NULL\nmysql> SELECT CONCAT(14.3);\n        -> ''14.3''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (10, 'GEOMETRY HIERARCHY', 30, 'Geometry is the base class. It is an abstract class. The instantiable\nsubclasses of Geometry are restricted to zero-, one-, and\ntwo-dimensional geometric objects that exist in two-dimensional\ncoordinate space. All instantiable geometry classes are defined so that\nvalid instances of a geometry class are topologically closed (that is,\nall defined geometries include their boundary).\n\nThe base Geometry class has subclasses for Point, Curve, Surface, and\nGeometryCollection:\n\no Point represents zero-dimensional objects.\n\no Curve represents one-dimensional objects, and has subclass\n  LineString, with sub-subclasses Line and LinearRing.\n\no Surface is designed for two-dimensional objects and has subclass\n  Polygon.\n\no GeometryCollection has specialized zero-, one-, and two-dimensional\n  collection classes named MultiPoint, MultiLineString, and\n  MultiPolygon for modeling geometries corresponding to collections of\n  Points, LineStrings, and Polygons, respectively. MultiCurve and\n  MultiSurface are introduced as abstract superclasses that generalize\n  the collection interfaces to handle Curves and Surfaces.\n\nGeometry, Curve, Surface, MultiCurve, and MultiSurface are defined as\nnon-instantiable classes. They define a common set of methods for their\nsubclasses and are included for extensibility.\n\nPoint, LineString, Polygon, GeometryCollection, MultiPoint,\nMultiLineString, and MultiPolygon are instantiable classes.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-geometry-class-hierarchy.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-geometry-class-hierarchy.html');
INSERT INTO `help_topic` VALUES (11, 'CHAR FUNCTION', 33, 'Syntax:\nCHAR(N,... [USING charset_name])\n\nCHAR() interprets each argument N as an integer and returns a string\nconsisting of the characters given by the code values of those\nintegers. NULL values are skipped.\nAs of MySQL 5.0.15, CHAR() arguments larger than 255 are converted into\nmultiple result bytes. For example, CHAR(256) is equivalent to\nCHAR(1,0), and CHAR(256*256) is equivalent to CHAR(1,0,0):\n\nmysql> SELECT HEX(CHAR(1,0)), HEX(CHAR(256));\n+----------------+----------------+\n| HEX(CHAR(1,0)) | HEX(CHAR(256)) |\n+----------------+----------------+\n| 0100           | 0100           |\n+----------------+----------------+\nmysql> SELECT HEX(CHAR(1,0,0)), HEX(CHAR(256*256));\n+------------------+--------------------+\n| HEX(CHAR(1,0,0)) | HEX(CHAR(256*256)) |\n+------------------+--------------------+\n| 010000           | 010000             |\n+------------------+--------------------+\n\nBy default, CHAR() returns a binary string. To produce a string in a\ngiven character set, use the optional USING clause:\n\nmysql> SELECT CHARSET(CHAR(0x65)), CHARSET(CHAR(0x65 USING utf8));\n+---------------------+--------------------------------+\n| CHARSET(CHAR(0x65)) | CHARSET(CHAR(0x65 USING utf8)) |\n+---------------------+--------------------------------+\n| binary              | utf8                           |\n+---------------------+--------------------------------+\n\nIf USING is given and the result string is illegal for the given\ncharacter set, a warning is issued. Also, if strict SQL mode is\nenabled, the result from CHAR() becomes NULL.\n\nBefore MySQL 5.0.15, CHAR() returns a string in the connection\ncharacter set and the USING clause is unavailable. In addition, each\nargument is interpreted modulo 256, so CHAR(256) and CHAR(256*256) both\nare equivalent to CHAR(0).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT CHAR(77,121,83,81,''76'');\n        -> ''MySQL''\nmysql> SELECT CHAR(77,77.3,''77.3'');\n        -> ''MMM''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (12, 'DATETIME', 20, 'DATETIME\n\nA date and time combination. The supported range is ''1000-01-01\n00:00:00'' to ''9999-12-31 23:59:59''. MySQL displays DATETIME values in\n''YYYY-MM-DD HH:MM:SS'' format, but allows assignment of values to\nDATETIME columns using either strings or numbers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html');
INSERT INTO `help_topic` VALUES (13, 'OPEN', 35, 'Syntax:\nOPEN cursor_name\n\nThis statement opens a previously declared cursor.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/open.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/open.html');
INSERT INTO `help_topic` VALUES (14, 'SHOW CREATE PROCEDURE', 25, 'Syntax:\nSHOW CREATE {PROCEDURE | FUNCTION} sp_name\n\nThese statements are MySQL extensions. Similar to SHOW CREATE TABLE,\nthey return the exact string that can be used to re-create the named\nroutine. The statements require that you be the owner of the routine or\nhave SELECT access to the mysql.proc table. If you do not have\nprivileges for the routine itself, the value displayed for the Create\nProcedure or Create Function field will be NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-create-procedure.html\n\n', 'mysql> SHOW CREATE FUNCTION test.hello\\G\n*************************** 1. row ***************************\n       Function: hello\n       sql_mode:\nCreate Function: CREATE FUNCTION `test`.`hello`(s CHAR(20)) RETURNS CHAR(50)\n                 RETURN CONCAT(''Hello, '',s,''!'')\n', 'http://dev.mysql.com/doc/refman/5.0/en/show-create-procedure.html');
INSERT INTO `help_topic` VALUES (15, 'INTEGER', 20, 'INTEGER[(M)] [UNSIGNED] [ZEROFILL]\n\nThis type is a synonym for INT.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (16, 'LOWER', 33, 'Syntax:\nLOWER(str)\n\nReturns the string str with all characters changed to lowercase\naccording to the current character set mapping. The default is latin1\n(cp1252 West European).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LOWER(''QUADRATICALLY'');\n        -> ''quadratically''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (17, 'CREATE TRIGGER', 21, 'Syntax:\nCREATE\n    [DEFINER = { user | CURRENT_USER }]\n    TRIGGER trigger_name trigger_time trigger_event\n    ON tbl_name FOR EACH ROW trigger_stmt\n\nThis statement creates a new trigger. A trigger is a named database\nobject that is associated with a table, and that activates when a\nparticular event occurs for the table. CREATE TRIGGER was added in\nMySQL 5.0.2. Currently, its use requires the SUPER privilege.\n\nThe trigger becomes associated with the table named tbl_name, which\nmust refer to a permanent table. You cannot associate a trigger with a\nTEMPORARY table or a view.\n\nWhen the trigger is activated, the DEFINER clause determines the\nprivileges that apply, as described later in this section.\n\ntrigger_time is the trigger action time. It can be BEFORE or AFTER to\nindicate that the trigger activates before or after the statement that\nactivated it.\n\ntrigger_event indicates the kind of statement that activates the\ntrigger. The trigger_event can be one of the following:\n\no INSERT: The trigger is activated whenever a new row is inserted into\n  the table; for example, through INSERT, LOAD DATA, and REPLACE\n  statements.\n\no UPDATE: The trigger is activated whenever a row is modified; for\n  example, through UPDATE statements.\n\no DELETE: The trigger is activated whenever a row is deleted from the\n  table; for example, through DELETE and REPLACE statements. However,\n  DROP TABLE and TRUNCATE statements on the table do not activate this\n  trigger, because they do not use DELETE. See [HELP TRUNCATE TABLE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-trigger.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-trigger.html');
INSERT INTO `help_topic` VALUES (18, 'SHOW COLUMNS', 25, 'Syntax:\nSHOW [FULL] COLUMNS FROM tbl_name [FROM db_name]\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW COLUMNS displays information about the columns in a given table.\nIt also works for views as of MySQL 5.0.1. The LIKE clause, if present,\nindicates which column names to match. The WHERE clause can be given to\nselect rows using more general conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nIf the data types differ from what you expect them to be based on your\nCREATE TABLE statement, note that MySQL sometimes changes data types\nwhen you create or alter a table. The conditions for which this occurs\nare described in\nhttp://dev.mysql.com/doc/refman/5.0/en/silent-column-changes.html.\n\nThe FULL keyword causes the output to include the privileges you have\nas well as any per-column comments for each column.\n\nYou can use db_name.tbl_name as an alternative to the tbl_name FROM\ndb_name syntax. In other words, these two statements are equivalent:\n\nmysql> SHOW COLUMNS FROM mytable FROM mydb;\nmysql> SHOW COLUMNS FROM mydb.mytable;\n\nSHOW FIELDS is a synonym for SHOW COLUMNS. You can also list a table''s\ncolumns with the mysqlshow db_name tbl_name command.\n\nThe DESCRIBE statement provides information similar to SHOW COLUMNS.\nSee [HELP DESCRIBE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-columns.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-columns.html');
INSERT INTO `help_topic` VALUES (19, 'MONTH', 28, 'Syntax:\nMONTH(date)\n\nReturns the month for date, in the range 1 to 12 for January to\nDecember, or 0 for dates such as ''0000-00-00'' or ''2008-00-00'' that have\na zero month part.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MONTH(''1998-02-03'');\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (20, 'TINYINT', 20, 'TINYINT[(M)] [UNSIGNED] [ZEROFILL]\n\nA very small integer. The signed range is -128 to 127. The unsigned\nrange is 0 to 255.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (21, 'SHOW TRIGGERS', 25, 'Syntax:\nSHOW TRIGGERS [FROM db_name]\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW TRIGGERS lists the triggers currently defined on the MySQL server.\nThis statement requires the SUPER privilege. It was implemented in\nMySQL 5.0.10. The LIKE clause, if present, indicates which trigger\nnames to match. The WHERE clause can be given to select rows using more\ngeneral conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nFor the trigger ins_sum as defined in\nhttp://dev.mysql.com/doc/refman/5.0/en/using-triggers.html, the output\nof this statement is as shown here:\n\nmysql> SHOW TRIGGERS LIKE ''acc%''\\G\n*************************** 1. row ***************************\n  Trigger: ins_sum\n    Event: INSERT\n    Table: account\nStatement: SET @sum = @sum + NEW.amount\n   Timing: BEFORE\n  Created: NULL\n sql_mode:\n  Definer: myname@localhost\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-triggers.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-triggers.html');
INSERT INTO `help_topic` VALUES (22, 'MASTER_POS_WAIT', 13, 'Syntax:\nMASTER_POS_WAIT(log_name,log_pos[,timeout])\n\nThis function is useful for control of master/slave synchronization. It\nblocks until the slave has read and applied all updates up to the\nspecified position in the master log. The return value is the number of\nlog events the slave had to wait for to advance to the specified\nposition. The function returns NULL if the slave SQL thread is not\nstarted, the slave''s master information is not initialized, the\narguments are incorrect, or an error occurs. It returns -1 if the\ntimeout has been exceeded. If the slave SQL thread stops while\nMASTER_POS_WAIT() is waiting, the function returns NULL. If the slave\nis past the specified position, the function returns immediately.\n\nIf a timeout value is specified, MASTER_POS_WAIT() stops waiting when\ntimeout seconds have elapsed. timeout must be greater than 0; a zero or\nnegative timeout means no timeout.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (23, 'REGEXP', 33, 'Syntax:\nexpr REGEXP pat, expr RLIKE pat\n\nPerforms a pattern match of a string expression expr against a pattern\npat. The pattern can be an extended regular expression. The syntax for\nregular expressions is discussed in\nhttp://dev.mysql.com/doc/refman/5.0/en/regexp.html. Returns 1 if expr\nmatches pat; otherwise it returns 0. If either expr or pat is NULL, the\nresult is NULL. RLIKE is a synonym for REGEXP, provided for mSQL\ncompatibility.\n\nThe pattern need not be a literal string. For example, it can be\nspecified as a string expression or table column.\n\n*Note*: Because MySQL uses the C escape syntax in strings (for example,\n"\\n" to represent the newline character), you must double any "\\" that\nyou use in your REGEXP strings.\n\nREGEXP is not case sensitive, except when used with binary strings.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html\n\n', 'mysql> SELECT ''Monty!'' REGEXP ''m%y%%'';\n        -> 0\nmysql> SELECT ''Monty!'' REGEXP ''.*'';\n        -> 1\nmysql> SELECT ''new*\\n*line'' REGEXP ''new\\\\*.\\\\*line'';\n        -> 1\nmysql> SELECT ''a'' REGEXP ''A'', ''a'' REGEXP BINARY ''A'';\n        -> 1  0\nmysql> SELECT ''a'' REGEXP ''^[a-d]'';\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html');
INSERT INTO `help_topic` VALUES (24, 'IF STATEMENT', 35, 'Syntax:\nIF search_condition THEN statement_list\n    [ELSEIF search_condition THEN statement_list] ...\n    [ELSE statement_list]\nEND IF\n\nIF implements a basic conditional construct. If the search_condition\nevaluates to true, the corresponding SQL statement list is executed. If\nno search_condition matches, the statement list in the ELSE clause is\nexecuted. Each statement_list consists of one or more statements.\n\n*Note*: There is also an IF() function, which differs from the IF\nstatement described here. See [HELP CASE operator].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/if-statement.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/if-statement.html');
INSERT INTO `help_topic` VALUES (25, '^', 18, 'Syntax:\n^\n\nBitwise XOR:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 1 ^ 1;\n        -> 0\nmysql> SELECT 1 ^ 0;\n        -> 1\nmysql> SELECT 11 ^ 3;\n        -> 8\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (26, 'DROP VIEW', 36, 'Syntax:\nDROP VIEW [IF EXISTS]\n    view_name [, view_name] ...\n    [RESTRICT | CASCADE]\n\nDROP VIEW removes one or more views. You must have the DROP privilege\nfor each view. If any of the views named in the argument list do not\nexist, MySQL returns an error indicating by name which non-existing\nviews it was unable to drop, but it also drops all of the views in the\nlist that do exist.\n\nThe IF EXISTS clause prevents an error from occurring for views that\ndon''t exist. When this clause is given, a NOTE is generated for each\nnon-existent view. See [HELP SHOW WARNINGS].\n\nRESTRICT and CASCADE, if given, are parsed and ignored.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-view.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-view.html');
INSERT INTO `help_topic` VALUES (27, 'WITHIN', 26, 'Within(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 is spatially within g2. This\ntests the opposite relationship as Contains().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (28, 'WEEK', 28, 'Syntax:\nWEEK(date[,mode])\n\nThis function returns the week number for date. The two-argument form\nof WEEK() allows you to specify whether the week starts on Sunday or\nMonday and whether the return value should be in the range from 0 to 53\nor from 1 to 53. If the mode argument is omitted, the value of the\ndefault_week_format system variable is used. See\nhttp://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT WEEK(''1998-02-20'');\n        -> 7\nmysql> SELECT WEEK(''1998-02-20'',0);\n        -> 7\nmysql> SELECT WEEK(''1998-02-20'',1);\n        -> 8\nmysql> SELECT WEEK(''1998-12-31'',1);\n        -> 53\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (29, 'PREPARE', 25, 'Syntax:\nPREPARE stmt_name FROM preparable_stmt\n\nThe PREPARE statement prepares a statement and assigns it a name,\nstmt_name, by which to refer to the statement later. Statement names\nare not case sensitive. preparable_stmt is either a string literal or a\nuser variable that contains the text of the statement. The text must\nrepresent a single SQL statement, not multiple statements. Within the\nstatement, "?" characters can be used as parameter markers to indicate\nwhere data values are to be bound to the query later when you execute\nit. The "?" characters should not be enclosed within quotes, even if\nyou intend to bind them to string values. Parameter markers can be used\nonly where data values should appear, not for SQL keywords,\nidentifiers, and so forth.\n\nIf a prepared statement with the given name already exists, it is\ndeallocated implicitly before the new statement is prepared. This means\nthat if the new statement contains an error and cannot be prepared, an\nerror is returned and no statement with the given name exists.\n\nThe scope of a prepared statement is the client session within which it\nis created. Other clients cannot see it.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/sqlps.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/sqlps.html');
INSERT INTO `help_topic` VALUES (30, 'LOCK', 7, 'Syntax:\nLOCK TABLES\n    tbl_name [[AS] alias] lock_type\n    [, tbl_name [[AS] alias] lock_type] ...\n\nlock_type:\n    READ [LOCAL]\n  | [LOW_PRIORITY] WRITE\n\nUNLOCK TABLES\n\nLOCK TABLES acquires table locks for the current thread. It locks base\ntables but not views. To use LOCK TABLES, you must have the LOCK TABLES\nprivilege, and the SELECT privilege for each table to be locked.\n\nUNLOCK TABLES explicitly releases any table locks held by the current\nthread. Another use for UNLOCK TABLES is to release the global read\nlock acquired with FLUSH TABLES WITH READ LOCK. (You can lock all\ntables in all databases with read locks with the FLUSH TABLES WITH READ\nLOCK statement. See [HELP FLUSH]. This is a very convenient way to get\nbackups if you have a filesystem such as Veritas that can take\nsnapshots in time.)\n\nThe following general rules apply to acquisition and release of locks\nby a given thread:\n\no Table locks are acquired with LOCK TABLES.\n\no If the LOCK TABLES statement must wait due to locks held by other\n  threads on any of the tables, it blocks until all locks can be\n  acquired.\n\no Table locks are released explicitly with UNLOCK TABLES.\n\no Table locks are released implicitly under these conditions:\n\n  o LOCK TABLES releases any table locks currently held by the thread\n    before acquiring new locks.\n\n  o Beginning a transaction (for example, with START TRANSACTION)\n    implicitly performs an UNLOCK TABLES. (Additional information about\n    the interaction between table locking and transactions is given\n    later in the section.)\n\n  o If a client connection drops, the server releases table locks held\n    by the client. If the client reconnects, the locks will no longer\n    be in effect. For this reason, clients may wish to disable\n    auto-reconnect. With auto-reconnect in effect, the client is not\n    notified if reconnect occurs but any table locks will have been\n    lost. With auto-reconnect disabled, if the connection drops, an\n    error occurs for the next statement issued. The client can detect\n    the error and take appropriate action such as reacquiring the\n    locks. See\n    http://dev.mysql.com/doc/refman/5.0/en/auto-reconnect.html.\n\no One thread cannot release locks held by another thread.\n\n*Note*: If you use ALTER TABLE on a locked table, it may become\nunlocked. See\nhttp://dev.mysql.com/doc/refman/5.0/en/alter-table-problems.html.\n\nThe main reasons to use LOCK TABLES are to emulate transactions or to\nget more speed when updating tables. This is explained in more detail\nlater in this section.\n\nA table lock protects only against inappropriate reads or writes by\nother clients. The client holding the lock, even a read lock, can\nperform table-level operations such as DROP TABLE. Truncate operations\nare not transaction-safe, so an error occurs if the client attempts one\nduring an active transaction or while holding a table lock.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/lock-tables.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/lock-tables.html');
INSERT INTO `help_topic` VALUES (31, 'RESET SLAVE', 25, 'Syntax:\nRESET SLAVE\n\nRESET SLAVE makes the slave forget its replication position in the\nmaster''s binary logs. This statement is meant to be used for a clean\nstart: It deletes the master.info and relay-log.info files, all the\nrelay logs, and starts a new relay log.\n\n*Note*: All relay logs are deleted, even if they have not been\ncompletely executed by the slave SQL thread. (This is a condition\nlikely to exist on a replication slave if you have issued a STOP SLAVE\nstatement or if the slave is highly loaded.)\n\nConnection information stored in the master.info file is immediately\nreset using any values specified in the corresponding startup options.\nThis information includes values such as master host, master port,\nmaster user, and master password. If the slave SQL thread was in the\nmiddle of replicating temporary tables when it was stopped, and RESET\nSLAVE is issued, these replicated temporary tables are deleted on the\nslave.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/reset-slave.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/reset-slave.html');
INSERT INTO `help_topic` VALUES (32, 'SHOW BINARY LOGS', 25, 'Syntax:\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 [HELP PURGE MASTER LOGS], that shows\nhow to 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\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-binary-logs.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-binary-logs.html');
INSERT INTO `help_topic` VALUES (33, 'POLYGON', 22, 'Polygon(ls1,ls2,...)\n\nConstructs a WKB Polygon value from a number of WKB LineString\narguments. If any argument does not represent the WKB of a LinearRing\n(that is, not a closed and simple LineString) the return value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (34, 'MINUTE', 28, 'Syntax:\nMINUTE(time)\n\nReturns the minute for time, in the range 0 to 59.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MINUTE(''98-02-03 10:05:03'');\n        -> 5\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (35, 'DAY', 28, 'Syntax:\nDAY(date)\n\nDAY() is a synonym for DAYOFMONTH().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (36, 'MID', 33, 'Syntax:\nMID(str,pos,len)\n\nMID(str,pos,len) is a synonym for SUBSTRING(str,pos,len).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (37, 'REPLACE INTO', 25, 'Syntax:\nREPLACE [LOW_PRIORITY | DELAYED]\n    [INTO] tbl_name [(col_name,...)]\n    VALUES ({expr | DEFAULT},...),(...),...\n\nOr:\n\nREPLACE [LOW_PRIORITY | DELAYED]\n    [INTO] tbl_name\n    SET col_name={expr | DEFAULT}, ...\n\nOr:\n\nREPLACE [LOW_PRIORITY | DELAYED]\n    [INTO] tbl_name [(col_name,...)]\n    SELECT ...\n\nREPLACE works exactly like INSERT, except that if an old row in the\ntable has the same value as a new row for a PRIMARY KEY or a UNIQUE\nindex, the old row is deleted before the new row is inserted. See [HELP\nINSERT].\n\nREPLACE is a MySQL extension to the SQL standard. It either inserts, or\ndeletes and inserts. For another MySQL extension to standard SQL ---\nthat either inserts or updates --- see\nhttp://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html.\n\nNote that unless the table has a PRIMARY KEY or UNIQUE index, using a\nREPLACE statement makes no sense. It becomes equivalent to INSERT,\nbecause there is no index to be used to determine whether a new row\nduplicates another.\n\nValues for all columns are taken from the values specified in the\nREPLACE statement. Any missing columns are set to their default values,\njust as happens for INSERT. You cannot refer to values from the current\nrow and use them in the new row. If you use an assignment such as SET\ncol_name = col_name + 1, the reference to the column name on the right\nhand side is treated as DEFAULT(col_name), so the assignment is\nequivalent to SET col_name = DEFAULT(col_name) + 1.\n\nTo use REPLACE, you must have both the INSERT and DELETE privileges for\nthe table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/replace.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/replace.html');
INSERT INTO `help_topic` VALUES (38, 'UUID', 13, 'Syntax:\nUUID()\n\nReturns a Universal Unique Identifier (UUID) generated according to\n"DCE 1.1: Remote Procedure Call" (Appendix A) CAE (Common Applications\nEnvironment) Specifications published by The Open Group in October 1997\n(Document Number C706,\nhttp://www.opengroup.org/public/pubs/catalog/c706.htm).\n\nA UUID is designed as a number that is globally unique in space and\ntime. Two calls to UUID() are expected to generate two different\nvalues, even if these calls are performed on two separate computers\nthat are not connected to each other.\n\nA UUID is a 128-bit number represented by a string of five hexadecimal\nnumbers in aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee format:\n\no The first three numbers are generated from a timestamp.\n\no The fourth number preserves temporal uniqueness in case the timestamp\n  value loses monotonicity (for example, due to daylight saving time).\n\no The fifth number is an IEEE 802 node number that provides spatial\n  uniqueness. A random number is substituted if the latter is not\n  available (for example, because the host computer has no Ethernet\n  card, or we do not know how to find the hardware address of an\n  interface on your operating system). In this case, spatial uniqueness\n  cannot be guaranteed. Nevertheless, a collision should have very low\n  probability.\n\n  Currently, the MAC address of an interface is taken into account only\n  on FreeBSD and Linux. On other operating systems, MySQL uses a\n  randomly generated 48-bit number.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', 'mysql> SELECT UUID();\n        -> ''6ccd780c-baba-1026-9564-0040f4311e29''\n', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (39, 'LINESTRING', 22, 'LineString(pt1,pt2,...)\n\nConstructs a WKB LineString value from a number of WKB Point arguments.\nIf any argument is not a WKB Point, the return value is NULL. If the\nnumber of Point arguments is less than two, the return value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (40, 'SLEEP', 13, 'Syntax:\nSLEEP(duration)\n\nSleeps (pauses) for the number of seconds given by the duration\nargument, then returns 0. If SLEEP() is interrupted, it returns 1. The\nduration may have a fractional part given in microseconds. This\nfunction was added in MySQL 5.0.12.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (41, 'CONNECTION_ID', 15, 'Syntax:\nCONNECTION_ID()\n\nReturns the connection ID (thread ID) for the connection. Every\nconnection has an ID that is unique among the set of currently\nconnected clients.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT CONNECTION_ID();\n        -> 23786\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (42, 'DELETE', 25, 'Syntax:\nSingle-table syntax:\n\nDELETE [LOW_PRIORITY] [QUICK] [IGNORE] FROM tbl_name\n    [WHERE where_condition]\n    [ORDER BY ...]\n    [LIMIT row_count]\n\nMultiple-table syntax:\n\nDELETE [LOW_PRIORITY] [QUICK] [IGNORE]\n    tbl_name[.*] [, tbl_name[.*]] ...\n    FROM table_references\n    [WHERE where_condition]\n\nOr:\n\nDELETE [LOW_PRIORITY] [QUICK] [IGNORE]\n    FROM tbl_name[.*] [, tbl_name[.*]] ...\n    USING table_references\n    [WHERE where_condition]\n\nFor the single-table syntax, the DELETE statement deletes rows from\ntbl_name. The number of rows deleted is returned by the ROW_COUNT()\nfunction (see [HELP BENCHMARK]). The WHERE clause, if given, specifies\nthe conditions that identify which rows to delete. With no WHERE\nclause, all rows are deleted. If the ORDER BY clause is specified, the\nrows are deleted in the order that is specified. The LIMIT clause\nplaces a limit on the number of rows that can be deleted.\n\nFor the multiple-table syntax, DELETE deletes from each tbl_name the\nrows that satisfy the conditions. In this case, ORDER BY and LIMIT\ncannot be used.\n\nwhere_condition is an expression that evaluates to true for each row to\nbe deleted. It is specified as described in [HELP SELECT].\n\nAs stated, a DELETE statement with no WHERE clause deletes all rows. A\nfaster way to do this, when you do not want to know the number of\ndeleted rows, is to use TRUNCATE TABLE. See [HELP TRUNCATE TABLE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/delete.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/delete.html');
INSERT INTO `help_topic` VALUES (43, 'ROUND', 4, 'Syntax:\nROUND(X), ROUND(X,D)\n\nRounds the argument X to D decimal places. The rounding algorithm\ndepends on the data type of X. D defaults to 0 if not specified. D can\nbe negative to cause D digits left of the decimal point of the value X\nto become zero.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT ROUND(-1.23);\n        -> -1\nmysql> SELECT ROUND(-1.58);\n        -> -2\nmysql> SELECT ROUND(1.58);\n        -> 2\nmysql> SELECT ROUND(1.298, 1);\n        -> 1.3\nmysql> SELECT ROUND(1.298, 0);\n        -> 1\nmysql> SELECT ROUND(23.298, -1);\n        -> 20\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (44, 'NULLIF', 6, 'Syntax:\nNULLIF(expr1,expr2)\n\nReturns NULL if expr1 = expr2 is true, otherwise returns expr1. This is\nthe same as CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html\n\n', 'mysql> SELECT NULLIF(1,1);\n        -> NULL\nmysql> SELECT NULLIF(1,2);\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html');
INSERT INTO `help_topic` VALUES (45, 'CLOSE', 35, 'Syntax:\nCLOSE cursor_name\n\nThis statement closes a previously opened cursor.\n\nIf not closed explicitly, a cursor is closed at the end of the compound\nstatement in which it was declared.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/close.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/close.html');
INSERT INTO `help_topic` VALUES (46, 'STOP SLAVE', 25, 'Syntax:\nSTOP SLAVE [thread_type [, thread_type] ... ]\n\nthread_type: IO_THREAD | SQL_THREAD\n\nStops the slave threads. STOP SLAVE requires the SUPER privilege.\n\nLike START SLAVE, this statement may be used with the IO_THREAD and\nSQL_THREAD options to name the thread or threads to be stopped.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/stop-slave.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/stop-slave.html');
INSERT INTO `help_topic` VALUES (47, 'TIMEDIFF', 28, 'Syntax:\nTIMEDIFF(expr1,expr2)\n\nTIMEDIFF() returns expr1 - expr2 expressed as a time value. expr1 and\nexpr2 are time or date-and-time expressions, but both must be of the\nsame type.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TIMEDIFF(''2000:01:01 00:00:00'',\n    ->                 ''2000:01:01 00:00:00.000001'');\n        -> ''-00:00:00.000001''\nmysql> SELECT TIMEDIFF(''1997-12-31 23:59:59.000001'',\n    ->                 ''1997-12-30 01:01:01.000002'');\n        -> ''46:58:57.999999''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (48, 'LINEFROMTEXT', 3, 'LineFromText(wkt[,srid]), LineStringFromText(wkt[,srid])\n\nConstructs a LINESTRING value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (49, 'CASE OPERATOR', 6, 'Syntax:\nCASE value WHEN [compare_value] THEN result [WHEN [compare_value] THEN\nresult ...] [ELSE result] END\n\nCASE WHEN [condition] THEN result [WHEN [condition] THEN result ...]\n[ELSE result] END\n\nThe first version returns the result where value=compare_value. The\nsecond version returns the result for the first condition that is true.\nIf there was no matching result value, the result after ELSE is\nreturned, or NULL if there is no ELSE part.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html\n\n', 'mysql> SELECT CASE 1 WHEN 1 THEN ''one''\n    ->     WHEN 2 THEN ''two'' ELSE ''more'' END;\n        -> ''one''\nmysql> SELECT CASE WHEN 1>0 THEN ''true'' ELSE ''false'' END;\n        -> ''true''\nmysql> SELECT CASE BINARY ''B''\n    ->     WHEN ''a'' THEN 1 WHEN ''b'' THEN 2 END;\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html');
INSERT INTO `help_topic` VALUES (50, 'SHOW MASTER STATUS', 25, 'Syntax:\nSHOW MASTER STATUS\n\nProvides status information about the binary log files of the master.\nExample:\n\nmysql > SHOW MASTER STATUS;\n+---------------+----------+--------------+------------------+\n| File          | Position | Binlog_Do_DB | Binlog_Ignore_DB |\n+---------------+----------+--------------+------------------+\n| mysql-bin.003 | 73       | test         | manual,mysql     |\n+---------------+----------+--------------+------------------+\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-master-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-master-status.html');
INSERT INTO `help_topic` VALUES (51, 'ADDTIME', 28, 'Syntax:\nADDTIME(expr1,expr2)\n\nADDTIME() adds expr2 to expr1 and returns the result. expr1 is a time\nor datetime expression, and expr2 is a time expression.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT ADDTIME(''1997-12-31 23:59:59.999999'',\n    ->                ''1 1:1:1.000002'');\n        -> ''1998-01-02 01:01:01.000001''\nmysql> SELECT ADDTIME(''01:00:00.999999'', ''02:00:00.999998'');\n        -> ''03:00:01.999997''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (52, 'SPATIAL', 30, 'MySQL can create spatial indexes using syntax similar to that for\ncreating regular indexes, but extended with the SPATIAL keyword.\nCurrently, columns in spatial indexes must be declared NOT NULL. The\nfollowing examples demonstrate how to create spatial indexes:\n\no With CREATE TABLE:\n\nCREATE TABLE geom (g GEOMETRY NOT NULL, SPATIAL INDEX(g));\n\no With ALTER TABLE:\n\nALTER TABLE geom ADD SPATIAL INDEX(g);\n\no With CREATE INDEX:\n\nCREATE SPATIAL INDEX sp_index ON geom (g);\n\nFor MyISAM tables, SPATIAL INDEX creates an R-tree index. For storage\nengines that support non-spatial indexing of spatial columns, the\nengine creates a B-tree index. A B-tree index on spatial values will be\nuseful for exact-value lookups, but not for range scans.\n\nFor more information on indexing spatial columns, see [HELP CREATE\nINDEX].\n\nTo drop spatial indexes, use ALTER TABLE or DROP INDEX:\n\no With ALTER TABLE:\n\nALTER TABLE geom DROP INDEX g;\n\no With DROP INDEX:\n\nDROP INDEX sp_index ON geom;\n\nExample: Suppose that a table geom contains more than 32,000\ngeometries, which are stored in the column g of type GEOMETRY. The\ntable also has an AUTO_INCREMENT column fid for storing object ID\nvalues.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/creating-spatial-indexes.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/creating-spatial-indexes.html');
INSERT INTO `help_topic` VALUES (53, 'TIMESTAMPDIFF', 28, 'Syntax:\nTIMESTAMPDIFF(unit,datetime_expr1,datetime_expr2)\n\nReturns the integer difference between the date or datetime expressions\ndatetime_expr1 and datetime_expr2. The unit for the result is given by\nthe unit argument. The legal values for unit are the same as those\nlisted in the description of the TIMESTAMPADD() function.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TIMESTAMPDIFF(MONTH,''2003-02-01'',''2003-05-01'');\n        -> 3\nmysql> SELECT TIMESTAMPDIFF(YEAR,''2002-05-01'',''2001-01-01'');\n        -> -1\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (54, 'UPPER', 33, 'Syntax:\nUPPER(str)\n\nReturns the string str with all characters changed to uppercase\naccording to the current character set mapping. The default is latin1\n(cp1252 West European).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT UPPER(''Hej'');\n        -> ''HEJ''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (55, 'FROM_UNIXTIME', 28, 'Syntax:\nFROM_UNIXTIME(unix_timestamp), FROM_UNIXTIME(unix_timestamp,format)\n\nReturns a representation of the unix_timestamp argument as a value in\n''YYYY-MM-DD HH:MM:SS'' or YYYYMMDDHHMMSS.uuuuuu format, depending on\nwhether the function is used in a string or numeric context. The value\nis expressed in the current time zone. unix_timestamp is an internal\ntimestamp value such as is produced by the UNIX_TIMESTAMP() function.\n\nIf format is given, the result is formatted according to the format\nstring, which is used the same way as listed in the entry for the\nDATE_FORMAT() function.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT FROM_UNIXTIME(1196440219);\n        -> ''2007-11-30 10:30:19''\nmysql> SELECT FROM_UNIXTIME(1196440219) + 0;\n        -> 20071130103019.000000\nmysql> SELECT FROM_UNIXTIME(UNIX_TIMESTAMP(),\n    ->                      ''%Y %D %M %h:%i:%s %x'');\n        -> ''2007 30th November 10:30:59 2007''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (56, 'MEDIUMBLOB', 20, 'MEDIUMBLOB\n\nA BLOB column with a maximum length of 16,777,215 (224 - 1) bytes. Each\nMEDIUMBLOB value is stored using a three-byte length prefix that\nindicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (57, 'IFNULL', 6, 'Syntax:\nIFNULL(expr1,expr2)\n\nIf expr1 is not NULL, IFNULL() returns expr1; otherwise it returns\nexpr2. IFNULL() returns a numeric or string value, depending on the\ncontext in which it is used.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html\n\n', 'mysql> SELECT IFNULL(1,0);\n        -> 1\nmysql> SELECT IFNULL(NULL,10);\n        -> 10\nmysql> SELECT IFNULL(1/0,10);\n        -> 10\nmysql> SELECT IFNULL(1/0,''yes'');\n        -> ''yes''\n', 'http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html');
INSERT INTO `help_topic` VALUES (58, 'SHOW ERRORS', 25, 'Syntax:\nSHOW ERRORS [LIMIT [offset,] row_count]\nSHOW COUNT(*) ERRORS\n\nThis statement is similar to SHOW WARNINGS, except that instead of\ndisplaying errors, warnings, and notes, it displays only errors.\n\nThe LIMIT clause has the same syntax as for the SELECT statement. See\n[HELP SELECT].\n\nThe SHOW COUNT(*) ERRORS statement displays the number of errors. You\ncan also retrieve this number from the error_count variable:\n\nSHOW COUNT(*) ERRORS;\nSELECT @@error_count;\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-errors.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-errors.html');
INSERT INTO `help_topic` VALUES (59, 'LEAST', 17, 'Syntax:\nLEAST(value1,value2,...)\n\nWith two or more arguments, returns the smallest (minimum-valued)\nargument. The arguments are compared using the following rules:\n\no If the return value is used in an INTEGER context or all arguments\n  are integer-valued, they are compared as integers.\n\no If the return value is used in a REAL context or all arguments are\n  real-valued, they are compared as reals.\n\no If any argument is a case-sensitive string, the arguments are\n  compared as case-sensitive strings.\n\no In all other cases, the arguments are compared as case-insensitive\n  strings.\n\nBefore MySQL 5.0.13, LEAST() returns NULL only if all arguments are\nNULL. As of 5.0.13, it returns NULL if any argument is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT LEAST(2,0);\n        -> 0\nmysql> SELECT LEAST(34.0,3.0,5.0,767.0);\n        -> 3.0\nmysql> SELECT LEAST(''B'',''A'',''C'');\n        -> ''A''\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (60, '=', 17, '=\n\nEqual:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 = 0;\n        -> 0\nmysql> SELECT ''0'' = 0;\n        -> 1\nmysql> SELECT ''0.0'' = 0;\n        -> 1\nmysql> SELECT ''0.01'' = 0;\n        -> 0\nmysql> SELECT ''.01'' = 0.01;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (61, 'REVERSE', 33, 'Syntax:\nREVERSE(str)\n\nReturns the string str with the order of the characters reversed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT REVERSE(''abc'');\n        -> ''cba''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (62, 'ISNULL', 17, 'Syntax:\nISNULL(expr)\n\nIf expr is NULL, ISNULL() returns 1, otherwise it returns 0.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT ISNULL(1+1);\n        -> 0\nmysql> SELECT ISNULL(1/0);\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (63, 'BINARY', 20, 'BINARY(M)\n\nThe BINARY type is similar to the CHAR type, but stores binary byte\nstrings rather than non-binary character strings. M represents the\ncolumn length in bytes.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (64, 'BLOB DATA TYPE', 20, '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\nhttp://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/blob.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/blob.html');
INSERT INTO `help_topic` VALUES (65, 'BOUNDARY', 32, 'Boundary(g)\n\nReturns a geometry that is the closure of the combinatorial boundary of\nthe geometry value g.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (66, 'CREATE USER', 8, 'Syntax:\nCREATE USER user [IDENTIFIED BY [PASSWORD] ''password'']\n    [, user [IDENTIFIED BY [PASSWORD] ''password'']] ...\n\nThe CREATE USER statement was added in MySQL 5.0.2. This statement\ncreates new MySQL accounts. To use it, you must have the global CREATE\nUSER privilege or the INSERT privilege for the mysql database. For each\naccount, CREATE USER creates a new record in the mysql.user table that\nhas no privileges. An error occurs if the account already exists. Each\naccount is named using the same format as for the GRANT statement; for\nexample, ''jeffrey''@''localhost''. If you specify only the username part\nof the account name, a hostname part of ''%'' is used. For additional\ninformation about specifying account names, see [HELP GRANT].\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 [HELP GRANT].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-user.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-user.html');
INSERT INTO `help_topic` VALUES (67, 'POINT', 22, 'Point(x,y)\n\nConstructs a WKB Point using its coordinates.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (68, 'CURRENT_USER', 15, '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. As of MySQL 5.0.10, within a stored\nroutine that is defined with the SQL SECURITY DEFINER characteristic,\nCURRENT_USER() returns the creator of the routine. The return value is\na string in the utf8 character set.\n\nThe value of CURRENT_USER() can differ from the value of USER().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\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', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (69, 'LCASE', 33, 'Syntax:\nLCASE(str)\n\nLCASE() is a synonym for LOWER().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (70, '<=', 17, 'Syntax:\n<=\n\nLess than or equal:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 0.1 <= 2;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (71, 'SHOW PROFILES', 25, 'Syntax:\nSHOW PROFILES\n\nSHOW PROFILE [type [, type] ... ]\n    [FOR QUERY n]\n    [LIMIT n [OFFSET n]]\n\ntype:\n    ALL\n  | BLOCK IO\n  | CONTEXT SWITCHES\n  | CPU\n  | IPC\n  | MEMORY\n  | PAGE FAULTS\n  | SOURCE\n  | SWAPS\n\nThe SHOW PROFILES and SHOW PROFILE statements display profiling\ninformation that indicates resource usage for statements executed\nduring the course of the current session.\n\nProfiling is controlled by the profiling session variable, which has a\ndefault value of 0 (OFF). Profiling is enabled by setting profiling to\n1 or ON:\n\nmysql> SET profiling = 1;\n\nSHOW PROFILES displays a list of the most recent statements sent to the\nmaster. The size of the list is controlled by the\nprofiling_history_size session variable, which has a default value of\n15. The maximum value is 100. Setting the value to 0 has the practical\neffect of disabling profiling.\n\nAll statements are profiled except SHOW PROFILES and SHOW PROFILE, so\nyou will find neither of those statements in the profile list.\nMalformed statements are profiled. For example, SHOW PROFILING is an\nillegal statement, and a syntax error occurs if you try to execute it,\nbut it will show up in the profiling list.\n\nSHOW PROFILE displays detailed information about a single statement.\nWithout the FOR QUERY n clause, the output pertains to the most\nrecently executed statement. If FOR QUERY n is included, SHOW PROFILE\ndisplays information for statement n. The values of n correspond to the\nQuery_ID values displayed by SHOW PROFILES.\n\nThe LIMIT n clause may be given to limit the output to n rows. If LIMIT\nis given, OFFSET n may be added to begin the output n rows into the\nfull set of rows.\n\nBy default, SHOW PROFILE displays Status and Duration columns. The\nStatus values are like the State values displayed by SHOW PROCESSLIST,\nalthought there might be some minor differences in interpretion for the\ntwo statements for some status values (see\nhttp://dev.mysql.com/doc/refman/5.0/en/thread-information.html).\n\nOptional type values may be specified to display specific additional\ntypes of information:\n\no ALL displays all information\n\no BLOCK IO displays counts for block input and output operations\n\no CONTEXT SWITCHES displays counts for voluntary and involuntary\n  context switches\n\no CPU displays user and system CPU usage times\n\no IPC displays counts for messages sent and received\n\no MEMORY is not currently implemented\n\no PAGE FAULTS displays counts for major and minor page faults\n\no SOURCE displays the names of functions from the source code, together\n  with the name and line number of the file in which the function\n  occurs\n\no SWAPS displays swap counts\n\nProfiling is enabled per session. When a session ends, its profiling\ninformation is lost.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-profiles.html\n\n', 'mysql> SELECT @@profiling;\n+-------------+\n| @@profiling |\n+-------------+\n|           0 |\n+-------------+\n1 row in set (0.00 sec)\n\nmysql> SET profiling = 1;\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> DROP TABLE IF EXISTS t1;\nQuery OK, 0 rows affected, 1 warning (0.00 sec)\n\nmysql> CREATE TABLE T1 (id INT);\nQuery OK, 0 rows affected (0.01 sec)\n\nmysql> SHOW PROFILES;\n+----------+----------+--------------------------+\n| Query_ID | Duration | Query                    |\n+----------+----------+--------------------------+\n|        0 | 0.000088 | SET PROFILING = 1        |\n|        1 | 0.000136 | DROP TABLE IF EXISTS t1  |\n|        2 | 0.011947 | CREATE TABLE t1 (id INT) |\n+----------+----------+--------------------------+\n3 rows in set (0.00 sec)\n\nmysql> SHOW PROFILE;\n+----------------------+----------+\n| Status               | Duration |\n+----------------------+----------+\n| checking permissions | 0.000040 |\n| creating table       | 0.000056 |\n| After create         | 0.011363 |\n| query end            | 0.000375 |\n| freeing items        | 0.000089 |\n| logging slow query   | 0.000019 |\n| cleaning up          | 0.000005 |\n+----------------------+----------+\n7 rows in set (0.00 sec)\n\nmysql> SHOW PROFILE FOR QUERY 1;\n+--------------------+----------+\n| Status             | Duration |\n+--------------------+----------+\n| query end          | 0.000107 |\n| freeing items      | 0.000008 |\n| logging slow query | 0.000015 |\n| cleaning up        | 0.000006 |\n+--------------------+----------+\n4 rows in set (0.00 sec)\n\nmysql> SHOW PROFILE CPU FOR QUERY 2;\n+----------------------+----------+----------+------------+\n| Status               | Duration | CPU_user | CPU_system |\n+----------------------+----------+----------+------------+\n| checking permissions | 0.000040 | 0.000038 |   0.000002 |\n| creating table       | 0.000056 | 0.000028 |   0.000028 |\n| After create         | 0.011363 | 0.000217 |   0.001571 |\n| query end            | 0.000375 | 0.000013 |   0.000028 |\n| freeing items        | 0.000089 | 0.000010 |   0.000014 |\n| logging slow query   | 0.000019 | 0.000009 |   0.000010 |\n| cleaning up          | 0.000005 | 0.000003 |   0.000002 |\n+----------------------+----------+----------+------------+\n7 rows in set (0.00 sec)\n', 'http://dev.mysql.com/doc/refman/5.0/en/show-profiles.html');
INSERT INTO `help_topic` VALUES (72, 'UPDATE', 25, '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 [HELP 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. This\n  affects only storage engines that use only table-level locking\n  (MyISAM, MEMORY, MERGE).\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  closest valid values instead.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/update.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/update.html');
INSERT INTO `help_topic` VALUES (73, 'IS NOT NULL', 17, 'Syntax:\nIS NOT NULL\n\nTests whether a value is not NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 IS NOT NULL, 0 IS NOT NULL, NULL IS NOT NULL;\n        -> 1, 1, 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (74, 'CASE STATEMENT', 35, '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\n*Note*: The syntax of the CASE statement shown here for use inside\nstored routines differs slightly from that of the SQL CASE expression\ndescribed in [HELP CASE operator]. The CASE statement cannot have an\nELSE NULL clause, and it is terminated with END CASE instead of END.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/case-statement.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/case-statement.html');
INSERT INTO `help_topic` VALUES (75, 'EXECUTE STATEMENT', 25, '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\nURL: http://dev.mysql.com/doc/refman/5.0/en/sqlps.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/sqlps.html');
INSERT INTO `help_topic` VALUES (76, 'DROP INDEX', 36, '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 [HELP ALTER TABLE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-index.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-index.html');
INSERT INTO `help_topic` VALUES (77, 'MATCH AGAINST', 33, 'Syntax:\nMATCH (col1,col2,...) AGAINST (expr [search_modifier])\n\nMySQL has support for full-text indexing and searching:\n\no A full-text index in MySQL is an index of type FULLTEXT.\n\no Full-text indexes can be used only with MyISAM tables, and can be\n  created only for CHAR, VARCHAR, or TEXT columns.\n\no A FULLTEXT index definition can be given in the CREATE TABLE\n  statement when a table is created, or added later using ALTER TABLE\n  or CREATE INDEX.\n\no For large data sets, it is much faster to load your data into a table\n  that has no FULLTEXT index and then create the index after that, than\n  to load data into a table that has an existing FULLTEXT index.\n\nFull-text searching is performed using MATCH() ... AGAINST syntax.\nMATCH() takes a comma-separated list that names the columns to be\nsearched. AGAINST takes a string to search for, and an optional\nmodifier that indicates what type of search to perform. The search\nstring must be a literal string, not a variable or a column name. There\nare three types of full-text searches:\n\no A boolean search interprets the search string using the rules of a\n  special query language. The string contains the words to search for.\n  It can also contain operators that specify requirements such that a\n  word must be present or absent in matching rows, or that it should be\n  weighted higher or lower than usual. Common words such as "some" or\n  "then" are stopwords and do not match if present in the search\n  string. The IN BOOLEAN MODE modifier specifies a boolean search. For\n  more information, see\n  http://dev.mysql.com/doc/refman/5.0/en/fulltext-boolean.html.\n\no A natural language search interprets the search string as a phrase in\n  natural human language (a phrase in free text). There are no special\n  operators. The stopword list applies. In addition, words that are\n  present in 50% or more of the rows are considered common and do not\n  match. Full-text searches are natural language searches if no\n  modifier is given.\n\no A query expansion search is a modification of a natural language\n  search. The search string is used to perform a natural language\n  search. Then words from the most relevant rows returned by the search\n  are added to the search string and the search is done again. The\n  query returns the rows from the second search. The WITH QUERY\n  EXPANSION modifier specifies a query expansion search. For more\n  information, see\n  http://dev.mysql.com/doc/refman/5.0/en/fulltext-query-expansion.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html\n\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', 'http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html');
INSERT INTO `help_topic` VALUES (78, 'ABS', 4, 'Syntax:\nABS(X)\n\nReturns the absolute value of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT ABS(2);\n        -> 2\nmysql> SELECT ABS(-32);\n        -> 32\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (79, 'POLYFROMWKB', 29, 'PolyFromWKB(wkb[,srid]), PolygonFromWKB(wkb[,srid])\n\nConstructs a POLYGON value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (80, 'NOT LIKE', 33, 'Syntax:\nexpr NOT LIKE pat [ESCAPE ''escape_char'']\n\nThis is the same as NOT (expr LIKE pat [ESCAPE ''escape_char'']).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html');
INSERT INTO `help_topic` VALUES (81, 'SPACE', 33, 'Syntax:\nSPACE(N)\n\nReturns a string consisting of N space characters.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT SPACE(6);\n        -> ''      ''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (82, 'MBR DEFINITION', 5, 'Its MBR (Minimum Bounding Rectangle), or Envelope. This is the bounding\ngeometry, formed by the minimum and maximum (X,Y) coordinates:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-class-geometry.html\n\n', '((MINX MINY, MAXX MINY, MAXX MAXY, MINX MAXY, MINX MINY))\n', 'http://dev.mysql.com/doc/refman/5.0/en/gis-class-geometry.html');
INSERT INTO `help_topic` VALUES (83, 'GEOMETRYCOLLECTION', 22, '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\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (84, 'MAX', 14, 'Syntax:\nMAX([DISTINCT] expr)\n\nReturns the maximum value of expr. MAX() may take a string argument; in\nsuch cases, it returns the maximum string value. See\nhttp://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html. The DISTINCT\nkeyword can be used to find the maximum of the distinct values of expr,\nhowever, this produces the same result as omitting DISTINCT.\n\nMAX() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', 'mysql> SELECT student_name, MIN(test_score), MAX(test_score)\n    ->        FROM student\n    ->        GROUP BY student_name;\n', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (85, '*', 4, 'Syntax:\n*\n\nMultiplication:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT 3*5;\n        -> 15\nmysql> SELECT 18014398509481984*18014398509481984.0;\n        -> 324518553658426726783156020576256.0\nmysql> SELECT 18014398509481984*18014398509481984;\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (86, 'TIMESTAMP', 20, 'TIMESTAMP\n\nA timestamp. The range is ''1970-01-01 00:00:01'' UTC to partway through\nthe year 2038. TIMESTAMP values are stored as the number of seconds\nsince the epoch (''1970-01-01 00:00:00'' UTC). A TIMESTAMP cannot\nrepresent the value ''1970-01-01 00:00:00'' because that is equivalent to\n0 seconds from the epoch and the value 0 is reserved for representing\n''0000-00-00 00:00:00'', the "zero" TIMESTAMP value.\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\nhttp://dev.mysql.com/doc/refman/5.0/en/timestamp.html.\n\nA TIMESTAMP value is returned as a string in the format ''YYYY-MM-DD\nHH:MM:SS'' with a display width fixed at 19 characters. To obtain the\nvalue as a number, you should add +0 to the timestamp column.\n\n*Note*: The TIMESTAMP format that was used prior to MySQL 4.1 is not\nsupported in MySQL 5.0; see MySQL 3.23, 4.0, 4.1 Reference Manual for\ninformation regarding the old format.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html');
INSERT INTO `help_topic` VALUES (87, 'DES_DECRYPT', 10, 'Syntax:\nDES_DECRYPT(crypt_str[,key_str])\n\nDecrypts a string encrypted with DES_ENCRYPT(). If an error occurs,\nthis function returns NULL.\n\nThis function works only if MySQL has been configured with SSL support.\nSee http://dev.mysql.com/doc/refman/5.0/en/secure-connections.html.\n\nIf no key_str argument is given, DES_DECRYPT() examines the first byte\nof the encrypted string to determine the DES key number that was used\nto encrypt the original string, and then reads the key from the DES key\nfile to decrypt the message. For this to work, the user must have the\nSUPER privilege. The key file can be specified with the --des-key-file\nserver option.\n\nIf you pass this function a key_str argument, that string is used as\nthe key for decrypting the message.\n\nIf the crypt_str argument does not appear to be an encrypted string,\nMySQL returns the given crypt_str.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (88, 'ENDPOINT', 11, 'EndPoint(ls)\n\nReturns the Point that is the endpoint of the LineString value ls.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html\n\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', 'http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html');
INSERT INTO `help_topic` VALUES (89, 'CACHE INDEX', 25, '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\nURL: http://dev.mysql.com/doc/refman/5.0/en/cache-index.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/cache-index.html');
INSERT INTO `help_topic` VALUES (90, 'COMPRESS', 10, '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\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\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', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (91, 'INSERT', 25, '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 [HELP INSERT SELECT].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/insert.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/insert.html');
INSERT INTO `help_topic` VALUES (92, 'COUNT', 14, 'Syntax:\nCOUNT(expr)\n\nReturns a count of the number of non-NULL values of expr in the rows\nretrieved by a SELECT statement. The result is a BIGINT value.\n\nCOUNT() returns 0 if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', 'mysql> SELECT student.student_name,COUNT(*)\n    ->        FROM student,course\n    ->        WHERE student.student_id=course.student_id\n    ->        GROUP BY student_name;\n', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (93, 'HANDLER', 25, '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\nURL: http://dev.mysql.com/doc/refman/5.0/en/handler.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/handler.html');
INSERT INTO `help_topic` VALUES (94, 'MLINEFROMTEXT', 3, 'MLineFromText(wkt[,srid]), MultiLineStringFromText(wkt[,srid])\n\nConstructs a MULTILINESTRING value using its WKT representation and\nSRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (95, 'GEOMCOLLFROMWKB', 29, 'GeomCollFromWKB(wkb[,srid]), GeometryCollectionFromWKB(wkb[,srid])\n\nConstructs a GEOMETRYCOLLECTION value using its WKB representation and\nSRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (96, 'RENAME TABLE', 36, 'Syntax:\nRENAME TABLE tbl_name TO new_tbl_name\n    [, tbl_name2 TO new_tbl_name2] ...\n\nThis statement renames one or more tables.\n\nThe rename operation is done atomically, which means that no other\nthread can access any of the tables while the rename is running. For\nexample, if you have an existing table old_table, you can create\nanother table new_table that has the same structure but is empty, and\nthen replace the existing table with the empty one as follows (assuming\nthat backup_table does not already exist):\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/rename-table.html\n\n', 'CREATE TABLE new_table (...);\nRENAME TABLE old_table TO backup_table, new_table TO old_table;\n', 'http://dev.mysql.com/doc/refman/5.0/en/rename-table.html');
INSERT INTO `help_topic` VALUES (97, 'BOOLEAN', 20, 'BOOL, BOOLEAN\n\nThese types are synonyms for TINYINT(1). A value of zero is considered\nfalse. Non-zero values are considered true:\n\nmysql> SELECT IF(0, ''true'', ''false'');\n+------------------------+\n| IF(0, ''true'', ''false'') |\n+------------------------+\n| false                  |\n+------------------------+\n\nmysql> SELECT IF(1, ''true'', ''false'');\n+------------------------+\n| IF(1, ''true'', ''false'') |\n+------------------------+\n| true                   |\n+------------------------+\n\nmysql> SELECT IF(2, ''true'', ''false'');\n+------------------------+\n| IF(2, ''true'', ''false'') |\n+------------------------+\n| true                   |\n+------------------------+\n\nHowever, the values TRUE and FALSE are merely aliases for 1 and 0,\nrespectively, as shown here:\n\nmysql> SELECT IF(0 = FALSE, ''true'', ''false'');\n+--------------------------------+\n| IF(0 = FALSE, ''true'', ''false'') |\n+--------------------------------+\n| true                           |\n+--------------------------------+\n\nmysql> SELECT IF(1 = TRUE, ''true'', ''false'');\n+-------------------------------+\n| IF(1 = TRUE, ''true'', ''false'') |\n+-------------------------------+\n| true                          |\n+-------------------------------+\n\nmysql> SELECT IF(2 = TRUE, ''true'', ''false'');\n+-------------------------------+\n| IF(2 = TRUE, ''true'', ''false'') |\n+-------------------------------+\n| false                         |\n+-------------------------------+\n\nmysql> SELECT IF(2 = FALSE, ''true'', ''false'');\n+--------------------------------+\n| IF(2 = FALSE, ''true'', ''false'') |\n+--------------------------------+\n| false                          |\n+--------------------------------+\n\nThe last two statements display the results shown because 2 is equal to\nneither 1 nor 0.\n\nWe intend to implement full boolean type handling, in accordance with\nstandard SQL, in a future MySQL release.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (98, 'DEFAULT', 13, 'Syntax:\nDEFAULT(col_name)\n\nReturns the default value for a table column. Starting with MySQL\n5.0.2, an error results if the column has no default value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', 'mysql> UPDATE t SET i = DEFAULT(i)+1 WHERE id < 100;\n', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (99, 'MOD', 4, 'Syntax:\nMOD(N,M), N % M, N MOD M\n\nModulo operation. Returns the remainder of N divided by M.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT MOD(234, 10);\n        -> 4\nmysql> SELECT 253 % 7;\n        -> 1\nmysql> SELECT MOD(29,9);\n        -> 2\nmysql> SELECT 29 MOD 9;\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (100, 'TINYTEXT', 20, 'TINYTEXT [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 255 (28 - 1) characters. The\neffective maximum length is less if the value contains multi-byte\ncharacters. Each TINYTEXT value is stored using a one-byte length\nprefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (101, 'OPTIMIZE TABLE', 19, 'Syntax:\nOPTIMIZE [LOCAL | NO_WRITE_TO_BINLOG] TABLE tbl_name [, tbl_name] ...\n\nOPTIMIZE TABLE should be used if you have deleted a large part of a\ntable or if you have made many changes to a table with variable-length\nrows (tables that have VARCHAR, VARBINARY, BLOB, or TEXT columns).\nDeleted rows are maintained in a linked list and subsequent INSERT\noperations reuse old row positions. You can use OPTIMIZE TABLE to\nreclaim the unused space and to defragment the data file.\n\nThis statement requires SELECT and INSERT privileges for the table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/optimize-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/optimize-table.html');
INSERT INTO `help_topic` VALUES (102, 'DECODE', 10, 'Syntax:\nDECODE(crypt_str,pass_str)\n\nDecrypts the encrypted string crypt_str using pass_str as the password.\ncrypt_str should be a string returned from ENCODE().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (103, '<=>', 17, 'Syntax:\n<=>\n\nNULL-safe equal. This operator performs an equality comparison like the\n= operator, but returns 1 rather than NULL if both operands are NULL,\nand 0 rather than NULL if one operand is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 <=> 1, NULL <=> NULL, 1 <=> NULL;\n        -> 1, 1, 0\nmysql> SELECT 1 = 1, NULL = NULL, 1 = NULL;\n        -> 1, NULL, NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (104, 'LOAD DATA FROM MASTER', 25, 'Syntax:\nLOAD DATA FROM MASTER\n\nThis feature is deprecated. We recommend not using it anymore. It is\nsubject to removal in a future version of MySQL.\n\nSince the current implementation of LOAD DATA FROM MASTER and LOAD\nTABLE FROM MASTER is very limited, these statements are deprecated in\nversions 4.1 of MySQL and above. We will introduce a more advanced\ntechnique (called "online backup") in a future version. That technique\nwill have the additional advantage of working with more storage\nengines.\n\nFor MySQL 5.1 and earlier, the recommended alternative solution to\nusing LOAD DATA FROM MASTER or LOAD TABLE FROM MASTER is using\nmysqldump or mysqlhotcopy. The latter requires Perl and two Perl\nmodules (DBI and DBD:mysql) and works for MyISAM and ARCHIVE tables\nonly. With mysqldump, you can create SQL dumps on the master and pipe\n(or copy) these to a mysql client on the slave. This has the advantage\nof working for all storage engines, but can be quite slow, since it\nworks using SELECT.\n\nThis statement takes a snapshot of the master and copies it to the\nslave. It updates the values of MASTER_LOG_FILE and MASTER_LOG_POS so\nthat the slave starts replicating from the correct position. Any table\nand database exclusion rules specified with the --replicate-*-do-* and\n--replicate-*-ignore-* options are honored. --replicate-rewrite-db is\nnot taken into account because a user could use this option to set up a\nnon-unique mapping such as --replicate-rewrite-db="db1->db3" and\n--replicate-rewrite-db="db2->db3", which would confuse the slave when\nloading tables from the master.\n\nUse of this statement is subject to the following conditions:\n\no It works only for MyISAM tables. Attempting to load a non-MyISAM\n  table results in the following error:\n\nERROR 1189 (08S01): Net error reading from master\n\no It acquires a global read lock on the master while taking the\n  snapshot, which prevents updates on the master during the load\n  operation.\n\nIf you are loading large tables, you might have to increase the values\nof net_read_timeout and net_write_timeout on both the master and slave\nservers. See\nhttp://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html.\n\nNote that LOAD DATA FROM MASTER does not copy any tables from the mysql\ndatabase. This makes it easy to have different users and privileges on\nthe master and the slave.\n\nTo use LOAD DATA FROM MASTER, the replication account that is used to\nconnect to the master must have the RELOAD and SUPER privileges on the\nmaster and the SELECT privilege for all master tables you want to load.\nAll master tables for which the user does not have the SELECT privilege\nare ignored by LOAD DATA FROM MASTER. This is because the master hides\nthem from the user: LOAD DATA FROM MASTER calls SHOW DATABASES to know\nthe master databases to load, but SHOW DATABASES returns only databases\nfor which the user has some privilege. See [HELP SHOW DATABASES]. On\nthe slave side, the user that issues LOAD DATA FROM MASTER must have\nprivileges for dropping and creating the databases and tables that are\ncopied.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/load-data-from-master.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/load-data-from-master.html');
INSERT INTO `help_topic` VALUES (105, 'RESET', 25, 'Syntax:\nRESET reset_option [, reset_option] ...\n\nThe RESET statement is used to clear the state of various server\noperations. You must have the RELOAD privilege to execute RESET.\n\nRESET acts as a stronger version of the FLUSH statement. See [HELP\nFLUSH].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/reset.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/reset.html');
INSERT INTO `help_topic` VALUES (106, 'HELP STATEMENT', 24, 'Syntax:\nHELP ''search_string''\n\nThe HELP statement returns online information from the MySQL Reference\nmanual. Its proper operation requires that the help tables in the mysql\ndatabase be initialized with help topic information (see\nhttp://dev.mysql.com/doc/refman/5.0/en/server-side-help-support.html).\n\nThe HELP statement searches the help tables for the given search string\nand displays the result of the search. The search string is not case\nsensitive.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/help.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/help.html');
INSERT INTO `help_topic` VALUES (107, 'GET_LOCK', 13, 'Syntax:\nGET_LOCK(str,timeout)\n\nTries to obtain a lock with a name given by the string str, using a\ntimeout of timeout seconds. Returns 1 if the lock was obtained\nsuccessfully, 0 if the attempt timed out (for example, because another\nclient has previously locked the name), or NULL if an error occurred\n(such as running out of memory or the thread was killed with mysqladmin\nkill). If you have a lock obtained with GET_LOCK(), it is released when\nyou execute RELEASE_LOCK(), execute a new GET_LOCK(), or your\nconnection terminates (either normally or abnormally). Locks obtained\nwith GET_LOCK() do not interact with transactions. That is, committing\na transaction does not release any such locks obtained during the\ntransaction.\n\nThis function can be used to implement application locks or to simulate\nrecord locks. Names are locked on a server-wide basis. If a name has\nbeen locked by one client, GET_LOCK() blocks any request by another\nclient for a lock with the same name. This allows clients that agree on\na given lock name to use the name to perform cooperative advisory\nlocking. But be aware that it also allows a client that is not among\nthe set of cooperating clients to lock a name, either inadvertently or\ndeliberately, and thus prevent any of the cooperating clients from\nlocking that name. One way to reduce the likelihood of this is to use\nlock names that are database-specific or application-specific. For\nexample, use lock names of the form db_name.str or app_name.str.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', 'mysql> SELECT GET_LOCK(''lock1'',10);\n        -> 1\nmysql> SELECT IS_FREE_LOCK(''lock2'');\n        -> 1\nmysql> SELECT GET_LOCK(''lock2'',10);\n        -> 1\nmysql> SELECT RELEASE_LOCK(''lock2'');\n        -> 1\nmysql> SELECT RELEASE_LOCK(''lock1'');\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (108, 'UCASE', 33, 'Syntax:\nUCASE(str)\n\nUCASE() is a synonym for UPPER().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (109, 'SHOW BINLOG EVENTS', 25, 'Syntax:\nSHOW BINLOG EVENTS\n   [IN ''log_name''] [FROM pos] [LIMIT [offset,] row_count]\n\nShows the events in the binary log. If you do not specify ''log_name'',\nthe first binary log is displayed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-binlog-events.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-binlog-events.html');
INSERT INTO `help_topic` VALUES (110, 'MPOLYFROMWKB', 29, 'MPolyFromWKB(wkb[,srid]), MultiPolygonFromWKB(wkb[,srid])\n\nConstructs a MULTIPOLYGON value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (111, 'ITERATE', 35, 'Syntax:\nITERATE label\n\nITERATE can appear only within LOOP, REPEAT, and WHILE statements.\nITERATE means "do the loop again."\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/iterate-statement.html\n\n', 'CREATE 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;\n  SET @x = p1;\nEND\n', 'http://dev.mysql.com/doc/refman/5.0/en/iterate-statement.html');
INSERT INTO `help_topic` VALUES (112, 'DO', 25, 'Syntax:\nDO expr [, expr] ...\n\nDO executes the expressions but does not return any results. In most\nrespects, DO is shorthand for SELECT expr, ..., but has the advantage\nthat it is slightly faster when you do not care about the result.\n\nDO is useful primarily with functions that have side effects, such as\nRELEASE_LOCK().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/do.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/do.html');
INSERT INTO `help_topic` VALUES (113, 'CURTIME', 28, 'Syntax:\nCURTIME()\n\nReturns the current time as a value in ''HH:MM:SS'' or HHMMSS.uuuuuu\nformat, depending on whether the function is used in a string or\nnumeric context. The value is expressed in the current time zone.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT CURTIME();\n        -> ''23:50:26''\nmysql> SELECT CURTIME() + 0;\n        -> 235026.000000\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (114, 'CHAR_LENGTH', 33, 'Syntax:\nCHAR_LENGTH(str)\n\nReturns the length of the string str, measured in characters. A\nmulti-byte character counts as a single character. This means that for\na string containing five two-byte characters, LENGTH() returns 10,\nwhereas CHAR_LENGTH() returns 5.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (115, 'BIGINT', 20, 'BIGINT[(M)] [UNSIGNED] [ZEROFILL]\n\nA large integer. The signed range is -9223372036854775808 to\n9223372036854775807. The unsigned range is 0 to 18446744073709551615.\n\nSERIAL is an alias for BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (116, 'SET', 25, 'Syntax:\nSET variable_assignment [, variable_assignment] ...\n\nvariable_assignment:\n      user_var_name = expr\n    | [GLOBAL | SESSION] system_var_name = expr\n    | [@@global. | @@session. | @@]system_var_name = expr\n\nThe SET statement assigns values to different types of variables that\naffect the operation of the server or your client. Older versions of\nMySQL employed SET OPTION, but this syntax is deprecated in favor of\nSET without OPTION.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-option.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-option.html');
INSERT INTO `help_topic` VALUES (117, 'CONV', 4, 'Syntax:\nCONV(N,from_base,to_base)\n\nConverts numbers between different number bases. Returns a string\nrepresentation of the number N, converted from base from_base to base\nto_base. Returns NULL if any argument is NULL. The argument N is\ninterpreted as an integer, but may be specified as an integer or a\nstring. The minimum base is 2 and the maximum base is 36. If to_base is\na negative number, N is regarded as a signed number. Otherwise, N is\ntreated as unsigned. CONV() works with 64-bit precision.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT CONV(''a'',16,2);\n        -> ''1010''\nmysql> SELECT CONV(''6E'',18,8);\n        -> ''172''\nmysql> SELECT CONV(-17,10,-18);\n        -> ''-H''\nmysql> SELECT CONV(10+''10''+''10''+0xa,10,10);\n        -> ''40''\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (118, 'DATE', 20, 'DATE\n\nA date. The supported range is ''1000-01-01'' to ''9999-12-31''. MySQL\ndisplays DATE values in ''YYYY-MM-DD'' format, but allows assignment of\nvalues to DATE columns using either strings or numbers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html');
INSERT INTO `help_topic` VALUES (119, 'SHOW OPEN TABLES', 25, 'Syntax:\nSHOW OPEN TABLES [FROM db_name]\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW OPEN TABLES lists the non-TEMPORARY tables that are currently open\nin the table cache. See\nhttp://dev.mysql.com/doc/refman/5.0/en/table-cache.html. The LIKE\nclause, if present, indicates which table names to match. The WHERE\nclause can be given to select rows using more general conditions, as\ndiscussed in http://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-open-tables.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-open-tables.html');
INSERT INTO `help_topic` VALUES (120, 'EXTRACT', 28, 'Syntax:\nEXTRACT(unit FROM date)\n\nThe EXTRACT() function uses the same kinds of unit specifiers as\nDATE_ADD() or DATE_SUB(), but extracts parts from the date rather than\nperforming date arithmetic.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT EXTRACT(YEAR FROM ''1999-07-02'');\n       -> 1999\nmysql> SELECT EXTRACT(YEAR_MONTH FROM ''1999-07-02 01:02:03'');\n       -> 199907\nmysql> SELECT EXTRACT(DAY_MINUTE FROM ''1999-07-02 01:02:03'');\n       -> 20102\nmysql> SELECT EXTRACT(MICROSECOND\n    ->                FROM ''2003-01-02 10:30:00.000123'');\n        -> 123\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (121, 'ENCRYPT', 10, 'Syntax:\nENCRYPT(str[,salt])\n\nEncrypts str using the Unix crypt() system call and returns a binary\nstring. The salt argument should be a string with at least two\ncharacters. If no salt argument is given, a random value is used.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT ENCRYPT(''hello'');\n        -> ''VxuFAJXVARROc''\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (122, 'SHOW STATUS', 25, 'Syntax:\nSHOW [GLOBAL | SESSION] STATUS\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW STATUS provides server status information. This information also\ncan be obtained using the mysqladmin extended-status command. The LIKE\nclause, if present, indicates which variable names to match. The WHERE\nclause can be given to select rows using more general conditions, as\ndiscussed in http://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\nWith a LIKE clause, the statement displays only rows for those\nvariables with names that match the pattern:\n\nmysql> SHOW STATUS LIKE ''Key%'';\n+--------------------+----------+\n| Variable_name      | Value    |\n+--------------------+----------+\n| Key_blocks_used    | 14955    |\n| Key_read_requests  | 96854827 |\n| Key_reads          | 162040   |\n| Key_write_requests | 7589728  |\n| Key_writes         | 3813196  |\n+--------------------+----------+\n\nThe GLOBAL and SESSION options are new in MySQL 5.0.2. With the GLOBAL\nmodifier, SHOW STATUS displays the status values for all connections to\nMySQL. With SESSION, it displays the status values for the current\nconnection. If no modifier is present, the default is SESSION. LOCAL is\na synonym for SESSION.\n\nSome status variables have only a global value. For these, you get the\nsame value for both GLOBAL and SESSION. The scope for each status\nvariable is listed at\nhttp://dev.mysql.com/doc/refman/5.0/en/server-status-variables.html.\n\n*Note*: Before MySQL 5.0.2, SHOW STATUS returned global status values.\nBecause the default as of 5.0.2 is to return session values, this is\nincompatible with previous versions. To issue a SHOW STATUS statement\nthat will retrieve global status values for all versions of MySQL,\nwrite it like this:\n\nSHOW /*!50002 GLOBAL */ STATUS;\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-status.html');
INSERT INTO `help_topic` VALUES (123, 'OLD_PASSWORD', 10, 'Syntax:\nOLD_PASSWORD(str)\n\nOLD_PASSWORD() was added to MySQL when the implementation of PASSWORD()\nwas changed to improve security. OLD_PASSWORD() returns the value of\nthe old (pre-4.1) implementation of PASSWORD() as a binary string, and\nis intended to permit you to reset passwords for any pre-4.1 clients\nthat need to connect to your version 5.0 MySQL server without locking\nthem out. See\nhttp://dev.mysql.com/doc/refman/5.0/en/password-hashing.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (124, 'SET VARIABLE', 35, 'Syntax:\nSET var_name = expr [, var_name = expr] ...\n\nThe SET statement in stored routines is an extended version of the\ngeneral SET statement. Referenced variables may be ones declared inside\na routine, or global system variables.\n\nThe SET statement in stored routines is implemented as part of the\npre-existing SET syntax. This allows an extended syntax of SET a=x,\nb=y, ... where different variable types (locally declared variables and\nglobal and session server variables) can be mixed. This also allows\ncombinations of local variables and some options that make sense only\nfor system variables; in that case, the options are recognized but\nignored.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-statement.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-statement.html');
INSERT INTO `help_topic` VALUES (125, 'FORMAT', 33, 'Syntax:\nFORMAT(X,D)\n\nFormats the number X to a format like ''#,###,###.##'', rounded to D\ndecimal places, and returns the result as a string. If D is 0, the\nresult has no decimal point or fractional part.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT FORMAT(12332.123456, 4);\n        -> ''12,332.1235''\nmysql> SELECT FORMAT(12332.1,4);\n        -> ''12,332.1000''\nmysql> SELECT FORMAT(12332.2,0);\n        -> ''12,332''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (126, '||', 12, 'Syntax:\nOR, ||\n\nLogical OR. When both operands are non-NULL, the result is 1 if any\noperand is non-zero, and 0 otherwise. With a NULL operand, the result\nis 1 if the other operand is non-zero, and NULL otherwise. If both\noperands are NULL, the result is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html\n\n', 'mysql> SELECT 1 || 1;\n        -> 1\nmysql> SELECT 1 || 0;\n        -> 1\nmysql> SELECT 0 || 0;\n        -> 0\nmysql> SELECT 0 || NULL;\n        -> NULL\nmysql> SELECT 1 || NULL;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html');
INSERT INTO `help_topic` VALUES (127, 'BIT_LENGTH', 33, 'Syntax:\nBIT_LENGTH(str)\n\nReturns the length of the string str in bits.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT BIT_LENGTH(''text'');\n        -> 32\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (128, 'EXTERIORRING', 2, 'ExteriorRing(poly)\n\nReturns the exterior ring of the Polygon value poly as a LineString.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html\n\n', 'mysql> SET @poly =\n    -> ''Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))'';\nmysql> SELECT AsText(ExteriorRing(GeomFromText(@poly)));\n+-------------------------------------------+\n| AsText(ExteriorRing(GeomFromText(@poly))) |\n+-------------------------------------------+\n| LINESTRING(0 0,0 3,3 3,3 0,0 0)           |\n+-------------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html');
INSERT INTO `help_topic` VALUES (129, 'GEOMFROMWKB', 29, 'GeomFromWKB(wkb[,srid]), GeometryFromWKB(wkb[,srid])\n\nConstructs a geometry value of any type using its WKB representation\nand SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (130, 'SHOW SLAVE HOSTS', 25, 'Syntax:\n          SHOW SLAVE HOSTS\n\nDisplays a list of replication slaves currently registered with the\nmaster. Only slaves started with the --report-host=slave_name option\nare visible in this list.\n\nThe list is displayed on any server (not just the master server). The\noutput looks like this: mysql> SHOW SLAVE HOSTS;\n+------------+-----------+------+-----------+ | Server_id | Host | Port\n| Master_id | +------------+-----------+------+-----------+ | 192168010\n| iconnect2 | 3306 | 192168011 | | 1921680101 | athena | 3306 |\n192168011 | +------------+-----------+------+-----------+ Server_id:\nThe unique server ID of the slave server, as configured in the server''s\noption file, or on the command line with --server-id=value . Host: The\nhost name of the slave server, as configured in the server''s option\nfile, or on the command line with --report-host=value. Note that this\ncan differ from the machine name as configured in the operating system.\nPort: The port the slave server is listening on. Master_id: The unique\nserver ID of the master server that the slave server is replicating\nfrom. Some MySQL versions report another variable, Rpl_recovery_rank.\nThis variable was never used, and was eventually removed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-slave-hosts.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-slave-hosts.html');
INSERT INTO `help_topic` VALUES (131, 'START TRANSACTION', 7, 'Syntax:\nSTART TRANSACTION [WITH CONSISTENT SNAPSHOT] | BEGIN [WORK]\nCOMMIT [WORK] [AND [NO] CHAIN] [[NO] RELEASE]\nROLLBACK [WORK] [AND [NO] CHAIN] [[NO] RELEASE]\nSET AUTOCOMMIT = {0 | 1}\n\nThe START TRANSACTION and BEGIN statement begin a new transaction.\nCOMMIT commits the current transaction, making its changes permanent.\nROLLBACK rolls back the current transaction, canceling its changes. The\nSET AUTOCOMMIT statement disables or enables the default autocommit\nmode for the current connection.\n\nBeginning with MySQL 5.0.3, the optional WORK keyword is supported for\nCOMMIT and ROLLBACK, as are the CHAIN and RELEASE clauses. CHAIN and\nRELEASE can be used for additional control over transaction completion.\nThe value of the completion_type system variable determines the default\ncompletion behavior. See\nhttp://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html.\n\nThe AND CHAIN clause causes a new transaction to begin as soon as the\ncurrent one ends, and the new transaction has the same isolation level\nas the just-terminated transaction. The RELEASE clause causes the\nserver to disconnect the current client connection after terminating\nthe current transaction. Including the NO keyword suppresses CHAIN or\nRELEASE completion, which can be useful if the completion_type system\nvariable is set to cause chaining or release completion by default.\n\nBy default, MySQL runs with autocommit mode enabled. This means that as\nsoon as you execute a statement that updates (modifies) a table, MySQL\nstores the update on disk.\n\nIf you are using a transaction-safe storage engine (such as InnoDB,\nBDB, or NDB Cluster), you can disable autocommit mode with the\nfollowing statement:\n\nSET AUTOCOMMIT=0;\n\nAfter disabling autocommit mode by setting the AUTOCOMMIT variable to\nzero, you must use COMMIT to store your changes to disk or ROLLBACK if\nyou want to ignore the changes you have made since the beginning of\nyour transaction.\n\nTo disable autocommit mode for a single series of statements, use the\nSTART TRANSACTION statement:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/commit.html\n\n', 'START TRANSACTION;\nSELECT @A:=SUM(salary) FROM table1 WHERE type=1;\nUPDATE table2 SET summary=@A WHERE type=1;\nCOMMIT;\n', 'http://dev.mysql.com/doc/refman/5.0/en/commit.html');
INSERT INTO `help_topic` VALUES (132, 'BETWEEN AND', 17, 'Syntax:\nexpr BETWEEN min AND max\n\nIf expr is greater than or equal to min and expr is less than or equal\nto max, BETWEEN returns 1, otherwise it returns 0. This is equivalent\nto the expression (min <= expr AND expr <= max) if all the arguments\nare of the same type. Otherwise type conversion takes place according\nto the rules described in\nhttp://dev.mysql.com/doc/refman/5.0/en/type-conversion.html, but\napplied to all the three arguments.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 BETWEEN 2 AND 3;\n        -> 0\nmysql> SELECT ''b'' BETWEEN ''a'' AND ''c'';\n        -> 1\nmysql> SELECT 2 BETWEEN 2 AND ''3'';\n        -> 1\nmysql> SELECT 2 BETWEEN 2 AND ''x-3'';\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (133, 'MULTIPOLYGON', 22, 'MultiPolygon(poly1,poly2,...)\n\nConstructs a WKB MultiPolygon value from a set of WKB Polygon\narguments. If any argument is not a WKB Polygon, the return value is\nNULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (134, 'TIME_FORMAT', 28, 'Syntax:\nTIME_FORMAT(time,format)\n\nThis is used like the DATE_FORMAT() function, but the format string may\ncontain format specifiers only for hours, minutes, and seconds. Other\nspecifiers produce a NULL value or 0.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TIME_FORMAT(''100:00:00'', ''%H %k %h %I %l'');\n        -> ''100 100 04 04 4''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (135, 'LEFT', 33, 'Syntax:\nLEFT(str,len)\n\nReturns the leftmost len characters from the string str, or NULL if any\nargument is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LEFT(''foobarbar'', 5);\n        -> ''fooba''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (136, 'FLUSH QUERY CACHE', 24, 'You can defragment the query cache to better utilize its memory with\nthe FLUSH QUERY CACHE statement. The statement does not remove any\nqueries from the cache.\n\nThe RESET QUERY CACHE statement removes all query results from the\nquery cache. The FLUSH TABLES statement also does this.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/query-cache-status-and-maintenance.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/query-cache-status-and-maintenance.html');
INSERT INTO `help_topic` VALUES (137, 'SET DATA TYPE', 20, 'SET(''value1'',''value2'',...) [CHARACTER SET charset_name] [COLLATE\ncollation_name]\n\nA set. A string object that can have zero or more values, each of which\nmust be chosen from the list of values ''value1'', ''value2'', ... A SET\ncolumn can have a maximum of 64 members. SET values are represented\ninternally as integers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (138, 'RAND', 4, 'Syntax:\nRAND(), RAND(N)\n\nReturns a random floating-point value v in the range 0 <= v < 1.0. If a\nconstant integer argument N is specified, it is used as the seed value,\nwhich produces a repeatable sequence of column values.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT RAND();\n        -> 0.9233482386203\nmysql> SELECT RAND(20);\n        -> 0.15888261251047\nmysql> SELECT RAND(20);\n        -> 0.15888261251047\nmysql> SELECT RAND();\n        -> 0.63553050033332\nmysql> SELECT RAND();\n        -> 0.70100469486881\nmysql> SELECT RAND(20);\n        -> 0.15888261251047\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (139, 'RPAD', 33, 'Syntax:\nRPAD(str,len,padstr)\n\nReturns the string str, right-padded with the string padstr to a length\nof len characters. If str is longer than len, the return value is\nshortened to len characters.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT RPAD(''hi'',5,''?'');\n        -> ''hi???''\nmysql> SELECT RPAD(''hi'',1,''?'');\n        -> ''h''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (140, 'CREATE DATABASE', 36, 'Syntax:\nCREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name\n    [create_specification ...]\n\ncreate_specification:\n    [DEFAULT] CHARACTER SET charset_name\n  | [DEFAULT] COLLATE collation_name\n\nCREATE DATABASE creates a database with the given name. To use this\nstatement, you need the CREATE privilege for the database. CREATE\nSCHEMA is a synonym for CREATE DATABASE as of MySQL 5.0.2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-database.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-database.html');
INSERT INTO `help_topic` VALUES (141, 'DEC', 20, 'DEC[(M[,D])] [UNSIGNED] [ZEROFILL], NUMERIC[(M[,D])] [UNSIGNED]\n[ZEROFILL], FIXED[(M[,D])] [UNSIGNED] [ZEROFILL]\n\nThese types are synonyms for DECIMAL. The FIXED synonym is available\nfor compatibility with other database systems.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (142, 'VAR_POP', 14, 'Syntax:\nVAR_POP(expr)\n\nReturns the population standard variance of expr. It considers rows as\nthe whole population, not as a sample, so it has the number of rows as\nthe denominator. This function was added in MySQL 5.0.3. Before 5.0.3,\nyou can use VARIANCE(), which is equivalent but is not standard SQL.\n\nVAR_POP() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (143, 'ELT', 33, 'Syntax:\nELT(N,str1,str2,str3,...)\n\nReturns str1 if N = 1, str2 if N = 2, and so on. Returns NULL if N is\nless than 1 or greater than the number of arguments. ELT() is the\ncomplement of FIELD().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT ELT(1, ''ej'', ''Heja'', ''hej'', ''foo'');\n        -> ''ej''\nmysql> SELECT ELT(4, ''ej'', ''Heja'', ''hej'', ''foo'');\n        -> ''foo''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (144, 'ALTER VIEW', 36, 'Syntax:\nALTER\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\nThis statement changes the definition of a view, which must exist. The\nsyntax is similar to that for CREATE VIEW and the effect is the same as\nfor CREATE OR REPLACE VIEW. See [HELP CREATE VIEW]. This statement\nrequires the CREATE VIEW and DROP privileges for the view, and some\nprivilege for each column referred to in the SELECT statement. As of\nMySQL 5.0.52, ALTER VIEW is allowed only to the original definer or\nusers with the SUPER privilege.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/alter-view.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/alter-view.html');
INSERT INTO `help_topic` VALUES (145, 'SHOW DATABASES', 25, 'Syntax:\nSHOW {DATABASES | SCHEMAS}\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW DATABASES lists the databases on the MySQL server host. SHOW\nSCHEMAS is a synonym for SHOW DATABASES as of MySQL 5.0.2. The LIKE\nclause, if present, indicates which database names to match. The WHERE\nclause can be given to select rows using more general conditions, as\ndiscussed in http://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nYou see only those databases for which you have some kind of privilege,\nunless you have the global SHOW DATABASES privilege. You can also get\nthis list using the mysqlshow command.\n\nIf the server was started with the --skip-show-database option, you\ncannot use this statement at all unless you have the SHOW DATABASES\nprivilege.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-databases.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-databases.html');
INSERT INTO `help_topic` VALUES (146, '~', 18, 'Syntax:\n~\n\nInvert all bits.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 5 & ~1;\n        -> 4\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (147, 'TEXT', 20, 'TEXT[(M)] [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 65,535 (216 - 1) characters. The\neffective maximum length is less if the value contains multi-byte\ncharacters. Each TEXT value is stored using a two-byte length prefix\nthat indicates the number of bytes in the value.\n\nAn optional length M can be given for this type. If this is done, MySQL\ncreates the column as the smallest TEXT type large enough to hold\nvalues M characters long.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (148, 'CONCAT_WS', 33, 'Syntax:\nCONCAT_WS(separator,str1,str2,...)\n\nCONCAT_WS() stands for Concatenate With Separator and is a special form\nof CONCAT(). The first argument is the separator for the rest of the\narguments. The separator is added between the strings to be\nconcatenated. The separator can be a string, as can the rest of the\narguments. If the separator is NULL, the result is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT CONCAT_WS('','',''First name'',''Second name'',''Last Name'');\n        -> ''First name,Second name,Last Name''\nmysql> SELECT CONCAT_WS('','',''First name'',NULL,''Last Name'');\n        -> ''First name,Last Name''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (149, 'ROW_COUNT', 15, 'Syntax:\nROW_COUNT()\n\nROW_COUNT() returns the number of rows updated, inserted, or deleted by\nthe preceding statement. This is the same as the row count that the\nmysql client displays and the value from the mysql_affected_rows() C\nAPI function.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> INSERT INTO t VALUES(1),(2),(3);\nQuery OK, 3 rows affected (0.00 sec)\nRecords: 3  Duplicates: 0  Warnings: 0\n\nmysql> SELECT ROW_COUNT();\n+-------------+\n| ROW_COUNT() |\n+-------------+\n|           3 |\n+-------------+\n1 row in set (0.00 sec)\n\nmysql> DELETE FROM t WHERE i IN(1,2);\nQuery OK, 2 rows affected (0.00 sec)\n\nmysql> SELECT ROW_COUNT();\n+-------------+\n| ROW_COUNT() |\n+-------------+\n|           2 |\n+-------------+\n1 row in set (0.00 sec)\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (150, 'ASIN', 4, 'Syntax:\nASIN(X)\n\nReturns the arc sine of X, that is, the value whose sine is X. Returns\nNULL if X is not in the range -1 to 1.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT ASIN(0.2);\n        -> 0.20135792079033\nmysql> SELECT ASIN(''foo'');\n\n+-------------+\n| ASIN(''foo'') |\n+-------------+\n|           0 |\n+-------------+\n1 row in set, 1 warning (0.00 sec)\n\nmysql> SHOW WARNINGS;\n+---------+------+-----------------------------------------+\n| Level   | Code | Message                                 |\n+---------+------+-----------------------------------------+\n| Warning | 1292 | Truncated incorrect DOUBLE value: ''foo'' |\n+---------+------+-----------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (151, 'SHOW LOGS', 25, 'Syntax:\nSHOW [BDB] LOGS\n\nIn MySQL 5.0, this is a deprecated synonym for SHOW ENGINE BDB LOGS.\nSee [HELP SHOW ENGINE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-logs.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-logs.html');
INSERT INTO `help_topic` VALUES (152, 'SIGN', 4, 'Syntax:\nSIGN(X)\n\nReturns the sign of the argument as -1, 0, or 1, depending on whether X\nis negative, zero, or positive.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT SIGN(-32);\n        -> -1\nmysql> SELECT SIGN(0);\n        -> 0\nmysql> SELECT SIGN(234);\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (153, 'SEC_TO_TIME', 28, 'Syntax:\nSEC_TO_TIME(seconds)\n\nReturns the seconds argument, converted to hours, minutes, and seconds,\nas a TIME value. The range of the result is constrained to that of the\nTIME data type. A warning occurs if the argument corresponds to a value\noutside that range.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT SEC_TO_TIME(2378);\n        -> ''00:39:38''\nmysql> SELECT SEC_TO_TIME(2378) + 0;\n        -> 3938\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (154, 'FLOAT', 20, 'FLOAT[(M,D)] [UNSIGNED] [ZEROFILL]\n\nA small (single-precision) floating-point number. Allowable values are\n-3.402823466E+38 to -1.175494351E-38, 0, and 1.175494351E-38 to\n3.402823466E+38. These are the theoretical limits, based on the IEEE\nstandard. The actual range might be slightly smaller depending on your\nhardware or operating system.\n\nM is the total number of digits and D is the number of digits following\nthe decimal point. If M and D are omitted, values are stored to the\nlimits allowed by the hardware. A single-precision floating-point\nnumber is accurate to approximately 7 decimal places.\n\nUNSIGNED, if specified, disallows negative values.\n\nUsing FLOAT might give you some unexpected problems because all\ncalculations in MySQL are done with double precision. See\nhttp://dev.mysql.com/doc/refman/5.0/en/no-matching-rows.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (155, 'LOCATE', 33, 'Syntax:\nLOCATE(substr,str), LOCATE(substr,str,pos)\n\nThe first syntax returns the position of the first occurrence of\nsubstring substr in string str. The second syntax returns the position\nof the first occurrence of substring substr in string str, starting at\nposition pos. Returns 0 if substr is not in str.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LOCATE(''bar'', ''foobarbar'');\n        -> 4\nmysql> SELECT LOCATE(''xbar'', ''foobar'');\n        -> 0\nmysql> SELECT LOCATE(''bar'', ''foobarbar'', 5);\n        -> 7\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (156, 'CHARSET', 15, 'Syntax:\nCHARSET(str)\n\nReturns the character set of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT CHARSET(''abc'');\n        -> ''latin1''\nmysql> SELECT CHARSET(CONVERT(''abc'' USING utf8));\n        -> ''utf8''\nmysql> SELECT CHARSET(USER());\n        -> ''utf8''\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (157, 'SUBDATE', 28, 'Syntax:\nSUBDATE(date,INTERVAL expr unit), SUBDATE(expr,days)\n\nWhen invoked with the INTERVAL form of the second argument, SUBDATE()\nis a synonym for DATE_SUB(). For information on the INTERVAL unit\nargument, see the discussion for DATE_ADD().\n\nmysql> SELECT DATE_SUB(''1998-01-02'', INTERVAL 31 DAY);\n        -> ''1997-12-02''\nmysql> SELECT SUBDATE(''1998-01-02'', INTERVAL 31 DAY);\n        -> ''1997-12-02''\n\nThe second form allows the use of an integer value for days. In such\ncases, it is interpreted as the number of days to be subtracted from\nthe date or datetime expression expr.\n\nmysql> SELECT SUBDATE(''1998-01-02 12:00:00'', 31);\n        -> ''1997-12-02 12:00:00''\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (158, 'DAYOFYEAR', 28, 'Syntax:\nDAYOFYEAR(date)\n\nReturns the day of the year for date, in the range 1 to 366.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DAYOFYEAR(''1998-02-03'');\n        -> 34\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (159, 'LONGTEXT', 20, 'LONGTEXT [CHARACTER SET charset_name] [COLLATE collation_name]\n\nA TEXT column with a maximum length of 4,294,967,295 or 4GB (232 - 1)\ncharacters. The effective maximum length is less if the value contains\nmulti-byte characters. The effective maximum length of LONGTEXT columns\nalso depends on the configured maximum packet size in the client/server\nprotocol and available memory. Each LONGTEXT value is stored using a\nfour-byte length prefix that indicates the number of bytes in the\nvalue.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (160, '%', 4, 'Syntax:\nN % M\n\nModulo operation. Returns the remainder of N divided by M. For more\ninformation, see the description for the MOD() function in [HELP ABS].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (161, 'DISJOINT', 26, 'Disjoint(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 is spatially disjoint from (does\nnot intersect) g2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (162, 'KILL', 25, 'Syntax:\nKILL [CONNECTION | QUERY] thread_id\n\nEach connection to mysqld runs in a separate thread. You can see which\nthreads are running with the SHOW PROCESSLIST statement and kill a\nthread with the KILL thread_id statement.\n\nIn MySQL 5.0.0, KILL allows the optional CONNECTION or QUERY modifier:\n\no KILL CONNECTION is the same as KILL with no modifier: It terminates\n  the connection associated with the given thread_id.\n\no KILL QUERY terminates the statement that the connection is currently\n  executing, but leaves the connection itself intact.\n\nIf you have the PROCESS privilege, you can see all threads. If you have\nthe SUPER privilege, you can kill all threads and statements.\nOtherwise, you can see and kill only your own threads and statements.\n\nYou can also use the mysqladmin processlist and mysqladmin kill\ncommands to examine and kill threads.\n\n*Note*: You cannot use KILL with the Embedded MySQL Server library,\nbecause the embedded server merely runs inside the threads of the host\napplication. It does not create any connection threads of its own.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/kill.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/kill.html');
INSERT INTO `help_topic` VALUES (163, 'ASTEXT', 3, 'AsText(g)\n\nConverts a value in internal geometry format to its WKT representation\nand returns the string result.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-to-convert-geometries-between-formats.html\n\n', 'mysql> SET @g = ''LineString(1 1,2 2,3 3)'';\nmysql> SELECT AsText(GeomFromText(@g));\n+--------------------------+\n| AsText(GeomFromText(@g)) |\n+--------------------------+\n| LINESTRING(1 1,2 2,3 3)  |\n+--------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/functions-to-convert-geometries-between-formats.html');
INSERT INTO `help_topic` VALUES (164, 'LPAD', 33, 'Syntax:\nLPAD(str,len,padstr)\n\nReturns the string str, left-padded with the string padstr to a length\nof len characters. If str is longer than len, the return value is\nshortened to len characters.\n\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LPAD(''hi'',4,''??'');\n        -> ''??hi''\nmysql> SELECT LPAD(''hi'',1,''??'');\n        -> ''h''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (165, 'RESTORE TABLE', 19, 'Syntax:\nRESTORE TABLE tbl_name [, tbl_name] ... FROM ''/path/to/backup/directory''\n\nRESTORE TABLE restores the table or tables from a backup that was made\nwith BACKUP TABLE. The directory should be specified as a full\npathname.\n\nExisting tables are not overwritten; if you try to restore over an\nexisting table, an error occurs. Just as for BACKUP TABLE, RESTORE\nTABLE currently works only for MyISAM tables. Restored tables are not\nreplicated from master to slave.\n\nThe backup for each table consists of its .frm format file and .MYD\ndata file. The restore operation restores those files, and then uses\nthem to rebuild the .MYI index file. Restoring takes longer than\nbacking up due to the need to rebuild the indexes. The more indexes the\ntable has, the longer it takes.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/restore-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/restore-table.html');
INSERT INTO `help_topic` VALUES (166, 'DECLARE CONDITION', 35, 'Syntax:\nDECLARE condition_name CONDITION FOR condition_value\n\ncondition_value:\n    SQLSTATE [VALUE] sqlstate_value\n  | mysql_error_code\n\nThis statement specifies conditions that need specific handling. It\nassociates a name with a specified error condition. The name can\nsubsequently be used in a DECLARE HANDLER statement. See [HELP DECLARE\nHANDLER].\n\nA condition_value can be an SQLSTATE value or a MySQL error code.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/declare-conditions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/declare-conditions.html');
INSERT INTO `help_topic` VALUES (167, 'OVERLAPS', 26, 'Overlaps(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 spatially overlaps g2. The term\nspatially overlaps is used if two geometries intersect and their\nintersection results in a geometry of the same dimension but not equal\nto either of the given geometries.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (168, 'NUMGEOMETRIES', 23, 'NumGeometries(gc)\n\nReturns the number of geometries in the GeometryCollection value gc.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/geometrycollection-property-functions.html\n\n', 'mysql> SET @gc = ''GeometryCollection(Point(1 1),LineString(2 2, 3 3))'';\nmysql> SELECT NumGeometries(GeomFromText(@gc));\n+----------------------------------+\n| NumGeometries(GeomFromText(@gc)) |\n+----------------------------------+\n|                                2 |\n+----------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/geometrycollection-property-functions.html');
INSERT INTO `help_topic` VALUES (169, 'SET GLOBAL SQL_SLAVE_SKIP_COUNTER', 25, 'Syntax:\nSET GLOBAL SQL_SLAVE_SKIP_COUNTER = N\n\nThis statement skips the next N events from the master. This is useful\nfor recovering from replication stops caused by a statement.\n\nThis statement is valid only when the slave thread is not running.\nOtherwise, it produces an error.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-global-sql-slave-skip-counter.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-global-sql-slave-skip-counter.html');
INSERT INTO `help_topic` VALUES (170, 'MONTHNAME', 28, 'Syntax:\nMONTHNAME(date)\n\nReturns the full name of the month for date. As of MySQL 5.0.25, the\nlanguage used for the name is controlled by the value of the\nlc_time_names system variable\n(http://dev.mysql.com/doc/refman/5.0/en/locale-support.html).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MONTHNAME(''1998-02-05'');\n        -> ''February''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (171, 'PROCEDURE ANALYSE', 34, 'Syntax:\nanalyse([max_elements[,max_memory]])\n\nThis procedure is defined in the sql/sql_analyse.cc file. It examines\nthe result from a query and returns an analysis of the results that\nsuggests optimal data types for each column. To obtain this analysis,\nappend PROCEDURE ANALYSE to the end of a SELECT statement:\n\nSELECT ... FROM ... WHERE ... PROCEDURE ANALYSE([max_elements,[max_memory]])\n\nFor example:\n\nSELECT col1, col2 FROM table1 PROCEDURE ANALYSE(10, 2000);\n\nThe results show some statistics for the values returned by the query,\nand propose an optimal data type for the columns. This can be helpful\nfor checking your existing tables, or after importing new data. You may\nneed to try different settings for the arguments so that PROCEDURE\nANALYSE() does not suggest the ENUM data type when it is not\nappropriate.\n\nThe arguments are optional and are used as follows:\n\no max_elements (default 256) is the maximum number of distinct values\n  that analyse notices per column. This is used by analyse to check\n  whether the optimal data type should be of type ENUM.\n\no max_memory (default 8192) is the maximum amount of memory that\n  analyse should allocate per column while trying to find all distinct\n  values.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/procedure-analyse.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/procedure-analyse.html');
INSERT INTO `help_topic` VALUES (172, 'MBREQUAL', 5, 'MBREqual(g1,g2)\n\nReturns 1 or 0 to indicate whether the Minimum Bounding Rectangles of\nthe two geometries g1 and g2 are the same.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (173, 'CHANGE MASTER TO', 25, 'Syntax:\nCHANGE MASTER TO master_def [, master_def] ...\n\nmaster_def:\n    MASTER_HOST = ''host_name''\n  | MASTER_USER = ''user_name''\n  | MASTER_PASSWORD = ''password''\n  | MASTER_PORT = port_num\n  | MASTER_CONNECT_RETRY = count\n  | MASTER_LOG_FILE = ''master_log_name''\n  | MASTER_LOG_POS = master_log_pos\n  | RELAY_LOG_FILE = ''relay_log_name''\n  | RELAY_LOG_POS = relay_log_pos\n  | MASTER_SSL = {0|1}\n  | MASTER_SSL_CA = ''ca_file_name''\n  | MASTER_SSL_CAPATH = ''ca_directory_name''\n  | MASTER_SSL_CERT = ''cert_file_name''\n  | MASTER_SSL_KEY = ''key_file_name''\n  | MASTER_SSL_CIPHER = ''cipher_list''\n\nCHANGE MASTER TO changes the parameters that the slave server uses for\nconnecting to and communicating with the master server. It also updates\nthe contents of the master.info and relay-log.info files.\n\nMASTER_USER, MASTER_PASSWORD, MASTER_SSL, MASTER_SSL_CA,\nMASTER_SSL_CAPATH, MASTER_SSL_CERT, MASTER_SSL_KEY, and\nMASTER_SSL_CIPHER provide information to the slave about how to connect\nto its master.\n\nThe SSL options (MASTER_SSL, MASTER_SSL_CA, MASTER_SSL_CAPATH,\nMASTER_SSL_CERT, MASTER_SSL_KEY, and MASTER_SSL_CIPHER) can be changed\neven on slaves that are compiled without SSL support. They are saved to\nthe master.info file, but are ignored unless you use a server that has\nSSL support enabled.\n\nIf you don''t specify a given parameter, it keeps its old value, except\nas indicated in the following discussion. For example, if the password\nto connect to your MySQL master has changed, you just need to issue\nthese statements to tell the slave about the new password:\n\nSTOP SLAVE; -- if replication was running\nCHANGE MASTER TO MASTER_PASSWORD=''new3cret'';\nSTART SLAVE; -- if you want to restart replication\n\nThere is no need to specify the parameters that do not change (host,\nport, user, and so forth).\n\nMASTER_HOST and MASTER_PORT are the hostname (or IP address) of the\nmaster host and its TCP/IP port. Note that if MASTER_HOST is equal to\nlocalhost, then, like in other parts of MySQL, the port number might be\nignored.\n\n*Note*: Replication cannot use Unix socket files. You must be able to\nconnect to the master MySQL server using TCP/IP.\n\nIf you specify MASTER_HOST or MASTER_PORT, the slave assumes that the\nmaster server is different from before (even if you specify a host or\nport value that is the same as the current value.) In this case, the\nold values for the master binary log name and position are considered\nno longer applicable, so if you do not specify MASTER_LOG_FILE and\nMASTER_LOG_POS in the statement, MASTER_LOG_FILE='''' and\nMASTER_LOG_POS=4 are silently appended to it.\n\nMASTER_LOG_FILE and MASTER_LOG_POS are the coordinates at which the\nslave I/O thread should begin reading from the master the next time the\nthread starts. If you specify either of them, you cannot specify\nRELAY_LOG_FILE or RELAY_LOG_POS. If neither of MASTER_LOG_FILE or\nMASTER_LOG_POS are specified, the slave uses the last coordinates of\nthe slave SQL thread before CHANGE MASTER was issued. This ensures that\nthere is no discontinuity in replication, even if the slave SQL thread\nwas late compared to the slave I/O thread, when you merely want to\nchange, say, the password to use.\n\nCHANGE MASTER deletes all relay log files and starts a new one, unless\nyou specify RELAY_LOG_FILE or RELAY_LOG_POS. In that case, relay logs\nare kept; the relay_log_purge global variable is set silently to 0.\n\nCHANGE MASTER is useful for setting up a slave when you have the\nsnapshot of the master and have recorded the log and the offset\ncorresponding to it. After loading the snapshot into the slave, you can\nrun CHANGE MASTER TO MASTER_LOG_FILE=''log_name_on_master'',\nMASTER_LOG_POS=log_offset_on_master on the slave.\n\nThe following example changes the master and master''s binary log\ncoordinates. This is used when you want to set up the slave to\nreplicate the master:\n\nCHANGE MASTER TO\n  MASTER_HOST=''master2.mycompany.com'',\n  MASTER_USER=''replication'',\n  MASTER_PASSWORD=''bigs3cret'',\n  MASTER_PORT=3306,\n  MASTER_LOG_FILE=''master2-bin.001'',\n  MASTER_LOG_POS=4,\n  MASTER_CONNECT_RETRY=10;\n\nThe next example shows an operation that is less frequently employed.\nIt is used when the slave has relay logs that you want it to execute\nagain for some reason. To do this, the master need not be reachable.\nYou need only use CHANGE MASTER TO and start the SQL thread (START\nSLAVE SQL_THREAD):\n\nCHANGE MASTER TO\n  RELAY_LOG_FILE=''slave-relay-bin.006'',\n  RELAY_LOG_POS=4025;\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/change-master-to.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/change-master-to.html');
INSERT INTO `help_topic` VALUES (174, 'DROP DATABASE', 36, 'Syntax:\nDROP {DATABASE | SCHEMA} [IF EXISTS] db_name\n\nDROP DATABASE drops all tables in the database and deletes the\ndatabase. Be very careful with this statement! To use DROP DATABASE,\nyou need the DROP privilege on the database. DROP SCHEMA is a synonym\nfor DROP DATABASE as of MySQL 5.0.2.\n\n*Important*: When a database is dropped, user privileges on the\ndatabase are not automatically dropped. See [HELP GRANT].\n\nIF EXISTS is used to prevent an error from occurring if the database\ndoes not exist.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-database.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-database.html');
INSERT INTO `help_topic` VALUES (175, 'TIMESTAMP FUNCTION', 28, 'Syntax:\nTIMESTAMP(expr), TIMESTAMP(expr1,expr2)\n\nWith a single argument, this function returns the date or datetime\nexpression expr as a datetime value. With two arguments, it adds the\ntime expression expr2 to the date or datetime expression expr1 and\nreturns the result as a datetime value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TIMESTAMP(''2003-12-31'');\n        -> ''2003-12-31 00:00:00''\nmysql> SELECT TIMESTAMP(''2003-12-31 12:00:00'',''12:00:00'');\n        -> ''2004-01-01 00:00:00''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (176, 'CHARACTER_LENGTH', 33, 'Syntax:\nCHARACTER_LENGTH(str)\n\nCHARACTER_LENGTH() is a synonym for CHAR_LENGTH().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (177, 'SHOW GRANTS', 25, 'Syntax:\nSHOW GRANTS [FOR user]\n\nThis statement lists the GRANT statement or statements that must be\nissued to duplicate the privileges that are granted to a MySQL user\naccount. The account is named using the same format as for the GRANT\nstatement; for example, ''jeffrey''@''localhost''. If you specify only the\nusername part of the account name, a hostname part of ''%'' is used. For\nadditional information about specifying account names, see [HELP\nGRANT].\n\nmysql> SHOW GRANTS FOR ''root''@''localhost'';\n+---------------------------------------------------------------------+\n| Grants for root@localhost                                           |\n+---------------------------------------------------------------------+\n| GRANT ALL PRIVILEGES ON *.* TO ''root''@''localhost'' WITH GRANT OPTION |\n+---------------------------------------------------------------------+\n\nTo list the privileges granted to the account that you are using to\nconnect to the server, you can use any of the following statements:\n\nSHOW GRANTS;\nSHOW GRANTS FOR CURRENT_USER;\nSHOW GRANTS FOR CURRENT_USER();\n\nAs of MySQL 5.0.24, if SHOW GRANTS FOR CURRENT_USER (or any of the\nequivalent syntaxes) is used in DEFINER context, such as within a\nstored procedure that is defined with SQL SECURITY DEFINER), the grants\ndisplayed are those of the definer and not the invoker.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-grants.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-grants.html');
INSERT INTO `help_topic` VALUES (178, 'SHOW PRIVILEGES', 25, 'Syntax:\nSHOW PRIVILEGES\n\nSHOW PRIVILEGES shows the list of system privileges that the MySQL\nserver supports. The exact list of privileges depends on the version of\nyour server.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-privileges.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-privileges.html');
INSERT INTO `help_topic` VALUES (179, 'INSERT FUNCTION', 33, 'Syntax:\nINSERT(str,pos,len,newstr)\n\nReturns the string str, with the substring beginning at position pos\nand len characters long replaced by the string newstr. Returns the\noriginal string if pos is not within the length of the string. Replaces\nthe rest of the string from position pos if len is not within the\nlength of the rest of the string. Returns NULL if any argument is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT INSERT(''Quadratic'', 3, 4, ''What'');\n        -> ''QuWhattic''\nmysql> SELECT INSERT(''Quadratic'', -1, 4, ''What'');\n        -> ''Quadratic''\nmysql> SELECT INSERT(''Quadratic'', 3, 100, ''What'');\n        -> ''QuWhat''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (180, 'CRC32', 4, 'Syntax:\nCRC32(expr)\n\nComputes a cyclic redundancy check value and returns a 32-bit unsigned\nvalue. The result is NULL if the argument is NULL. The argument is\nexpected to be a string and (if possible) is treated as one if it is\nnot.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT CRC32(''MySQL'');\n        -> 3259397556\nmysql> SELECT CRC32(''mysql'');\n        -> 2501908538\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (181, 'XOR', 12, 'Syntax:\nXOR\n\nLogical XOR. Returns NULL if either operand is NULL. For non-NULL\noperands, evaluates to 1 if an odd number of operands is non-zero,\notherwise 0 is returned.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html\n\n', 'mysql> SELECT 1 XOR 1;\n        -> 0\nmysql> SELECT 1 XOR 0;\n        -> 1\nmysql> SELECT 1 XOR NULL;\n        -> NULL\nmysql> SELECT 1 XOR 1 XOR 1;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html');
INSERT INTO `help_topic` VALUES (182, 'STARTPOINT', 11, 'StartPoint(ls)\n\nReturns the Point that is the start point of the LineString value ls.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html\n\n', 'mysql> SET @ls = ''LineString(1 1,2 2,3 3)'';\nmysql> SELECT AsText(StartPoint(GeomFromText(@ls)));\n+---------------------------------------+\n| AsText(StartPoint(GeomFromText(@ls))) |\n+---------------------------------------+\n| POINT(1 1)                            |\n+---------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html');
INSERT INTO `help_topic` VALUES (183, 'DECLARE VARIABLE', 35, 'Syntax:\nDECLARE var_name[,...] type [DEFAULT value]\n\nThis statement is used to declare local variables. To provide a default\nvalue for the variable, include a DEFAULT clause. The value can be\nspecified as an expression; it need not be a constant. If the DEFAULT\nclause is missing, the initial value is NULL.\n\nLocal variables are treated like routine parameters with respect to\ndata type and overflow checking. See [HELP CREATE PROCEDURE].\n\nThe scope of a local variable is within the BEGIN ... END block where\nit is declared. The variable can be referred to in blocks nested within\nthe declaring block, except those blocks that declare a variable with\nthe same name.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/declare-local-variables.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/declare-local-variables.html');
INSERT INTO `help_topic` VALUES (184, 'MPOLYFROMTEXT', 3, 'MPolyFromText(wkt[,srid]), MultiPolygonFromText(wkt[,srid])\n\nConstructs a MULTIPOLYGON value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (185, 'GRANT', 8, 'Syntax:\nGRANT priv_type [(column_list)] [, priv_type [(column_list)]] ...\n    ON [object_type] {tbl_name | * | *.* | db_name.*}\n    TO user [IDENTIFIED BY [PASSWORD] ''password'']\n        [, user [IDENTIFIED BY [PASSWORD] ''password'']] ...\n    [REQUIRE\n        NONE |\n        [{SSL| X509}]\n        [CIPHER ''cipher'' [AND]]\n        [ISSUER ''issuer'' [AND]]\n        [SUBJECT ''subject'']]\n    [WITH with_option [with_option] ...]\n\nobject_type =\n    TABLE\n  | FUNCTION\n  | PROCEDURE\n\nwith_option =\n    GRANT OPTION\n  | MAX_QUERIES_PER_HOUR count\n  | MAX_UPDATES_PER_HOUR count\n  | MAX_CONNECTIONS_PER_HOUR count\n  | MAX_USER_CONNECTIONS count\n\nThe GRANT statement enables system administrators to create MySQL user\naccounts and to grant rights to from accounts. To use GRANT, you must\nhave the GRANT OPTION privilege, and you must have the privileges that\nyou are granting. The REVOKE statement is related and enables\nadministrators to remove account privileges. See [HELP REVOKE].\n\nMySQL account information is stored in the tables of the mysql\ndatabase. This database and the access control system are discussed\nextensively in\nhttp://dev.mysql.com/doc/refman/5.0/en/server-administration.html,\nwhich you should consult for additional details.\n\n*Important*: Some releases of MySQL introduce changes to the structure\nof the grant tables to add new privileges or features. Whenever you\nupdate to a new version of MySQL, you should update your grant tables\nto make sure that they have the current structure so that you can take\nadvantage of any new capabilities. See\nhttp://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html.\n\nIf the grant tables hold privilege rows that contain mixed-case\ndatabase or table names and the lower_case_table_names system variable\nis set to a non-zero value, REVOKE cannot be used to revoke these\nprivileges. It will be necessary to manipulate the grant tables\ndirectly. (GRANT will not create such rows when lower_case_table_names\nis set, but such rows might have been created prior to setting the\nvariable.)\n\nPrivileges can be granted at several levels. The examples shown here\ninclude no IDENTIFIED BY ''password'' clause for brevity, but you should\ninclude one if the account does not already exist to avoid creating an\naccount with no password.\n\no Global level\n\n  Global privileges apply to all databases on a given server. These\n  privileges are stored in the mysql.user table. GRANT ALL ON *.* and\n  REVOKE ALL ON *.* grant and revoke only global privileges.\n\nGRANT ALL ON *.* TO ''someuser''@''somehost'';\nGRANT SELECT, INSERT ON *.* TO ''someuser''@''somehost'';\n\no Database level\n\n  Database privileges apply to all objects in a given database. These\n  privileges are stored in the mysql.db and mysql.host tables. GRANT\n  ALL ON db_name.* and REVOKE ALL ON db_name.* grant and revoke only\n  database privileges.\n\nGRANT ALL ON mydb.* TO ''someuser''@''somehost'';\nGRANT SELECT, INSERT ON mydb.* TO ''someuser''@''somehost'';\n\no Table level\n\n  Table privileges apply to all columns in a given table. These\n  privileges are stored in the mysql.tables_priv table. GRANT ALL ON\n  db_name.tbl_name and REVOKE ALL ON db_name.tbl_name grant and revoke\n  only table privileges.\n\nGRANT ALL ON mydb.mytbl TO ''someuser''@''somehost'';\nGRANT SELECT, INSERT ON mydb.mytbl TO ''someuser''@''somehost'';\n\no Column level\n\n  Column privileges apply to single columns in a given table. These\n  privileges are stored in the mysql.columns_priv table. When using\n  REVOKE, you must specify the same columns that were granted. The\n  column or columns for which the privileges are to be granted must be\n  enclosed within parentheses.\n\nGRANT SELECT (col1), INSERT (col1,col2) ON mydb.mytbl TO ''someuser''@''somehost'';\n\no Routine level\n\n  The CREATE ROUTINE, ALTER ROUTINE, EXECUTE, and GRANT privileges\n  apply to stored routines (functions and procedures). They can be\n  granted at the global and database levels. Also, except for CREATE\n  ROUTINE, these privileges can be granted at the routine level for\n  individual routines and are stored in the mysql.procs_priv table.\n\nGRANT CREATE ROUTINE ON mydb.* TO ''someuser''@''somehost'';\nGRANT EXECUTE ON PROCEDURE mydb.myproc TO ''someuser''@''somehost'';\n\nThe object_type clause was added in MySQL 5.0.6. It should be specified\nas TABLE, FUNCTION, or PROCEDURE when the following object is a table,\na stored function, or a stored procedure.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/grant.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/grant.html');
INSERT INTO `help_topic` VALUES (186, 'MBRINTERSECTS', 5, 'MBRIntersects(g1,g2)\n\nReturns 1 or 0 to indicate whether the Minimum Bounding Rectangles of\nthe two geometries g1 and g2 intersect.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (187, 'BIT_OR', 14, 'Syntax:\nBIT_OR(expr)\n\nReturns the bitwise OR of all bits in expr. The calculation is\nperformed with 64-bit (BIGINT) precision.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (188, 'YEARWEEK', 28, 'Syntax:\nYEARWEEK(date), YEARWEEK(date,mode)\n\nReturns year and week for a date. The mode argument works exactly like\nthe mode argument to WEEK(). The year in the result may be different\nfrom the year in the date argument for the first and the last week of\nthe year.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT YEARWEEK(''1987-01-01'');\n        -> 198653\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (189, 'NOT BETWEEN', 17, 'Syntax:\nexpr NOT BETWEEN min AND max\n\nThis is the same as NOT (expr BETWEEN min AND max).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (190, 'IS NOT', 17, 'Syntax:\nIS NOT boolean_value\n\nTests a value against a boolean value, where boolean_value can be TRUE,\nFALSE, or UNKNOWN.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 IS NOT UNKNOWN, 0 IS NOT UNKNOWN, NULL IS NOT UNKNOWN;\n        -> 1, 1, 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (191, 'LOG10', 4, 'Syntax:\nLOG10(X)\n\nReturns the base-10 logarithm of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT LOG10(2);\n        -> 0.30102999566398\nmysql> SELECT LOG10(100);\n        -> 2\nmysql> SELECT LOG10(-100);\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (192, 'SQRT', 4, 'Syntax:\nSQRT(X)\n\nReturns the square root of a non-negative number X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT SQRT(4);\n        -> 2\nmysql> SELECT SQRT(20);\n        -> 4.4721359549996\nmysql> SELECT SQRT(-16);\n        -> NULL        \n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (193, 'DECIMAL', 20, 'DECIMAL[(M[,D])] [UNSIGNED] [ZEROFILL]\n\nFor MySQL 5.0.3 and above:\n\nA packed "exact" fixed-point number. M is the total number of digits\n(the precision) and D is the number of digits after the decimal point\n(the scale). The decimal point and (for negative numbers) the "-" sign\nare not counted in M. If D is 0, values have no decimal point or\nfractional part. The maximum number of digits (M) for DECIMAL is 65 (64\nfrom 5.0.3 to 5.0.5). The maximum number of supported decimals (D) is\n30. If D is omitted, the default is 0. If M is omitted, the default is\n10.\n\nUNSIGNED, if specified, disallows negative values.\n\nAll basic calculations (+, -, *, /) with DECIMAL columns are done with\na precision of 65 digits.\n\nBefore MySQL 5.0.3:\n\nAn unpacked fixed-point number. Behaves like a CHAR column; "unpacked"\nmeans the number is stored as a string, using one character for each\ndigit of the value. M is the total number of digits and D is the number\nof digits after the decimal point. The decimal point and (for negative\nnumbers) the "-" sign are not counted in M, although space for them is\nreserved. If D is 0, values have no decimal point or fractional part.\nThe maximum range of DECIMAL values is the same as for DOUBLE, but the\nactual range for a given DECIMAL column may be constrained by the\nchoice of M and D. If D is omitted, the default is 0. If M is omitted,\nthe default is 10.\n\nUNSIGNED, if specified, disallows negative values.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (194, 'CREATE FUNCTION', 34, 'Syntax:\nCREATE [AGGREGATE] FUNCTION function_name RETURNS {STRING|INTEGER|REAL|DECIMAL}\n    SONAME shared_library_name\n\nA user-defined function (UDF) is a way to extend MySQL with a new\nfunction that works like a native (built-in) MySQL function such as\nABS() or CONCAT().\n\nfunction_name is the name that should be used in SQL statements to\ninvoke the function. The RETURNS clause indicates the type of the\nfunction''s return value. As of MySQL 5.0.3, DECIMAL is a legal value\nafter RETURNS, but currently DECIMAL functions return string values and\nshould be written like STRING functions.\n\nshared_library_name is the basename of the shared object file that\ncontains the code that implements the function. The file must be\nlocated in a directory that is searched by your system''s dynamic\nlinker.\n\nTo create a function, you must have the INSERT and privilege for the\nmysql database. This is necessary because CREATE FUNCTION adds a row to\nthe mysql.func system table that records the function''s name, type, and\nshared library name. If you do not have this table, you should run the\nmysql_upgrade command to create it. See\nhttp://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-function.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-function.html');
INSERT INTO `help_topic` VALUES (195, 'GEOMETRYN', 23, 'GeometryN(gc,N)\n\nReturns the N-th geometry in the GeometryCollection value gc.\nGeometries are numbered beginning with 1.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/geometrycollection-property-functions.html\n\n', 'mysql> SET @gc = ''GeometryCollection(Point(1 1),LineString(2 2, 3 3))'';\nmysql> SELECT AsText(GeometryN(GeomFromText(@gc),1));\n+----------------------------------------+\n| AsText(GeometryN(GeomFromText(@gc),1)) |\n+----------------------------------------+\n| POINT(1 1)                             |\n+----------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/geometrycollection-property-functions.html');
INSERT INTO `help_topic` VALUES (196, 'CREATE INDEX', 36, 'Syntax:\nCREATE [UNIQUE|FULLTEXT|SPATIAL] INDEX index_name\n    [index_type]\n    ON tbl_name (index_col_name,...)\n\nindex_col_name:\n    col_name [(length)] [ASC | DESC]\n\nindex_type:\n    USING {BTREE | HASH}\n\nCREATE INDEX is mapped to an ALTER TABLE statement to create indexes.\nSee [HELP ALTER TABLE]. CREATE INDEX cannot be used to create a PRIMARY\nKEY; use ALTER TABLE instead. For more information about indexes, see\nhttp://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-index.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-index.html');
INSERT INTO `help_topic` VALUES (197, 'ALTER DATABASE', 36, 'Syntax:\nALTER {DATABASE | SCHEMA} [db_name]\n    alter_specification ...\n\nalter_specification:\n    [DEFAULT] CHARACTER SET charset_name\n  | [DEFAULT] COLLATE collation_name\n\nALTER DATABASE enables you to change the overall characteristics of a\ndatabase. These characteristics are stored in the db.opt file in the\ndatabase directory. To use ALTER DATABASE, you need the ALTER privilege\non the database. ALTER SCHEMA is a synonym for ALTER DATABASE as of\nMySQL 5.0.2.\n\nThe CHARACTER SET clause changes the default database character set.\nThe COLLATE clause changes the default database collation.\nhttp://dev.mysql.com/doc/refman/5.0/en/charset.html, discusses\ncharacter set and collation names.\n\nThe database name can be omitted, in which case the statement applies\nto the default database.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/alter-database.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/alter-database.html');
INSERT INTO `help_topic` VALUES (198, '<<', 18, 'Syntax:\n<<\n\nShifts a longlong (BIGINT) number to the left.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 1 << 2;\n        -> 4\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (199, 'SHOW TABLE STATUS', 25, 'Syntax:\nSHOW TABLE STATUS [FROM db_name]\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW TABLE STATUS works likes SHOW TABLES, but provides a lot of\ninformation about each table. You can also get this list using the\nmysqlshow --status db_name command. The LIKE clause, if present,\nindicates which table names to match. The WHERE clause can be given to\nselect rows using more general conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-table-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-table-status.html');
INSERT INTO `help_topic` VALUES (200, 'MD5', 10, 'Syntax:\nMD5(str)\n\nCalculates an MD5 128-bit checksum for the string. The value is\nreturned as a binary string of 32 hex digits, or NULL if the argument\nwas NULL. The return value can, for example, be used as a hash key.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT MD5(''testing'');\n        -> ''ae2b1fca515949e5d54fb22b8ed95575''\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (201, '<', 17, 'Syntax:\n<\n\nLess than:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 2 < 2;\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (202, 'UNIX_TIMESTAMP', 28, 'Syntax:\nUNIX_TIMESTAMP(), UNIX_TIMESTAMP(date)\n\nIf called with no argument, returns a Unix timestamp (seconds since\n''1970-01-01 00:00:00'' UTC) as an unsigned integer. If UNIX_TIMESTAMP()\nis called with a date argument, it returns the value of the argument as\nseconds since ''1970-01-01 00:00:00'' UTC. date may be a DATE string, a\nDATETIME string, a TIMESTAMP, or a number in the format YYMMDD or\nYYYYMMDD. The server interprets date as a value in the current time\nzone and converts it to an internal value in UTC. Clients can set their\ntime zone as described in\nhttp://dev.mysql.com/doc/refman/5.0/en/time-zone-support.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT UNIX_TIMESTAMP();\n        -> 1196440210\nmysql> SELECT UNIX_TIMESTAMP(''2007-11-30 10:30:19'');\n        -> 1196440219\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (203, 'DAYOFMONTH', 28, 'Syntax:\nDAYOFMONTH(date)\n\nReturns the day of the month for date, in the range 1 to 31, or 0 for\ndates such as ''0000-00-00'' or ''2008-00-00'' that have a zero day part.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DAYOFMONTH(''1998-02-03'');\n        -> 3\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (204, 'ASCII', 33, 'Syntax:\nASCII(str)\n\nReturns the numeric value of the leftmost character of the string str.\nReturns 0 if str is the empty string. Returns NULL if str is NULL.\nASCII() works for 8-bit characters.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT ASCII(''2'');\n        -> 50\nmysql> SELECT ASCII(2);\n        -> 50\nmysql> SELECT ASCII(''dx'');\n        -> 100\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (205, 'DIV', 4, 'Syntax:\nDIV\n\nInteger division. Similar to FLOOR(), but is safe with BIGINT values.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT 5 DIV 2;\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (206, 'RENAME USER', 8, 'Syntax:\nRENAME USER old_user TO new_user\n    [, old_user TO new_user] ...\n\nThe RENAME USER statement renames existing MySQL accounts. To use it,\nyou must have the global CREATE USER privilege or the UPDATE privilege\nfor the mysql database. An error occurs if any old account does not\nexist or any new account exists. Each account is named using the same\nformat as for the GRANT statement; for example, ''jeffrey''@''localhost''.\nIf you specify only the username part of the account name, a hostname\npart of ''%'' is used. For additional information about specifying\naccount names, see [HELP GRANT].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/rename-user.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/rename-user.html');
INSERT INTO `help_topic` VALUES (207, 'SHOW SLAVE STATUS', 25, 'Syntax:\nSHOW SLAVE STATUS\n\nThis statement provides status information on essential parameters of\nthe slave threads. If you issue this statement using the mysql client,\nyou can use a \\G statement terminator rather than a semicolon to obtain\na more readable vertical layout:\n\nmysql> SHOW SLAVE STATUS\\G\n*************************** 1. row ***************************\n       Slave_IO_State: Waiting for master to send event\n          Master_Host: localhost\n          Master_User: root\n          Master_Port: 3306\n        Connect_Retry: 3\n      Master_Log_File: gbichot-bin.005\n  Read_Master_Log_Pos: 79\n       Relay_Log_File: gbichot-relay-bin.005\n        Relay_Log_Pos: 548\nRelay_Master_Log_File: gbichot-bin.005\n     Slave_IO_Running: Yes\n    Slave_SQL_Running: Yes\n      Replicate_Do_DB:\n  Replicate_Ignore_DB:\n           Last_Errno: 0\n           Last_Error:\n         Skip_Counter: 0\n  Exec_Master_Log_Pos: 79\n      Relay_Log_Space: 552\n      Until_Condition: None\n       Until_Log_File:\n        Until_Log_Pos: 0\n   Master_SSL_Allowed: No\n   Master_SSL_CA_File:\n   Master_SSL_CA_Path:\n      Master_SSL_Cert:\n    Master_SSL_Cipher:\n       Master_SSL_Key:\nSeconds_Behind_Master: 8\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-slave-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-slave-status.html');
INSERT INTO `help_topic` VALUES (208, 'GEOMETRY', 30, 'MySQL provides a standard way of creating spatial columns for geometry\ntypes, for example, with CREATE TABLE or ALTER TABLE. Currently,\nspatial columns are supported for MyISAM, InnoDB, NDB, BDB, and ARCHIVE\ntables. (Support for storage engines other than MyISAM was added in\nMySQL 5.0.16.) See also the annotations about spatial indexes under\n[HELP SPATIAL].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/creating-spatial-columns.html\n\n', 'CREATE TABLE geom (g GEOMETRY);\n', 'http://dev.mysql.com/doc/refman/5.0/en/creating-spatial-columns.html');
INSERT INTO `help_topic` VALUES (209, 'NUMPOINTS', 11, 'NumPoints(ls)\n\nReturns the number of Point objects in the LineString value ls.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html\n\n', 'mysql> SET @ls = ''LineString(1 1,2 2,3 3)'';\nmysql> SELECT NumPoints(GeomFromText(@ls));\n+------------------------------+\n| NumPoints(GeomFromText(@ls)) |\n+------------------------------+\n|                            3 |\n+------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html');
INSERT INTO `help_topic` VALUES (210, '&', 18, 'Syntax:\n&\n\nBitwise AND:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 29 & 15;\n        -> 13\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (211, 'LOCALTIMESTAMP', 28, 'Syntax:\nLOCALTIMESTAMP, LOCALTIMESTAMP()\n\nLOCALTIMESTAMP and LOCALTIMESTAMP() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (212, 'CONVERT', 33, 'Syntax:\nCONVERT(expr,type), CONVERT(expr USING transcoding_name)\n\nThe CONVERT() and CAST() functions take a value of one type and produce\na value of another type.\n\nThe type can be one of the following values:\n\no BINARY[(N)]\n\no CHAR[(N)]\n\no DATE\n\no DATETIME\n\no DECIMAL\n\no SIGNED [INTEGER]\n\no TIME\n\no UNSIGNED [INTEGER]\n\nBINARY produces a string with the BINARY data type. See\nhttp://dev.mysql.com/doc/refman/5.0/en/binary-varbinary.html for a\ndescription of how this affects comparisons. If the optional length N\nis given, BINARY(N) causes the cast to use no more than N bytes of the\nargument. As of MySQL 5.0.17, values shorter than N bytes are padded\nwith 0x00 bytes to a length of N.\n\nCHAR(N) causes the cast to use no more than N characters of the\nargument.\n\nThe DECIMAL type is available as of MySQL 5.0.8.\n\nCAST() and CONVERT(... USING ...) are standard SQL syntax. The\nnon-USING form of CONVERT() is ODBC syntax.\n\nCONVERT() with USING is used to convert data between different\ncharacter sets. In MySQL, transcoding names are the same as the\ncorresponding character set names. For example, this statement converts\nthe string ''abc'' in the default character set to the corresponding\nstring in the utf8 character set:\n\nSELECT CONVERT(''abc'' USING utf8);\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html\n\n', 'SELECT enum_col FROM tbl_name ORDER BY CAST(enum_col AS CHAR);\n', 'http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html');
INSERT INTO `help_topic` VALUES (213, 'ADDDATE', 28, 'Syntax:\nADDDATE(date,INTERVAL expr unit), ADDDATE(expr,days)\n\nWhen invoked with the INTERVAL form of the second argument, ADDDATE()\nis a synonym for DATE_ADD(). The related function SUBDATE() is a\nsynonym for DATE_SUB(). For information on the INTERVAL unit argument,\nsee the discussion for DATE_ADD().\n\nmysql> SELECT DATE_ADD(''1998-01-02'', INTERVAL 31 DAY);\n        -> ''1998-02-02''\nmysql> SELECT ADDDATE(''1998-01-02'', INTERVAL 31 DAY);\n        -> ''1998-02-02''\n\nWhen invoked with the days form of the second argument, MySQL treats it\nas an integer number of days to be added to expr.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT ADDDATE(''1998-01-02'', 31);\n        -> ''1998-02-02''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (214, 'REPEAT LOOP', 35, 'Syntax:\n[begin_label:] REPEAT\n    statement_list\nUNTIL search_condition\nEND REPEAT [end_label]\n\nThe statement list within a REPEAT statement is repeated until the\nsearch_condition is true. Thus, a REPEAT always enters the loop at\nleast once. statement_list consists of one or more statements.\n\nA REPEAT statement can be labeled. end_label cannot be given unless\nbegin_label also is present. If both are present, they must be the\nsame.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/repeat-statement.html\n\n', 'mysql> delimiter //\n\nmysql> CREATE PROCEDURE dorepeat(p1 INT)\n    -> BEGIN\n    ->   SET @x = 0;\n    ->   REPEAT SET @x = @x + 1; UNTIL @x > p1 END REPEAT;\n    -> END\n    -> //\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> CALL dorepeat(1000)//\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT @x//\n+------+\n| @x   |\n+------+\n| 1001 |\n+------+\n1 row in set (0.00 sec)\n', 'http://dev.mysql.com/doc/refman/5.0/en/repeat-statement.html');
INSERT INTO `help_topic` VALUES (215, 'SMALLINT', 20, 'SMALLINT[(M)] [UNSIGNED] [ZEROFILL]\n\nA small integer. The signed range is -32768 to 32767. The unsigned\nrange is 0 to 65535.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (216, 'DOUBLE PRECISION', 20, 'DOUBLE PRECISION[(M,D)] [UNSIGNED] [ZEROFILL], REAL[(M,D)] [UNSIGNED]\n[ZEROFILL]\n\nThese types are synonyms for DOUBLE. Exception: If the REAL_AS_FLOAT\nSQL mode is enabled, REAL is a synonym for FLOAT rather than DOUBLE.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (217, 'ORD', 33, 'Syntax:\nORD(str)\n\nIf the leftmost character of the string str is a multi-byte character,\nreturns the code for that character, calculated from the numeric values\nof its constituent bytes using this formula:\n\n  (1st byte code)\n+ (2nd byte code x 256)\n+ (3rd byte code x 2562) ...\n\nIf the leftmost character is not a multi-byte character, ORD() returns\nthe same value as the ASCII() function.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT ORD(''2'');\n        -> 50\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (218, 'ENVELOPE', 32, 'Envelope(g)\n\nReturns the Minimum Bounding Rectangle (MBR) for the geometry value g.\nThe result is returned as a Polygon value.\n\nThe polygon is defined by the corner points of the bounding box:\n\nPOLYGON((MINX MINY, MAXX MINY, MAXX MAXY, MINX MAXY, MINX MINY))\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html\n\n', 'mysql> SELECT AsText(Envelope(GeomFromText(''LineString(1 1,2 2)'')));\n+-------------------------------------------------------+\n| AsText(Envelope(GeomFromText(''LineString(1 1,2 2)''))) |\n+-------------------------------------------------------+\n| POLYGON((1 1,2 1,2 2,1 2,1 1))                        |\n+-------------------------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (219, 'DEALLOCATE PREPARE', 25, 'Syntax:\n{DEALLOCATE | DROP} PREPARE stmt_name\n\nTo deallocate a prepared statement, use the DEALLOCATE PREPARE\nstatement. Attempting to execute a prepared statement after\ndeallocating it results in an error.\n\nIf you terminate a client session without deallocating a previously\nprepared statement, the server deallocates it automatically.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/sqlps.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/sqlps.html');
INSERT INTO `help_topic` VALUES (220, 'IS_FREE_LOCK', 13, 'Syntax:\nIS_FREE_LOCK(str)\n\nChecks whether the lock named str is free to use (that is, not locked).\nReturns 1 if the lock is free (no one is using the lock), 0 if the lock\nis in use, and NULL if an error occurs (such as an incorrect argument).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (221, 'TOUCHES', 26, 'Touches(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 spatially touches g2. Two\ngeometries spatially touch if the interiors of the geometries do not\nintersect, but the boundary of one of the geometries intersects either\nthe boundary or the interior of the other.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (222, 'INET_ATON', 13, 'Syntax:\nINET_ATON(expr)\n\nGiven the dotted-quad representation of a network address as a string,\nreturns an integer that represents the numeric value of the address.\nAddresses may be 4- or 8-byte addresses.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', 'mysql> SELECT INET_ATON(''209.207.224.40'');\n        -> 3520061480\n', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (223, 'UNCOMPRESS', 10, 'Syntax:\nUNCOMPRESS(string_to_uncompress)\n\nUncompresses a string compressed by the COMPRESS() function. If the\nargument is not a compressed value, the result is NULL. This function\nrequires MySQL to have been compiled with a compression library such as\nzlib. Otherwise, the return value is always NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT UNCOMPRESS(COMPRESS(''any string''));\n        -> ''any string''\nmysql> SELECT UNCOMPRESS(''any string'');\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (224, 'AUTO_INCREMENT', 20, 'The AUTO_INCREMENT attribute can be used to generate a unique identity\nfor new rows:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html\n\n', 'CREATE TABLE animals (\n     id MEDIUMINT NOT NULL AUTO_INCREMENT,\n     name CHAR(30) NOT NULL,\n     PRIMARY KEY (id)\n );\n\nINSERT INTO animals (name) VALUES \n    (''dog''),(''cat''),(''penguin''),\n    (''lax''),(''whale''),(''ostrich'');\n\nSELECT * FROM animals;\n', 'http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html');
INSERT INTO `help_topic` VALUES (225, 'ISSIMPLE', 32, 'IsSimple(g)\n\nCurrently, this function is a placeholder and should not be used. If\nimplemented, its behavior will be as described in the next paragraph.\n\nReturns 1 if the geometry value g has no anomalous geometric points,\nsuch as self-intersection or self-tangency. IsSimple() returns 0 if the\nargument is not simple, and -1 if it is NULL.\n\nThe description of each instantiable geometric class given earlier in\nthe chapter includes the specific conditions that cause an instance of\nthat class to be classified as not simple. (See [HELP Geometry\nhierarchy].)\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (226, '- BINARY', 4, 'Syntax:\n-\n\nSubtraction:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT 3-5;\n        -> -2\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (227, 'GEOMCOLLFROMTEXT', 3, 'GeomCollFromText(wkt[,srid]), GeometryCollectionFromText(wkt[,srid])\n\nConstructs a GEOMETRYCOLLECTION value using its WKT representation and\nSRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (228, 'WKT DEFINITION', 3, 'The Well-Known Text (WKT) representation of Geometry is designed to\nexchange geometry data in ASCII form.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-format.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-format.html');
INSERT INTO `help_topic` VALUES (229, 'CURRENT_TIME', 28, 'Syntax:\nCURRENT_TIME, CURRENT_TIME()\n\nCURRENT_TIME and CURRENT_TIME() are synonyms for CURTIME().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (230, 'REVOKE', 8, 'Syntax:\nREVOKE priv_type [(column_list)] [, priv_type [(column_list)]] ...\n    ON [object_type] {tbl_name | * | *.* | db_name.*}\n    FROM user [, user] ...\n\nREVOKE ALL PRIVILEGES, GRANT OPTION FROM user [, user] ...\n\nThe REVOKE statement enables system administrators to revoke privileges\nfrom MySQL accounts. To use REVOKE, you must have the GRANT OPTION\nprivilege, and you must have the privileges that you are revoking.\n\nEach account is named using the same format as for the GRANT statement;\nfor example, ''jeffrey''@''localhost''. If you specify only the username\npart of the account name, a hostname part of ''%'' is used. For\nadditional information about specifying account names, see [HELP\nGRANT].\n\nFor details on the levels at which privileges exist, the allowable\npriv_type values, and the syntax for specifying users and passwords,\nsee [HELP GRANT]\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/revoke.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/revoke.html');
INSERT INTO `help_topic` VALUES (231, 'LAST_INSERT_ID', 15, 'Syntax:\nLAST_INSERT_ID(), LAST_INSERT_ID(expr)\n\nLAST_INSERT_ID() (with no argument) returns the first automatically\ngenerated value that was set for an AUTO_INCREMENT column by the most\nrecently executed INSERT statement to affect such a column. For\nexample, after inserting a row that generates an AUTO_INCREMENT value,\nyou can get the value like this:\n\nmysql> SELECT LAST_INSERT_ID();\n        -> 195\n\nThe currently executing statement does not affect the value of\nLAST_INSERT_ID(). Suppose that you generate an AUTO_INCREMENT value\nwith one statement, and then refer to LAST_INSERT_ID() in a\nmultiple-row INSERT statement that inserts rows into a table with its\nown AUTO_INCREMENT column. The value of LAST_INSERT_ID() will remain\nstable in the second statement; its value for the second and later rows\nis not affected by the earlier row insertions. (However, if you mix\nreferences to LAST_INSERT_ID() and LAST_INSERT_ID(expr), the effect is\nundefined.)\n\nIf the previous statement returned an error, the value of\nLAST_INSERT_ID() is undefined. For transactional tables, if the\nstatement is rolled back due to an error, the value of LAST_INSERT_ID()\nis left undefined. For manual ROLLBACK, the value of LAST_INSERT_ID()\nis not restored to that before the transaction; it remains as it was at\nthe point of the ROLLBACK.\n\nWithin the body of a stored routine (procedure or function) or a\ntrigger, the value of LAST_INSERT_ID() changes the same way as for\nstatements executed outside the body of these kinds of objects. The\neffect of a stored routine or trigger upon the value of\nLAST_INSERT_ID() that is seen by following statements depends on the\nkind of routine:\n\no If a stored procedure executes statements that change the value of\n  LAST_INSERT_ID(), the changed value will be seen by statements that\n  follow the procedure call.\n\no For stored functions and triggers that change the value, the value is\n  restored when the function or trigger ends, so following statements\n  will not see a changed value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (232, 'LAST_DAY', 28, 'Syntax:\nLAST_DAY(date)\n\nTakes a date or datetime value and returns the corresponding value for\nthe last day of the month. Returns NULL if the argument is invalid.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT LAST_DAY(''2003-02-05'');\n        -> ''2003-02-28''\nmysql> SELECT LAST_DAY(''2004-02-05'');\n        -> ''2004-02-29''\nmysql> SELECT LAST_DAY(''2004-01-01 01:01:01'');\n        -> ''2004-01-31''\nmysql> SELECT LAST_DAY(''2003-03-32'');\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (233, 'MEDIUMINT', 20, 'MEDIUMINT[(M)] [UNSIGNED] [ZEROFILL]\n\nA medium-sized integer. The signed range is -8388608 to 8388607. The\nunsigned range is 0 to 16777215.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (234, 'FLOOR', 4, 'Syntax:\nFLOOR(X)\n\nReturns the largest integer value not greater than X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT FLOOR(1.23);\n        -> 1\nmysql> SELECT FLOOR(-1.23);\n        -> -2\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (235, 'RTRIM', 33, 'Syntax:\nRTRIM(str)\n\nReturns the string str with trailing space characters removed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT RTRIM(''barbar   '');\n        -> ''barbar''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (236, 'DEGREES', 4, 'Syntax:\nDEGREES(X)\n\nReturns the argument X, converted from radians to degrees.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT DEGREES(PI());\n        -> 180\nmysql> SELECT DEGREES(PI() / 2);\n        -> 90\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (237, 'EXPLAIN', 25, 'Syntax:\nEXPLAIN tbl_name\n\nOr:\n\nEXPLAIN [EXTENDED] SELECT select_options\n\nThe EXPLAIN statement can be used either as a synonym for DESCRIBE or\nas a way to obtain information about how MySQL executes a SELECT\nstatement:\n\no EXPLAIN tbl_name is synonymous with DESCRIBE tbl_name or SHOW COLUMNS\n  FROM tbl_name.\n\no When you precede a SELECT statement with the keyword EXPLAIN, MySQL\n  displays information from the optimizer about the query execution\n  plan. That is, MySQL explains how it would process the SELECT,\n  including information about how tables are joined and in which order.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/explain.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/explain.html');
INSERT INTO `help_topic` VALUES (238, 'VARCHAR', 20, '[NATIONAL] VARCHAR(M) [CHARACTER SET charset_name] [COLLATE\ncollation_name]\n\nA variable-length string. M represents the maximum column length in\ncharacters. In MySQL 5.0, the range of M is 0 to 255 before MySQL\n5.0.3, and 0 to 65,535 in MySQL 5.0.3 and later. The effective maximum\nlength of a VARCHAR in MySQL 5.0.3 and later is subject to the maximum\nrow size (65,535 bytes, which is shared among all columns) and the\ncharacter set used. For example, utf8 characters can require up to\nthree bytes per character, so a VARCHAR column that uses the utf8\ncharacter set can be declared to be a maximum of 21,844 characters.\n\nMySQL stores VARCHAR values as a one-byte or two-byte length prefix\nplus data. The length prefix indicates the number of bytes in the\nvalue. A VARCHAR column uses one length byte if values require no more\nthan 255 bytes, two length bytes if values may require more than 255\nbytes.\n\n*Note*: Before 5.0.3, trailing spaces were removed when VARCHAR values\nwere stored, which differs from the standard SQL specification.\n\nPrior to MySQL 5.0.3, a VARCHAR column with a length specification\ngreater than 255 is converted to the smallest TEXT type that can hold\nvalues of the given length. For example, VARCHAR(500) is converted to\nTEXT, and VARCHAR(200000) is converted to MEDIUMTEXT. However, this\nconversion affects trailing-space removal.\n\nVARCHAR is shorthand for CHARACTER VARYING. NATIONAL VARCHAR is the\nstandard SQL way to define that a VARCHAR column should use some\npredefined character set. MySQL 4.1 and up uses utf8 as this predefined\ncharacter set.\nhttp://dev.mysql.com/doc/refman/5.0/en/charset-national.html. NVARCHAR\nis shorthand for NATIONAL VARCHAR.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (239, 'UNHEX', 33, 'Syntax:\n\nUNHEX(str)\n\nPerforms the inverse operation of HEX(str). That is, it interprets each\npair of hexadecimal digits in the argument as a number and converts it\nto the character represented by the number. The resulting characters\nare returned as a binary string.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT UNHEX(''4D7953514C'');\n        -> ''MySQL''\nmysql> SELECT 0x4D7953514C;\n        -> ''MySQL''\nmysql> SELECT UNHEX(HEX(''string''));\n        -> ''string''\nmysql> SELECT HEX(UNHEX(''1267''));\n        -> ''1267''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (240, '- UNARY', 4, 'Syntax:\n-\n\nUnary minus. This operator changes the sign of the argument.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT - 2;\n        -> -2\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (241, 'SELECT INTO', 35, 'Syntax:\nSELECT col_name[,...] INTO var_name[,...] table_expr\n\nThis SELECT syntax stores selected columns directly into variables.\nTherefore, only a single row may be retrieved.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/select-into-statement.html\n\n', 'SELECT id,data INTO x,y FROM test.t1 LIMIT 1;\n', 'http://dev.mysql.com/doc/refman/5.0/en/select-into-statement.html');
INSERT INTO `help_topic` VALUES (242, 'STD', 14, 'Syntax:\nSTD(expr)\n\nReturns the population standard deviation of expr. This is an extension\nto standard SQL. As of MySQL 5.0.3, the standard SQL function\nSTDDEV_POP() can be used instead.\n\nThis function returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (243, 'COS', 4, 'Syntax:\nCOS(X)\n\nReturns the cosine of X, where X is given in radians.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT COS(PI());\n        -> -1\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (244, 'DATE FUNCTION', 28, 'Syntax:\nDATE(expr)\n\nExtracts the date part of the date or datetime expression expr.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DATE(''2003-12-31 01:02:03'');\n        -> ''2003-12-31''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (245, 'DROP TRIGGER', 21, 'Syntax:\nDROP TRIGGER [IF EXISTS] [schema_name.]trigger_name\n\nThis statement drops a trigger. The schema (database) name is optional.\nIf the schema is omitted, the trigger is dropped from the default\nschema. DROP TRIGGER was added in MySQL 5.0.2. Its use requires the\nSUPER privilege.\n\nUse IF EXISTS to prevent an error from occurring for a trigger that\ndoes not exist. A NOTE is generated for a non-existent trigger when\nusing IF EXISTS. See [HELP SHOW WARNINGS]. The IF EXISTS clause was\nadded in MySQL 5.0.32.\n\nTriggers for a table are also dropped if you drop the table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-trigger.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-trigger.html');
INSERT INTO `help_topic` VALUES (246, 'RESET MASTER', 25, 'Syntax:\nRESET MASTER\n\nDeletes all binary logs listed in the index file, resets the binary log\nindex file to be empty, and creates a new binary log file.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/reset-master.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/reset-master.html');
INSERT INTO `help_topic` VALUES (247, 'TAN', 4, 'Syntax:\nTAN(X)\n\nReturns the tangent of X, where X is given in radians.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT TAN(PI());\n        -> -1.2246063538224e-16\nmysql> SELECT TAN(PI()+1);\n        -> 1.5574077246549\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (248, 'PI', 4, 'Syntax:\nPI()\n\nReturns the value of π (pi). The default number of decimal places\ndisplayed is seven, but MySQL uses the full double-precision value\ninternally.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT PI();\n        -> 3.141593\nmysql> SELECT PI()+0.000000000000000000;\n        -> 3.141592653589793116\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (249, 'WEEKOFYEAR', 28, 'Syntax:\nWEEKOFYEAR(date)\n\nReturns the calendar week of the date as a number in the range from 1\nto 53. WEEKOFYEAR() is a compatibility function that is equivalent to\nWEEK(date,3).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT WEEKOFYEAR(''1998-02-20'');\n        -> 8\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (250, '/', 4, 'Syntax:\n/\n\nDivision:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT 3/5;\n        -> 0.60\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (251, 'STDDEV_SAMP', 14, 'Syntax:\nSTDDEV_SAMP(expr)\n\nReturns the sample standard deviation of expr (the square root of\nVAR_SAMP(). This function was added in MySQL 5.0.3.\n\nSTDDEV_SAMP() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (252, 'SCHEMA', 15, 'Syntax:\nSCHEMA()\n\nThis function is a synonym for DATABASE(). It was added in MySQL 5.0.2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (253, 'MLINEFROMWKB', 29, 'MLineFromWKB(wkb[,srid]), MultiLineStringFromWKB(wkb[,srid])\n\nConstructs a MULTILINESTRING value using its WKB representation and\nSRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (254, 'LOG2', 4, 'Syntax:\nLOG2(X)\n\nReturns the base-2 logarithm of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT LOG2(65536);\n        -> 16\nmysql> SELECT LOG2(-100);\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (255, 'SUBTIME', 28, 'Syntax:\nSUBTIME(expr1,expr2)\n\nSUBTIME() returns expr1 - expr2 expressed as a value in the same format\nas expr1. expr1 is a time or datetime expression, and expr2 is a time\nexpression.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT SUBTIME(''1997-12-31 23:59:59.999999'',''1 1:1:1.000002'');\n        -> ''1997-12-30 22:58:58.999997''\nmysql> SELECT SUBTIME(''01:00:00.999999'', ''02:00:00.999998'');\n        -> ''-00:59:59.999999''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (256, 'UNCOMPRESSED_LENGTH', 10, 'Syntax:\nUNCOMPRESSED_LENGTH(compressed_string)\n\nReturns the length that the compressed string had before being\ncompressed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT UNCOMPRESSED_LENGTH(COMPRESS(REPEAT(''a'',30)));\n        -> 30\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (257, 'DROP TABLE', 36, 'Syntax:\nDROP [TEMPORARY] TABLE [IF EXISTS]\n    tbl_name [, tbl_name] ...\n    [RESTRICT | CASCADE]\n\nDROP TABLE removes one or more tables. You must have the DROP privilege\nfor each table. All table data and the table definition are removed, so\nbe careful with this statement! If any of the tables named in the\nargument list do not exist, MySQL returns an error indicating by name\nwhich non-existing tables it was unable to drop, but it also drops all\nof the tables in the list that do exist.\n\n*Important*: When a table is dropped, user privileges on the table are\nnot automatically dropped. See [HELP GRANT].\n\nUse IF EXISTS to prevent an error from occurring for tables that do not\nexist. A NOTE is generated for each non-existent table when using IF\nEXISTS. See [HELP SHOW WARNINGS].\n\nRESTRICT and CASCADE are allowed to make porting easier. In MySQL 5.0,\nthey do nothing.\n\n*Note*: DROP TABLE automatically commits the current active\ntransaction, unless you use the TEMPORARY keyword.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-table.html');
INSERT INTO `help_topic` VALUES (258, 'POW', 4, 'Syntax:\nPOW(X,Y)\n\nReturns the value of X raised to the power of Y.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT POW(2,2);\n        -> 4\nmysql> SELECT POW(2,-2);\n        -> 0.25\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (259, 'SHOW CREATE TABLE', 25, 'Syntax:\nSHOW CREATE TABLE tbl_name\n\nShows the CREATE TABLE statement that creates the given table. As of\nMySQL 5.0.1, this statement also works with views.\nSHOW CREATE TABLE quotes table and column names according to the value\nof the SQL_QUOTE_SHOW_CREATE option. See [HELP SET].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-create-table.html\n\n', 'mysql> SHOW CREATE TABLE t\\G\n*************************** 1. row ***************************\n       Table: t\nCreate Table: CREATE TABLE t (\n  id INT(11) default NULL auto_increment,\n  s char(60) default NULL,\n  PRIMARY KEY (id)\n) ENGINE=MyISAM\n', 'http://dev.mysql.com/doc/refman/5.0/en/show-create-table.html');
INSERT INTO `help_topic` VALUES (260, 'DUAL', 25, 'You are allowed to specify DUAL as a dummy table name in situations\nwhere no tables are referenced:\n\nmysql> SELECT 1 + 1 FROM DUAL;\n        -> 2\n\nDUAL is purely for the convenience of people who require that all\nSELECT statements should have FROM and possibly other clauses. MySQL\nmay ignore the clauses. MySQL does not require FROM DUAL if no tables\nare referenced.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/select.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/select.html');
INSERT INTO `help_topic` VALUES (261, 'INSTR', 33, 'Syntax:\nINSTR(str,substr)\n\nReturns the position of the first occurrence of substring substr in\nstring str. This is the same as the two-argument form of LOCATE(),\nexcept that the order of the arguments is reversed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT INSTR(''foobarbar'', ''bar'');\n        -> 4\nmysql> SELECT INSTR(''xbar'', ''foobar'');\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (262, 'NOW', 28, '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.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (263, 'SHOW ENGINES', 25, '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. SHOW TABLE\nTYPES is a deprecated synonym.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-engines.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-engines.html');
INSERT INTO `help_topic` VALUES (264, 'SHOW MUTEX STATUS', 25, 'Syntax:\nSHOW MUTEX STATUS\n\nSHOW MUTEX STATUS displays InnoDB mutex statistics. From MySQL 5.0.3 to\n5.0.32, the statement displays the following output fields:\n\no Mutex\n\n  The mutex name. The name indicates the mutex purpose. For example,\n  the log_sys mutex is used by the InnoDB logging subsystem and\n  indicates how intensive logging activity is. The buf_pool mutex\n  protects the InnoDB buffer pool.\n\no Module\n\n  The source file where the mutex is implemented.\n\no Count indicates how many times the mutex was requested.\n\no Spin_waits indicates how many times the spinlock had to run.\n\no Spin_rounds indicates the number of spinlock rounds. (spin_rounds\n  divided by spin_waits provides the average round count.)\n\no OS_waits indicates the number of operating system waits. This occurs\n  when the spinlock did not work (the mutex was not locked during the\n  spinlock and it was necessary to yield to the operating system and\n  wait).\n\no OS_yields indicates the number of times that a thread trying to lock\n  a mutex gave up its timeslice and yielded to the operating system (on\n  the presumption that allowing other threads to run will free the\n  mutex so that it can be locked).\n\no OS_waits_time indicates the amount of time (in ms) spent in operating\n  system waits, if the timed_mutexes system variable is 1 (ON). If\n  timed_mutexes is 0 (OFF), timing is disabled, so OS_waits_time is 0.\n  timed_mutexes is off by default.\n\nFrom MySQL 5.0.33 on, the statement uses the same output format as that\njust described, but only if UNIV_DEBUG was defined at MySQL compilation\ntime (for example, in include/univ.h in the InnoDB part of the MySQL\nsource tree). If UNIV_DEBUG was not defined, the statement displays the\nfollowing fields. In the latter case (without UNIV_DEBUG), the\ninformation on which the statement output is based is insufficient to\ndistinguish regular mutexes and mutexes that protect rw-locks (which\nallow multiple readers or a single writer). Consequently, the output\nmay appear to contain multiple rows for the same mutex.\n\no File\n\n  The source file where the mutex is implemented.\n\no Line\n\n  The line number in the source file where the mutex is created. This\n  may change depending on your version of MySQL.\n\no OS_waits\n\n  Same as OS_waits_time.\n\nInformation from this statement can be used to diagnose system\nproblems. For example, large values of spin_waits and spin_rounds may\nindicate scalability problems.\n\nSHOW MUTEX STATUS was added in MySQL 5.0.3. In MySQL 5.1, SHOW MUTEX\nSTATUS is renamed to SHOW ENGINE INNODB MUTEX. The latter statement\ndisplays similar information but in a somewhat different output format.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-mutex-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-mutex-status.html');
INSERT INTO `help_topic` VALUES (265, '>=', 17, 'Syntax:\n>=\n\nGreater than or equal:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 2 >= 2;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (266, 'EXP', 4, 'Syntax:\nEXP(X)\n\nReturns the value of e (the base of natural logarithms) raised to the\npower of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT EXP(2);\n        -> 7.3890560989307\nmysql> SELECT EXP(-2);\n        -> 0.13533528323661\nmysql> SELECT EXP(0);\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (267, 'LONGBLOB', 20, '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 four-byte\nlength prefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (268, 'POINTN', 11, 'PointN(ls,N)\n\nReturns the N-th Point in the Linestring value ls. Points are numbered\nbeginning with 1.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html\n\n', 'mysql> SET @ls = ''LineString(1 1,2 2,3 3)'';\nmysql> SELECT AsText(PointN(GeomFromText(@ls),2));\n+-------------------------------------+\n| AsText(PointN(GeomFromText(@ls),2)) |\n+-------------------------------------+\n| POINT(2 2)                          |\n+-------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html');
INSERT INTO `help_topic` VALUES (269, 'YEAR DATA TYPE', 20, 'YEAR[(2|4)]\n\nA year in two-digit or four-digit format. The default is four-digit\nformat. In four-digit format, the allowable values are 1901 to 2155,\nand 0000. In two-digit format, the allowable values are 70 to 69,\nrepresenting years from 1970 to 2069. MySQL displays YEAR values in\nYYYY format, but allows you to assign values to YEAR columns using\neither strings or numbers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html');
INSERT INTO `help_topic` VALUES (270, 'SUM', 14, '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 in MySQL 5.0 to sum only the\ndistinct values of expr.\n\nSUM() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (271, 'OCT', 33, 'Syntax:\nOCT(N)\n\nReturns a string representation of the octal value of N, where N is a\nlonglong (BIGINT) number. This is equivalent to CONV(N,10,8). Returns\nNULL if N is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT OCT(12);\n        -> ''14''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (272, 'SYSDATE', 28, 'Syntax:\nSYSDATE()\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.\n\nAs of MySQL 5.0.13, SYSDATE() returns the time at which it executes.\nThis differs from the behavior for NOW(), which returns a constant time\nthat indicates the time at which the statement began to execute.\n(Within a stored routine or trigger, NOW() returns the time at which\nthe routine or triggering statement began to execute.)\n\nmysql> SELECT NOW(), SLEEP(2), NOW();\n+---------------------+----------+---------------------+\n| NOW()               | SLEEP(2) | NOW()               |\n+---------------------+----------+---------------------+\n| 2006-04-12 13:47:36 |        0 | 2006-04-12 13:47:36 |\n+---------------------+----------+---------------------+\n\nmysql> SELECT SYSDATE(), SLEEP(2), SYSDATE();\n+---------------------+----------+---------------------+\n| SYSDATE()           | SLEEP(2) | SYSDATE()           |\n+---------------------+----------+---------------------+\n| 2006-04-12 13:47:44 |        0 | 2006-04-12 13:47:46 |\n+---------------------+----------+---------------------+\n\nIn addition, the SET TIMESTAMP statement affects the value returned by\nNOW() but not by SYSDATE(). This means that timestamp settings in the\nbinary log have no effect on invocations of SYSDATE().\n\nBecause SYSDATE() can return different values even within the same\nstatement, and is not affected by SET TIMESTAMP, it is\nnon-deterministic and therefore unsafe for replication. If that is a\nproblem, you can start the server with the --sysdate-is-now option to\ncause SYSDATE() to be an alias for NOW(). The non-deterministic nature\nof SYSDATE() also means that indexes cannot be used for evaluating\nexpressions that refer to it.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (273, 'ASBINARY', 29, 'AsBinary(g)\n\nConverts a value in internal geometry format to its WKB representation\nand returns the binary result.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-to-convert-geometries-between-formats.html\n\n', 'SELECT AsBinary(g) FROM geom;\n', 'http://dev.mysql.com/doc/refman/5.0/en/functions-to-convert-geometries-between-formats.html');
INSERT INTO `help_topic` VALUES (274, 'REPEAT FUNCTION', 33, '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.0/en/string-functions.html\n\n', 'mysql> SELECT REPEAT(''MySQL'', 3);\n        -> ''MySQLMySQLMySQL''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (275, 'SHOW TABLES', 25, 'Syntax:\nSHOW [FULL] TABLES [FROM db_name]\n    [LIKE ''pattern'' | WHERE expr]\n\nSHOW TABLES lists the non-TEMPORARY tables in a given database. You can\nalso get this list using the mysqlshow db_name command. The LIKE\nclause, if present, indicates which table names to match. The WHERE\nclause can be given to select rows using more general conditions, as\ndiscussed in http://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nBefore MySQL 5.0.1, the output from SHOW TABLES contains a single\ncolumn of table names. Beginning with MySQL 5.0.1, this statement also\nlists any views in the database. As of MySQL 5.0.2, the FULL modifier\nis supported such that SHOW FULL TABLES displays a second output\ncolumn. Values for the second column are BASE TABLE for a table and\nVIEW for a view.\n\n*Note*: If you have no privileges for a table, the table does not show\nup in the output from SHOW TABLES or mysqlshow db_name.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-tables.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-tables.html');
INSERT INTO `help_topic` VALUES (276, 'MAKEDATE', 28, 'Syntax:\nMAKEDATE(year,dayofyear)\n\nReturns a date, given year and day-of-year values. dayofyear must be\ngreater than 0 or the result is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MAKEDATE(2001,31), MAKEDATE(2001,32);\n        -> ''2001-01-31'', ''2001-02-01''\nmysql> SELECT MAKEDATE(2001,365), MAKEDATE(2004,365);\n        -> ''2001-12-31'', ''2004-12-30''\nmysql> SELECT MAKEDATE(2001,0);\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (277, 'BINARY OPERATOR', 33, 'Syntax:\nBINARY\n\nThe BINARY operator casts the string following it to a binary string.\nThis is an easy way to force a column comparison to be done byte by\nbyte rather than character by character. This causes the comparison to\nbe case sensitive even if the column isn''t defined as BINARY or BLOB.\nBINARY also causes trailing spaces to be significant.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html\n\n', 'mysql> SELECT ''a'' = ''A'';\n        -> 1\nmysql> SELECT BINARY ''a'' = ''A'';\n        -> 0\nmysql> SELECT ''a'' = ''a '';\n        -> 1\nmysql> SELECT BINARY ''a'' = ''a '';\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html');
INSERT INTO `help_topic` VALUES (278, 'MBROVERLAPS', 5, 'MBROverlaps(g1,g2)\n\nReturns 1 or 0 to indicate whether the Minimum Bounding Rectangles of\nthe two geometries g1 and g2 overlap. The term spatially overlaps is\nused if two geometries intersect and their intersection results in a\ngeometry of the same dimension but not equal to either of the given\ngeometries.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (279, 'SOUNDEX', 33, '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 non-alphabetic 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 multi-byte character sets, including utf-8.\n\n  We hope to remove these limitations in a future release. See\n  Bug#22638 (http://bugs.mysql.com/22638) for more information.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (280, 'MBRTOUCHES', 5, '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.0/en/relations-on-geometry-mbr.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (281, 'CREATE PROCEDURE', 35, 'Syntax:\nCREATE\n    [DEFINER = { user | CURRENT_USER }]\n    PROCEDURE sp_name ([proc_parameter[,...]])\n    [characteristic ...] routine_body\n\nCREATE\n    [DEFINER = { user | CURRENT_USER }]\n    FUNCTION sp_name ([func_parameter[,...]])\n    RETURNS type\n    [characteristic ...] routine_body\n    \nproc_parameter:\n    [ IN | OUT | INOUT ] param_name type\n    \nfunc_parameter:\n    param_name type\n\ntype:\n    Any valid MySQL data type\n\ncharacteristic:\n    LANGUAGE SQL\n  | [NOT] DETERMINISTIC\n  | { CONTAINS SQL | NO SQL | READS SQL DATA | MODIFIES SQL DATA }\n  | SQL SECURITY { DEFINER | INVOKER }\n  | COMMENT ''string''\n\nroutine_body:\n    Valid SQL procedure statement\n\nThese statements create stored routines. As of MySQL 5.0.3, to execute\nthese statements, it is necessary to have the CREATE ROUTINE privilege.\nIf binary logging is enabled, these statements might also require the\nSUPER privilege, as described in\nhttp://dev.mysql.com/doc/refman/5.0/en/stored-procedure-logging.html.\nMySQL automatically grants the ALTER ROUTINE and EXECUTE privileges to\nthe routine creator.\n\nBy default, the routine is associated with the default database. To\nassociate the routine explicitly with a given database, specify the\nname as db_name.sp_name when you create it.\n\nIf the routine name is the same as the name of a built-in SQL function,\nyou must use a space between the name and the following parenthesis\nwhen defining the routine, or a syntax error occurs. This is also true\nwhen you invoke the routine later. For this reason, we suggest that it\nis better to avoid re-using the names of existing SQL functions for\nyour own stored routines.\n\nThe IGNORE_SPACE SQL mode applies to built-in functions, not to stored\nroutines. It is always allowable to have spaces after a routine name,\nregardless of whether IGNORE_SPACE is enabled.\n\nThe parameter list enclosed within parentheses must always be present.\nIf there are no parameters, an empty parameter list of () should be\nused.\n\nEach parameter can be declared to use any valid data type, except that\nthe COLLATE attribute cannot be used.\n\nEach parameter is an IN parameter by default. To specify otherwise for\na parameter, use the keyword OUT or INOUT before the parameter name.\n\n*Note*: Specifying a parameter as IN, OUT, or INOUT is valid only for a\nPROCEDURE. (FUNCTION parameters are always regarded as IN parameters.)\n\nAn IN parameter passes a value into a procedure. The procedure might\nmodify the value, but the modification is not visible to the caller\nwhen the procedure returns. An OUT parameter passes a value from the\nprocedure back to the caller. Its initial value is NULL within the\nprocedure, and its value is visible to the caller when the procedure\nreturns. An INOUT parameter is initialized by the caller, can be\nmodified by the procedure, and any change made by the procedure is\nvisible to the caller when the procedure returns.\n\nFor each OUT or INOUT parameter, pass a user-defined variable so that\nyou can obtain its value when the procedure returns. (For an example,\nsee [HELP CALL].) If you are calling the procedure from within another\nstored procedure or function, you can also pass a routine parameter or\nlocal routine variable as an IN or INOUT parameter.\n\nThe RETURNS clause may be specified only for a FUNCTION, for which it\nis mandatory. It indicates the return type of the function, and the\nfunction body must contain a RETURN value statement. If the RETURN\nstatement returns a value of a different type, the value is coerced to\nthe proper type. For example, if a function specifies an ENUM or SET\nvalue in the RETURNS clause, but the RETURN statement returns an\ninteger, the value returned from the function is the string for the\ncorresponding ENUM member of set of SET members.\n\nThe routine_body consists of a valid SQL procedure statement. This can\nbe a simple statement such as SELECT or INSERT, or it can be a compound\nstatement written using BEGIN and END. Compound statement syntax is\ndescribed in [HELP BEGIN END]. Compound statements can contain\ndeclarations, loops, and other control structure statements. The syntax\nfor these statements is described later in this chapter. See, for\nexample, http://dev.mysql.com/doc/refman/5.0/en/declare.html, and [HELP\nIF statement]. Some statements are not allowed in stored routines; see\nhttp://dev.mysql.com/doc/refman/5.0/en/routine-restrictions.html.\n\nMySQL stores the sql_mode system variable setting that is in effect at\nthe time a routine is created, and always executes the routine with\nthis setting in force, regardless of the current server SQL mode.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-procedure.html\n\n', 'mysql> delimiter //\n\nmysql> CREATE PROCEDURE simpleproc (OUT param1 INT)\n    -> BEGIN\n    ->   SELECT COUNT(*) INTO param1 FROM t;\n    -> END;\n    -> //\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> delimiter ;\n\nmysql> CALL simpleproc(@a);\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT @a;\n+------+\n| @a   |\n+------+\n| 3    |\n+------+\n1 row in set (0.00 sec)\n', 'http://dev.mysql.com/doc/refman/5.0/en/create-procedure.html');
INSERT INTO `help_topic` VALUES (282, 'INSERT SELECT', 25, 'Syntax:\nINSERT [LOW_PRIORITY | HIGH_PRIORITY] [IGNORE]\n    [INTO] tbl_name [(col_name,...)]\n    SELECT ...\n    [ ON DUPLICATE KEY UPDATE col_name=expr, ... ]\n\nWith INSERT ... SELECT, you can quickly insert many rows into a table\nfrom one or many tables. For example:\n\nINSERT INTO tbl_temp2 (fld_id)\n  SELECT tbl_temp1.fld_order_id\n  FROM tbl_temp1 WHERE tbl_temp1.fld_order_id > 100;\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/insert-select.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/insert-select.html');
INSERT INTO `help_topic` VALUES (283, 'VARBINARY', 20, 'VARBINARY(M)\n\nThe VARBINARY type is similar to the VARCHAR type, but stores binary\nbyte strings rather than non-binary character strings. M represents the\nmaximum column length in bytes.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (284, 'LOAD INDEX', 25, 'Syntax:\nLOAD INDEX INTO CACHE\n  tbl_index_list [, tbl_index_list] ...\n\ntbl_index_list:\n  tbl_name\n    [[INDEX|KEY] (index_name[, index_name] ...)]\n    [IGNORE LEAVES]\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. LOAD INDEX INTO\nCACHE is used only for MyISAM tables.\n\nThe IGNORE LEAVES modifier causes only blocks for the non-leaf nodes of\nthe index to be preloaded.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/load-index.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/load-index.html');
INSERT INTO `help_topic` VALUES (285, 'UNION', 25, '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.0/en/union.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/union.html');
INSERT INTO `help_topic` VALUES (286, 'TO_DAYS', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TO_DAYS(950501);\n        -> 728779\nmysql> SELECT TO_DAYS(''1997-10-07'');\n        -> 729669\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (287, 'NOT REGEXP', 33, 'Syntax:\nexpr NOT REGEXP pat, expr NOT RLIKE pat\n\nThis is the same as NOT (expr REGEXP pat).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html');
INSERT INTO `help_topic` VALUES (288, 'SHOW INDEX', 25, 'Syntax:\nSHOW INDEX FROM tbl_name [FROM db_name]\n\nSHOW INDEX returns table index information. The format resembles that\nof the SQLStatistics call in ODBC.\nThe LIKE clause, if present, indicates which event 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.0/en/extended-show.html.\n\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\nSHOW KEYS is a synonym for SHOW INDEX. You can also list a table''s\nindexes with the mysqlshow -k db_name tbl_name command.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-index.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-index.html');
INSERT INTO `help_topic` VALUES (289, 'SHOW CREATE DATABASE', 25, 'Syntax:\nSHOW CREATE {DATABASE | SCHEMA} db_name\n\nShows the CREATE DATABASE statement that creates the given database.\nSHOW CREATE SCHEMA is a synonym for SHOW CREATE DATABASE as of MySQL\n5.0.2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/show-create-database.html');
INSERT INTO `help_topic` VALUES (290, 'LEAVE', 35, 'Syntax:\nLEAVE label\n\nThis statement is used to exit any labeled flow control construct. It\ncan be used within BEGIN ... END or loop constructs (LOOP, REPEAT,\nWHILE).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/leave-statement.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/leave-statement.html');
INSERT INTO `help_topic` VALUES (291, 'NOT IN', 17, 'Syntax:\nexpr NOT IN (value,...)\n\nThis is the same as NOT (expr IN (value,...)).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (292, '!', 12, 'Syntax:\nNOT, !\n\nLogical NOT. Evaluates to 1 if the operand is 0, to 0 if the operand is\nnon-zero, and NOT NULL returns NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/logical-operators.html');
INSERT INTO `help_topic` VALUES (293, 'DECLARE HANDLER', 35, 'Syntax:\nDECLARE handler_type HANDLER FOR condition_value[,...] statement\n\nhandler_type:\n    CONTINUE\n  | EXIT\n  | UNDO\n\ncondition_value:\n    SQLSTATE [VALUE] sqlstate_value\n  | condition_name\n  | SQLWARNING\n  | NOT FOUND\n  | SQLEXCEPTION\n  | mysql_error_code\n\nThe DECLARE ... HANDLER statement specifies handlers that each may deal\nwith one or more conditions. If one of these conditions occurs, the\nspecified statement is executed. statement can be a simple statement\n(for example, SET var_name = value), or it can be a compound statement\nwritten using BEGIN and END (see [HELP BEGIN END]).\n\nFor a CONTINUE handler, execution of the current routine continues\nafter execution of the handler statement. For an EXIT handler,\nexecution terminates for the BEGIN ... END compound statement in which\nthe handler is declared. (This is true even if the condition occurs in\nan inner block.) The UNDO handler type statement is not yet supported.\n\nIf a condition occurs for which no handler has been declared, the\ndefault action is EXIT.\n\nA condition_value can be any of the following values:\n\no An SQLSTATE value or a MySQL error code.\n\no A condition name previously specified with DECLARE ... CONDITION. See\n  [HELP DECLARE CONDITION].\n\no SQLWARNING is shorthand for all SQLSTATE codes that begin with 01.\n\no NOT FOUND is shorthand for all SQLSTATE codes that begin with 02.\n  This is relevant only within the context of cursors and is used to\n  control what happens when a cursor reaches the end of a data set.\n\no SQLEXCEPTION is shorthand for all SQLSTATE codes not caught by\n  SQLWARNING or NOT FOUND.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/declare-handlers.html\n\n', 'mysql> CREATE TABLE test.t (s1 int,primary key (s1));\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> delimiter //\n\nmysql> CREATE PROCEDURE handlerdemo ()\n    -> BEGIN\n    ->   DECLARE CONTINUE HANDLER FOR SQLSTATE ''23000'' SET @x2 = 1;\n    ->   SET @x = 1;\n    ->   INSERT INTO test.t VALUES (1);\n    ->   SET @x = 2;\n    ->   INSERT INTO test.t VALUES (1);\n    ->   SET @x = 3;\n    -> END;\n    -> //\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> CALL handlerdemo()//\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> SELECT @x//\n    +------+\n    | @x   |\n    +------+\n    | 3    |\n    +------+\n    1 row in set (0.00 sec)\n', 'http://dev.mysql.com/doc/refman/5.0/en/declare-handlers.html');
INSERT INTO `help_topic` VALUES (294, 'DOUBLE', 20, 'DOUBLE[(M,D)] [UNSIGNED] [ZEROFILL]\n\nA normal-size (double-precision) floating-point number. Allowable\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 allowed 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.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (295, 'TIME', 20, 'TIME\n\nA time. The range is ''-838:59:59'' to ''838:59:59''. MySQL displays TIME\nvalues in ''HH:MM:SS'' format, but allows assignment of values to TIME\ncolumns using either strings or numbers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html');
INSERT INTO `help_topic` VALUES (296, '&&', 12, 'Syntax:\nAND, &&\n\nLogical AND. Evaluates to 1 if all operands are non-zero and not NULL,\nto 0 if one or more operands are 0, otherwise NULL is returned.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html\n\n', 'mysql> SELECT 1 && 1;\n        -> 1\nmysql> SELECT 1 && 0;\n        -> 0\nmysql> SELECT 1 && NULL;\n        -> NULL\nmysql> SELECT 0 && NULL;\n        -> 0\nmysql> SELECT NULL && 0;\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/logical-operators.html');
INSERT INTO `help_topic` VALUES (297, 'X', 9, 'X(p)\n\nReturns the X-coordinate value for the point p as a double-precision\nnumber.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/point-property-functions.html\n\n', 'mysql> SET @pt = ''Point(56.7 53.34)'';\nmysql> SELECT X(GeomFromText(@pt));\n+----------------------+\n| X(GeomFromText(@pt)) |\n+----------------------+\n|                 56.7 |\n+----------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/point-property-functions.html');
INSERT INTO `help_topic` VALUES (298, 'FOUND_ROWS', 15, 'Syntax:\nFOUND_ROWS()\n\nA SELECT statement may include a LIMIT clause to restrict the number of\nrows the server returns to the client. In some cases, it is desirable\nto know how many rows the statement would have returned without the\nLIMIT, but without running the statement again. To obtain this row\ncount, include a SQL_CALC_FOUND_ROWS option in the SELECT statement,\nand then invoke FOUND_ROWS() afterward:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT SQL_CALC_FOUND_ROWS * FROM tbl_name\n    -> WHERE id > 100 LIMIT 10;\nmysql> SELECT FOUND_ROWS();\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (299, 'SYSTEM_USER', 15, 'Syntax:\nSYSTEM_USER()\n\nSYSTEM_USER() is a synonym for USER().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (300, 'CROSSES', 26, 'Crosses(g1,g2)\n\nReturns 1 if g1 spatially crosses g2. Returns NULL if g1 is a Polygon\nor a MultiPolygon, or if g2 is a Point or a MultiPoint. Otherwise,\nreturns 0.\n\nThe term spatially crosses denotes a spatial relation between two given\ngeometries that has the following properties:\n\no The two geometries intersect\n\no Their intersection results in a geometry that has a dimension that is\n  one less than the maximum dimension of the two given geometries\n\no Their intersection is not equal to either of the two given geometries\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (301, 'TRUNCATE TABLE', 25, 'Syntax:\nTRUNCATE [TABLE] tbl_name\n\nTRUNCATE TABLE empties a table completely. Logically, this is\nequivalent to a DELETE statement that deletes all rows, but there are\npractical differences under some circumstances.\n\nFor InnoDB before version 5.0.3, TRUNCATE TABLE is mapped to DELETE, so\nthere is no difference. Starting with MySQL 5.0.3, fast TRUNCATE TABLE\nis available. However, the operation is still mapped to DELETE if there\nare foreign key constraints that reference the table. (When fast\ntruncate is used, it resets any AUTO_INCREMENT counter. From MySQL\n5.0.13 on, the AUTO_INCREMENT counter is reset by TRUNCATE TABLE,\nregardless of whether there is a foreign key constraint.)\n\nFor other storage engines, TRUNCATE TABLE differs from DELETE in the\nfollowing ways in MySQL 5.0:\n\no Truncate operations drop and re-create the table, which is much\n  faster than deleting rows one by one.\n\no Truncate operations are not transaction-safe; an error occurs when\n  attempting one in the course of an active transaction or active table\n  lock.\n\no The number of deleted rows is not returned.\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 The table handler does not remember the last used AUTO_INCREMENT\n  value, but starts counting from the beginning. This is true even for\n  MyISAM and InnoDB, which normally do not reuse sequence values.\n\no Since truncation of a table does not make any use of DELETE, the\n  TRUNCATE statement does not invoke ON DELETE triggers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/truncate.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/truncate.html');
INSERT INTO `help_topic` VALUES (302, 'BIT_XOR', 14, 'Syntax:\nBIT_XOR(expr)\n\nReturns the bitwise XOR of all bits in expr. The calculation is\nperformed with 64-bit (BIGINT) precision.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (303, 'CURRENT_DATE', 28, 'Syntax:\nCURRENT_DATE, CURRENT_DATE()\n\nCURRENT_DATE and CURRENT_DATE() are synonyms for CURDATE().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (304, 'AREA', 2, 'Area(poly)\n\nReturns as a double-precision number the area of the Polygon value\npoly, as measured in its spatial reference system.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/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', 'http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html');
INSERT INTO `help_topic` VALUES (305, 'START SLAVE', 25, 'Syntax:\nSTART SLAVE [thread_type [, thread_type] ... ]\nSTART SLAVE [SQL_THREAD] UNTIL\n    MASTER_LOG_FILE = ''log_name'', MASTER_LOG_POS = log_pos\nSTART SLAVE [SQL_THREAD] UNTIL\n    RELAY_LOG_FILE = ''log_name'', RELAY_LOG_POS = log_pos\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 queries from the master server and stores\nthem in the relay log. The SQL thread reads the relay log and executes\nthe queries. 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 logs, 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.0/en/start-slave.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/start-slave.html');
INSERT INTO `help_topic` VALUES (306, 'BEGIN END', 35, 'Syntax:\n[begin_label:] BEGIN\n    [statement_list]\nEND [end_label]\n\nBEGIN ... END syntax is used for writing compound statements, which can\nappear within stored routines and triggers. A compound statement can\ncontain multiple statements, enclosed by the BEGIN and END keywords.\nstatement_list represents a list of one or more statements. Each\nstatement within statement_list must be terminated by a semicolon (;)\nstatement delimiter. Note that statement_list is optional, which means\nthat the empty compound statement (BEGIN END) is legal.\n\nUse of multiple statements requires that a client is able to send\nstatement strings containing the ; statement delimiter. This is handled\nin the mysql command-line client with the delimiter command. Changing\nthe ; end-of-statement delimiter (for example, to //) allows ; to be\nused in a routine body. For an example, see [HELP CREATE PROCEDURE].\n\nA compound statement can be labeled. end_label cannot be given unless\nbegin_label also is present. If both are present, they must be the\nsame.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/begin-end.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/begin-end.html');
INSERT INTO `help_topic` VALUES (307, 'FLUSH', 25, 'Syntax:\nFLUSH [LOCAL | NO_WRITE_TO_BINLOG]\n    flush_option [, flush_option] ...\n\nThe FLUSH statement clears or reloads various internal caches used by\nMySQL. To execute FLUSH, you must have the RELOAD privilege.\n\nThe RESET statement is similar to FLUSH. See [HELP RESET].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/flush.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/flush.html');
INSERT INTO `help_topic` VALUES (308, 'SHOW PROCEDURE STATUS', 25, 'Syntax:\nSHOW {PROCEDURE | FUNCTION} STATUS\n    [LIKE ''pattern'' | WHERE expr]\n\nThese statements are MySQL extensions. They return characteristics of\nroutines, such as the database, name, type, creator, and creation and\nmodification dates. The LIKE clause, if present, indicates which\nprocedure or function names to match. The WHERE clause can be given to\nselect rows using more general conditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.0/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-procedure-status.html\n\n', 'mysql> SHOW FUNCTION STATUS LIKE ''hello''\\G\n*************************** 1. row ***************************\n           Db: test\n         Name: hello\n         Type: FUNCTION\n      Definer: testuser@localhost\n     Modified: 2004-08-03 15:29:37\n      Created: 2004-08-03 15:29:37\nSecurity_type: DEFINER\n      Comment:\n', 'http://dev.mysql.com/doc/refman/5.0/en/show-procedure-status.html');
INSERT INTO `help_topic` VALUES (309, 'SHOW WARNINGS', 25, 'Syntax:\nSHOW WARNINGS [LIMIT [offset,] row_count]\nSHOW COUNT(*) WARNINGS\n\nSHOW WARNINGS shows the error, warning, and note messages that resulted\nfrom the last statement that generated messages, or nothing if the last\nstatement that used a table generated no messages. A related statement,\nSHOW ERRORS, shows only the errors. See [HELP SHOW ERRORS].\n\nThe list of messages is reset for each new statement that uses a table.\n\nThe SHOW COUNT(*) WARNINGS statement displays the total number of\nerrors, warnings, and notes. You can also retrieve this number from the\nwarning_count variable:\n\nSHOW COUNT(*) WARNINGS;\nSELECT @@warning_count;\n\nThe value of warning_count might be greater than the number of messages\ndisplayed by SHOW WARNINGS if the max_error_count system variable is\nset so low that not all messages are stored. An example shown later in\nthis section demonstrates how this can happen.\n\nThe LIMIT clause has the same syntax as for the SELECT statement. See\n[HELP SELECT].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-warnings.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-warnings.html');
INSERT INTO `help_topic` VALUES (310, 'DESCRIBE', 24, 'Syntax:\n{DESCRIBE | DESC} tbl_name [col_name | wild]\n\nDESCRIBE provides information about the columns in a table. It is a\nshortcut for SHOW COLUMNS FROM. As of MySQL 5.0.1, these statements\nalso display information for views. (See [HELP SHOW COLUMNS].)\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/describe.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/describe.html');
INSERT INTO `help_topic` VALUES (311, 'DROP USER', 8, 'Syntax:\nDROP USER user [, user] ...\n\nThe DROP USER statement removes one or more MySQL accounts. To use it,\nyou must have the global CREATE USER privilege or the DELETE privilege\nfor the mysql database. Each account is named using the same format as\nfor the GRANT statement; for example, ''jeffrey''@''localhost''. If you\nspecify only the username part of the account name, a hostname part of\n''%'' is used. For additional information about specifying account names,\nsee [HELP GRANT].\n\nDROP USER as present in MySQL 5.0.0 removes only accounts that have no\nprivileges. In MySQL 5.0.2, it was modified to remove account\nprivileges as well. This means that the procedure for removing an\naccount depends on your version of MySQL.\n\nAs of MySQL 5.0.2, you can remove an account and its privileges as\nfollows:\n\nDROP USER user;\n\nThe statement removes privilege rows for the account from all grant\ntables.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-user.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-user.html');
INSERT INTO `help_topic` VALUES (312, 'STDDEV_POP', 14, 'Syntax:\nSTDDEV_POP(expr)\n\nReturns the population standard deviation of expr (the square root of\nVAR_POP()). This function was added in MySQL 5.0.3. Before 5.0.3, you\ncan use STD() or STDDEV(), which are equivalent but not standard SQL.\n\nSTDDEV_POP() returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (313, 'SHOW CHARACTER SET', 25, 'Syntax:\nSHOW CHARACTER SET\n    [LIKE ''pattern'' | WHERE expr]\n\nThe SHOW CHARACTER SET statement shows all available character sets.\nThe LIKE clause, if present, indicates which character set 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.0/en/extended-show.html. For example:\n\nmysql> SHOW CHARACTER SET LIKE ''latin%'';\n+---------+-----------------------------+-------------------+--------+\n| Charset | Description                 | Default collation | Maxlen |\n+---------+-----------------------------+-------------------+--------+\n| latin1  | cp1252 West European        | latin1_swedish_ci |      1 |\n| latin2  | ISO 8859-2 Central European | latin2_general_ci |      1 |\n| latin5  | ISO 8859-9 Turkish          | latin5_turkish_ci |      1 |\n| latin7  | ISO 8859-13 Baltic          | latin7_general_ci |      1 |\n+---------+-----------------------------+-------------------+--------+\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-character-set.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-character-set.html');
INSERT INTO `help_topic` VALUES (314, 'SUBSTRING', 33, '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.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (315, 'ISEMPTY', 32, 'IsEmpty(g)\n\nReturns 1 if the geometry value g is the empty geometry, 0 if it is not\nempty, and -1 if the argument is NULL. If the geometry is empty, it\nrepresents the empty point set.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (316, 'LTRIM', 33, 'Syntax:\nLTRIM(str)\n\nReturns the string str with leading space characters removed.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LTRIM(''  barbar'');\n        -> ''barbar''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (317, 'INTERSECTS', 26, 'Intersects(g1,g2)\n\nReturns 1 or 0 to indicate whether g1 spatially intersects g2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (318, 'CALL', 35, 'Syntax:\nCALL sp_name([parameter[,...]])\nCALL sp_name[()]\n\nThe CALL statement invokes a procedure that was defined previously with\nCREATE PROCEDURE.\n\nCALL can pass back values to its caller using parameters that are\ndeclared as OUT or INOUT parameters. It also "returns" the number of\nrows affected, which a client program can obtain at the SQL level by\ncalling the ROW_COUNT() function and from C by calling the\nmysql_affected_rows() C API function.\n\nAs of MySQL 5.1.13, stored procedures that take no arguments now can be\ninvoked without parentheses. That is, CALL p() and CALL p are\nequivalent.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/call.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/call.html');
INSERT INTO `help_topic` VALUES (319, 'MBRDISJOINT', 5, '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.0/en/relations-on-geometry-mbr.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (320, 'VALUES', 13, '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 INSERT ... ON DUPLICATE KEY UPDATE\nstatements and returns NULL otherwise.\nhttp://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (321, 'SUBSTRING_INDEX', 33, '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.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (322, 'ENCODE', 10, 'Syntax:\nENCODE(str,pass_str)\n\nEncrypt str using pass_str as the password. To decrypt the result, use\nDECODE().\n\nThe result is a binary string of the same length as str.\n\nThe strength of the encryption is based on how good the random\ngenerator is. It should suffice for short strings.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (323, 'LOOP', 35, 'Syntax:\n[begin_label:] LOOP\n    statement_list\nEND LOOP [end_label]\n\nLOOP implements a simple loop construct, enabling repeated execution of\nthe statement list, which consists of one or more statements. The\nstatements within the loop are repeated until the loop is exited;\nusually this is accomplished with a LEAVE statement.\n\nA LOOP statement can be labeled. end_label cannot be given unless\nbegin_label also is present. If both are present, they must be the\nsame.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/loop-statement.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/loop-statement.html');
INSERT INTO `help_topic` VALUES (324, 'TRUNCATE', 4, '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.0/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.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (325, 'TIMESTAMPADD', 28, '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: FRAC_SECOND\n(microseconds), SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, QUARTER, or\nYEAR.\n\nThe unit value may be specified using one of keywords as shown, or with\na prefix of SQL_TSI_. For example, DAY and SQL_TSI_DAY both are legal.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (326, 'SHOW', 25, 'SHOW has many forms that provide information about databases, tables,\ncolumns, or status information about the server. This section describes\nthose following:\n\nSHOW [FULL] COLUMNS FROM tbl_name [FROM db_name] [like_or_where]\nSHOW CREATE DATABASE db_name\nSHOW CREATE FUNCTION funcname\nSHOW CREATE PROCEDURE procname\nSHOW CREATE TABLE tbl_name\nSHOW DATABASES [like_or_where]\nSHOW ENGINE engine_name {LOGS | STATUS }\nSHOW [STORAGE] ENGINES\nSHOW ERRORS [LIMIT [offset,] row_count]\nSHOW FUNCTION CODE sp_name\nSHOW FUNCTION STATUS [like_or_where]\nSHOW GRANTS FOR user\nSHOW INDEX FROM tbl_name [FROM db_name]\nSHOW INNODB STATUS\nSHOW PROCEDURE CODE sp_name\nSHOW PROCEDURE STATUS [like_or_where]\nSHOW [BDB] LOGS\nSHOW MUTEX STATUS\nSHOW OPEN TABLES [FROM db_name] [like_or_where]\nSHOW PRIVILEGES\nSHOW [FULL] PROCESSLIST\nSHOW PROFILE [types] [FOR QUERY n] [OFFSET n] [LIMIT n]\nSHOW PROFILES\nSHOW [GLOBAL | SESSION] STATUS [like_or_where]\nSHOW TABLE STATUS [FROM db_name] [like_or_where]\nSHOW 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\nThe SHOW statement also has forms that provide information about\nreplication master and slave servers and are described in [HELP PURGE\nMASTER LOGS]:\n\nSHOW BINARY LOGS\nSHOW BINLOG EVENTS\nSHOW MASTER STATUS\nSHOW SLAVE HOSTS\nSHOW SLAVE STATUS\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.0/en/extended-show.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show.html');
INSERT INTO `help_topic` VALUES (327, 'GREATEST', 17, 'Syntax:\nGREATEST(value1,value2,...)\n\nWith two or more arguments, returns the largest (maximum-valued)\nargument. The arguments are compared using the same rules as for\nLEAST().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT GREATEST(2,0);\n        -> 2\nmysql> SELECT GREATEST(34.0,3.0,5.0,767.0);\n        -> 767.0\nmysql> SELECT GREATEST(''B'',''A'',''C'');\n        -> ''C''\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (328, 'SHOW VARIABLES', 25, '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.0/en/extended-show.html.\n\nWith the GLOBAL modifier, SHOW VARIABLES displays the values that are\nused for new connections to MySQL. With SESSION, it displays the values\nthat are in effect for the current connection. If no modifier is\npresent, the default 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.0/en/show-variables.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-variables.html');
INSERT INTO `help_topic` VALUES (329, 'BIT_AND', 14, 'Syntax:\nBIT_AND(expr)\n\nReturns the bitwise AND of all bits in expr. The calculation is\nperformed with 64-bit (BIGINT) precision.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (330, 'SECOND', 28, 'Syntax:\nSECOND(time)\n\nReturns the second for time, in the range 0 to 59.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT SECOND(''10:05:03'');\n        -> 3\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (331, 'ATAN2', 4, '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.0/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.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (332, 'MBRCONTAINS', 5, 'MBRContains(g1,g2)\n\nReturns 1 or 0 to indicate whether the Minimum Bounding Rectangle of g1\ncontains the Minimum Bounding Rectangle of g2. This tests the opposite\nrelationship as MBRWithin().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html\n\n', 'mysql> SET @g1 = GeomFromText(''Polygon((0 0,0 3,3 3,3 0,0 0))'');\nmysql> SET @g2 = GeomFromText(''Point(1 1)'');\nmysql> SELECT MBRContains(@g1,@g2), MBRContains(@g2,@g1);\n----------------------+----------------------+\n| MBRContains(@g1,@g2) | MBRContains(@g2,@g1) |\n+----------------------+----------------------+\n|                    1 |                    0 |\n+----------------------+----------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (333, 'HOUR', 28, '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.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (334, 'SELECT', 25, '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, ...\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'' 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.0/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 clause, you can use any of the functions and operators\n  that MySQL supports, except for aggregate (summary) functions. See\n  [HELP =].\n\nSELECT can also be used to retrieve rows computed without reference to\nany table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/select.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/select.html');
INSERT INTO `help_topic` VALUES (335, 'COT', 4, 'Syntax:\nCOT(X)\n\nReturns the cotangent of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT COT(12);\n        -> -1.5726734063977\nmysql> SELECT COT(0);\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (336, 'BACKUP TABLE', 19, 'Syntax:\nBACKUP TABLE tbl_name [, tbl_name] ... TO ''/path/to/backup/directory''\n\n*Note*: This statement is deprecated. We are working on a better\nreplacement for it that will provide online backup capabilities. In the\nmeantime, the mysqlhotcopy script can be used instead.\n\nBACKUP TABLE copies to the backup directory the minimum number of table\nfiles needed to restore the table, after flushing any buffered changes\nto disk. The statement works only for MyISAM tables. It copies the .frm\ndefinition and .MYD data files. The .MYI index file can be rebuilt from\nthose two files. The directory should be specified as a full pathname.\nTo restore the table, use RESTORE TABLE.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/backup-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/backup-table.html');
INSERT INTO `help_topic` VALUES (337, 'LOAD_FILE', 33, 'Syntax:\nLOAD_FILE(file_name)\n\nReads the file and returns the file contents as a string. To use this\nfunction, the file must be located on the server host, you must specify\nthe full pathname to the file, and you must have the FILE privilege.\nThe file must be readable by all and its size less than\nmax_allowed_packet bytes.\n\nIf the file does not exist or cannot be read because one of the\npreceding conditions is not satisfied, the function returns NULL.\n\nAs of MySQL 5.0.19, the character_set_filesystem system variable\ncontrols interpretation of filenames that are given as literal strings.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> UPDATE t\n            SET blob_col=LOAD_FILE(''/tmp/picture'')\n            WHERE id=1;\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (338, 'POINTFROMTEXT', 3, 'PointFromText(wkt[,srid])\n\nConstructs a POINT value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (339, 'LOAD TABLE FROM MASTER', 25, 'Syntax:\nLOAD TABLE tbl_name FROM MASTER\n\nThis feature is deprecated. We recommend not using it anymore. It is\nsubject to removal in a future version of MySQL.\n\nSince the current implementation of LOAD DATA FROM MASTER and LOAD\nTABLE FROM MASTER is very limited, these statements are deprecated in\nversions 4.1 of MySQL and above. We will introduce a more advanced\ntechnique (called "online backup") in a future version. That technique\nwill have the additional advantage of working with more storage\nengines.\n\nFor MySQL 5.1 and earlier, the recommended alternative solution to\nusing LOAD DATA FROM MASTER or LOAD TABLE FROM MASTER is using\nmysqldump or mysqlhotcopy. The latter requires Perl and two Perl\nmodules (DBI and DBD:mysql) and works for MyISAM and ARCHIVE tables\nonly. With mysqldump, you can create SQL dumps on the master and pipe\n(or copy) these to a mysql client on the slave. This has the advantage\nof working for all storage engines, but can be quite slow, since it\nworks using SELECT.\n\nTransfers a copy of the table from the master to the slave. This\nstatement is implemented mainly debugging LOAD DATA FROM MASTER\noperations. To use LOAD TABLE, the account used for connecting to the\nmaster server must have the RELOAD and SUPER privileges on the master\nand the SELECT privilege for the master table to load. On the slave\nside, the user that issues LOAD TABLE FROM MASTER must have privileges\nfor dropping and creating the table.\n\nThe conditions for LOAD DATA FROM MASTER apply here as well. For\nexample, LOAD TABLE FROM MASTER works only for MyISAM tables. The\ntimeout notes for LOAD DATA FROM MASTER apply as well.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/load-table-from-master.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/load-table-from-master.html');
INSERT INTO `help_topic` VALUES (340, 'GROUP_CONCAT', 14, '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.0/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.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (341, 'DATE_FORMAT', 28, 'Syntax:\nDATE_FORMAT(date,format)\n\nFormats the date value according to the format string.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DATE_FORMAT(''1997-10-04 22:23:00'', ''%W %M %Y'');\n        -> ''Saturday October 1997''\nmysql> SELECT DATE_FORMAT(''1997-10-04 22:23:00'', ''%H:%i:%s'');\n        -> ''22:23:00''\nmysql> SELECT DATE_FORMAT(''1997-10-04 22:23:00'',\n                          ''%D %y %a %d %m %b %j'');\n        -> ''4th 97 Sat 04 10 Oct 277''\nmysql> SELECT DATE_FORMAT(''1997-10-04 22:23:00'',\n                          ''%H %k %I %r %T %S %w'');\n        -> ''22 22 10 10:23:00 PM 22:23:00 00 6''\nmysql> SELECT DATE_FORMAT(''1999-01-01'', ''%X %V'');\n        -> ''1998 52''\nmysql> SELECT DATE_FORMAT(''2006-06-00'', ''%d'');\n        -> ''00''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (342, 'BENCHMARK', 15, '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.0/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.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (343, 'YEAR', 28, 'Syntax:\nYEAR(date)\n\nReturns the year for date, in the range 1000 to 9999, or 0 for the\n"zero" date.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT YEAR(''98-02-03'');\n        -> 1998\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (344, 'SHOW ENGINE', 25, 'Syntax:\nSHOW ENGINE engine_name {LOGS | STATUS }\n\nSHOW ENGINE displays log or status information about a storage engine.\nThe following statements currently are supported:\n\nSHOW ENGINE BDB LOGS\nSHOW ENGINE INNODB STATUS\nSHOW ENGINE NDB STATUS\nSHOW ENGINE NDBCLUSTER STATUS\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-engine.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-engine.html');
INSERT INTO `help_topic` VALUES (345, 'NAME_CONST', 13, '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.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (346, 'RELEASE_LOCK', 13, '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.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (347, 'IS NULL', 17, 'Syntax:\nIS NULL\n\nTests whether a value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 IS NULL, 0 IS NULL, NULL IS NULL;\n        -> 0, 0, 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (348, 'CONVERT_TZ', 28, '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.0/en/time-zone-support.html. This\nfunction returns NULL if the arguments are invalid.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (349, 'TIME_TO_SEC', 28, 'Syntax:\nTIME_TO_SEC(time)\n\nReturns the time argument, converted to seconds.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (350, 'WEEKDAY', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT WEEKDAY(''1998-02-03 22:23:00'');\n        -> 1\nmysql> SELECT WEEKDAY(''1997-11-05'');\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (351, 'EXPORT_SET', 33, '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\n(defaults to 64).\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (352, 'TIME FUNCTION', 28, 'Syntax:\nTIME(expr)\n\nExtracts the time part of the time or datetime expression expr and\nreturns it as a string.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT TIME(''2003-12-31 01:02:03'');\n        -> ''01:02:03''\nmysql> SELECT TIME(''2003-12-31 01:02:03.000123'');\n        -> ''01:02:03.000123''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (353, 'DATE_ADD', 28, 'Syntax:\nDATE_ADD(date,INTERVAL expr unit), DATE_SUB(date,INTERVAL expr unit)\n\nThese functions perform date arithmetic. date is a DATETIME or DATE\nvalue specifying the starting date. expr is an expression specifying\nthe interval value to be added or subtracted from the starting date.\nexpr is a string; it may start with a "-" for negative intervals. unit\nis a keyword indicating the units in which the expression should be\ninterpreted.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT ''1997-12-31 23:59:59'' + INTERVAL 1 SECOND;\n        -> ''1998-01-01 00:00:00''\nmysql> SELECT INTERVAL 1 DAY + ''1997-12-31'';\n        -> ''1998-01-01''\nmysql> SELECT ''1998-01-01'' - INTERVAL 1 SECOND;\n        -> ''1997-12-31 23:59:59''\nmysql> SELECT DATE_ADD(''1997-12-31 23:59:59'',\n    ->                 INTERVAL 1 SECOND);\n        -> ''1998-01-01 00:00:00''\nmysql> SELECT DATE_ADD(''1997-12-31 23:59:59'',\n    ->                 INTERVAL 1 DAY);\n        -> ''1998-01-01 23:59:59''\nmysql> SELECT DATE_ADD(''1997-12-31 23:59:59'',\n    ->                 INTERVAL ''1:1'' MINUTE_SECOND);\n        -> ''1998-01-01 00:01:00''\nmysql> SELECT DATE_SUB(''1998-01-01 00:00:00'',\n    ->                 INTERVAL ''1 1:1:1'' DAY_SECOND);\n        -> ''1997-12-30 22:58:59''\nmysql> SELECT DATE_ADD(''1998-01-01 00:00:00'',\n    ->                 INTERVAL ''-1 10'' DAY_HOUR);\n        -> ''1997-12-30 14:00:00''\nmysql> SELECT DATE_SUB(''1998-01-02'', INTERVAL 31 DAY);\n        -> ''1997-12-02''\nmysql> SELECT DATE_ADD(''1992-12-31 23:59:59.000002'',\n    ->            INTERVAL ''1.999999'' SECOND_MICROSECOND);\n        -> ''1993-01-01 00:00:01.000001''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (354, 'CAST', 33, 'Syntax:\nCAST(expr AS type)\n\nThe CAST() function takes a value of one type and produce a value of\nanother type, similar to CONVERT(). See the description of CONVERT()\nfor more information.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/cast-functions.html');
INSERT INTO `help_topic` VALUES (355, 'SOUNDS LIKE', 33, 'Syntax:\nexpr1 SOUNDS LIKE expr2\n\nThis is the same as SOUNDEX(expr1) = SOUNDEX(expr2).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (356, 'PERIOD_DIFF', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT PERIOD_DIFF(9802,199703);\n        -> 11\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (357, 'LIKE', 33, 'Syntax:\nexpr LIKE pat [ESCAPE ''escape_char'']\n\nPattern matching using SQL simple regular expression comparison.\nReturns 1 (TRUE) or 0 (FALSE). If either expr or pat is NULL, the\nresult is NULL.\n\nThe pattern need not be a literal string. For example, it can be\nspecified as a string expression or table column.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html\n\n', 'mysql> SELECT ''David!'' LIKE ''David_'';\n        -> 1\nmysql> SELECT ''David!'' LIKE ''%D%v%'';\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html');
INSERT INTO `help_topic` VALUES (358, 'MULTIPOINT', 22, 'MultiPoint(pt1,pt2,...)\n\nConstructs a WKB MultiPoint value using WKB Point arguments. If any\nargument is not a WKB Point, the return value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (359, '>>', 18, 'Syntax:\n>>\n\nShifts a longlong (BIGINT) number to the right.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 4 >> 2;\n        -> 1\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (360, 'FETCH', 35, 'Syntax:\nFETCH cursor_name INTO var_name [, var_name] ...\n\nThis statement fetches the next row (if a row exists) using the\nspecified open cursor, and advances the cursor pointer.\n\nIf no more rows are available, a No Data condition occurs with SQLSTATE\nvalue 02000. To detect this condition, you can set up a handler for it\n(or for a NOT FOUND condition). An example is shown in [HELP DECLARE\nCURSOR].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/fetch.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/fetch.html');
INSERT INTO `help_topic` VALUES (361, 'AVG', 14, 'Syntax:\nAVG([DISTINCT] expr)\n\nReturns the average value of expr. The DISTINCT option can be used as\nof MySQL 5.0.3 to return 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.0/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.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (362, 'TRUE FALSE', 27, 'The constants TRUE and FALSE evaluate to 1 and 0, respectively. The\nconstant names can be written in any lettercase.\n\nmysql> SELECT TRUE, true, FALSE, false;\n        -> 1, 1, 0, 0\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/boolean-values.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/boolean-values.html');
INSERT INTO `help_topic` VALUES (363, 'MBRWITHIN', 5, 'MBRWithin(g1,g2)\n\nReturns 1 or 0 to indicate whether the Minimum Bounding Rectangle of g1\nis within the Minimum Bounding Rectangle of g2. This tests the opposite\nrelationship as MBRContains().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html\n\n', 'mysql> SET @g1 = GeomFromText(''Polygon((0 0,0 3,3 3,3 0,0 0))'');\nmysql> SET @g2 = GeomFromText(''Polygon((0 0,0 5,5 5,5 0,0 0))'');\nmysql> SELECT MBRWithin(@g1,@g2), MBRWithin(@g2,@g1);\n+--------------------+--------------------+\n| MBRWithin(@g1,@g2) | MBRWithin(@g2,@g1) |\n+--------------------+--------------------+\n|                  1 |                  0 |\n+--------------------+--------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/relations-on-geometry-mbr.html');
INSERT INTO `help_topic` VALUES (364, 'IN', 17, '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.0/en/type-conversion.html, but\napplied to all the arguments.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (365, 'QUOTE', 33, '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 quotes and with each instance of single quote ("''"),\nbackslash ("\\"), ASCII NUL, and Control-Z preceded by a backslash. If\nthe argument is NULL, the return value is the word "NULL" without\nenclosing single quotes.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (366, 'SESSION_USER', 15, 'Syntax:\nSESSION_USER()\n\nSESSION_USER() is a synonym for USER().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (367, 'HELP COMMAND', 24, '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.0/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   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-master-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\nURL: http://dev.mysql.com/doc/refman/5.0/en/mysql-server-side-help.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/mysql-server-side-help.html');
INSERT INTO `help_topic` VALUES (368, 'QUARTER', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT QUARTER(''98-04-01'');\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (369, 'POSITION', 33, '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.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (370, 'IS_USED_LOCK', 13, '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.0/en/miscellaneous-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (371, 'POLYFROMTEXT', 3, '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.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (372, 'DES_ENCRYPT', 10, '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.0/en/secure-connections.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'key_num des_key_str\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (373, 'CEIL', 4, 'Syntax:\nCEIL(X)\n\nCEIL() is a synonym for CEILING().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (374, 'LENGTH', 33, 'Syntax:\nLENGTH(str)\n\nReturns the length of the string str, measured in bytes. A multi-byte\ncharacter counts as multiple bytes. This means that for a string\ncontaining five two-byte characters, LENGTH() returns 10, whereas\nCHAR_LENGTH() returns 5.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT LENGTH(''text'');\n        -> 4\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (375, 'STR_TO_DATE', 28, 'Syntax:\nSTR_TO_DATE(str,format)\n\nThis is the inverse of the DATE_FORMAT() function. It takes a string\nstr and a format string format. STR_TO_DATE() returns a DATETIME value\nif the format string contains both date and time parts, or a DATE or\nTIME value if the string contains only date or time parts.\n\nThe date, time, or datetime values contained in str should be given in\nthe format indicated by format. For the specifiers that can be used in\nformat, see the DATE_FORMAT() function description. If str contains an\nillegal date, time, or datetime value, STR_TO_DATE() returns NULL.\nStarting from MySQL 5.0.3, an illegal value also produces a warning.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (376, 'Y', 9, 'Y(p)\n\nReturns the Y-coordinate value for the point p as a double-precision\nnumber.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/point-property-functions.html\n\n', 'mysql> SET @pt = ''Point(56.7 53.34)'';\nmysql> SELECT Y(GeomFromText(@pt));\n+----------------------+\n| Y(GeomFromText(@pt)) |\n+----------------------+\n|                53.34 |\n+----------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/point-property-functions.html');
INSERT INTO `help_topic` VALUES (377, 'SHOW INNODB STATUS', 25, 'Syntax:\nSHOW INNODB STATUS\n\nIn MySQL 5.0, this is a deprecated synonym for SHOW ENGINE INNODB\nSTATUS. See [HELP SHOW ENGINE].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-innodb-status.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-innodb-status.html');
INSERT INTO `help_topic` VALUES (378, 'CHECKSUM TABLE', 19, 'Syntax:\nCHECKSUM TABLE tbl_name [, tbl_name] ... [ QUICK | EXTENDED ]\n\nCHECKSUM TABLE reports a table checksum.\n\nWith QUICK, the live table checksum is reported if it is available, or\nNULL otherwise. This is very fast. A live checksum is enabled by\nspecifying the CHECKSUM=1 table option when you create the table;\ncurrently, this is supported only for MyISAM tables. See [HELP CREATE\nTABLE].\n\nWith EXTENDED, the entire table is read row by row and the checksum is\ncalculated. This can be very slow for large tables.\n\nIf neither QUICK nor EXTENDED is specified, MySQL returns a live\nchecksum if the table storage engine supports it and scans the table\notherwise.\n\nFor a non-existent table, CHECKSUM TABLE returns NULL and, as of MySQL\n5.0.3, generates a warning.\n\nThe checksum value depends on the table row format. If the row format\nchanges, the checksum will change. For example, the storage format for\nVARCHAR changed between MySQL 4.1 and 5.0, so if a 4.1 table is\nupgraded to MySQL 5.0, the checksum value may change.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/checksum-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/checksum-table.html');
INSERT INTO `help_topic` VALUES (379, 'NUMINTERIORRINGS', 2, 'NumInteriorRings(poly)\n\nReturns the number of interior rings in the Polygon value poly.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html\n\n', 'mysql> SET @poly =\n    -> ''Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))'';\nmysql> SELECT NumInteriorRings(GeomFromText(@poly));\n+---------------------------------------+\n| NumInteriorRings(GeomFromText(@poly)) |\n+---------------------------------------+\n|                                     1 |\n+---------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html');
INSERT INTO `help_topic` VALUES (380, 'INTERIORRINGN', 2, 'InteriorRingN(poly,N)\n\nReturns the N-th interior ring for the Polygon value poly as a\nLineString. Rings are numbered beginning with 1.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html\n\n', 'mysql> SET @poly =\n    -> ''Polygon((0 0,0 3,3 3,3 0,0 0),(1 1,1 2,2 2,2 1,1 1))'';\nmysql> SELECT AsText(InteriorRingN(GeomFromText(@poly),1));\n+----------------------------------------------+\n| AsText(InteriorRingN(GeomFromText(@poly),1)) |\n+----------------------------------------------+\n| LINESTRING(1 1,1 2,2 2,2 1,1 1)              |\n+----------------------------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/polygon-property-functions.html');
INSERT INTO `help_topic` VALUES (381, 'UTC_TIME', 28, 'Syntax:\nUTC_TIME, UTC_TIME()\n\nReturns the current UTC time as a value in ''HH:MM:SS'' or HHMMSS.uuuuuu\nformat, depending on whether the function is used in a string or\nnumeric context.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT UTC_TIME(), UTC_TIME() + 0;\n        -> ''18:07:53'', 180753.000000\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (382, 'DROP FUNCTION', 34, 'Syntax:\nDROP FUNCTION function_name\n\nThis statement drops the user-defined function (UDF) named\nfunction_name.\n\nTo drop a function, you must have the DELETE privilege for the mysql\ndatabase. This is because DROP FUNCTION removes a row from the\nmysql.func system table that records the function''s name, type, and\nshared library name.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/drop-function.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-function.html');
INSERT INTO `help_topic` VALUES (383, 'STDDEV', 14, 'Syntax:\nSTDDEV(expr)\n\nReturns the population standard deviation of expr. This function is\nprovided for compatibility with Oracle. As of MySQL 5.0.3, the standard\nSQL function STDDEV_POP() can be used instead.\n\nThis function returns NULL if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (384, 'DATE_SUB', 28, 'Syntax:\nDATE_SUB(date,INTERVAL expr unit)\n\nSee the description for DATE_ADD().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (385, 'PERIOD_ADD', 28, 'Syntax:\nPERIOD_ADD(P,N)\n\nAdds N months to period P (in the format YYMM or YYYYMM). Returns a\nvalue in the format YYYYMM. Note that the period argument P is not a\ndate value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT PERIOD_ADD(9801,2);\n        -> 199803\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (386, '|', 18, 'Syntax:\n|\n\nBitwise OR:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT 29 | 15;\n        -> 31\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (387, 'GEOMFROMTEXT', 3, '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.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (388, 'RIGHT', 33, 'Syntax:\nRIGHT(str,len)\n\nReturns the rightmost len characters from the string str, or NULL if\nany argument is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT RIGHT(''foobarbar'', 4);\n        -> ''rbar''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (389, 'DATEDIFF', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DATEDIFF(''1997-12-31 23:59:59'',''1997-12-30'');\n        -> 1\nmysql> SELECT DATEDIFF(''1997-11-30 23:59:59'',''1997-12-31'');\n        -> -31\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (390, 'DROP PROCEDURE', 35, '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. As of MySQL 5.0.3,\nyou must have the ALTER ROUTINE privilege for the routine. (That\nprivilege is granted automatically to the routine creator.)\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.0/en/drop-procedure.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/drop-procedure.html');
INSERT INTO `help_topic` VALUES (391, 'CHECK TABLE', 19, 'Syntax:\nCHECK TABLE tbl_name [, tbl_name] ... [option] ...\n\noption = {FOR UPGRADE | QUICK | FAST | MEDIUM | EXTENDED | CHANGED}\n\nCHECK TABLE checks a table or tables for errors. CHECK TABLE works for\nMyISAM, InnoDB, and (as of MySQL 5.0.16) ARCHIVE tables. For MyISAM\ntables, the key statistics are updated as well.\n\nAs of MySQL 5.0.2, CHECK TABLE can also check views for problems, such\nas tables that are referenced in the view definition that no longer\nexist.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/check-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/check-table.html');
INSERT INTO `help_topic` VALUES (392, 'BIN', 33, 'Syntax:\nBIN(N)\n\nReturns a string representation of the binary value of N, where N is a\nlonglong (BIGINT) number. This is equivalent to CONV(N,10,2). Returns\nNULL if N is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT BIN(12);\n        -> ''1100''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (393, 'DECLARE CURSOR', 35, 'Syntax:\nDECLARE cursor_name CURSOR FOR select_statement\n\nThis statement declares a cursor. Multiple cursors may be declared in a\nroutine, but each cursor in a given block must have a unique name.\n\nThe SELECT statement cannot have an INTO clause.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/declare-cursors.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/declare-cursors.html');
INSERT INTO `help_topic` VALUES (394, 'MULTILINESTRING', 22, 'MultiLineString(ls1,ls2,...)\n\nConstructs a WKB MultiLineString value using WKB LineString arguments.\nIf any argument is not a WKB LineString, the return value is NULL.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-mysql-specific-functions.html');
INSERT INTO `help_topic` VALUES (395, 'LOAD DATA', 25, '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\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]\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. The filename must be given as a literal string.\n\nLOAD DATA INFILE is the complement of SELECT ... INTO OUTFILE. (See\n[HELP SELECT].) To write data from a table to a file, use SELECT ...\nINTO OUTFILE. To read the file back into a table, use LOAD DATA INFILE.\nThe syntax of the FIELDS and LINES clauses is the same for both\nstatements. Both clauses are optional, but FIELDS must precede LINES if\nboth are specified.\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.0/en/insert-speed.html.\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. Beginning with MySQL 5.0.38, if the contents of the input file\nuse a character set that differs from the default, it is possible (and\nusually preferable) to use the CHARACTER SET clause to specify the\ncharacter set of the file.\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 with mysqldump or mysql so that output\nis written in the character set to be used when the file is loaded with\nLOAD DATA INFILE.\n\nNote that it is currently not possible to load data files that use the\nucs2 character set.\n\nAs of MySQL 5.0.19, the character_set_filesystem system variable\ncontrols the interpretation of the filename.\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.0/en/mysqlimport.html.\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 (MyISAM, MEMORY,\nMERGE).\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. Using this option affects the performance of\nLOAD DATA a bit, even if no other thread is using the table at the same\ntime.\n\nThe LOCAL keyword, if specified, is interpreted with respect to the\nclient end of the connection:\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  pathname to specify its exact location. If given as a relative\n  pathname, the name is interpreted relative to the directory in which\n  the client program was started.\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 filename is an absolute pathname, the server uses it as\n    given.\n\n  o If the filename is a relative pathname 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 filename with no leading components is given, the server looks\n    for the file in the database directory of the default database.\n\nNote that, in 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\nWindows pathnames are specified using forward slashes rather than\nbackslashes. If you do use backslashes, you must double them.\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.0/en/privileges-provided.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/load-data.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/load-data.html');
INSERT INTO `help_topic` VALUES (396, 'LOCALTIME', 28, 'Syntax:\nLOCALTIME, LOCALTIME()\n\nLOCALTIME and LOCALTIME() are synonyms for NOW().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (397, 'MPOINTFROMTEXT', 3, 'MPointFromText(wkt[,srid]), MultiPointFromText(wkt[,srid])\n\nConstructs a MULTIPOINT value using its WKT representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkt-functions.html');
INSERT INTO `help_topic` VALUES (398, 'BLOB', 20, 'BLOB[(M)]\n\nA BLOB column with a maximum length of 65,535 (216 - 1) bytes. Each\nBLOB value is stored using a two-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.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (399, 'SHA1', 10, '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 binary\nstring of 40 hex digits, or NULL if the argument was NULL. One of the\npossible uses for this function is as a hash key. You can also use it\nas a cryptographic function for storing passwords. SHA() is synonymous\nwith SHA1().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT SHA1(''abc'');\n        -> ''a9993e364706816aba3e25717850c26c9cd0d89d''\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (400, 'SUBSTR', 33, 'Syntax:\nSUBSTR(str,pos), SUBSTR(str FROM pos), SUBSTR(str,pos,len), SUBSTR(str\nFROM pos FOR len)\n\nSUBSTR() is a synonym for SUBSTRING().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (401, 'PASSWORD', 10, 'Syntax:\nPASSWORD(str)\n\nCalculates and returns a password string from the plaintext password\nstr and returns a binary string, or NULL if the argument was NULL. This\nis the function that is used for encrypting MySQL passwords for storage\nin the Password column of the user grant table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'mysql> SELECT PASSWORD(''badpwd'');\n        -> ''*AAB3E285149C0135D51A520E1940DD3263DC008C''\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (402, 'CHAR', 20, '[NATIONAL] CHAR[(M)] [CHARACTER SET charset_name] [COLLATE\ncollation_name]\n\nA fixed-length string that is always right-padded with spaces to the\nspecified length when stored. M represents the column length in\ncharacters. The range of M is 0 to 255. If M is omitted, the length is\n1.\n\n*Note*: Trailing spaces are removed when CHAR values are retrieved.\n\nBefore MySQL 5.0.3, a CHAR column with a length specification greater\nthan 255 is converted to the smallest TEXT type that can hold values of\nthe given length. For example, CHAR(500) is converted to TEXT, and\nCHAR(200000) is converted to MEDIUMTEXT. However, this conversion\ncauses the column to become a variable-length column, and also affects\ntrailing-space removal.\n\nIn MySQL 5.0.3 and later, a CHAR length greater than 255 is illegal and\nfails with an error:\n\nmysql> CREATE TABLE c1 (col1 INT, col2 CHAR(500));\nERROR 1074 (42000): Column length too big for column ''col'' (max = 255);\nuse BLOB or TEXT instead\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (403, 'UTC_DATE', 28, '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.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (404, 'DIMENSION', 32, '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 [HELP MBR\ndefinition].\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-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.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (405, 'COUNT DISTINCT', 14, 'Syntax:\nCOUNT(DISTINCT expr,[expr...])\n\nReturns a count of the number of different non-NULL values.\n\nCOUNT(DISTINCT) returns 0 if there were no matching rows.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html\n\n', 'mysql> SELECT COUNT(DISTINCT results) FROM student;\n', 'http://dev.mysql.com/doc/refman/5.0/en/group-by-functions.html');
INSERT INTO `help_topic` VALUES (406, 'BIT', 20, '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\nThis data type was added in MySQL 5.0.3 for MyISAM, and extended in\n5.0.5 to MEMORY, InnoDB, and BDB. Before 5.0.3, BIT is a synonym for\nTINYINT(1).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (407, 'EQUALS', 26, '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.0/en/functions-that-test-spatial-relationships-between-geometries.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/functions-that-test-spatial-relationships-between-geometries.html');
INSERT INTO `help_topic` VALUES (408, 'SHOW CREATE VIEW', 25, 'Syntax:\nSHOW CREATE VIEW view_name\n\nThis statement shows a CREATE VIEW statement that creates the given\nview.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-create-view.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-create-view.html');
INSERT INTO `help_topic` VALUES (409, 'INTERVAL', 17, 'Syntax:\nINTERVAL(N,N1,N2,N3,...)\n\nReturns 0 if N < N1, 1 if N < N2 and so on or -1 if N is NULL. All\narguments are treated as integers. It is required that N1 < N2 < N3 <\n... < Nn for this function to work correctly. This is because a binary\nsearch is used (very fast).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT INTERVAL(23, 1, 15, 17, 30, 44, 200);\n        -> 3\nmysql> SELECT INTERVAL(10, 1, 10, 100, 1000);\n        -> 2\nmysql> SELECT INTERVAL(22, 23, 30, 44, 200);\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (410, 'FROM_DAYS', 28, 'Syntax:\nFROM_DAYS(N)\n\nGiven a day number N, returns a DATE value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT FROM_DAYS(729669);\n        -> ''1997-10-07''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (411, 'ALTER PROCEDURE', 35, 'Syntax:\nALTER {PROCEDURE | FUNCTION} sp_name [characteristic ...]\n\ncharacteristic:\n    { CONTAINS SQL | NO SQL | READS SQL DATA | MODIFIES SQL DATA }\n  | SQL SECURITY { DEFINER | INVOKER }\n  | COMMENT ''string''\n\nThis statement can be used to change the characteristics of a stored\nprocedure or function. As of MySQL 5.0.3, you must have the ALTER\nROUTINE privilege for the routine. (That privilege is granted\nautomatically to the routine creator.) If binary logging is enabled,\nthis statement might also require the SUPER privilege, as described in\nhttp://dev.mysql.com/doc/refman/5.0/en/stored-procedure-logging.html.\n\nMore than one change may be specified in an ALTER PROCEDURE or ALTER\nFUNCTION statement.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/alter-procedure.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/alter-procedure.html');
INSERT INTO `help_topic` VALUES (412, 'BIT_COUNT', 18, 'Syntax:\nBIT_COUNT(N)\n\nReturns the number of bits that are set in the argument N.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html\n\n', 'mysql> SELECT BIT_COUNT(29), BIT_COUNT(b''101010'');\n        -> 4, 3\n', 'http://dev.mysql.com/doc/refman/5.0/en/bit-functions.html');
INSERT INTO `help_topic` VALUES (413, 'OCTET_LENGTH', 33, 'Syntax:\nOCTET_LENGTH(str)\n\nOCTET_LENGTH() is a synonym for LENGTH().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (414, 'UTC_TIMESTAMP', 28, '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.0/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.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (415, 'AES_ENCRYPT', 10, 'Syntax:\nAES_ENCRYPT(str,key_str)\n\nAES_ENCRYPT() and AES_DECRYPT() allow encryption and decryption of data\nusing the official AES (Advanced Encryption Standard) algorithm,\npreviously known as "Rijndael." Encoding with a 128-bit key length is\nused, but you can extend it up to 256 bits by modifying the source. We\nchose 128 bits because it is much faster and it is secure enough for\nmost purposes.\n\nAES_ENCRYPT() encrypts a string and returns a binary string.\nAES_DECRYPT() decrypts the encrypted string and returns the original\nstring. The input arguments may be any length. If either argument is\nNULL, the result of this function is also NULL.\n\nBecause AES is a block-level algorithm, padding is used to encode\nuneven length strings and so the result string length may be calculated\nusing this formula:\n\n16 x (trunc(string_length / 16) + 1)\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\nYou can use the AES functions to store data in an encrypted form by\nmodifying your queries:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', 'INSERT INTO t VALUES (1,AES_ENCRYPT(''text'',''password''));\n', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (416, '+', 4, 'Syntax:\n+\n\nAddition:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html\n\n', 'mysql> SELECT 3+5;\n        -> 8\n', 'http://dev.mysql.com/doc/refman/5.0/en/arithmetic-functions.html');
INSERT INTO `help_topic` VALUES (417, 'INET_NTOA', 13, 'Syntax:\nINET_NTOA(expr)\n\nGiven a numeric network address (4 or 8 byte), returns the dotted-quad\nrepresentation of the address as a string.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html\n\n', 'mysql> SELECT INET_NTOA(3520061480);\n        -> ''209.207.224.40''\n', 'http://dev.mysql.com/doc/refman/5.0/en/miscellaneous-functions.html');
INSERT INTO `help_topic` VALUES (418, 'ACOS', 4, 'Syntax:\nACOS(X)\n\nReturns the arc cosine of X, that is, the value whose cosine is X.\nReturns NULL if X is not in the range -1 to 1.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT ACOS(1);\n        -> 0\nmysql> SELECT ACOS(1.0001);\n        -> NULL\nmysql> SELECT ACOS(0);\n        -> 1.5707963267949\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (419, 'ISOLATION', 7, 'Syntax:\nSET [GLOBAL | SESSION] TRANSACTION ISOLATION LEVEL\n{ READ UNCOMMITTED | READ COMMITTED | REPEATABLE READ | SERIALIZABLE }\n\nThis statement sets the transaction isolation level for the next\ntransaction, globally, or for the current session.\n\nThe default behavior of SET TRANSACTION is to set the isolation level\nfor the next (not yet started) transaction. If you use the GLOBAL\nkeyword, the statement sets the default transaction level globally for\nall new connections created from that point on. Existing connections\nare unaffected. You need the SUPER privilege to do this. Using the\nSESSION keyword sets the default transaction level for all future\ntransactions performed on the current connection.\n\nFor descriptions of each InnoDB transaction isolation level, see\nhttp://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-isolation.htm\nl. InnoDB supports each of these levels in MySQL 5.0. The default level\nis REPEATABLE READ.\n\nTo set the initial default global isolation level for mysqld, use the\n--transaction-isolation option. See\nhttp://dev.mysql.com/doc/refman/5.0/en/server-options.html.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-transaction.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-transaction.html');
INSERT INTO `help_topic` VALUES (420, 'CEILING', 4, 'Syntax:\nCEILING(X)\n\nReturns the smallest integer value not less than X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (421, 'SIN', 4, 'Syntax:\nSIN(X)\n\nReturns the sine of X, where X is given in radians.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT SIN(PI());\n        -> 1.2246063538224e-16\nmysql> SELECT ROUND(SIN(PI()));\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (422, 'DAYOFWEEK', 28, '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.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DAYOFWEEK(''1998-02-03'');\n        -> 3\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (423, 'LINEFROMWKB', 29, '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.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (424, 'SHOW PROCESSLIST', 25, 'Syntax:\nSHOW [FULL] PROCESSLIST\n\nSHOW PROCESSLIST shows you which threads are running. You can also get\nthis information using the mysqladmin processlist command. If you have\nthe PROCESS privilege, you can see all threads. Otherwise, you can see\nonly your own threads (that is, threads associated with the MySQL\naccount that you are using). If you do not use the FULL keyword, only\nthe first 100 characters of each statement are shown in the Info field.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/show-processlist.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-processlist.html');
INSERT INTO `help_topic` VALUES (425, 'GEOMETRYTYPE', 32, 'GeometryType(g)\n\nReturns as a string the name of the geometry type of which the geometry\ninstance g is a member. The name corresponds to one of the instantiable\nGeometry subclasses.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/general-geometry-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.0/en/general-geometry-property-functions.html');
INSERT INTO `help_topic` VALUES (426, 'CREATE VIEW', 36, '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. This statement was added in\nMySQL 5.0.1. If the view does not exist, CREATE OR REPLACE VIEW is the\nsame as CREATE VIEW. If the view does exist, CREATE OR REPLACE VIEW is\nthe 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.\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\nBase tables and views share the same namespace within a database, so a\ndatabase cannot contain a base table and a view that have the same\nname.\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\nWhen you modify an existing view, the current view definition is backed\nup and saved. It is stored in that table''s database directory, in a\nsub-folder named arc. The backup file will be named\nview_name.frm-00001. If you alter the view again, the next backup will\nbe named view_name.frm-00002. The three latest view backup definitions\nwill be stored.\n\n*Note*: Backed up view definitions will not be preserved by mysqldump,\nor any other such programs, but you could retain it from a file copy.\nHowever, they are not needed for anything, but to provide you with a\nbackup of your previous view definition.\n\nAlso note that while it is safe to remove these, it is not safe to do\nso while mysqld is running. If you delete this folder (or sub-files)\nwhile mysqld is running, you will receive an error the next time you\ntry to alter that view:\n\nmysql> ALTER VIEW v AS SELECT * FROM t;\nERROR 6 (HY000): Error on delete of ''.\\test\\arc/v.frm-0004'' (Errcode:\n2)\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\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 The SELECT statement cannot refer to prepared statement parameters.\n\no Within a stored routine, the definition cannot refer to routine\n  parameters or local variables.\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 The tables named in the view definition must already exist.\n\no You cannot associate a trigger with a view.\n\nORDER BY is allowed 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 specify the security context to be\nused when checking access privileges at view invocation time. They were\naddded in MySQL 5.0.13, but have no effect until MySQL 5.0.16.\n\nThe default DEFINER value is the user who executes the CREATE VIEW\nstatement. This is the same as specifying DEFINER = CURRENT_USER\nexplicitly. CURRENT_USER also can be given as CURRENT_USER(). If a user\nvalue is given, it should be a MySQL account in ''user_name''@''host_name''\nformat (the same format used in the GRANT statement). The user_name and\nhost_name values both are required.\n\nIf you specify the DEFINER clause, you cannot set the value to any user\nbut your own unless you have the SUPER privilege. These rules determine\nthe legal DEFINER user values:\n\no If you do not have the SUPER privilege, the only legal 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  legal account name. If the account does not actually exist, a warning\n  is generated.\n\nWithin a stored routine that is defined with the SQL SECURITY DEFINER\ncharacteristic, CURRENT_USER returns the routine creator. This also\naffects a view defined within such a routine, if the view definition\ncontains a DEFINER value of CURRENT_USER.\n\nThe SQL SECURITY characteristic determines which MySQL account to use\nwhen checking access privileges for the view when a statement is\nexecuted that references the view. The legal characteristic values are\nDEFINER and INVOKER. These indicate that the required privileges must\nbe held by the user who defined or invoked the view, respectively. The\ndefault SQL SECURITY value is DEFINER. If the value is DEFINER but the\ndefiner account does not exist when the view is referenced, an error\noccurs.\n\nAs of MySQL 5.0.16 (when the DEFINER and SQL SECURITY clauses were\nimplemented), view 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 privileges for the columns, as described previously. If the\n  definition refers to a stored function, only the privileges needed to\n  invoke the function can be checked. The privileges required when the\n  function runs can be checked only as it executes: For different\n  invocations of the function, different execution paths within the\n  function might be taken.\n\no When a view is referenced, privileges for objects accessed by the\n  view are checked against the privileges held by the view creator or\n  invoker, depending on whether the SQL SECURITY characteristic is\n  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 is defined with a SQL SECURITY characteristic\n  of DEFINER or INVOKER. If the security characteristic is DEFINER, the\n  function runs with the privileges of its creator. If the\n  characteristic is INVOKER, the function runs with the privileges\n  determined by the view''s SQL SECURITY characteristic.\n\nPrior to MySQL 5.0.16 (before the DEFINER and SQL SECURITY clauses were\nimplemented), privileges required for objects used in a view are\nchecked at view creation time.\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 INVOKER.\n\nIf you invoke a view that was created before MySQL 5.0.13, it is\ntreated as though it was created with a SQL SECURITY DEFINER clause and\nwith a DEFINER value that is the same as your account. However, because\nthe actual definer is unknown, MySQL issues a warning. To make the\nwarning go away, it is sufficient to re-create the view so that the\nview definition includes a DEFINER clause.\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.\n\nFor MERGE, the text of a statement that refers to the view and the view\ndefinition are merged such that parts of the view definition replace\ncorresponding parts of the statement.\n\nFor TEMPTABLE, the results from the view are retrieved into a temporary\ntable, which then is used to execute the statement.\n\nFor UNDEFINED, MySQL chooses which algorithm to use. It prefers MERGE\nover TEMPTABLE if possible, because MERGE is usually more efficient and\nbecause a view cannot be updatable if a temporary table is used.\n\nA reason to choose TEMPTABLE explicitly is that locks can be released\non underlying tables after the temporary table has been created and\nbefore it is used to finish processing the statement. This might result\nin quicker lock release than the MERGE algorithm so that other clients\nthat use the view are not blocked as long.\n\nA view algorithm can be UNDEFINED for three reasons:\n\no No ALGORITHM clause is present in the CREATE VIEW statement.\n\no The CREATE VIEW statement has an explicit ALGORITHM = UNDEFINED\n  clause.\n\no ALGORITHM = MERGE is specified for a view that can be processed only\n  with a temporary table. In this case, MySQL generates a warning and\n  sets the algorithm to UNDEFINED.\n\nAs mentioned earlier, MERGE is handled by merging corresponding parts\nof a view definition into the statement that refers to the view. The\nfollowing examples briefly illustrate how the MERGE algorithm works.\nThe examples assume that there is a view v_merge that has this\ndefinition:\n\nCREATE ALGORITHM = MERGE VIEW v_merge (vc1, vc2) AS\nSELECT c1, c2 FROM t WHERE c3 > 100;\n\nExample 1: Suppose that we issue this statement:\n\nSELECT * FROM v_merge;\n\nMySQL handles the statement as follows:\n\no v_merge becomes t\n\no * becomes vc1, vc2, which corresponds to c1, c2\n\no The view WHERE clause is added\n\nThe resulting statement to be executed becomes:\n\nSELECT c1, c2 FROM t WHERE c3 > 100;\n\nExample 2: Suppose that we issue this statement:\n\nSELECT * FROM v_merge WHERE vc1 < 100;\n\nThis statement is handled similarly to the previous one, except that\nvc1 < 100 becomes c1 < 100 and the view WHERE clause is added to the\nstatement WHERE clause using an AND connective (and parentheses are\nadded to make sure the parts of the clause are executed with correct\nprecedence). The resulting statement to be executed becomes:\n\nSELECT c1, c2 FROM t WHERE (c3 > 100) AND (c1 < 100);\n\nEffectively, the statement to be executed has a WHERE clause of this\nform:\n\nWHERE (select WHERE) AND (view WHERE)\n\nThe MERGE algorithm requires a one-to-one relationship between the rows\nin the view and the rows in the underlying table. If this relationship\ndoes not hold, a temporary table must be used instead. Lack of a\none-to-one relationship occurs if the view contains any of a number of\nconstructs:\n\no Aggregate functions (SUM(), MIN(), MAX(), COUNT(), and so forth)\n\no DISTINCT\n\no GROUP BY\n\no HAVING\n\no UNION or UNION ALL\n\no Subquery in the select list\n\no Refers only to literal values (in this case, there is no underlying\n  table)\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 non-updatable. To be more specific, a view is not updatable if it\ncontains any of the following:\n\no Aggregate functions (SUM(), MIN(), MAX(), COUNT(), and so forth)\n\no DISTINCT\n\no GROUP BY\n\no HAVING\n\no UNION or UNION ALL\n\no Subquery in the select list\n\no Certain joins (see additional join discussion later in this section)\n\no Non-updatable view in the FROM clause\n\no A subquery in the WHERE clause that refers to a table in the FROM\n  clause\n\no Refers only to literal values (in this case, there is no underlying\n  table to update)\n\no ALGORITHM = TEMPTABLE (use of a temporary table always makes a view\n  non-updatable)\n\nWith respect to insertability (being updatable with INSERT statements),\nan updatable view is insertable if it also satisfies these additional\nrequirements for the view columns:\n\no There must be no duplicate view column names.\n\no The view must contain all columns in the base table that do not have\n  a default value.\n\no The view columns must be simple column references and not derived\n  columns. A derived column is one that is not a simple column\n  reference but is derived from an expression. These are examples of\n  derived columns:\n\n3.14159\ncol1 + 3\nUPPER(col2)\ncol3 / col4\n(subquery)\n\nA view that has a mix of simple column references and derived columns\nis not insertable, but it can be updatable if you update only those\ncolumns that are not derived. Consider this view:\n\nCREATE VIEW v AS SELECT col1, 1 AS col2 FROM t;\n\nThis view is not insertable because col2 is derived from an expression.\nBut it is updatable if the update does not try to update col2. This\nupdate is allowable:\n\nUPDATE v SET col1 = 0;\n\nThis update is not allowable because it attempts to update a derived\ncolumn:\n\nUPDATE v SET col2 = 0;\n\nIt is sometimes possible for a multiple-table view to be updatable,\nassuming that it can be processed with the MERGE algorithm. For this to\nwork, the view must use an inner join (not an outer join or a UNION).\nAlso, only a single table in the view definition can be updated, so the\nSET clause must name only columns from one of the tables in the view.\nViews that use UNION ALL are disallowed even though they might be\ntheoretically updatable, because the implementation uses temporary\ntables to process them.\n\nFor a multiple-table updatable view, INSERT can work if it inserts into\na single table. DELETE is not supported.\n\nINSERT DELAYED is not supported for views.\n\nIf a table contains an AUTO_INCREMENT column, inserting into an\ninsertable view on the table that does not include the AUTO_INCREMENT\ncolumn does not change the value of LAST_INSERT_ID(), because the side\neffects of inserting default values into columns not part of the view\nshould not be visible.\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. The WITH CHECK OPTION clause\nwas implemented in MySQL 5.0.2.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-view.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-view.html');
INSERT INTO `help_topic` VALUES (427, 'TRIM', 33, '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.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (428, 'IS', 17, 'Syntax:\nIS boolean_value\n\nTests a value against a boolean value, where boolean_value can be TRUE,\nFALSE, or UNKNOWN.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 1 IS TRUE, 0 IS FALSE, NULL IS UNKNOWN;\n        -> 1, 1, 1\n        -> 1, 1, 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (429, 'GET_FORMAT', 28, 'Syntax:\nGET_FORMAT(DATE|TIME|DATETIME, ''EUR''|''USA''|''JIS''|''ISO''|''INTERNAL'')\n\nReturns a format string. This function is useful in combination with\nthe DATE_FORMAT() and the STR_TO_DATE() functions.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DATE_FORMAT(''2003-10-03'',GET_FORMAT(DATE,''EUR''));\n        -> ''03.10.2003''\nmysql> SELECT STR_TO_DATE(''10.31.2003'',GET_FORMAT(DATE,''USA''));\n        -> ''2003-10-31''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (430, 'TINYBLOB', 20, 'TINYBLOB\n\nA BLOB column with a maximum length of 255 (28 - 1) bytes. Each\nTINYBLOB value is stored using a one-byte length prefix that indicates\nthe number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (431, 'SAVEPOINT', 7, 'Syntax:\nSAVEPOINT identifier\nROLLBACK [WORK] TO SAVEPOINT identifier\nRELEASE SAVEPOINT identifier\n\nInnoDB supports the SQL statements SAVEPOINT and ROLLBACK TO SAVEPOINT.\nStarting from MySQL 5.0.3, RELEASE SAVEPOINT and the optional WORK\nkeyword for ROLLBACK are supported as well.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/savepoints.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/savepoints.html');
INSERT INTO `help_topic` VALUES (432, 'USER', 15, 'Syntax:\nUSER()\n\nReturns the current MySQL username and hostname as a string in the utf8\ncharacter set.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT USER();\n        -> ''davida@localhost''\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (433, 'MPOINTFROMWKB', 29, '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.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (434, 'ALTER TABLE', 36, 'Syntax:\nALTER [IGNORE] TABLE tbl_name\n    alter_specification [, alter_specification] ...\n\nalter_specification:\n    table_option ...\n  | ADD [COLUMN] col_name column_definition [FIRST | AFTER col_name ]\n  | ADD [COLUMN] (col_name column_definition,...)\n  | ADD {INDEX|KEY} [index_name] [index_type] (index_col_name,...)\n  | ADD [CONSTRAINT [symbol]]\n        PRIMARY KEY [index_type] (index_col_name,...)\n  | ADD [CONSTRAINT [symbol]]\n        UNIQUE [INDEX|KEY] [index_name] [index_type] (index_col_name,...)\n  | ADD [FULLTEXT|SPATIAL] [INDEX|KEY] [index_name] (index_col_name,...)\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 [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] 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\nindex_col_name:\n    col_name [(length)] [ASC | DESC]\n\nindex_type:\n    USING {BTREE | HASH | RTREE}\n\nALTER TABLE enables you to change the structure of an existing table.\nFor example, you can add or delete columns, create or destroy indexes,\nchange the type of existing columns, or rename columns or the table\nitself. You can also change the comment for the table and type of the\ntable.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/alter-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/alter-table.html');
INSERT INTO `help_topic` VALUES (435, 'PURGE MASTER LOGS', 25, 'Syntax:\nPURGE {MASTER | BINARY} LOGS TO ''log_name''\nPURGE {MASTER | BINARY} LOGS BEFORE ''date''\n\nDeletes all the binary logs listed in the log index prior to the\nspecified log or date. The logs also are removed from the list recorded\nin the log index file, so that the given log becomes the first.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/purge-master-logs.html\n\n', 'PURGE MASTER LOGS TO ''mysql-bin.010'';\nPURGE MASTER LOGS BEFORE ''2003-04-02 22:46:26'';\n', 'http://dev.mysql.com/doc/refman/5.0/en/purge-master-logs.html');
INSERT INTO `help_topic` VALUES (436, 'CHAR BYTE', 20, '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.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (437, 'REPAIR TABLE', 19, 'Syntax:\nREPAIR [LOCAL | NO_WRITE_TO_BINLOG] TABLE\n    tbl_name [, tbl_name] ... [QUICK] [EXTENDED] [USE_FRM]\n\nREPAIR TABLE repairs a possibly corrupted table. By default, it has the\nsame effect as myisamchk --recover tbl_name. REPAIR TABLE works for\nMyISAM and for ARCHIVE tables. See\nhttp://dev.mysql.com/doc/refman/5.0/en/myisam-storage-engine.html, and\nhttp://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html.\n\nThis statement requires SELECT and INSERT privileges for the table.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/repair-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/repair-table.html');
INSERT INTO `help_topic` VALUES (438, 'MERGE', 36, 'The MERGE storage engine, also known as the MRG_MyISAM engine, is a\ncollection of identical MyISAM tables that can be used as one.\n"Identical" means that all tables have identical column and index\ninformation. You cannot merge MyISAM tables in which the columns are\nlisted in a different order, do not have exactly the same columns, or\nhave the indexes in different order. However, any or all of the MyISAM\ntables can be compressed with myisampack. See\nhttp://dev.mysql.com/doc/refman/5.0/en/myisampack.html. Differences in\ntable options such as AVG_ROW_LENGTH, MAX_ROWS, or PACK_KEYS do not\nmatter.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/merge-storage-engine.html\n\n', 'mysql> CREATE TABLE t1 (\n    ->    a INT NOT NULL AUTO_INCREMENT PRIMARY KEY,\n    ->    message CHAR(20)) ENGINE=MyISAM;\nmysql> CREATE TABLE t2 (\n    ->    a INT NOT NULL AUTO_INCREMENT PRIMARY KEY,\n    ->    message CHAR(20)) ENGINE=MyISAM;\nmysql> INSERT INTO t1 (message) VALUES (''Testing''),(''table''),(''t1'');\nmysql> INSERT INTO t2 (message) VALUES (''Testing''),(''table''),(''t2'');\nmysql> CREATE TABLE total (\n    ->    a INT NOT NULL AUTO_INCREMENT,\n    ->    message CHAR(20), INDEX(a))\n    ->    ENGINE=MERGE UNION=(t1,t2) INSERT_METHOD=LAST;\n', 'http://dev.mysql.com/doc/refman/5.0/en/merge-storage-engine.html');
INSERT INTO `help_topic` VALUES (439, 'CREATE TABLE', 36, 'Syntax:\nCREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name\n    (create_definition,...)\n    [table_option ...]\n\nOr:\n\nCREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name\n    [(create_definition,...)]\n    [table_option ...]\n    select_statement\n\nOr:\n\nCREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name\n    { LIKE old_tbl_name | (LIKE old_tbl_name) }\n\ncreate_definition:\n    col_name column_definition\n  | [CONSTRAINT [symbol]] PRIMARY KEY [index_type] (index_col_name,...)\n  | {INDEX|KEY} [index_name] [index_type] (index_col_name,...)\n  | [CONSTRAINT [symbol]] UNIQUE [INDEX|KEY]\n      [index_name] [index_type] (index_col_name,...)\n  | {FULLTEXT|SPATIAL} [INDEX|KEY] [index_name] (index_col_name,...)\n  | [CONSTRAINT [symbol]] FOREIGN KEY\n      [index_name] (index_col_name,...) reference_definition\n  | CHECK (expr)\n\ncolumn_definition:\n    data_type [NOT NULL | NULL] [DEFAULT default_value]\n      [AUTO_INCREMENT] [UNIQUE [KEY] | [PRIMARY] KEY]\n      [COMMENT ''string''] [reference_definition]\n\ndata_type:\n    BIT[(length)]\n  | TINYINT[(length)] [UNSIGNED] [ZEROFILL]\n  | SMALLINT[(length)] [UNSIGNED] [ZEROFILL]\n  | MEDIUMINT[(length)] [UNSIGNED] [ZEROFILL]\n  | INT[(length)] [UNSIGNED] [ZEROFILL]\n  | INTEGER[(length)] [UNSIGNED] [ZEROFILL]\n  | BIGINT[(length)] [UNSIGNED] [ZEROFILL]\n  | REAL[(length,decimals)] [UNSIGNED] [ZEROFILL]\n  | DOUBLE[(length,decimals)] [UNSIGNED] [ZEROFILL]\n  | FLOAT[(length,decimals)] [UNSIGNED] [ZEROFILL]\n  | DECIMAL(length,decimals) [UNSIGNED] [ZEROFILL]\n  | NUMERIC(length,decimals) [UNSIGNED] [ZEROFILL]\n  | DATE\n  | TIME\n  | TIMESTAMP\n  | DATETIME\n  | YEAR\n  | CHAR(length)\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | VARCHAR(length)\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | BINARY(length)\n  | VARBINARY(length)\n  | TINYBLOB\n  | BLOB\n  | MEDIUMBLOB\n  | LONGBLOB\n  | TINYTEXT [BINARY]\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | TEXT [BINARY]\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | MEDIUMTEXT [BINARY]\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | LONGTEXT [BINARY]\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | ENUM(value1,value2,value3,...)\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | SET(value1,value2,value3,...)\n      [CHARACTER SET charset_name] [COLLATE collation_name]\n  | spatial_type\n\nindex_col_name:\n    col_name [(length)] [ASC | DESC]\n\nindex_type:\n    USING {BTREE | HASH | RTREE}\n\nreference_definition:\n    REFERENCES tbl_name [(index_col_name,...)]\n      [MATCH FULL | MATCH PARTIAL | MATCH SIMPLE]\n      [ON DELETE reference_option]\n      [ON UPDATE reference_option]\n\nreference_option:\n    RESTRICT | CASCADE | SET NULL | NO ACTION\n\ntable_option:\n    {ENGINE|TYPE} [=] engine_name\n  | AUTO_INCREMENT [=] value\n  | AVG_ROW_LENGTH [=] value\n  | [DEFAULT] CHARACTER SET charset_name\n  | CHECKSUM [=] {0 | 1}\n  | COLLATE collation_name\n  | COMMENT [=] ''string''\n  | CONNECTION [=] ''connect_string''\n  | DATA DIRECTORY [=] ''absolute path to directory''\n  | DELAY_KEY_WRITE [=] {0 | 1}\n  | INDEX DIRECTORY [=] ''absolute path to directory''\n  | INSERT_METHOD [=] { NO | FIRST | LAST }\n  | MAX_ROWS [=] value\n  | MIN_ROWS [=] value\n  | PACK_KEYS [=] {0 | 1 | DEFAULT}\n  | PASSWORD [=] ''string''\n  | ROW_FORMAT [=] {DEFAULT|DYNAMIC|FIXED|COMPRESSED|REDUNDANT|COMPACT}\n  | UNION [=] (tbl_name[,tbl_name]...)\n\nselect_statement:\n    [IGNORE | REPLACE] [AS] SELECT ...   (Some legal select statement)\n\nCREATE TABLE creates a table with the given name. You must have the\nCREATE privilege for the table.\n\nRules for allowable table names are given in\nhttp://dev.mysql.com/doc/refman/5.0/en/identifiers.html. By default,\nthe table is created in the default database. An error occurs if the\ntable exists, if there is no default database, or if the database does\nnot exist.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/create-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/create-table.html');
INSERT INTO `help_topic` VALUES (440, '>', 17, 'Syntax:\n>\n\nGreater than:\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html\n\n', 'mysql> SELECT 2 > 2;\n        -> 0\n', 'http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (441, 'ANALYZE TABLE', 19, 'Syntax:\nANALYZE [LOCAL | NO_WRITE_TO_BINLOG] TABLE 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 MyISAM\nand BDB. For InnoDB the table is locked with a write lock. This\nstatement works with MyISAM, BDB, and InnoDB tables. For MyISAM tables,\nthis statement is equivalent to using myisamchk --analyze.\n\nFor more information on how the analysis works withinInnoDB, see\nhttp://dev.mysql.com/doc/refman/5.0/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\nURL: http://dev.mysql.com/doc/refman/5.0/en/analyze-table.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/analyze-table.html');
INSERT INTO `help_topic` VALUES (442, 'MICROSECOND', 28, 'Syntax:\nMICROSECOND(expr)\n\nReturns the microseconds from the time or datetime expression expr as a\nnumber in the range from 0 to 999999.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MICROSECOND(''12:00:00.123456'');\n        -> 123456\nmysql> SELECT MICROSECOND(''1997-12-31 23:59:59.000010'');\n        -> 10\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (443, 'CONSTRAINT', 36, 'InnoDB also supports foreign key constraints. The syntax for a foreign\nkey constraint definition in InnoDB looks like this:\n\n[CONSTRAINT symbol] FOREIGN KEY [id] (index_col_name, ...)\n    REFERENCES tbl_name (index_col_name, ...)\n    [ON DELETE {RESTRICT | CASCADE | SET NULL | NO ACTION}]\n    [ON UPDATE {RESTRICT | CASCADE | SET NULL | NO ACTION}]\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/innodb-foreign-key-constraints.html\n\n', 'CREATE TABLE product (category INT NOT NULL, id INT NOT NULL,\n                      price DECIMAL,\n                      PRIMARY KEY(category, id)) ENGINE=INNODB;\nCREATE TABLE customer (id INT NOT NULL,\n                       PRIMARY KEY (id)) ENGINE=INNODB;\nCREATE TABLE product_order (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                            PRIMARY KEY(no),\n                            INDEX (product_category, product_id),\n                            FOREIGN KEY (product_category, product_id)\n                              REFERENCES product(category, id)\n                              ON UPDATE CASCADE ON DELETE RESTRICT,\n                            INDEX (customer_id),\n                            FOREIGN KEY (customer_id)\n                              REFERENCES customer(id)) ENGINE=INNODB;\n', 'http://dev.mysql.com/doc/refman/5.0/en/innodb-foreign-key-constraints.html');
INSERT INTO `help_topic` VALUES (444, 'FIELD', 33, '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.0/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.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (445, 'MAKETIME', 28, 'Syntax:\nMAKETIME(hour,minute,second)\n\nReturns a time value calculated from the hour, minute, and second\narguments.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT MAKETIME(12,15,30);\n        -> ''12:15:30''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (446, 'CURDATE', 28, 'Syntax:\nCURDATE()\n\nReturns the current date as a value in ''YYYY-MM-DD'' or YYYYMMDD format,\ndepending on whether the function is used in a string or numeric\ncontext.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT CURDATE();\n        -> ''1997-12-15''\nmysql> SELECT CURDATE() + 0;\n        -> 19971215\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (447, 'SET PASSWORD', 8, 'Syntax:\nSET PASSWORD [FOR user] = PASSWORD(''some password'')\n\nThe SET PASSWORD statement assigns a password to an existing MySQL user\naccount.\n\nWith no FOR clause, this statement sets the password for the current\nuser. Any client that has connected to the server using a non-anonymous\naccount can change the password for that account.\n\nWith a FOR clause, this statement sets the password for a specific\naccount on the current server host. Only clients that have the UPDATE\nprivilege for the mysql database can do this. The user value should be\ngiven in user_name@host_name format, where user_name and host_name are\nexactly as they are listed in the User and Host columns of the\nmysql.user table entry. For example, if you had an entry with User and\nHost column values of ''bob'' and ''%.loc.gov'', you would write the\nstatement like this:\n\nSET PASSWORD FOR ''bob''@''%.loc.gov'' = PASSWORD(''newpass'');\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-password.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-password.html');
INSERT INTO `help_topic` VALUES (448, 'IF FUNCTION', 6, 'Syntax:\nIF(expr1,expr2,expr3)\n\nIf expr1 is TRUE (expr1 <> 0 and expr1 <> NULL) then IF() returns\nexpr2; otherwise it returns expr3. IF() returns a numeric or string\nvalue, depending on the context in which it is used.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html\n\n', 'mysql> SELECT IF(1>2,2,3);\n        -> 3\nmysql> SELECT IF(1<2,''yes'',''no'');\n        -> ''yes''\nmysql> SELECT IF(STRCMP(''test'',''test1''),''no'',''yes'');\n        -> ''no''\n', 'http://dev.mysql.com/doc/refman/5.0/en/control-flow-functions.html');
INSERT INTO `help_topic` VALUES (449, 'ENUM', 20, '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. An ENUM column can have a maximum of 65,535 distinct\nvalues. ENUM values are represented internally as integers.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (450, 'DATABASE', 15, 'Syntax:\nDATABASE()\n\nReturns the default (current) database name as a string in the utf8\ncharacter set. If there is no default database, DATABASE() returns\nNULL. Within a stored routine, the default database is the database\nthat the routine is associated with, which is not necessarily the same\nas the database that is the default in the calling context.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT DATABASE();\n        -> ''test''\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (451, 'POINTFROMWKB', 29, 'PointFromWKB(wkb[,srid])\n\nConstructs a POINT value using its WKB representation and SRID.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/gis-wkb-functions.html');
INSERT INTO `help_topic` VALUES (452, 'POWER', 4, 'Syntax:\nPOWER(X,Y)\n\nThis is a synonym for POW().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (453, 'ATAN', 4, 'Syntax:\nATAN(X)\n\nReturns the arc tangent of X, that is, the value whose tangent is X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT ATAN(2);\n        -> 1.1071487177941\nmysql> SELECT ATAN(-2);\n        -> -1.1071487177941\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (454, 'STRCMP', 33, '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.0/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.0/en/string-comparison-functions.html');
INSERT INTO `help_topic` VALUES (455, 'INSERT DELAYED', 25, '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, and ARCHIVE tables.\n  See\n  http://dev.mysql.com/doc/refman/5.0/en/myisam-storage-engine.html,\n  http://dev.mysql.com/doc/refman/5.0/en/memory-storage-engine.html,\n  and\n  http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html.\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 DELAYED is ignored on slave replication servers because it could\n  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\nURL: http://dev.mysql.com/doc/refman/5.0/en/insert-delayed.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/insert-delayed.html');
INSERT INTO `help_topic` VALUES (456, 'SHOW PROCEDURE CODE', 25, 'Syntax:\nSHOW {PROCEDURE | FUNCTION} CODE sp_name\n\nThese statements are MySQL extensions that are available only for\nservers that have been built with debugging support. They display a\nrepresentation of the internal implementation of the named routine. The\nstatements require that you be the owner of the routine or have SELECT\naccess 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.0/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.0/en/show-procedure-code.html');
INSERT INTO `help_topic` VALUES (457, 'MEDIUMTEXT', 20, '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 multi-byte\ncharacters. Each MEDIUMTEXT value is stored using a three-byte length\nprefix that indicates the number of bytes in the value.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html');
INSERT INTO `help_topic` VALUES (458, 'LN', 4, 'Syntax:\nLN(X)\n\nReturns the natural logarithm of X; that is, the base-e logarithm of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html\n\n', 'mysql> SELECT LN(2);\n        -> 0.69314718055995\nmysql> SELECT LN(-2);\n        -> NULL\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (459, 'SHOW COLLATION', 25, 'Syntax:\nSHOW COLLATION\n    [LIKE ''pattern'' | WHERE expr]\n\nThe output from SHOW COLLATION includes all available character sets.\nThe LIKE clause, if present, indicates which collation names to match.\nThe WHERE clause can be given to select rows using more general\nconditions, as discussed in\nhttp://dev.mysql.com/doc/refman/5.0/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.0/en/show-collation.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/show-collation.html');
INSERT INTO `help_topic` VALUES (460, 'LOG', 4, 'Syntax:\nLOG(X), LOG(B,X)\n\nIf called with one parameter, this function returns the natural\nlogarithm of X.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (461, 'SET SQL_LOG_BIN', 25, 'Syntax:\nSET SQL_LOG_BIN = {0|1}\n\nDisables or enables binary logging for the current connection\n(SQL_LOG_BIN is a session variable) if the client has the SUPER\nprivilege. The statement is refused with an error if the client does\nnot have that privilege.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/set-sql-log-bin.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/set-sql-log-bin.html');
INSERT INTO `help_topic` VALUES (462, '!=', 17, 'Syntax:\n<>, !=\n\nNot equal:\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (463, 'WHILE', 35, '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 is true. statement_list consists of one or more\nstatements.\n\nA WHILE statement can be labeled. end_label cannot be given unless\nbegin_label also is present. If both are present, they must be the\nsame.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/while-statement.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.0/en/while-statement.html');
INSERT INTO `help_topic` VALUES (464, 'AES_DECRYPT', 10, 'Syntax:\nAES_DECRYPT(crypt_str,key_str)\n\nThis function allows decryption of data using the official AES\n(Advanced Encryption Standard) algorithm. For more information, see the\ndescription of AES_ENCRYPT().\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/encryption-functions.html');
INSERT INTO `help_topic` VALUES (465, 'DAYNAME', 28, 'Syntax:\nDAYNAME(date)\n\nReturns the name of the weekday for date. As of MySQL 5.0.25, the\nlanguage used for the name is controlled by the value of the\nlc_time_names system variable\n(http://dev.mysql.com/doc/refman/5.0/en/locale-support.html).\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html\n\n', 'mysql> SELECT DAYNAME(''1998-02-05'');\n        -> ''Thursday''\n', 'http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html');
INSERT INTO `help_topic` VALUES (466, 'COERCIBILITY', 15, 'Syntax:\nCOERCIBILITY(str)\n\nReturns the collation coercibility value of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT COERCIBILITY(''abc'' COLLATE latin1_swedish_ci);\n        -> 0\nmysql> SELECT COERCIBILITY(USER());\n        -> 3\nmysql> SELECT COERCIBILITY(''abc'');\n        -> 4\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (467, 'INT', 20, 'INT[(M)] [UNSIGNED] [ZEROFILL]\n\nA normal-size integer. The signed range is -2147483648 to 2147483647.\nThe unsigned range is 0 to 4294967295.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html\n\n', '', 'http://dev.mysql.com/doc/refman/5.0/en/numeric-type-overview.html');
INSERT INTO `help_topic` VALUES (468, 'GLENGTH', 11, 'GLength(ls)\n\nReturns as a double-precision number the length of the LineString value\nls in its associated spatial reference.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html\n\n', 'mysql> SET @ls = ''LineString(1 1,2 2,3 3)'';\nmysql> SELECT GLength(GeomFromText(@ls));\n+----------------------------+\n| GLength(GeomFromText(@ls)) |\n+----------------------------+\n|            2.8284271247462 |\n+----------------------------+\n', 'http://dev.mysql.com/doc/refman/5.0/en/linestring-property-functions.html');
INSERT INTO `help_topic` VALUES (469, 'RADIANS', 4, '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.0/en/mathematical-functions.html\n\n', 'mysql> SELECT RADIANS(90);\n        -> 1.5707963267949\n', 'http://dev.mysql.com/doc/refman/5.0/en/mathematical-functions.html');
INSERT INTO `help_topic` VALUES (470, 'COLLATION', 15, 'Syntax:\nCOLLATION(str)\n\nReturns the collation of the string argument.\n\nURL: http://dev.mysql.com/doc/refman/5.0/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.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (471, 'COALESCE', 17, '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.0/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.0/en/comparison-operators.html');
INSERT INTO `help_topic` VALUES (472, 'VERSION', 15, 'Syntax:\nVERSION()\n\nReturns a string that indicates the MySQL server version. The string\nuses the utf8 character set.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/information-functions.html\n\n', 'mysql> SELECT VERSION();\n        -> ''5.0.56-standard''\n', 'http://dev.mysql.com/doc/refman/5.0/en/information-functions.html');
INSERT INTO `help_topic` VALUES (473, 'MAKE_SET', 33, 'Syntax:\nMAKE_SET(bits,str1,str2,...)\n\nReturns a set value (a string containing substrings separated by ","\ncharacters) consisting of the strings that have the corresponding bit\nin bits set. str1 corresponds to bit 0, str2 to bit 1, and so on. NULL\nvalues in str1, str2, ... are not appended to the result.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT MAKE_SET(1,''a'',''b'',''c'');\n        -> ''a''\nmysql> SELECT MAKE_SET(1 | 4,''hello'',''nice'',''world'');\n        -> ''hello,world''\nmysql> SELECT MAKE_SET(1 | 4,''hello'',''nice'',NULL,''world'');\n        -> ''hello''\nmysql> SELECT MAKE_SET(0,''a'',''b'',''c'');\n        -> ''''\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');
INSERT INTO `help_topic` VALUES (474, 'FIND_IN_SET', 33, 'Syntax:\nFIND_IN_SET(str,strlist)\n\nReturns a value in the range of 1 to N if the string str is in the\nstring list strlist consisting of N substrings. A string list is a\nstring composed of substrings separated by "," characters. If the first\nargument is a constant string and the second is a column of type SET,\nthe FIND_IN_SET() function is optimized to use bit arithmetic. Returns\n0 if str is not in strlist or if strlist is the empty string. Returns\nNULL if either argument is NULL. This function does not work properly\nif the first argument contains a comma (",") character.\n\nURL: http://dev.mysql.com/doc/refman/5.0/en/string-functions.html\n\n', 'mysql> SELECT FIND_IN_SET(''b'',''a,b,c,d'');\n        -> 2\n', 'http://dev.mysql.com/doc/refman/5.0/en/string-functions.html');

-- --------------------------------------------------------

-- 
-- 資料表格式： `host`
-- 

CREATE TABLE `host` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `Db` char(64) collate utf8_bin NOT NULL default '',
  `Select_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Insert_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Update_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Delete_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Drop_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Grant_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `References_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Index_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_tmp_table_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Lock_tables_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Show_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Execute_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  PRIMARY KEY  (`Host`,`Db`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Host privileges;  Merged with database privileges';

-- 
-- 列出以下資料庫的數據： `host`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `proc`
-- 

CREATE TABLE `proc` (
  `db` char(64) character set utf8 collate utf8_bin NOT NULL default '',
  `name` char(64) NOT NULL default '',
  `type` enum('FUNCTION','PROCEDURE') NOT NULL,
  `specific_name` char(64) NOT NULL default '',
  `language` enum('SQL') NOT NULL default 'SQL',
  `sql_data_access` enum('CONTAINS_SQL','NO_SQL','READS_SQL_DATA','MODIFIES_SQL_DATA') NOT NULL default 'CONTAINS_SQL',
  `is_deterministic` enum('YES','NO') NOT NULL default 'NO',
  `security_type` enum('INVOKER','DEFINER') NOT NULL default 'DEFINER',
  `param_list` blob NOT NULL,
  `returns` char(64) NOT NULL default '',
  `body` longblob NOT NULL,
  `definer` char(77) character set utf8 collate utf8_bin NOT NULL default '',
  `created` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  `modified` timestamp NOT NULL default '0000-00-00 00:00:00',
  `sql_mode` set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE') NOT NULL default '',
  `comment` char(64) character set utf8 collate utf8_bin NOT NULL default '',
  PRIMARY KEY  (`db`,`name`,`type`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Stored Procedures';

-- 
-- 列出以下資料庫的數據： `proc`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `procs_priv`
-- 

CREATE TABLE `procs_priv` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `Db` char(64) collate utf8_bin NOT NULL default '',
  `User` char(16) collate utf8_bin NOT NULL default '',
  `Routine_name` char(64) collate utf8_bin NOT NULL default '',
  `Routine_type` enum('FUNCTION','PROCEDURE') collate utf8_bin NOT NULL,
  `Grantor` char(77) collate utf8_bin NOT NULL default '',
  `Proc_priv` set('Execute','Alter Routine','Grant') character set utf8 NOT NULL default '',
  `Timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`Host`,`Db`,`User`,`Routine_name`,`Routine_type`),
  KEY `Grantor` (`Grantor`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Procedure privileges';

-- 
-- 列出以下資料庫的數據： `procs_priv`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `tables_priv`
-- 

CREATE TABLE `tables_priv` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `Db` char(64) collate utf8_bin NOT NULL default '',
  `User` char(16) collate utf8_bin NOT NULL default '',
  `Table_name` char(64) collate utf8_bin NOT NULL default '',
  `Grantor` char(77) collate utf8_bin NOT NULL default '',
  `Timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  `Table_priv` set('Select','Insert','Update','Delete','Create','Drop','Grant','References','Index','Alter','Create View','Show view') character set utf8 NOT NULL default '',
  `Column_priv` set('Select','Insert','Update','References') character set utf8 NOT NULL default '',
  PRIMARY KEY  (`Host`,`Db`,`User`,`Table_name`),
  KEY `Grantor` (`Grantor`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Table privileges';

-- 
-- 列出以下資料庫的數據： `tables_priv`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `time_zone`
-- 

CREATE TABLE `time_zone` (
  `Time_zone_id` int(10) unsigned NOT NULL auto_increment,
  `Use_leap_seconds` enum('Y','N') NOT NULL default 'N',
  PRIMARY KEY  (`Time_zone_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Time zones' AUTO_INCREMENT=1 ;

-- 
-- 列出以下資料庫的數據： `time_zone`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `time_zone_leap_second`
-- 

CREATE TABLE `time_zone_leap_second` (
  `Transition_time` bigint(20) NOT NULL,
  `Correction` int(11) NOT NULL,
  PRIMARY KEY  (`Transition_time`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Leap seconds information for time zones';

-- 
-- 列出以下資料庫的數據： `time_zone_leap_second`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `time_zone_name`
-- 

CREATE TABLE `time_zone_name` (
  `Name` char(64) NOT NULL,
  `Time_zone_id` int(10) unsigned NOT NULL,
  PRIMARY KEY  (`Name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Time zone names';

-- 
-- 列出以下資料庫的數據： `time_zone_name`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `time_zone_transition`
-- 

CREATE TABLE `time_zone_transition` (
  `Time_zone_id` int(10) unsigned NOT NULL,
  `Transition_time` bigint(20) NOT NULL,
  `Transition_type_id` int(10) unsigned NOT NULL,
  PRIMARY KEY  (`Time_zone_id`,`Transition_time`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Time zone transitions';

-- 
-- 列出以下資料庫的數據： `time_zone_transition`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `time_zone_transition_type`
-- 

CREATE TABLE `time_zone_transition_type` (
  `Time_zone_id` int(10) unsigned NOT NULL,
  `Transition_type_id` int(10) unsigned NOT NULL,
  `Offset` int(11) NOT NULL default '0',
  `Is_DST` tinyint(3) unsigned NOT NULL default '0',
  `Abbreviation` char(8) NOT NULL default '',
  PRIMARY KEY  (`Time_zone_id`,`Transition_type_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='Time zone transition types';

-- 
-- 列出以下資料庫的數據： `time_zone_transition_type`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `user`
-- 

CREATE TABLE `user` (
  `Host` char(60) collate utf8_bin NOT NULL default '',
  `User` char(16) collate utf8_bin NOT NULL default '',
  `Password` char(41) character set latin1 collate latin1_bin NOT NULL default '',
  `Select_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Insert_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Update_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Delete_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Drop_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Reload_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Shutdown_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Process_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `File_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Grant_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `References_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Index_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Show_db_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Super_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_tmp_table_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Lock_tables_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Execute_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Repl_slave_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Repl_client_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Show_view_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Alter_routine_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `Create_user_priv` enum('N','Y') character set utf8 NOT NULL default 'N',
  `ssl_type` enum('','ANY','X509','SPECIFIED') character set utf8 NOT NULL default '',
  `ssl_cipher` blob NOT NULL,
  `x509_issuer` blob NOT NULL,
  `x509_subject` blob NOT NULL,
  `max_questions` int(11) unsigned NOT NULL default '0',
  `max_updates` int(11) unsigned NOT NULL default '0',
  `max_connections` int(11) unsigned NOT NULL default '0',
  `max_user_connections` int(11) unsigned NOT NULL default '0',
  PRIMARY KEY  (`Host`,`User`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Users and global privileges';

-- 
-- 列出以下資料庫的數據： `user`
-- 

INSERT INTO `user` VALUES (0x6c6f63616c686f7374, 0x726f6f74, 0x2a36424234383337454237343332393130354545343536384444413744433637454432434132414439, 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', '', '', '', '', 0, 0, 0, 0);
INSERT INTO `user` VALUES (0x70726f64756374696f6e2e6d7973716c2e636f6d, 0x726f6f74, '', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', '', '', '', '', 0, 0, 0, 0);
INSERT INTO `user` VALUES (0x3132372e302e302e31, 0x726f6f74, '', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', '', '', '', '', 0, 0, 0, 0);
INSERT INTO `user` VALUES (0x6c6f63616c686f7374, '', '', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', '', '', '', '', 0, 0, 0, 0);
INSERT INTO `user` VALUES (0x70726f64756374696f6e2e6d7973716c2e636f6d, '', '', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', '', '', '', '', 0, 0, 0, 0);
INSERT INTO `user` VALUES (0x6c6f63616c686f7374, 0x666f72, 0x2a45383939373843303239423230454441373836383645313045303430454433364141413641413132, 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', '', '', '', '', 0, 0, 0, 0);
-- 
-- 資料庫: `phpmyadmin`
-- 
CREATE DATABASE `phpmyadmin` DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;
USE `phpmyadmin`;

-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_bookmark`
-- 

CREATE TABLE `pma_bookmark` (
  `id` int(11) NOT NULL auto_increment,
  `dbase` varchar(255) collate utf8_bin NOT NULL default '',
  `user` varchar(255) collate utf8_bin NOT NULL default '',
  `label` varchar(255) character set utf8 NOT NULL default '',
  `query` text collate utf8_bin NOT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Bookmarks' AUTO_INCREMENT=1 ;

-- 
-- 列出以下資料庫的數據： `pma_bookmark`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_column_info`
-- 

CREATE TABLE `pma_column_info` (
  `id` int(5) unsigned NOT NULL auto_increment,
  `db_name` varchar(64) collate utf8_bin NOT NULL default '',
  `table_name` varchar(64) collate utf8_bin NOT NULL default '',
  `column_name` varchar(64) collate utf8_bin NOT NULL default '',
  `comment` varchar(255) character set utf8 NOT NULL default '',
  `mimetype` varchar(255) character set utf8 NOT NULL default '',
  `transformation` varchar(255) collate utf8_bin NOT NULL default '',
  `transformation_options` varchar(255) collate utf8_bin NOT NULL default '',
  PRIMARY KEY  (`id`),
  UNIQUE KEY `db_name` (`db_name`,`table_name`,`column_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Column information for phpMyAdmin' AUTO_INCREMENT=1 ;

-- 
-- 列出以下資料庫的數據： `pma_column_info`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_history`
-- 

CREATE TABLE `pma_history` (
  `id` bigint(20) unsigned NOT NULL auto_increment,
  `username` varchar(64) collate utf8_bin NOT NULL default '',
  `db` varchar(64) collate utf8_bin NOT NULL default '',
  `table` varchar(64) collate utf8_bin NOT NULL default '',
  `timevalue` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  `sqlquery` text collate utf8_bin NOT NULL,
  PRIMARY KEY  (`id`),
  KEY `username` (`username`,`db`,`table`,`timevalue`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='SQL history for phpMyAdmin' AUTO_INCREMENT=1 ;

-- 
-- 列出以下資料庫的數據： `pma_history`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_pdf_pages`
-- 

CREATE TABLE `pma_pdf_pages` (
  `db_name` varchar(64) collate utf8_bin NOT NULL default '',
  `page_nr` int(10) unsigned NOT NULL auto_increment,
  `page_descr` varchar(50) character set utf8 NOT NULL default '',
  PRIMARY KEY  (`page_nr`),
  KEY `db_name` (`db_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='PDF relation pages for phpMyAdmin' AUTO_INCREMENT=1 ;

-- 
-- 列出以下資料庫的數據： `pma_pdf_pages`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_relation`
-- 

CREATE TABLE `pma_relation` (
  `master_db` varchar(64) collate utf8_bin NOT NULL default '',
  `master_table` varchar(64) collate utf8_bin NOT NULL default '',
  `master_field` varchar(64) collate utf8_bin NOT NULL default '',
  `foreign_db` varchar(64) collate utf8_bin NOT NULL default '',
  `foreign_table` varchar(64) collate utf8_bin NOT NULL default '',
  `foreign_field` varchar(64) collate utf8_bin NOT NULL default '',
  PRIMARY KEY  (`master_db`,`master_table`,`master_field`),
  KEY `foreign_field` (`foreign_db`,`foreign_table`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Relation table';

-- 
-- 列出以下資料庫的數據： `pma_relation`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_table_coords`
-- 

CREATE TABLE `pma_table_coords` (
  `db_name` varchar(64) collate utf8_bin NOT NULL default '',
  `table_name` varchar(64) collate utf8_bin NOT NULL default '',
  `pdf_page_number` int(11) NOT NULL default '0',
  `x` float unsigned NOT NULL default '0',
  `y` float unsigned NOT NULL default '0',
  PRIMARY KEY  (`db_name`,`table_name`,`pdf_page_number`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Table coordinates for phpMyAdmin PDF output';

-- 
-- 列出以下資料庫的數據： `pma_table_coords`
-- 


-- --------------------------------------------------------

-- 
-- 資料表格式： `pma_table_info`
-- 

CREATE TABLE `pma_table_info` (
  `db_name` varchar(64) collate utf8_bin NOT NULL default '',
  `table_name` varchar(64) collate utf8_bin NOT NULL default '',
  `display_field` varchar(64) collate utf8_bin NOT NULL default '',
  PRIMARY KEY  (`db_name`,`table_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin COMMENT='Table information for phpMyAdmin';

-- 
-- 列出以下資料庫的數據： `pma_table_info`
-- 

-- 
-- 資料庫: `test`
-- 
CREATE DATABASE `test` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;
USE `test`;