Script started on Mon Oct 28 14:41:05 2002 [deyom@green deyom]$ locate mysql [deyom@green deyom]$ ps -e     wget http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-g nu-i686.tar.gz --14:57:47-- http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Resolving mirror.sit.wisc.edu... done. Connecting to mirror.sit.wisc.edu[144.92.9.246]:80... connected. HTTP request sent, awaiting response... 302 Found Location: ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [following] --14:57:47-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /mirrors/mysql/Downloads/MySQL-Max-4.0 ... done. ==> PORT ... done. ==> RETR mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz ... done. Length: 10,876,397 (unauthoritative) 0% [ ] 0 --.--K/s ETA --:-- 0% [ ] 19,104 77.09K/s ETA 02:17 0% [ ] 80,192 177.18K/s ETA 00:59 1% [> ] 194,816 295.88K/s ETA 00:35 2% [> ] 293,680 339.00K/s ETA 00:30 3% [=> ] 378,464 338.15K/s ETA 00:30 3% [=> ] 410,320 307.05K/s ETA 00:33 4% [==> ] 465,344 296.82K/s ETA 00:34 4% [==> ] 534,848 301.04K/s ETA 00:33 5% [===> ] 639,104 322.21K/s ETA 00:31 6% [===> ] 749,152 341.71K/s ETA 00:28 7% [====> ] 863,544 359.31K/s ETA 00:27 8% [=====> ] 953,768 359.76K/s ETA 00:26 9% [=====> ] 1,047,888 366.92K/s ETA 00:26 10% [======> ] 1,127,528 358.90K/s ETA 00:26 10% [======> ] 1,181,104 352.94K/s ETA 00:26 11% [======> ] 1,216,808 337.77K/s ETA 00:27 11% [=======> ] 1,246,264 325.15K/s ETA 00:28 11% [=======> ] 1,281,016 315.11K/s ETA 00:29 12% [=======> ] 1,325,904 307.85K/s ETA 00:30 12% [=======> ] 1,373,688 304.47K/s ETA 00:30 13% [========> ] 1,420,024 301.07K/s ETA 00:30 13% [========> ] 1,479,392 300.61K/s ETA 00:30 14% [=========> ] 1,535,864 299.55K/s ETA 00:30 14% [=========> ] 1,595,232 299.18K/s ETA 00:30 15% [=========> ] 1,674,872 301.66K/s ETA 00:29 16% [==========> ] 1,750,168 303.20K/s ETA 00:29 16% [==========> ] 1,829,808 305.88K/s ETA 00:28 17% [===========> ] 1,906,552 308.15K/s ETA 00:28 18% [============> ] 1,993,432 311.47K/s ETA 00:27 19% [============> ] 2,090,448 315.33K/s ETA 00:27 20% [=============> ] 2,188,912 319.91K/s ETA 00:26 20% [=============> ] 2,246,832 318.50K/s ETA 00:26 21% [==============> ] 2,311,992 318.18K/s ETA 00:26 21% [==============> ] 2,380,048 318.04K/s ETA 00:26 22% [===============> ] 2,453,896 318.80K/s ETA 00:25 23% [===============> ] 2,534,984 320.67K/s ETA 00:25 24% [================> ] 2,614,624 322.39K/s ETA 00:25 24% [================> ] 2,700,056 324.73K/s ETA 00:24 25% [=================> ] 2,776,800 324.45K/s ETA 00:24 26% [=================> ] 2,856,440 323.98K/s ETA 00:24 26% [=================> ] 2,902,776 321.00K/s ETA 00:24 27% [==================> ] 2,946,216 317.57K/s ETA 00:24 27% [==================> ] 2,988,208 315.14K/s ETA 00:24 27% [==================> ] 3,040,336 313.86K/s ETA 00:24 28% [===================> ] 3,101,152 313.05K/s ETA 00:24 29% [===================> ] 3,172,104 313.70K/s ETA 00:23 29% [====================> ] 3,234,368 313.50K/s ETA 00:23 30% [====================> ] 3,312,560 314.74K/s ETA 00:23 31% [=====================> ] 3,389,304 315.56K/s ETA 00:23 31% [=====================> ] 3,479,080 317.73K/s ETA 00:22 32% [======================> ] 3,541,344 316.90K/s ETA 00:22 33% [======================> ] 3,606,504 316.90K/s ETA 00:22 33% [======================> ] 3,657,184 315.67K/s ETA 00:22 34% [=======================> ] 3,718,000 315.23K/s ETA 00:22 34% [=======================> ] 3,784,608 315.27K/s ETA 00:21 35% [=======================> ] 3,825,152 313.30K/s ETA 00:21 35% [========================> ] 3,867,144 311.28K/s ETA 00:21 35% [========================> ] 3,913,480 309.76K/s ETA 00:21 36% [========================> ] 3,968,504 309.08K/s ETA 00:21 [deyom@green deyom]$ ls log1.log log2d.log log3.log log5b.log mdapache mdwuftpd log2b.log log2e.log log4a.log log5.log mdlogcheck mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz log2c.log log2.log log4.log log6.log mdlynx wu-ftpd [deyom@green deyom]$ rm mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [deyom@green deyom]$ ls log1.log log2c.log log2e.log log3.log log4.log log5.log mdapache mdlynx wu-ftpd log2b.log log2d.log log2.log log4a.log log5b.log log6.log mdlogcheck mdwuftpd [deyom@green deyom]$ cd mysql        mkdir mysel  ql [deyom@green deyom]$ ls log1.log log2c.log log2e.log log3.log log4.log log5.log mdapache mdlynx mysql log2b.log log2d.log log2.log log4a.log log5b.log log6.log mdlogcheck mdwuftpd wu-ftpd [deyom@green deyom]$ cd myswl  ql [deyom@green mysql]$ ls [deyom@green mysql]$ wget mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz --15:00:37-- http://mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz/ => `index.html' Resolving mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz... failed: Host not found. [deyom@green mysql]$ wget http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-g nu-i686.tar.gz --15:00:56-- http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Resolving mirror.sit.wisc.edu... done. Connecting to mirror.sit.wisc.edu[144.92.9.246]:80... connected. HTTP request sent, awaiting response... 302 Found Location: ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [following] --15:00:56-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:01:03-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 2) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:01:05-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 3) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:01:08-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 4) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:01:12-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 5) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:01:23-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 6) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. [deyom@green mysql]$ ftp ftp://http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-li nux-gnu-i686.tar.gz$ wget http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [deyom@green mysql]$ wget http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux- [deyom@green mysql]$ ftp ftp://http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [deyom@green mysql]$ ftp ftp://http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-lmirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz]$ ftp ftp://http:/mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gzl]$ ftp ftp://http/mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gzql]$ ftp ftp://htt/mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gzsql]$ ftp ftp://ht/mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gzysql]$ ftp ftp://h/mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gzmysql]$ ftp ftp:///mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz mysql]$ ftp ftp://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gn -i686.tar.gz ftp: ftp://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz: Name or service not known ftp> ftp> exit [deyom@green mysql]$ ftp ftp://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu- -i686.tar.gz mysql]$ wget http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz --15:02:35-- http://mirror.sit.wisc.edu/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Resolving mirror.sit.wisc.edu... done. Connecting to mirror.sit.wisc.edu[144.92.9.246]:80... connected. HTTP request sent, awaiting response... 302 Found Location: ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [following] --15:02:35-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:02:36-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 2) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:02:39-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 3) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:02:42-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 4) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:02:46-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 5) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... The server refuses login. Retrying. --15:02:51-- ftp://mirror.sit.wisc.edu/mirrors/mysql/Downloads/MySQL-Max-4.0/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz (try: 6) => `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' Connecting to mirror.sit.wisc.edu[144.92.9.246]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /mirrors/mysql/Downloads/MySQL-Max-4.0 ... done. ==> PORT ... done. ==> RETR mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz ... done. Length: 10,876,397 (unauthoritative) 0% [ ] 0 --.--K/s ETA --:-- 0% [ ] 26,520 104.85K/s ETA 01:41 0% [ ] 90,152 190.56K/s ETA 00:55 1% [> ] 186,760 235.33K/s ETA 00:44 2% [> ] 263,704 263.32K/s ETA 00:39 3% [=> ] 331,760 274.56K/s ETA 00:37 3% [=> ] 414,296 291.28K/s ETA 00:35 4% [==> ] 498,280 306.23K/s ETA 00:33 5% [==> ] 577,920 315.29K/s ETA 00:31 5% [===> ] 651,768 317.61K/s ETA 00:31 6% [===> ] 744,440 326.44K/s ETA 00:30 7% [====> ] 808,152 323.58K/s ETA 00:30 7% [====> ] 861,728 315.42K/s ETA 00:31 8% [=====> ] 923,992 312.99K/s ETA 00:31 9% [=====> ] 997,840 316.07K/s ETA 00:30 9% [=====> ] 1,070,240 314.71K/s ETA 00:30 10% [======> ] 1,149,880 318.92K/s ETA 00:29 11% [=======> ] 1,238,208 324.01K/s ETA 00:29 12% [=======> ] 1,319,296 327.66K/s ETA 00:28 12% [========> ] 1,398,936 330.63K/s ETA 00:27 13% [========> ] 1,458,304 326.41K/s ETA 00:28 13% [========> ] 1,514,776 323.83K/s ETA 00:28 14% [=========> ] 1,582,832 323.85K/s ETA 00:28 15% [=========> ] 1,656,680 324.02K/s ETA 00:27 15% [==========> ] 1,739,216 325.87K/s ETA 00:27 16% [==========> ] 1,818,856 327.17K/s ETA 00:27 17% [===========> ] 1,907,184 330.81K/s ETA 00:26 18% [============> ] 2,005,648 335.84K/s ETA 00:25 19% [============> ] 2,112,800 341.38K/s ETA 00:25 20% [=============> ] 2,206,920 345.16K/s ETA 00:24 20% [=============> ] 2,276,424 344.93K/s ETA 00:24 21% [==============> ] 2,357,672 343.18K/s ETA 00:24 22% [==============> ] 2,440,208 343.28K/s ETA 00:23 23% [===============> ] 2,543,016 347.72K/s ETA 00:23 24% [================> ] 2,629,896 347.53K/s ETA 00:23 24% [================> ] 2,693,608 345.30K/s ETA 00:23 25% [================> ] 2,748,632 341.89K/s ETA 00:23 25% [=================> ] 2,793,520 338.85K/s ETA 00:23 26% [=================> ] 2,829,720 334.92K/s ETA 00:23 26% [=================> ] 2,884,744 332.33K/s ETA 00:23 27% [==================> ] 2,951,352 331.90K/s ETA 00:23 27% [==================> ] 3,022,304 332.22K/s ETA 00:23 28% [===================> ] 3,103,392 333.44K/s ETA 00:22 29% [===================> ] 3,196,064 335.68K/s ETA 00:22 30% [====================> ] 3,291,632 338.19K/s ETA 00:21 31% [=====================> ] 3,391,544 341.17K/s ETA 00:21 32% [=====================> ] 3,495,800 344.52K/s ETA 00:20 32% [======================> ] 3,585,576 345.66K/s ETA 00:20 33% [=======================> ] 3,694,176 348.43K/s ETA 00:20 34% [=======================> ] 3,757,888 346.54K/s ETA 00:20 35% [=======================> ] 3,821,600 343.30K/s ETA 00:20 35% [========================> ] 3,880,968 342.31K/s ETA 00:19 35% [========================> ] 3,914,272 338.61K/s ETA 00:20 36% [========================> ] 3,972,192 337.25K/s ETA 00:19 37% [=========================> ] 4,037,352 336.55K/s ETA 00:19 37% [=========================> ] 4,105,408 336.48K/s ETA 00:19 38% [==========================> ] 4,161,880 335.48K/s ETA 00:19 38% [==========================> ] 4,225,592 334.35K/s ETA 00:19 39% [==========================> ] 4,277,720 332.07K/s ETA 00:19 39% [===========================> ] 4,326,952 330.28K/s ETA 00:19 40% [===========================> ] 4,376,184 328.59K/s ETA 00:19 40% [===========================> ] 4,438,448 328.19K/s ETA 00:19 41% [============================> ] 4,497,816 327.57K/s ETA 00:19 41% [============================> ] 4,565,872 327.42K/s ETA 00:18 42% [=============================> ] 4,621,848 325.56K/s ETA 00:18 43% [=============================> ] 4,680,264 324.85K/s ETA 00:18 43% [=============================> ] 4,728,048 323.47K/s ETA 00:18 43% [==============================> ] 4,784,520 322.34K/s ETA 00:18 44% [==============================> ] 4,843,888 321.88K/s ETA 00:18 45% [===============================> ] 4,913,392 321.60K/s ETA 00:18 45% [===============================> ] 4,990,136 322.17K/s ETA 00:17 46% [================================> ] 5,071,224 323.11K/s ETA 00:17 47% [================================> ] 5,150,864 323.79K/s ETA 00:17 48% [=================================> ] 5,239,192 325.16K/s ETA 00:16 48% [=================================> ] 5,318,832 325.80K/s ETA 00:16 49% [==================================> ] 5,368,064 324.74K/s ETA 00:16 49% [==================================> ] 5,427,432 323.94K/s ETA 00:16 50% [==================================> ] 5,494,040 323.62K/s ETA 00:16 51% [===================================> ] 5,570,784 324.15K/s ETA 00:15 51% [===================================> ] 5,648,976 324.83K/s ETA 00:15 52% [====================================> ] 5,724,272 325.33K/s ETA 00:15 53% [====================================> ] 5,790,880 324.95K/s ETA 00:15 54% [=====================================> ] 5,882,104 326.17K/s ETA 00:14 54% [======================================> ] 5,976,224 327.34K/s ETA 00:14 55% [======================================> ] 6,022,560 325.80K/s ETA 00:14 56% [======================================> ] 6,099,304 325.75K/s ETA 00:14 56% [=======================================> ] 6,158,672 325.36K/s ETA 00:14 57% [=======================================> ] 6,223,832 325.11K/s ETA 00:13 57% [========================================> ] 6,293,336 325.02K/s ETA 00:13 58% [========================================> ] 6,365,736 324.54K/s ETA 00:13 59% [=========================================> ] 6,438,136 324.40K/s ETA 00:13 59% [=========================================> ] 6,500,400 324.16K/s ETA 00:13 60% [=========================================> ] 6,569,904 324.02K/s ETA 00:12 61% [==========================================> ] 6,646,648 324.49K/s ETA 00:12 61% [===========================================> ] 6,740,768 325.83K/s ETA 00:12 62% [===========================================> ] 6,830,544 326.93K/s ETA 00:12 63% [============================================> ] 6,914,528 327.74K/s ETA 00:11 64% [============================================> ] 6,999,960 328.32K/s ETA 00:11 65% [=============================================> ] 7,075,256 328.07K/s ETA 00:11 65% [=============================================> ] 7,149,104 328.30K/s ETA 00:11 66% [==============================================> ] 7,211,368 327.90K/s ETA 00:10 66% [==============================================> ] 7,282,320 328.00K/s ETA 00:10 67% [===============================================> ] 7,357,616 328.28K/s ETA 00:10 68% [===============================================> ] 7,440,152 328.90K/s ETA 00:10 69% [================================================> ] 7,525,584 329.55K/s ETA 00:09 69% [================================================> ] 7,612,464 330.39K/s ETA 00:09 70% [=================================================> ] 7,677,624 329.77K/s ETA 00:09 71% [=================================================> ] 7,771,744 330.90K/s ETA 00:09 72% [==================================================> ] 7,864,416 331.81K/s ETA 00:08 73% [===================================================> ] 7,970,120 332.62K/s ETA 00:08 73% [===================================================> ] 8,030,936 332.12K/s ETA 00:08 74% [===================================================> ] 8,094,648 331.83K/s ETA 00:08 74% [====================================================> ] 8,146,776 331.04K/s ETA 00:08 75% [====================================================> ] 8,201,800 330.47K/s ETA 00:07 75% [====================================================> ] 8,265,512 330.31K/s ETA 00:07 76% [=====================================================> ] 8,336,464 330.43K/s ETA 00:07 77% [=====================================================> ] 8,416,104 330.90K/s ETA 00:07 77% [======================================================> ] 8,459,544 329.34K/s ETA 00:07 78% [======================================================> ] 8,537,736 329.76K/s ETA 00:06 79% [=======================================================> ] 8,621,720 330.36K/s ETA 00:06 79% [=======================================================> ] 8,691,224 330.10K/s ETA 00:06 80% [========================================================> ] 8,739,008 329.26K/s ETA 00:06 80% [========================================================> ] 8,796,928 328.78K/s ETA 00:06 81% [========================================================> ] 8,856,296 328.25K/s ETA 00:06 81% [=========================================================> ] 8,917,112 327.90K/s ETA 00:05 82% [=========================================================> ] 8,988,064 327.88K/s ETA 00:05 83% [==========================================================> ] 9,073,496 328.53K/s ETA 00:05 84% [==========================================================> ] 9,156,032 328.95K/s ETA 00:05 84% [===========================================================> ] 9,232,776 329.25K/s ETA 00:04 85% [===========================================================> ] 9,300,832 329.27K/s ETA 00:04 86% [============================================================> ] 9,360,200 328.81K/s ETA 00:04 86% [============================================================> ] 9,455,768 329.72K/s ETA 00:04 87% [=============================================================> ] 9,564,368 331.13K/s ETA 00:03 88% [=============================================================> ] 9,642,560 331.49K/s ETA 00:03 89% [==============================================================> ] 9,696,136 330.99K/s ETA 00:03 89% [==============================================================> ] 9,755,504 330.56K/s ETA 00:03 90% [===============================================================> ] 9,822,112 330.29K/s ETA 00:03 90% [===============================================================> ] 9,894,512 330.41K/s ETA 00:02 91% [================================================================> ] 9,978,496 330.95K/s ETA 00:02 92% [================================================================> ] 10,040,760 330.74K/s ETA 00:02 93% [=================================================================> ] 10,126,192 331.23K/s ETA 00:02 94% [=================================================================> ] 10,226,104 332.27K/s ETA 00:01 94% [==================================================================> ] 10,327,464 333.32K/s ETA 00:01 95% [===================================================================> ] 10,440,408 334.75K/s ETA 00:01 96% [===================================================================> ] 10,521,496 334.93K/s ETA 00:01 97% [====================================================================> ] 10,599,688 335.02K/s ETA 00:00 97% [====================================================================> ] 10,651,816 334.30K/s ETA 00:00 98% [====================================================================> ] 10,714,080 334.05K/s ETA 00:00 99% [=====================================================================> ] 10,787,928 334.11K/s ETA 00:00 99% [=====================================================================> ] 10,855,984 333.85K/s ETA 00:00 100%[======================================================================>] 10,876,397 333.79K/s ETA 00:00 15:03:24 (333.79 KB/s) - `mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz' saved [10876397] [deyom@green mysql]$ sudo tcsh Password: Sorry, try again. Password: Sorry, try again. Password: Sorry, try again. sudo: 3 incorrect password attempts [deyom@green mysql]$ sudo tcsh Password: [root@green ~/mysql]$ ls mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [root@green ~/mysql]$ cd .. [root@green ~]$ [root@green ~]$ cd /usr/local [root@green local]$ ls apache2 bin doc etc games include info lib libexec maggiesapache man sbin share src tuxtype [root@green local]$ mkdir gunsipzip mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz gunzip: mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz: No such file or directory [root@green local]$ ls apache2 bin doc etc games include info lib libexec maggiesapache man sbin share src tuxtype [root@green local]$ cd .. [root@green /usr]$ cd .. [root@green /]$ ls answer dev fastmail lib misc newmail printmail sbin var bin elm frm listalias mmencode opt proc tmp wnewmail boot elmalias home lost+found mnt perllocal.pod readmsg user y checkalias etc initrd messages newalias pine root usr [root@green /]$ cd .. [root@green /]$ ls answer dev fastmail lib misc newmail printmail sbin var bin elm frm listalias mmencode opt proc tmp wnewmail boot elmalias home lost+found mnt perllocal.pod readmsg user y checkalias etc initrd messages newalias pine root usr [root@green /]$ cd home [root@green /home]$ ls bspratt deyom kbartley sunny [root@green /home]$ cd .. [root@green /]$ cd .. [root@green /]$ ls answer dev fastmail lib misc newmail printmail sbin var bin elm frm listalias mmencode opt proc tmp wnewmail boot elmalias home lost+found mnt perllocal.pod readmsg user y checkalias etc initrd messages newalias pine root usr [root@green /]$ cd . [root@green /]$ [root@green /]$ cd .. [root@green /]$ ls answer dev fastmail lib misc newmail printmail sbin var bin elm frm listalias mmencode opt proc tmp wnewmail boot elmalias home lost+found mnt perllocal.pod readmsg user y checkalias etc initrd messages newalias pine root usr [root@green /]$ cd usr/ [root@green /usr]$ ls bin dict doc etc games include kerberos lib libexec local man sbin share src ssl tmp X11R6 [root@green /usr]$ cd local [root@green local]$ ls apache2 bin doc etc games include info lib libexec maggiesapache man sbin share src tuxtype [root@green local]$ cp /hpoome/deyom,/mysql/mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz /usr/local [root@green local]$ ls apache2 doc games info libexec man sbin src bin etc include lib maggiesapache mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz share tuxtype [root@green local]$ gunzip mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar.gz [root@green local]$ ls apache2 doc games info libexec man sbin src bin etc include lib maggiesapache mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar share tuxtype [root@green local]$ tar xf mysql-max-4.0.3-beta-pc-linux-gnu-i686.tarf mysql-max-4.0.3-beta-pc-linux-gnu-i686.tartf mysql-max-4.0.3-beta-pc-linux-gnu-i686.tarf mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar mysql-max-4.0.3-beta-pc-linux-gnu-i686/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/comp_err mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/replace mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/perror mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/resolveip mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/my_print_defaults mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/resolve_stack_dump mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/isamchk mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/pack_isam mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/myisamchk mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/myisampack mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqld mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlbinlog mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlshow mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlcheck mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqladmin mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqldump mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlimport mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqltest mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlmanagerc mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlmanager-pwgen mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlmanager mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqld.sym.gz mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/safe_mysqld mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/msql2mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_config mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_convert_table_format mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_explain_log mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_find_rows mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_fix_extensions mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_fix_privilege_tables mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_secure_installation mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_setpermission mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_tableinfo mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysql_zap mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlaccess mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlaccess.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlbug mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqld_multi mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqld_safe mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqldumpslow mysql-max-4.0.3-beta-pc-linux-gnu-i686/bin/mysqlhotcopy mysql-max-4.0.3-beta-pc-linux-gnu-i686/data/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/data/mysql/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/data/test/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/config.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/config-os2.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/config-win.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/dbug.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/errmsg.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/ft_global.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/hash.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/heap.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/m_ctype.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/m_string.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/md5.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/merge.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_aes.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_alarm.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_alloc.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_base.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_bitmap.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_config.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_dir.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_getopt.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_global.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_list.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_net.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_no_pthread.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_nosys.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_pthread.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_semaphore.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_sys.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/my_tree.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/myisam.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/myisammrg.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/myisampack.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysql.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysql_com.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysql_embed.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysql_version.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysqld_error.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/mysys_err.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/nisam.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/queues.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/raid.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/rijndael.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/sha1.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/sslopt-longopts.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/sslopt-usage.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/sslopt-vars.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/t_ctype.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/thr_alarm.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/thr_lock.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/include/violite.h mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libmysqlclient.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libmygcc.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libmysqlclient_r.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libmysys.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libmystrings.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/lib/libdbug.a mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/magic mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/my-huge.cnf mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/my-large.cnf mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/my-medium.cnf mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/my-small.cnf mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/mysql-4.0.3-beta.spec mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/mysql-log-rotate mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/mysql.server mysql-max-4.0.3-beta-pc-linux-gnu-i686/support-files/mysql.spec mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/koi8_ru.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/latin1.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/latin2.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/dos.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/latin5.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/danish.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/Index mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/croat.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/README mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/koi8_ukr.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/swe7.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/cp1251.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/win1251ukr.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/cp1257.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/usa7.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/dec8.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/hungarian.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/greek.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/german1.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/win1250.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/win1251.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/hp8.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/hebrew.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/charsets/estonia.conf mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/czech/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/czech/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/czech/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/danish/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/danish/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/danish/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/dutch/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/dutch/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/dutch/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/english/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/english/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/english/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/estonian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/estonian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/estonian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/french/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/french/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/french/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/german/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/german/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/german/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/greek/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/greek/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/greek/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/hungarian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/hungarian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/hungarian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/italian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/italian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/italian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/japanese/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/japanese/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/japanese/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/korean/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/korean/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/korean/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian-ny/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian-ny/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/norwegian-ny/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/polish/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/polish/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/polish/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/portuguese/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/portuguese/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/portuguese/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/romanian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/romanian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/romanian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/russian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/russian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/russian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/slovak/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/slovak/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/slovak/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/spanish/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/spanish/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/spanish/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/swedish/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/swedish/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/swedish/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/ukrainian/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/ukrainian/errmsg.sys mysql-max-4.0.3-beta-pc-linux-gnu-i686/share/mysql/ukrainian/errmsg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/auto_increment.res mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/function.res mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/grant.res mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/lock_test.res mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/udf_test.res mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/auto_increment.tst mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/function.tst mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/big_record.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/export.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/fork2_test.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/fork_big.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/grant.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/insert_and_repair.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/lock_test.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/mail_to_db.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/pmail.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/table_types.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/tests/test_delayed_insert.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/scripts/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/scripts/mysql_install_db mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/ChangeLog mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/Empress.crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/mysql.benchmark mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/Informix.crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/postgres.benchmark mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/Adabas.crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/postgres.crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/FrontBase.benchmark mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Comments/Access.crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/restrict_class.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/airport.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/connect_leg.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/transport.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/month_name.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/airport_service.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/fare.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/date_day.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/restrict_carrier.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/ground_service.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/aircraft.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/dual_carrier.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/flight_class.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/compound_class.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/time_interval.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/code_description.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/flight_day.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/flight.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/flight_fare.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/time_zone.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/food_service.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/stop1.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/city.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/airline.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/state.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/restriction.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/class_of_service.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/fconnection.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/day_name.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/ATIS/stop.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/Wisconsin/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/Wisconsin/onek.data mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Data/Wisconsin/tenk.data mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/README mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-SunOS_5.5.1_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/transactions-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-pg_fast-Linux_2.2.14_my_SMP_i686-crashed mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-AdabasD-Linux_2.0.35_i686-cmp-adabasd,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-oracle-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.2.16_SMP_alpha mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-pg-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-msql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/wisconsin-frontbase-Linux_2.2.14_my_SMP_i686-cmp-frontbase,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-oracle_fast-Linux_2.0.36_i686-cmp-mysql,oracle mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-solid-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-HP_UX_B.10.20_9000_778 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/RUN-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-AdabasD-Linux_2.0.35_i686-cmp-adabasd,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/insert-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-Linux_2.4.16_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql_fast-Linux_2.2.10_i686-cmp-msql,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-pg-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-pg_fast-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql_odbc-win98 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.0.36_i686-cmp-mysql,pg,solid mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-SunOS_5.7_sun4m mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-SunOS_5.7_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-mysql-Linux_2.2.1_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/big-tables-mysql-SunOS_5.8_sun4u mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/create-mysql-NT_4.0 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/ATIS-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/select-mysql-Linux_2.4.0_64GB_SMP_i686 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-Adabas-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/alter-table-pg_fast-Linux_2.4.2_64GB_SMP_i686-cmp-mysql,pg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results/connect-mysql-Linux_2.0.35_i686-cmp-adabas,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/alter-table-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-ms-sql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-mysql-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/wisconsin-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-informix_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/create-oracle_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/ATIS-sybase_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-db2_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/select-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-access_odbc-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/insert-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/RUN-mysql_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/connect-mysql-win98-cmp-access,mysql mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/Results-win32/big-tables-solid_odbc-NT_4.0-cmp-db2,informix,ms-sql,mysql,oracle,solid,sybase mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/TODO mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/bench-count-distinct mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/bench-init.pl mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/compare-results mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/copy-db mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/crash-me mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/graph-compare-results mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest1a mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest1b mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest2 mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest2a mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/innotest2b mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/Informix.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/oracle.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/ms-sql.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/msql.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/Adabas.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/solid.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/mimer.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/frontbase.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/interbase.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/interbase-dialect1.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/interbase-dialect3.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/interbase-superserver.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/sybase.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/access.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/pg.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/solid-nt4.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/empress.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/access_odbc.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/mysql-3.22.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/mysql-3.23.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/mysql.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/db2.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/limits/ms-sql65.cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/run-all-tests mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/server-cfg mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-ATIS mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-alter-table mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-big-tables mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-connect mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-create mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-insert mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-select mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-transactions mysql-max-4.0.3-beta-pc-linux-gnu-i686/sql-bench/test-wisconsin mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/alias.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/alter_table.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/analyse.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/auto_increment.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/backup.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bdb-crash.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bdb-deadlock.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bdb.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bench_count_distinct.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bigint.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/binary.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/bulk_replace.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/case.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/check.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/comments.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/compare.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/count_distinct.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/count_distinct2.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/create.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/ctype_latin1_de.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/delayed.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/delete.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/dirty_close.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/distinct.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/drop.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/empty_table.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/err000001.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/explain.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/flush.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/flush_table.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/foreign_key.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_cache.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_distinct.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_left_join.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_multi.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_order_by.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_update.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/fulltext_var.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_concat.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_crypt.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_date_add.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_encrypt.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_equal.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_group.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_if.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_in.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_isnull.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_like.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_math.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_misc.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_op.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_regexp.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_set.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_str.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_system.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_test.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_time.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_timestamp.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/gcc296.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/grant_cache.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/group_by.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/handler.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/having.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/heap.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/innodb.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/innodb_cache.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/innodb_handler.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/ins000001.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/insert.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/insert_select.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/isam.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/join.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/join_crash.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/join_outer.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/key.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/key_diff.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/key_primary.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/keywords.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/kill.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/limit.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/lock.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/lock_multi.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/merge.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/multi_update.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/myisam.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/null.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/null_key.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/odbc.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/olap.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/openssl_1.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/openssl_2.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/order_by.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/order_fill_sortbuf.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/outfile.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/overflow.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/query_cache.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/raid.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/range.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rename.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/replace.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rollback.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000001.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000002.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000003.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000004.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000005.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000006.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000007.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000008.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000009.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000010.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000011.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000012.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000013.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000015.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000017.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000018.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_alter.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_empty_master_crash.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_failsafe.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_get_lock.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_log.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_log_pos.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_magic.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_mystery22.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_rotate_logs.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_skip_error.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_sporadic_master.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000001.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000002.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000003.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000031.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000032.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000033.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/sel000100.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/select.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/select_found.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/select_safe.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/show_check.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/status.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/symlink.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/tablelock.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/temp_table.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/truncate.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_blob.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_date.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_datetime.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_decimal.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_enum.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_float.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_ranges.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_set.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_time.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_timestamp.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_uint.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/type_year.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/union.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/update.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/user_var.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/varbinary.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/variables.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/warnings.test mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/count_distinct2-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/ctype_latin1_de-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/func_encrypt-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/grant_cache-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/innodb_cache-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/order_fill_sortbuf-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/query_cache-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000007-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000008-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000009-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000010-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000013-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000015-slave-master-info.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000016-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000017-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000018-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000018-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_rotate_logs-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_rotate_logs-slave-master-info.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_skip_error-slave.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_sporadic_master-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/variables-master.opt mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000015-slave.sh mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl000017-slave.sh mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/t/rpl_rotate_logs-slave.sh mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/alias.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/alter_table.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/analyse.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/auto_increment.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/backup.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bdb-crash.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bdb-deadlock.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bdb.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bench_count_distinct.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bigint.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/binary.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/bulk_replace.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/case.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/check.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/comments.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/compare.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/count_distinct.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/count_distinct2.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/create.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/ctype_latin1_de.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/delayed.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/delete.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/dirty_close.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/distinct.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/drop.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/empty_table.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/err000001.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/explain.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/flush.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/foreign_key.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_cache.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_distinct.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_left_join.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_multi.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_order_by.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_update.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/fulltext_var.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_concat.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_crypt.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_date_add.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_encrypt.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_equal.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_group.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_if.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_in.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_isnull.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_like.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_math.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_misc.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_op.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_regexp.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_set.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_str.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_system.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_test.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_time.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/func_timestamp.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/gcc296.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/grant_cache.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/group_by.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/handler.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/having.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/heap.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/innodb.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/innodb_cache.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/innodb_handler.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/ins000001.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/insert.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/insert_select.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/isam.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/join.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/join_crash.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/join_outer.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/key.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/key_diff.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/key_primary.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/keywords.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/kill.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/limit.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/lock.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/lock_multi.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/merge.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/multi_update.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/myisam.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/null.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/null_key.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/odbc.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/olap.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/openssl_1.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/openssl_2.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/order_by.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/order_fill_sortbuf.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/overflow.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/query_cache.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/raid.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/range.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rename.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/replace.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rollback.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000001.a.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000001.b.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000001.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000002.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000003.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000004.a.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000004.b.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000004.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000005.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000006.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000007.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000008.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000009.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000010.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000011.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000012.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000013.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000015.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000017.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl000018.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_alter.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_empty_master_crash.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_failsafe.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_get_lock.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_log.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_log_pos.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_magic.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_mystery22.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_rotate_logs.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_skip_error.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/rpl_sporadic_master.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000001.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000002.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000003.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000031.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000032.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000033.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/sel000100.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/select.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/select_found.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/select_safe.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/show_check.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/slave-running.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/slave-stopped.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/status.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/symlink.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/tablelock.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/temp_table.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/truncate.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_blob.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_date.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_datetime.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_decimal.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_enum.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_float.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_ranges.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_set.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_time.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_timestamp.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_uint.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/type_year.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/union.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/update.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/user_var.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/varbinary.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/variables.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/warnings.result mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/big_test.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_bdb.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_innodb.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_isam.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_openssl.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_openssl_1.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_openssl_2.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_query_cache.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_raid.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/have_symlink.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/r/not_embedded.require mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_bdb.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_innodb.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_isam.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_openssl.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_openssl_1.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_openssl_2.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/have_query_cache.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/master-slave.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/include/not_embedded.inc mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/std_data/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/std_data/words.dat mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/std_data/master-bin.001 mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/mysql-test-run mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/install_test_db mysql-max-4.0.3-beta-pc-linux-gnu-i686/mysql-test/README mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/ mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/isamchk.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/isamlog.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysql.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysql_zap.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqlaccess.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqladmin.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqld.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqld_multi.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqld_safe.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqldump.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/mysqlshow.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/perror.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/man/replace.1 mysql-max-4.0.3-beta-pc-linux-gnu-i686/ChangeLog mysql-max-4.0.3-beta-pc-linux-gnu-i686/COPYING mysql-max-4.0.3-beta-pc-linux-gnu-i686/COPYING.LIB mysql-max-4.0.3-beta-pc-linux-gnu-i686/README mysql-max-4.0.3-beta-pc-linux-gnu-i686/INSTALL-BINARY mysql-max-4.0.3-beta-pc-linux-gnu-i686/manual.html mysql-max-4.0.3-beta-pc-linux-gnu-i686/manual.txt mysql-max-4.0.3-beta-pc-linux-gnu-i686/manual_toc.html mysql-max-4.0.3-beta-pc-linux-gnu-i686/configure [root@green local]$ tar xf mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar [root@green local]$ ls apache2 games libexec mysql-max-4.0.3-beta-pc-linux-gnu-i686.tar tuxtype bin include maggiesapache sbin doc info man share etc lib mysql-max-4.0.3-beta-pc-linux-gnu-i686 src [root@green local]$ cd mysql-max-4.0.3-beta-pc-linux-gnu-i686 [root@green mysql-max-4.0.3-beta-pc-linux-gnu-i686]$ [root@green mysql-max-4.0.3-beta-pc-linux-gnu-i686]$ lynx ./manual.html (B)0[?7h[?1h=Getting file://localhost/usr/local/mysql-max-4.0.3-beta-pc-linux-gnu-i686/manual.htmlMySQL Reference Manual for version 4.0.3-beta. (p1 of 3) MySQL Reference Manual for version 4.0.3-beta. ___________________________________________________________________________________________________ 1 General Information The MySQL (TM) software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. MySQL is a trademark of MySQL AB. The MySQL software has Dual Licensing, which means you can use the MySQL software free of charge under the GNU General Public License (http://www.gnu.org/licenses/). You can also purchase commercial MySQL licenses from MySQL AB if you do not wish to be bound by the terms of the GPL. See section 1.4 MySQL Support and Licensing. The MySQL web site (http://www.mysql.com/) provides the latest information about the MySQL software. The following list describes some sections of particular interest in this manual: * For information about the company behind the MySQL Database Server, see section 1.3 What Is MySQL AB?. * For a discussion about the capabilities of the MySQL Database Server, see section 1.2.2 The Main Read 108 KB of data, 527 KB/sec.200480 MySQL Reference Manual for version 4.0.3-beta. (p1 of 121 7646 34821 42008 88396 54480 6067 680 7245 8041 8436 8827 921 761 1032 KB of data, 308 KB/sec.80 3 .124299 .6 3 .2087 .48 4 .7677 .Read 1304 KB of data, 271 KB/sec.Read 1328 KB of data, 265 KB/sec.Read 1360 KB of  KB of data, 198 KB/sec.Read 2216 KB of data, 197 KB/sec.Read 2240 KB of data, 195 KB/sec.Read 2268 KB of data, 19MySQL Reference Manual for version 4.0.3-beta. (p1 of 775)MySQL Reference Manual for version 4.0.3-beta. ___________________________________________________________________________________________________ 1 General Information The MySQL (TM) software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. MySQL is a trademark of MySQL AB. The MySQL software has Dual Licensing, which means you can use the MySQL software free of charge under the GNU General Public License (http://www.gnu.org/licenses/). You can also purchase commercial MySQL licenses from MySQL AB if you do not wish to be bound by the terms of the GPL. See section 1.4 MySQL Support and Licensing. The MySQL web site (http://www.mysql.com/) provides the latest information about the MySQL software. The following list describes some sections of particular interest in this manual: * For information about the company behind the MySQL Database Server, see section 1.3 What Is MySQL AB?. * For a discussion about the capabilities of the MySQL Database Server, see section 1.2.2 The Main Features of MySQL. * For installation instructions, see section 2 MySQL Installation. * For tips on porting the MySQL Database Software to new architectures or operating systems, see section E Porting to Other Systems. * For information about upgrading from a Version 3.23 release, see section 2.5.1 Upgrading From Version 3.23 to Version 4.0. * For information about upgrading from a Version 3.22 release, see section 2.5.2 Upgrading From Version 3.22 to Version 3.23. * For a tutorial introduction to the MySQL Database Server, see section 3 Tutorial Introduction. * For examples of SQL and benchmarking information, see the benchmarking directory (`sql-bench' in the distribution). * For a history of new features and bug fixes, see section D MySQL Change History. * For a list of currently known bugs and misfeatures, see section 1.7.5 Known Errors and Design Deficiencies in MySQL. * For future plans, see section 1.8 MySQL and The Future (The TODO). * For a list of all the contributors to this project, see section C Credits. Important: Reports of errors (often called bugs), as well as questions and comments, should be sent to the mailing list at mysql@lists.mysql.com. See section 1.6.2.3 How to Report Bugs or Problems. The mysqlbug script should be used to generate bug reports. For source distributions, the mysqlbug script can be found in the `scripts' directory. For binary distributions, mysqlbug can be found in the `bin' directory. If you have found a sensitive security bug in MySQL Server, you should send an e-mail to security@mysql.com. Arrow keys: Up and Down to move. Right to follow a link; Left to go back. H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list -- press space for next page --1 General Information1 General Information  Arrow keys: Up and Down to move. Right to follow a link; Left to go back. H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list -- press space for next page --http://www.gnu.org/licenses/http://www.gnu.org/licenses/1.4 MySQL Support and Licensing1.4 MySQL Support and Licensinghttp://www.mysql.com/http://www.mysql.com/1.3 What Is MySQL AB?1.3 What Is MySQL AB?1.2.2 The Main Features of MySQL1.2.2 The Main Features of MySQL2 MySQL Installation2 MySQL InstallationE Porting to Other SystemsE Porting to Other Systems2.5.1 Upgrading From Version 3.23 to Version 4.02.5.1 Upgrading From Version 3.23 to Version 4.02.5.2 Upgrading From Version 3.22 to Version 3.232.5.2 Upgrading From Version 3.22 to Version 3.233 Tutorial Introduction3 Tutorial IntroductionD MySQL Change HistoryD MySQL Change History1.7.5 Known Errors and Design Deficiencies in MySQL1.7.5 Known Errors and Design Deficiencies in MySQL1.8 MySQL and The Future (The TODO)1.8 MySQL and The Future (The TODO)C CreditsC Creditsmysql@lists.mysql.commysql@lists.mysql.com1.6.2.3 How to Report Bugs or Problems1.6.2.3 How to Report Bugs or Problemssecurity@mysql.com 2 1.1 About This Manual  This is the MySQL reference manual; it documents MySQL Version 4.0.3-beta. Being a reference manual, it does not provide general instruction on SQL or relational database concepts.  As the MySQL Database Software is under constant development, the manual is also updated frequently. The most recent version of this manual is available at http://www.mysql.com/documentation/ in many different formats, including Texinfo, plain text, Info, HTML, PostScript, PDF, and Windows HLP versions.  The primary document is the Texinfo file. The HTML version is produced automatically using a modified version of texi2html. The plain text and Info versions are produced with makeinfo. The PostScript version is produced using texi2dvi and dvips. The PDF version is produced with pdftex.  If you have a hard time finding information in the manual, you can try our searchable PHP version at http://www.mysql.com/doc/.  If you have any suggestions concerning additions or corrections to this manual, please send them to the documentation team at docs@mysql.com.  This manual was initially written by David Axmark and Michael (Monty) Widenius. It is currently maintained by Michael (Monty) Widenius, Arjen Lentz, and Paul DuBois. For other contributors, see section C Credits.  The copyright (2002) to this manual is owned by the Swedish company MySQL AB. See section 1.4.2 Copyrights and Licenses Used by MySQL.  1.1.1 Conventions Used in This Manual  This manual uses certain typographical conventions:  constant  Constant-width font is used for command names and options; SQL statements; database, table, and  column names; C and Perl code; and environment variables. Example: ``To see how mysqladmin works,  invoke it with the --help option.'' `filename'  Constant-width font with surrounding quotes is used for filenames and pathnames. Example: ``The  distribution is installed under the `/usr/local/' directory.'' `c'  Constant-width font with surrounding quotes is also used to indicate character sequences.Example: ``To specify a wildcard, use the `%' character.'' italic Italic font is used for emphasis, like this. boldface Boldface font is used in table headings and to convey especially strong emphasis.  When commands are shown that are meant to be executed by a particular program, the program is indicated  1.1 About This Manual 1.1 About This Manualhttp://www.mysql.com/documentation/http://www.mysql.com/documentation/ http://www.mysql.com/doc/ http://www.mysql.com/doc/docs@mysql.comdocs@mysql.comC CreditsC Credits1.4.2 Copyrights and Licenses Used by MySQL1.4.2 Copyrights and Licenses Used by MySQL 1.1.1 Conventions Used in This Manual3 by a prompt shown before the command. For example, shell> indicates a command that you execute from your login shell, and mysql> indicates a command that you execute from the mysql client program: shell> type a shell command here mysql> type a mysql command here Shell commands are shown using Bourne shell syntax. If you are using a csh-style shell, you may need to issue commands slightly differently. For example, the sequence to set an environment variable and run a command looks like this in Bourne shell syntax: shell> VARNAME=value some_command  For csh, you would execute the sequence like this: shell> setenv VARNAME value shell> some_command  Often database, table, and column names must be substituted into commands. To indicate that such substitution is necessary, this manual uses db_name, tbl_name and col_name. For example, you might see a statement like this: mysql> SELECT col_name FROM db_name.tbl_name;eans that if you were to enter a similar statement, you would supply your own database, table, and column names, perhaps like this: mysql> SELECT author_name FROM biblio_db.author_list; SQL keywords are not case-sensitive and may be written in uppercase or lowercase. This manual uses uppercase. In syntax descriptions, square brackets (`[' and `]') are used to indicate optional words or clauses. For example, in the following statement, IF EXISTS is optional: DROP TABLE [IF EXISTS] tbl_name When a syntax element consists of a number of alternatives, the alternatives are separated by vertical bars (`|'). When one member from a set of choices may be chosen, the alternatives are listed within square brackets (`[' and `]'): TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)  When one member from a set of choices must be chosen, the alternatives are listed within braces (`{' and `}'): {DESCRIBE | DESC} tbl_name {col_name | wild}  1.2 What Is MySQL?  MySQL, the most popular Open Source SQL database, is developed and provided by MySQL AB. MySQL AB is a commercial company that builds its business providing services around the MySQL database. See section 1.3 What Is MySQL AB?. The MySQL web site (http://www.mysql.com/) provides the latest information about MySQL software and 1.2 What Is MySQL?2 1.1 About This Manual  This is the MySQL reference manual; it documents MySQL Version 4.0.3-beta. Being a reference manual, it does not provide general instruction on SQL or relational database concepts. As the MySQL Database Software is under constant development, the manual is also updated frequently. The most recent version of this manual is available at http://www.mysql.com/documentation/ in many different formats, including Texinfo, plain text, Info, HTML, PostScript, PDF, and Windows HLP versions.  The primary document is the Texinfo file. The HTML version is produced automatically using a modified version of texi2html. The plain text and Info versions are produced with makeinfo. The PostScript version is produced using texi2dvi and dvips. The PDF version is produced with pdftex.  If you have a hard time finding information in the manual, you can try our searchable PHP version at http://www.mysql.com/doc/.  If you have any suggestions concerning additions or corrections to this manual, please send them to the documentation team at docs@mysql.com. anual was initially written by David Axmark and Michael (Monty) Widenius. It is currently maintained by Michael (Monty) Widenius, Arjen Lentz, and Paul DuBois. For other contributors, see section C Credits. The copyright (2002) to this manual is owned by the Swedish company MySQL AB. See section 1.4.2 Copyrights and Licenses Used by MySQL. 1.1.1 Conventions Used in This Manual  This manual uses certain typographical conventions: constant Constant-width font is used for command names and options; SQL statements; database, table, and column names; C and Perl code; and environment variables. Example: ``To see how mysqladmin works, invoke it with the --help option.'' `filename' Constant-width font with surrounding quotes is used for filenames and pathnames. Example: ``The distribution is installed under the `/usr/local/' directory.'' `c' Constant-width font with surrounding quotes is also used to indicate character sequences. Example: ``To specify a wildcard, use the `%' character.'' italic  Italic font is used for emphasis, like this. boldface Boldface font is used in table headings and to convey especially strong emphasis. When commands are shown that are meant to be executed by a particular program, the program is indicated  1.1.1 Conventions Used in This Manual 1.1.1 Conventions Used in This Manual1.4.2 Copyrights and Licenses Used by MySQL1.4.2 Copyrights and Licenses Used by MySQLC CreditsC Credits1.4.2 Copyrights and Licenses Used by MySQL1.4.2 Copyrights and Licenses Used by MySQL 1.1.1 Conventions Used in This Manual3 by a prompt shown before the command. For example, shell> indicates a command that you execute from your login shell, and mysql> indicates a command that you execute from the mysql client program: shell> type a shell command here mysql> type a mysql command here Shell commands are shown using Bourne shell syntax. If you are using a csh-style shell, you may need to issue commands slightly differently. For example, the sequence to set an environment variable and run a command looks like this in Bourne shell syntax: shell> VARNAME=value some_command  For csh, you would execute the sequence like this: shell> setenv VARNAME value shell> some_command  Often database, table, and column names must be substituted into commands. To indicate that such substitution is necessary, this manual uses db_name, tbl_name and col_name. For example, you might see a statement like this: mysql> SELECT col_name FROM db_name.tbl_name;eans that if you were to enter a similar statement, you would supply your own database, table, and column names, perhaps like this: mysql> SELECT author_name FROM biblio_db.author_list; SQL keywords are not case-sensitive and may be written in uppercase or lowercase. This manual uses uppercase. In syntax descriptions, square brackets (`[' and `]') are used to indicate optional words or clauses. For example, in the following statement, IF EXISTS is optional: DROP TABLE [IF EXISTS] tbl_name When a syntax element consists of a number of alternatives, the alternatives are separated by vertical bars (`|'). When one member from a set of choices may be chosen, the alternatives are listed within square brackets (`[' and `]'): TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)  When one member from a set of choices must be chosen, the alternatives are listed within braces (`{' and `}'): {DESCRIBE | DESC} tbl_name {col_name | wild}  1.2 What Is MySQL?  MySQL, the most popular Open Source SQL database, is developed and provided by MySQL AB. MySQL AB is a commercial company that builds its business providing services around the MySQL database. See section 1.3 What Is MySQL AB?. The MySQL web site (http://www.mysql.com/) provides the latest information about MySQL software and 1.2 What Is MySQL?1.2 What Is MySQL? 1.3 What Is MySQL AB?4 MySQL AB. MySQL is a database management system. A database is a structured collection of data. It may be anything from a simple shopping list to a picture gallery or the vast amounts of information in a corporate network. To add, access, andprocess data stored in a computer database, you need a database management system such as MySQL Server. Since computers are very good at handling large amounts of data, database management plays a central role in computing, as stand-alone utilities, or as parts of other applications. MySQL is a relational database management system. A relational database stores data in separate tables rather than putting all the data in one bigstoreroom. This adds speed and flexibility. The tables are linked by defined relations making it possible to combine data from several tables on request. The SQL part of ``MySQL'' stands for ``Structured Query Language''@-the most common standardised language used to access databases. MySQL software is Open Source.Open Source means that it is possible for anyone to use and modify. Anybody can download the MySQL software from the Internet and use it without paying anything. Anybody so inclined can study the source code and change it to fit their needs. The MySQL software uses the GPL (GNU General Public License), http://www.gnu.org/licenses/, to define what you may and may not do with the software in different situations. If you feel uncomfortable with the GPL or need to embedMySQL code into a commercial application you can buy a commercially licensed version from us. See section 1.4.3 MySQL Licenses. Why use the MySQL Database Server? The MySQL Database Server is very fast, reliable, and easy to use. If that is what you arelooking for, you should give it a try. MySQL Server also has a practical set of features developed in close cooperation with our users. You can find a performance comparison of MySQL Server to some other database managers on our benchmark page. See section 5.1.4 The MySQLBenchmark Suite. MySQL Server was originally developed to handle large databases much faster than existing solutions and has been successfully used in highly demanding production environments for several years. Though under constant development, MySQL Server today offers a rich and useful set of functions. Its connectivity, speed, and security make MySQL Server highly suited for accessingdatabases on the Internet. The technical features of MySQL Server For advanced technical information, see section 6 MySQL Language Reference. The MySQL Database Software is a client/server system that consists of a multi-threaded SQL server that supports different backends, several different client programs and libraries, administrative tools, and awide range of programming interfaces (APIs). We also provide MySQL Server as a multi-threaded library which you can link into your application to get a smaller, faster, easier-to-manage product. There is a large amount of contributed MySQL software available.It is very likely that you will find that your favorite application or language already supports the MySQL Database Server. The official way to pronounce MySQL is ``My Ess Que Ell'' (not ``my sequel''), but we don't mind if you pronounce it as ``my sequel'' or in some other localised way.  1.2.1 History of MySQL  http://www.gnu.org/licenses/http://www.gnu.org/licenses/1.4.3 MySQL Licenses5 We once started out with the intention of using mSQL to connect to our tables using our own fast low-level (ISAM) routines. However, after some testing we came to the conclusion that mSQL was not fast enough nor flexible enough for our needs. This resulted in a new SQL interface to our database but with almost the same API interface as mSQL. This API was chosen to ease porting of third-party code.  The derivation of the name MySQL is not perfectly clear. Our base directory and a large number of our libraries and tools have had the prefix ``my'' for well over 10 years. However, Monty's daughter (some years younger) is also named My. Which of the two gave its name to MySQL is still a mystery, even for us.  1.2.2 The Main Features of MySQL  The following list describes some of the important characteristics of the MySQL Database Software. See section 1.5 MySQL 4.x In A Nutshell. Internals and Portability+ Written in C and C++. Tested with a broad range of different compilers.+ Works on many different platforms. See section 2.2.2 Operating Systems Supported by MySQL. + Uses GNU Automake (1.4), Autoconf (Version 2.52 or newer), and Libtool for portability. + APIs for C, C++, Eiffel, Java, Perl, PHP, Python, Ruby, and Tcl. See section 8 MySQL APIs. + Fully multi-threaded using kernel threads. This means it can easily use multiple CPUs if available. + Very fast B-tree disk tables with index compression.+ A very fast thread-based memory allocation system.+ Very fast joins using an optimised one-sweep multi-join.+ In-memory hash tables which are used as temporary tables.+ SQL functions are implemented through a highly optimised class library and should be as fast as possible! Usually there isn't any memory allocation at all after query initialisation. + The MySQL code gets tested with Purify (a commercial memory leakage detector) as well as with  Valgrind, a GPL tool (http://developer.kde.org/~sewardj/). Column Types + Many column types: signed/unsigned integers 1, 2, 3, 4, and 8 bytes long, FLOAT, DOUBLE, CHAR, VARCHAR, TEXT, BLOB, DATE, TIME, DATETIME, TIMESTAMP, YEAR, SET, and ENUM types. See section 6.2 Column Types.+ Fixed-length and variable-length records.+ All columns have default values. You can use INSERT to insert a subset of a table's columns; those columns that are not explicitly given values are set to their default values. Commands and Functions + Full operator and function support in the SELECT and WHERE parts of queries. For example: mysql> SELECT CONCAT(first_name, " ", last_name) -> FROM tbl_name -> WHERE income/dependents > 10000 AND age > 30; + Full support for SQL GROUP BY and ORDER BY clauses. Support for group functions (COUNT(), COUNT(DISTINCT ...), AVG(), STD(), SUM(), MAX(), and MIN()).+ Support for LEFT OUTER JOIN and RIGHT OUTER JOIN with ANSI SQL and ODBC syntax. + Aliases on tables and columns are allowed as in the SQL92 standard.+ DELETE, INSERT, REPLACE, and UPDATE return the number of rows that were changed (affected). It  1.2.2 The Main Features of MySQL6 is possible to return the number of rows matched instead by setting a flag when connecting to the server. + The MySQL-specific SHOW command can be used to retrieve information about databases, tables, and indexes. The EXPLAIN command can be used to determine how the optimiser resolves a query.+ Function names do not clash with table or column names. For example, ABS is a valid column name. The only restriction is that for a function call, no spaces are allowed between the function name and the `(' that follows it. See section 6.1.7 Is MySQL Picky About Reserved Words?. + You can mix tables from different databases in the same query (as of Version 3.22). Security + A privilege and password system that is very flexible and secure, and allows host-basedverification. Passwords are secure because all password traffic is encrypted when you connect to a server. Scalability and Limits + Handles large databases. We are using MySQL Server with some databases that contain 50 million records and we know of users that use MySQL Server with 60,000 tables and about 5,000,000,000 rows. p to 32 indexes per table are allowed. Each index may consist of 1 to 16 columns or parts of columns. The maximum index width is 500 bytes (this may be changed when compiling MySQL  Server). An index may use a prefix of a CHAR or VARCHAR field. Connectivity Clients may connect to the MySQL server using TCP/IP Sockets, Unix Sockets (Unix), or Named Pipes (NT).ODBC (Open-DataBase-Connectivity) support for Win32 (with source). All ODBC 2.5 functions and many others. For example, you can use MS Access to connect to your MySQL server. See section 8.3 MySQL ODBC Support. Localisation server can provide error messages to clients in many languages. See section 4.6.2 Non-English Error Messages. + Full support for several different character sets, including ISO-8859-1 (Latin1), german, big5, ujis, and more. For example, the Scandinavian characters 'å', 'ä' and 'ö' are allowed in tableand column names.+ All data is saved in the chosen character set. All comparisons for normal string columns are case-insensitive.Sorting is done according to the chosen character set (the Swedish way by default). It is possible to change this when the MySQL server is started. To see an example of very advanced sorting, look at the Czech sorting code. MySQL Server supports many different character sets that can be specified at compile and runtime. Clients and Tools  + Includes myisamchk, a very fast utility for table checking, optimisation, and repair. All of  the functionality of myisamchk is also available through the SQL interface as well. See section 4 Database Administration.+ All MySQL programs can be invoked with the --help or -? options to obtain online assistance.  1.2.3 How Stable Is MySQL?  6.1.7 Is MySQL Picky About ReservedWords?7 This section addresses the questions ``How stable is MySQL Server?'' and ``Can I depend on MySQL Server in this project?'' We will try to clarify these issues and answer some important questions that concern many potential users. The information in this section is based on data gathered from the mailing list, which is very active in identifying problems as well as reporting types of use.  Original code stems back from the early '80s, providing a stable code base, and the ISAM table format remains backward-compatible. At TcX, the predecessor of MySQL AB, MySQL code has worked in projects since mid-1996, without any problems. When the MySQL Database Software was released to a wider public, we noticed that there were some pieces of ``untested code'' that were quickly found by the new users who made different types of queries from us. Each new release has had fewer portability problems (even though each new release has had many new features).  Each release of the MySQL Server has been usable. There have only been problems when users try code from the ``gray zones.'' Naturally, new users don't know what the gray zones are; this section attempts to indicate those that are currently known. The descriptions mostly deal with Version 3.23 of MySQL Server. All known and reported bugs are fixed in the latest version, with the exception of those listed in the bugs section, which are things that are design-related. See section 1.7.5 Known Errors and Design Deficiencies in MySQL.  The MySQL Server design is multi-layered with independent modules. Some of the newer modules are listed here with an indication of how well-tested each of them is:  Replication -- GammaLarge server clusters using replication are in production use, with good results. Work on enhanced replication features is continuing in MySQL 4.x. InnoDB tables -- Stable (in 3.23 from 3.23.49)  The InnoDB transactional table handler has now been declared stable in the MySQL 3.23 tree,starting from version 3.23.49. InnoDB is being used in large, heavy-load production systems. BDB tables -- Gamma The Berkeley DB code is very stable, but we are still improving the BDB transactional table handler interface in MySQL Server, so it will take some time before this is as well tested as theother table types. FULLTEXT -- BetaFull-text search works but is not yet widely used. Important enhancements are being implementedfor MySQL 4.0. MyODBC 2.50 (uses ODBC SDK 2.5) -- GammaIncreasingly in wide use. Some issues brought up appear to be application-related and independentof the ODBC driver or underlying database server. Automatic recovery of MyISAM tables -- GammaThis status only regards the new code in the MyISAM table handler that checks if the table wasclosed properly on open and executes an automatic check/repair of the table if it wasn't. Bulk-insert -- Alpha New feature in MyISAM tables in MySQL 4.0 for faster insert of many rows. Locking -- Gamma  This is very system-dependent. On some systems there are big problems using standard OS locking(fcntl()). In these cases, you should run mysqld with the --skip-external-locking flag. Problems 1.7.5 Known Errors and Design Deficiencies in MySQL8 are known to occur on some Linux systems, and on SunOS when using NFS-mounted filesystems.  MySQL AB provides high-quality support for paying customers, but the MySQL mailing list usually provides answers to common questions. Bugs are usually fixed right away with a patch; for serious bugs, there is almost always a new release.  1.2.4 How Big Can MySQL Tables Be?  MySQL Version 3.22 has a 4G limit on table size. With the new MyISAM table type in MySQL Version 3.23, the maximum table size is pushed up to 8 million terabytes (2 ^ 63 bytes).  Note, however, that operating systems have their own file-size limits. Here are some examples:  Operating System File-Size Limit Linux-Intel 32 bit 2G, 4G or more, depends on Linux version Linux-Alpha 8T (?) Solaris 2.5.1 2G (possible 4G with patch) Solaris 2.6 4G (can be changed with flag) Solaris 2.7 Intel 4G Solaris 2.7 UltraSPARC 512G  On Linux 2.2 you can get bigger tables than 2G by using the LFS patch for the ext2 filesystem. On Linux 2.4 patches also exist for ReiserFS to get support for big files.  This means that the table size for MySQL databases is normally limited by the operating system.  By default, MySQL tables have a maximum size of about 4G. You can check the maximum table size for a table with the SHOW TABLE STATUS command or with the myisamchk -dv table_name. See se4.5.6 SHOW Syntax.  If you need bigger tables than 4G (and your operating system supports this), you should set the AVG_ROW_LENGTH and MAX_ROWS parameter when you create your table. See section 6.5.3 CREATE TABLE Syntax. You can also set these later with ALTER TABLE. See section 6.5.4 ALTER TABLE Syntax.  If your big table is going to be read-only, you could use myisampack to merge and compress many tables to one. myisampack usually compresses a table by at least 50%, so you can have, in effect, much bigger tables. See section 4.7.4 myisampack, The MySQL Compressed Read-only Table Generator.  You can go around the operating system file limit for MyISAM data files by using the RAID option. See section 6.5.3 CREATE TABLE Syntax.  Another solution can be the included MERGE library, which allows you to handle a collection of identical tables as one. See section 7.2 MERGE Tables.  1.2.5 Year 2000 Compliance   1.2.4 How Big Can MySQL Tables Be?9 The MySQL Server itself has no problems with Year 2000 (Y2K) compliance: * MySQL Server uses Unix time functions and has no problems with dates until 2069; all 2-digit years are regarded to be in the range 1970 to 2069, which means that if you store 01 in a year column, MySQL Server treats it as 2001. * All MySQL date functions are stored in one file, `sql/time.cc', and are coded very carefully to be year 2000-safe. * In MySQL Version 3.22 and later, the new YEAR column type can store years 0 and 1901 to 2155 in 1 byte and display them using 2 or 4 digits.  You may run into problems with applications that use MySQL Server in a way that is not Y2K-safe. For example, many old applications store or manipulate years using 2-digit values (which are ambiguous) rather than 4-digit values. This problem may be compounded by applications that use values such as 00 or 99 as ``missing'' value indicators.  Unfortunately, these problems may be difficult to fix because different applications may be written by different programmers, each of whom may use a different set of conventions and date-handling functions.  Here is a simple demonstration illustrating that MySQL Server doesn't have any problems with dates until the year 2030: mysql> DROP TABLE IF EXISTS y2k; Query OK, 0 rows affected (0.01 sec)  mysql> CREATE TABLE y2k (date DATE, ->date_time DATETIME, -> time_stamp TIMESTAMP); Query OK, 0 rows affected (0.00 sec)  mysql> INSERT INTO y2k VALUES -> ("1998-12-31","1998-12-31 23:59:59",19981231235959), -> ("1999-01-01","1999-01-01 00:00:00",19990101000000), -> ("1999-09-09","1999-09-09 23:59:59",19990909235959), -> ("2000-01-01","2000-01-01 00:00:00",20000101000000), -> ("2000-02-28","2000-02-28 00:00:00",20000228000000), -> ("2000-02-29","2000-02-29 00:00:00",20000229000000), -> ("2000-03-01","2000-03-01 00:00:00",20000301000000), -> ("2000-12-31","2000-12-31 23:59:59",20001231235959), -> ("2001-01-01","2001-01-01 00:00:00",20010101000000), -> ("2004-12-31","2004-12-31 23:59:59",20041231235959), -> ("2005-01-01","2005-01-01 00:00:00",20050101000000), -> ("2030-01-01","2030-01-01 00:00:00",20300101000000), -> ("2050-01-01","2050-01-01 00:00:00",20500101000000); Query OK, 13 rows affected (0.01 sec) Records: 13 Duplicates: 0 Warnings: 0 mysql> SELECT * FROM y2k; +------------+---------------------+----------------+ MySQL Reference Manual for version 4.0.3-beta. (p10 | date | date_time | time_stamp | +------------+---------------------+----------------+ | 1998-12-31 | 1998-12-31 23:59:59 | 19981231235959 | | 1999-01-01 | 1999-01-01 00:00:00 | 19990101000000 | | 1999-09-09 | 1999-09-09 23:59:59 | 19990909235959 | | 2000-01-01 | 2000-01-01 00:00:00 | 20000101000000 | | 2000-02-28 | 2000-02-28 00:00:00 | 20000228000000 | | 2000-02-29 | 2000-02-29 00:00:00 | 20000229000000 | | 2000-03-01 | 2000-03-01 00:00:00 | 20000301000000 | | 2000-12-31 | 2000-12-31 23:59:59 | 20001231235959 | | 2001-01-01 | 2001-01-01 00:00:00 | 20010101000000 | | 2004-12-31 | 2004-12-31 23:59:59 | 20041231235959 | | 2005-01-01 | 2005-01-01 00:00:00 | 20050101000000 | | 2030-01-01 | 2030-01-01 00:00:00 | 20300101000000 | | 2050-01-01 | 2050-01-01 00:00:00 | 00000000000000 | +------------+---------------------+----------------+ 13 rows in set (0.00 sec)  This shows that the DATE and DATETIME types will not give any problems with future dates (they handle dates until the year 9999).  The TIMESTAMP type, which is used to store the current time, has a range up to only 2030-01-01. TIMESTAMP has a range of 1970 to 2030 on 32-bit machines (signed value). On 64-bit machines it handles times up to 2106 (unsigned value).  Even though MySQL Server is Y2K-compliant, it is your responsibility to provide unambiguous input. See section 6.2.2.1 Y2K Issues and Date Types for MySQL Server's rules for dealing with ambiguous date input data (data containing 2-digit year values).  1.3 What Is MySQL AB?  MySQL AB is the company of the MySQL founders and main developers. MySQL AB was originally established in Sweden by David Axmark, Allan Larsson, and Michael Monty Widenius.  All the developers of the MySQL server are employed by the company. We are a virtual organisation with people in a dozen countries around the world. We communicate extensively over the Net every day with each other and with our users, supporters and partners.  We are dedicated to developing the MySQL software and spreading our database to new users. MySQL AB owns the copyright to the MySQL source code, the MySQL logo and trademark, and this manual. See section 1.2 What Is MySQL?.  The MySQL core values show our dedication to MySQL and Open Source. We want the MySQL Database Software to be: * The best and the most widely used database in the world. 6.2.2.1 Y2K Issues and Date Types1 * Available and affordable for all. * Easy to use. * Continuously improving while remaining fast and safe. * Fun to use and improve. * Free from bugs.  MySQL AB and the people at MySQL AB: * Promote Open Source philosophy and support the Open Source community. * Aim to be good citizens. * Prefer partners that share our values and mind-set. * Answer e-mail and provide support. * Are a virtual company, networking with others. * Work against software patents.  The MySQL web site (http://www.mysql.com/) provides the latest information about MySQL and MySQL AB.  1.3.1 The Business Model and Services of MySQL AB One of the most common questions we encounter is: ``How can you make a living from something you give away for free?'' This is how. MySQL AB makes money on support, services, commercial licenses, and royalties, and we use these revenues to fund product development and to expand the MySQL business.  The company has been profitable since its inception. In October 2001, we accepted venture financing from leading Scandinavian investors and a handful of business angels. This investment is used to solidify our business model and build a basis for sustainable growth.  1.3.1.1 Support  MySQL AB is run and owned by the founders and main developers of the MySQL database. The developers are committed to giving support to customers and other users in order to stay in touch with their needs and problems. All our support is given by qualified developers. Really tricky questions are answered by Michael Monty Widenius, principal author of the MySQL Server. See section 1.4.1 Support Offered by MySQL AB.  For more information and ordering support at various levels, see http://www.mysql.com/support/ or contact our sales staff at sales@mysql.com.  1.3.1.2 Training and Certification  MySQL AB delivers MySQL and related training worldwide. We offer both open courses and in-house courses tailored to the specific needs of your company. MySQL Training is also available through our partners, the Authorised MySQL Training Centers.  Our training material uses the same example databases as our documentation and our sample applications, http://www.mysql.com/2 and it is always updated to reflect the latest MySQL version. Our trainers are backed by the development team to guarantee the quality of the training and the continuous development of the course material. This also ensures that no questions raised during the courses remain unanswered.  Attending our training courses will enable you to achieve your goals related to your MySQL applications. You will also: * Save time. Improve the performance of your application(s). Reduce or eliminate the need for additional hardware, decreasing cost. Enhance security. Increase customers' and co-workers' satisfaction. Prepare yourself for MySQL Certification.  If you are interested in our training as a potential participant or as a training partner, please visit the training section at http://www.mysql.com/training/ or contact us at: training@mysql.com. The MySQL Certification Program is being released in the second half of 2002. For details please see http://www.mysql.com/training/certification.html.  1.3.1.3 Consulting and its Authorised Partners offer consulting services to users of MySQL Server and to those who embed MySQL Server in their own software, all over the world Our consultants can help you design and tune your databases, construct efficient queries, tune your platform for optimal performance, resolve migration issues, set up replication, build robust transactional applications, and more. We also help customers embed MySQL Server in their products and applications for large-scale deployment.  Our consultants work in close collaboration with our development team, which ensures the technical quality of our professional services. Consulting assignments range from 2-day power-start sessions to projects that span weeks and months. Our expertise not only covers MySQL Server, but also extends into gramming and scripting languages such as PHP, Perl, and more.  If you are interested in our consulting services or want to become a consulting partner, please visit the consulting section of our web site at http://www.mysql.com/consulting/ or contact our consulting staff at consulting@mysql.com.  1.3.1.4 Commercial Licenses  The MySQL database is released under the GNU General Public License (GPL). This means that the MySQL software can be used free of charge under the GPL. If you do not want to be bound by the GPL terms (like he requirement that your own application becomes GPL as well), you may purchase a commercial license for the same product from MySQL AB. See http://www.mysql.com/support/arrangements/price.html. Since MySQL AB owns the copyright to the MySQL source code, we are able to employ Dual Licensing which means that the same product is available under GPL and under a commercial license. This does not in any way http://www.mysql.com/training/3 ffect the Open Source commitment of MySQL AB. For details about when a commercial license is required, please see section 1.4.3 MySQL Licenses.  We also sell commercial licenses of third-party Open Source GPL software that adds value to MySQL Server. A good example is the InnoDB transactional table handler that offers ACID support, row-level locking, crash recovery, multi-versioning, foreign key support, and more. See section 7.5 InnoDB Tables.  1.3.1.5 Partnering  MySQL AB has a worldwide partner programme that covers training courses, consulting & support, publications plus reselling and distributing MySQL and related products. MySQL AB Partners get visibility on the http://www.mysql.com/ web site and the right to use special versions of the MySQL trademarks to identify their products and promote their business.  If you are interested in becoming a MySQL AB Partner, please e-mail partner@mysql.com. word MySQL and the MySQL dolphin logo are trademarks of MySQL AB. See section 1.4.4 MySQL AB Logos and Trademarks. These trademarks represent a significant value that the MySQL founders have built over the years.  1.3.1.6 Advertising  The MySQL web site (http://www.mysql.com/) is popular among developers and users. In October 2001, we served 10 million page views. Our visitors represent a group that makes purchase decisions and recommendations for both software and hardware. Twelve percent of our visitors authorise purchase decisions, and only nine percent are not involved in purchase decisions at all. More than 65% have made one or more online business purchase within the last half-year, and 70% plan to make one in the next months. If you are interested in placing banner ads on our web site, http://www.mysql.com/, please send an e-mail message to advertising@mysql.com.  1.3.2 Contact Information The MySQL web site (http://www.mysql.com/) provides the latest information about MySQL and MySQL AB.  For press service and inquiries not covered in our News releases (http://www.mysql.com/news/), please send e-mail to press@mysql.com.  If you have a valid support contract with MySQL AB, you will get timely, precise answers to your technical questions about the MySQL software. For more information, see section 1.4.1 Support Offered by MySQL AB. On our website, see http://www.mysql.com/support/, or send an e-mail message to sales@mysql.com.  For information about MySQL training, please visit the training section at http://www.mysql.com/training/. If you have restricted access to the Internet, please contact the MySQL 1.4.3 MySQL Licenses4 AB training staff at training@mysql.com. See section 1.3.1.2 Training and Certification.  For information on the MySQL Certification Program, please see http://www.mysql.com/training/certification.html. See section 1.3.1.2 Training and Certification.  If you're interested in consulting, please visit the consulting section at http://www.mysql.com/consulting/. If you have restricted access to the Internet, please contact the MySQL AB consulting staff at consulting@mysql.com. See section 1.3.1.3 Consulting. Commercial licenses may be purchased online at https://order.mysql.com/. There you will also find information on how to fax your purchase order to MySQL AB. More information about licensing can be found at http://www.mysql.com/support/arrangements/price.html. If you have questions regarding licensing or you want a quote for a high-volume license deal, please fill in the contact form on our web site (http://www.mysql.com/) or send an e-mail message to licensing@mysql.com (for licensing questions) or to sales@mysql.com (for sales inquiries). See section 1.4.3 MySQL Licenses. If you represent a business that is interested in partnering with MySQL AB, please send e-mail to partner@mysql.com. See section 1.3.1.5 Partnering.  If you are interested in placing a banner advertisement on the MySQL web site (http://www.mysql.com/), please send e-mail to advertising@mysql.com. See section 1.3.1.6 Advertising. For more information on the MySQL trademark policy, refer to http://www.mysql.com/company/trademark.html or send e-mail to trademark@mysql.com. See section 1.4.4 MySQL AB Logos and Trademarks.  If you are interested in any of the MySQL AB jobs listed in our jobs section (http://www.mysql.com/company/jobs/), please send an e-mail message to jobs@mysql.com. Please do no send your CV as an attachment, but rather as plain text at the end of your e-mail message. For general discussion among our many users, please direct your attention to the appropriate mailing list. See section 1.6.2 MySQL Mailing Lists. Reports of errors (often called bugs), as well as questions and comments, should be sent to the mailing list at mysql@lists.mysql.com. If you have found a sensitive security bug in the MySQL Server, please send an e-mail to security@mysql.com. See section 1.6.2.3 How to Report Bugs or Problems. If you have benchmark results that we can publish, please contact us at benchmarks@mysql.com.  If you have any suggestions concerning additions or corrections to this manual, please send them to the manual team at docs@mysql.com.  For questions or comments about the workings or content of the MySQL web site (http://www.mysql.com/), please send e-mail to webmaster@mysql.com. Questions about the MySQL Portals (http://www.mysql.com/portal/) may be sent to portals@mysql.com.  training@mysql.com5 MySQL AB has a privacy policy, which can be read at http://www.mysql.com/company/privacy.html. For any queries regarding this policy, please e-mail privacy@mysql.com.  For all other inquires, please send e-mail to info@mysql.com. 1.4 MySQL Support and Licensing  This section describes MySQL support and licensing arrangements. 1.4.1 Support Offered by MySQL AB  Technical support from MySQL AB means individualised answers to your unique problems direct from the software engineers who code the MySQL database engine.  We try to take a broad and inclusive view of technical support. Almost any problem involving MySQL software is important to us if it's important to you. Typically customers seek help on how to get different commands and utilities to work, remove performance bottlenecks, restore crashed systems, understand operating system or networking impacts on MySQL, set up best practices for backup and recovery, utilise APIs, etc. Our support covers only the MySQL server and our own utilities, not third-party products that access the MySQL server, though we try to help with these where we can.  Detailed information about our various support options is given at http://www.mysql.com/support/, where support contracts can also be ordered online. If you have restricted access to the Internet, contact our sales staff at sales@mysql.com. Technical support is like life insurance. You can live happily without it for years, but when your hour arrives it becomes critically important, yet it's too late to buy it! If you use MySQL Server for important applications and encounter sudden troubles, it might take too long to figure out all the answers yourself. You may need immediate access to the most experienced MySQL troubleshooters available, those employed by MySQL AB.  1.4.2 Copyrights and Licenses Used by MySQL  MySQL AB owns the copyright to the MySQL source code, the MySQL logos and trademarks and this manual. See section 1.3 What Is MySQL AB?. Several different licenses are relevant to the MySQL distribution: 1. All the MySQL-specific source in the server, the mysqlclient library and the client, as well as the GNU readline library is covered by the GNU General Public License. See section H GNU General Public License. The text of this license can also be found as the file `COPYING' in the distributions. 2. The GNU getopt library is covered by the GNU Lesser General Public License. See section I GNU Lesser  General Public License. 3. Some parts of the source (the regexp library) are covered by a Berkeley-style copyright. 4. Older versions of MySQL (3.22 and earlier) are subject to a more strict license (http://www.mysql.com/support/arrangements/mypl.html). See the documentation of the specific version for information. 5. The manual is currently not distributed under a GPL-style license. Use of the manual is subject to the following terms:  http://www.mysql.com/company/privacy.html6 + Conversion to other formats is allowed, but the actual content may not be altered or edited in any way.+ You may create a printed copy for your own personal use. + For all other uses, such as selling printed copies or using (parts of) the manual in anotherpublication, prior written agreement from MySQL AB is required. Please e-mail docs@mysql.com for more information or if you are interested in doing a translation. For information about how the MySQL licenses work in practice, please refer to section 1.4.3 MySQL Licenses. Also see section 1.4.4 MySQL AB Logos and Trademarks.  1.4.3 MySQL Licenses  The MySQL software is released under the GNU General Public License (GPL), which probably is the best known Open Source license. The formal terms of the GPL license can be found at http://www.gnu.org/licenses/. See also http://www.gnu.org/licenses/gpl-faq.html and http://www.gnu.org/philosophy/enforcing-gpl.html.  Since the MySQL software is released under the GPL, it may often be used for free, but for certain uses you may want or need to buy commercial licenses from MySQL AB at https://order.mysql.com/. See http://www.mysql.com/support/arrangements.html for more information. Older versions of MySQL (3.22 and earlier) are subject to a more strict license (http://www.mysql.com/support/arrangements/mypl.html). See the documentation of the specific version fo information. Please note that the use of the MySQL software under commercial license, GPL, or the old MySQL license does not automatically give you the right to use MySQL AB trademarks. See section 1.4.4 MySQL AB Logos and Trademarks.  1.4.3.1 Using the MySQL Software Under a Commercial License  The GPL license is contagious in the sense that when a program is linked to a GPL program all the source code for all the parts of the resulting product must also be released under the GPL. Otherwise you break the license terms and forfeit your right to use the GPL program altogether and also risk damages.  You need a commercial license: * When you link a program with any GPL code from the MySQL software and don't want the resulting product to be GPL, maybe because you want to build a commercial product or keep the added non-GPL  code closed source for other reasons. When purchasing commercial licenses, you are not using the MySQL software under GPL even though it's the same code.  * When you distribute a non-GPL application that only works with the MySQL software and ship it with  the MySQL software. This type of solution is actually considered to be linking even if it's done over a network. * When you distribute copies of the MySQL software without providing the source code as required under  the GPL license. * When you want to support the further development of the MySQL database even if you don't formally docs@mysql.com7 need a commercial license. Purchasing support directly from MySQL AB is another good way of contributing to the development of the MySQL software, with immediate advantages for you. See section 1.4.1 Support Offered by MySQL AB.  If you require a license, you will need one for each installation of the MySQL software. This covers any number of CPUs on a machine, and there is no artificial limit on the number of clients that connect to the server in any way.  For commercial licenses, please visit our website at http://www.mysql.com/support/arrangements/price.html. For support contracts, see http://www.mysql.com/support/. If you have special needs or you have restricted access to the Internet, please contact our sales staff at sales@mysql.com.  1.4.3.2 Using the MySQL Software for Free Under GPL  You can use the MySQL software for free under the GPL if you adhere to the conditions of the GPL. For more complete coverage of the common questions about the GPL see the generic FAQ from the Free Software Foundation at http://www.gnu.org/licenses/gpl-faq.html. Some common cases: * When you distribute both your own application as well as the MySQL source code under the GPL with your product. * When you distribute the MySQL source code bundled with other programs that are not linked to or dependent on the MySQL system for their functionality even if you sell the distribution commercially. This is called mere aggregation in the GPL license. * If you are not distributing any part of the MySQL system, you can use it for free. * When you are an Internet Service Provider (ISP), offering web hosting with MySQL servers for your customers. However, we do encourage people to use ISPs that have MySQL support, as this will give them the confidence that if they have some problem with the MySQL installation, their ISP will in fact have the resources to solve the problem for them. Note that even if an ISP does not have a commercial license for MySQL Server, they should at least give their customers read access to the  source of the MySQL installation so that the customers can verify that it is patched correctly. * When you use the MySQL Database Software in conjunction with a web server, you do not need a commercial license (so long as it is not a product you distribute). This is true even if you run a commercial web server that uses MySQL Server, because you are not distributing any part of the MySQL system. However, in this case we would like you to purchase MySQL support because the MySQL software is helping your enterprise.  If your use of MySQL database software does not require a commercial license, we encourage you to purchase support from MySQL AB anyway. This way you contribute toward MySQL development and also gain immediate advantages for yourself. See section 1.4.1 Support Offered by MySQL AB.  If you use the MySQL database software in a commercial context such that you profit by its use, we ask that you further the development of the MySQL software by purchasing some level of support. We feel that if the MySQL database helps your business, it is reasonable to ask that you help MySQL AB. (Otherwise, if you ask us support questions, you are not only using for free something into which we've put a lot a work, you're asking us to provide free support, too.)  1.4.1 Support Offered by MySQL AB8 1.4.4 MySQL AB Logos and Trademarks  Many users of the MySQL database want to display the MySQL AB dolphin logo on their web sites, books, or boxed products. We welcome and encourage this, although it should be noted that the word MySQL and the MySQL dolphin logo are trademarks of MySQL AB and may only be used as stated in our trademark policy at http://www.mysql.com/company/trademark.html.  1.4.4.1 The Original MySQL Logo  The MySQL dolphin logo was designed by the Finnish advertising agency Priority in 2001. The dolphin was chosen as a suitable symbol for the MySQL database since it is a smart, fast, and lean animal, effortlessly navigating oceans of data. We also happen to like dolphins. The original MySQL logo may only be used by representatives of MySQL AB and by those having a written agreement allowing them to do so.  1.4.4.2 MySQL Logos that may be Used Without Written Permission  We have designed a set of special Conditional Use logos that may be downloaded from our web site at http://www.mysql.com/press/logos.html and used on third-party web sites without written permission from MySQL AB. The use of these logos is not entirely unrestricted but, as the name implies, subject to our trademark policy that is also available on our web site. You should read through the trademark policy if you plan to use them. The requirements are basically: Use the logo you need as displayed on the http://www.mysql.com/ site. You may scale it to fit your  needs, but not change colours or design, or alter the graphics in any way. * Make it evident that you, and not MySQL AB, are the creator and owner of the site that displays the MySQL trademark. * Don't ustrademark in a way that is detrimental to MySQL AB or to the value of MySQL AB trademarks. We reserve the right to revoke the right to use the MySQL AB trademark. * If you use the trademark on a web site, make it clickable, leading directly to  http://www.mysql.com/. * If you are using the MySQL database under GPL in an application, your application must be Open Source and be able to connect to a MySQL server.  Contact us at trademark@mysql.com to inquire about special arrangements to fit your needs. 1.4.4.3 When do you need a Written Permission to use MySQL Logos?  In the following cases you need a written permission from MySQL AB before using MySQL logos: * When displaying any MySQL AB logo anywhere except on your web site. * When displaying any MySQL AB logo except the Conditional Use logos mentioned previously on web sites or elsewhere.  Out of legal and commercial reasons we have to monitor the use of MySQL trademarks on products, books, etc. We will usually require a fee for displaying MySQL AB logos on commercial products, since we think it is reasonable that some of the revenue is returned to fund further development of the MySQL database.  1.4.4 MySQL AB Logos and Trademarks9  1.4.4.4 MySQL AB Partnership Logos  MySQL partnership logos may only be used by companies and persons having a written partnership agreement with MySQL AB. Partnerships include certification as a MySQL trainer or consultant. Please see section 1.3.1.5 Partnering.5 Using the word MySQL in Printed Text or Presentations MySQL AB welcomes references to the MySQL database, but note that the word MySQL is a trademark of MySQL AB. Because of this, you should append the trademark symbol (TM) to the first or most prominent use of the word MySQL in a text and where appropriate, state that MySQL is a trademark of MySQL AB. Please refer to our trademark policy at http://www.mysql.com/company/trademark.html for details.  1.4.4.6 Using the word MySQL in Company and Product Names Use of the word MySQL in product or company names or in Internet domain names is not allowed without written permission from MySQL AB.  1.5 MySQL 4.x In A Nutshell  Long promised by MySQL AB and long awaited by our users, MySQL Server 4.0 is now available in beta version for download from http://www.mysql.com/ and our mirrors.  Main new features of MySQL Server 4.0 are geared toward our existing business and community users, enhancing the MySQL database software as the solution for mission-critical, heavy-load database systems. Other new features target the users of embedded databases.  1.5.1 Stepwise Rollout  The rollout of MySQL Server 4.x comes in several steps, with the first version labelled 4.0.0-alpha already containing most of the new features. Additional features have since been incorporated into MySQL 4.0.1, 4.0.2, and onward; MySQL 4.0.3 has been labelled beta. Further new features are being added in MySQL 4.1, targeted for alpha release in third quarter 2002.  1.5.2 Ready for Immediate Development Use  Users are not recommended to switch their production systems to a MySQL Server 4.x until it is released in beta version (such as 4.0.3 beta). However, even the initial release has passed our extensive test suite without any errors on any of the platforms we test on. Due to the large number of new features, we thus recommend MySQL Server 4.x even in alpha form for development use, with the release schedule of MySQL Server 4.x being such that it will reach stable state before the deployment of user applications now under development.  1.5.3 Embedded MySQL   1.4.4.4 MySQL AB Partnership Logos20 libmysqld makes MySQL Server suitable for a vastly expanded realm of applications. Using the embedded MySQL server library, one can embed MySQL Server into various applications and electronics devices, where the end user has no knowledge of there actually being an underlying database. Embedded MySQL Server is ideal for use behind the scenes in Internet appliances, public kiosks, turnkey hardware/software combination units, high performance Internet servers, self-contained databases distributed on CD-ROM, etc. Many users of libmysqld will benefit from the MySQL Dual Licensing. For those not wishing to be bound by the GPL, the software is also made available under a commercial license. The embedded MySQL library uses the same interface as the normal client library, so it is convenient and easy to use. See section 8.4.9 libmysqld, the Embedded MySQL Server Library.  1.5.4 Other Features Available From MySQL 4.0  * Version 4.0 further increases the speed of MySQL Server in a number of areas, such as bulk INSERTs, searching on packed indexes, creation of FULLTEXT indexes, as well as COUNT(DISTINCT). * The InnoDB table handler is now offered as a feature of the standard MySQL server, including full support for transactions and row-level locking. * Our German, Austrian, and Swiss users will note that we have a new character set, latin_de, which corrects the German sorting order, placing German umlauts in the same order as German telephone books. * Features to simplify migration from other database systems to MySQL Server include TRUNCATE TABLE (like in Oracle) and IDENTITY as a synonym for automatically incremented keys (like in Sybase). Many users will also be happy to learn that MySQL Server now supports the UNION statement, a long-awaited standard SQL feature. * In the process of building features for new users, we have not forgotten requests by the community of loyal users. We have multi-table DELETE statements. By adding support for symbolic linking to MyISAM on the table level (and not just the database level as before), as well as by enabling symlink handling by default on Windows, we hope to show that we take enhancement requests seriously. Functions like SQL_CALC_FOUND_ROWS and FOUND_ROWS() make it possible to know how many rows a query would have returned without a LIMIT clause.  1.5.5 Future MySQL 4.x Features  For the upcoming MySQL Server 4.x releases, expect the following features now still under development: * Mission-critical, heavy-load users of MySQL Server will appreciate the additions to our replication system and our online hot backup. Later versions of 4.x will include fail-safe replication; already existing in 4.0, the LOAD DATA FROM MASTER command will soon automate slave setup. The online backup will make it easy to add a new replication slave without taking down the master, and have a very low performance penalty on update-heavy systems. * A convenience feature for Database Administrators is that mysqld parameters (startup options) can soon be set without taking down the servers. * The new FULLTEXT search properties of MySQL Server 4.0 enable the use of FULLTEXT indexing of large text masses with both binary and natural-language searching logic. Users can customise minimal word length and define their own stop word lists in any human language, enabling a new set of applications to be built on MySQL Server. 8.4.9 libmysqld, the Embedded MySQL Server Library1 * Many read-heavy applications will benefit from further increased speed through the rewritten key cache. * Many developers will also be happy to see the MySQL command help in the client.  1.5.6 MySQL 4.1, The Following Development Release  MySQL Server 4.0 lays the foundation for the new features of MySQL Server 4.1 and onward, such as nested subqueries, stored procedures, and foreign key integrity rules, which form the top of the wish list for many of our customers. Along with those, we will also include simpler additions, such as multi-table UPDATE statements.  After those additions, critics of the MySQL Database Server have to be more imaginative than ever in pointing out deficiencies in the MySQL Database Management System. For long already known for its stability, speed, and ease of use, MySQL Server will then match the requirement checklist of very demanding buyers.  1.6 MySQL Information Sources  1.6.1 MySQL Portals  The MySQL Portals (http://www.mysql.com/portal/) represent the ultimate resource to find MySQL AB Partners, as well as books, or other MySQL-related solutions that you may be looking for. Items are categorised and rated in order to make it easy for you to locate information.  By registering as a user, you will have the ability to comment on and rate items presented in portals. You will also receive relevant newsletters according to your user profile that you may update at any time.  Some of the current MySQL Portal categories include: Partners  Find MySQL AB partners worldwide. Books  Comment on, vote for, and buy books related to MySQL. Development  Various links to different sites that are using MySQL Server for different purposes, with a  description of each site. This information can give you an idea of who uses the MySQL database  software and how MySQL Server can fulfill requirements. Let us know about your site or success  story, too! Visit http://www.mysql.com/feedback/testimonial.php. Software  Find, buy, and download several applications and wrappers that make use of the MySQL server. Distributions  From here you can find the various Linux distributions and other software packages that contain  the MySQL software. Service Providers  Companies providing MySQL-related services.   1.5.6 MySQL 4.1, The Following Development Release2 1.6.2 MySQL Mailing Lists  This section introduces you to the MySQL mailing lists, and gives some guidelines as to how to use them. By subscribing to a mailing list, you will receive as e-mail messages all other postings on the list, and you will be able to send in your own questions and answers. 1.6.2.1 The MySQL Mailing Lists  To subscribe to the main MySQL mailing list, send a message to the electronic mail address mysql-subscribe@lists.mysql.com. To unsubscribe from the main MySQL mailing list, send a message to the electronic mail address mysql-unsubscribe@lists.mysql.com.  Only the address to which you send your messages is significant. The subject line and the body of the message are ignored.  If your reply address is not valid, you can specify your address explicitly, by adding a hyphen to the subscribe or unsubscribe command word, followed by your address with the `@' character in your address replaced by a `='. For example, to subscribe your_name@host.domain, send a message to mysql-subscribe-your_name=host.domain@lists.mysql.com.  Mail to mysql-subscribe@lists.mysql.com or mysql-unsubscribe@lists.mysql.com is handled automatically by the ezmlm mailing list processor. Information about ezmlm is available at the ezmlm web site (http://www.ezmlm.org/).  To post a message to the list itself, send your message to mysql@lists.mysql.com. However, please do not send mail about subscribing or unsubscribing to mysql@lists.mysql.com because any mail sent to that address is distributed automatically to thousands of other users.  Your local site may have many subscribers to mysql@lists.mysql.com. If so, it may have a local mailing list, so messages sent from lists.mysql.com to your site are propagated to the local list. In such cases, please contact your system administrator to be added to or dropped from the local MySQL list.  If you wish to have traffic for a mailing list go to a separate mailbox in your mail program, set up a filter based on the message headers. You can use either the List-ID: or Delivered-To: headers to identify list messages.  The following MySQL mailing lists exist: announce-subscribe@lists.mysql.com announce This is for announcement of new versions of MySQL and related programs. This is a low-volume listall MySQL users should subscribe to. mysql-subscribe@lists.mysql.com mysql The main list for general MySQL discussion. Please note that some topics are better discussed onthe more-specialised lists. If you post to the wrong list, you may not get an answer! mysql-digest-subscribe@lists.mysql.com mysql-digest  1.6.2 MySQL Mailing Lists3 The mysql list in digest form. That means you get all individual messages, sent as one large mailmessage once a day. bugs-subscribe@lists.mysql.com bugs On this list you should only post a full, repeatable bug report using the mysqlbug script (if you are running on Windows, you should include a description of the operating system and the MySQLversion). Preferably, you should test the problem using the latest stable or development version  of MySQL Server before posting! Anyone should be able to repeat the bug by just using mysql test< script on the included test case. All bugs posted on this list will be corrected or documented in the next MySQL release! If only small code changes are needed, we will also post a patch that fixes the problem. bugs-digest-subscribe@lists.mysql.com bugs-digest The bugs list in digest form. internals-subscribe@lists.mysql.com internalsA list for people who work on the MySQL code. On this list one can also discuss MySQL development and post patches. internals-digest-subscribe@lists.mysql.com internals-digestA digest version of the internals list. java-subscribe@lists.mysql.com java Discussion about the MySQL server and Java. Mostly about the JDBC drivers. java-digest-subscribe@lists.mysql.com java-digest A digest version of the java list. win32-subscribe@lists.mysql.com win32 All things concerning the MySQL software on Microsoft operating systems such as Windows 9x/Me/NT/2000/XP. win32-digest-subscribe@lists.mysql.com win32-digestA digest version of the win32 list. myodbc-subscribe@lists.mysql.com myodbc All things about connecting to the MySQL server with ODBC. myodbc-digest-subscribe@lists.mysql.com myodbc-digest A digest version of the myodbc list. mycc-subscribe@lists.mysql.com mycc All things about the MySQL MyCC graphical client. mycc-digest-subscribe@lists.mysql.com mycc-digestA digest version of the mycc list. plusplus-subscribe@lists.mysql.com plusplus All things concerning programming with the C++ API to MySQL. plusplus-digest-subscribe@lists.mysql.com plusplus-digestA digest version of the plusplus list. msql-mysql-modules-subscribe@lists.mysql.com msql-mysql-modules A list about the Perl support for MySQL with msql-mysql-modules. msql-mysql-modules-digest-subscribe@lists.mysql.com msql-mysql-modules-digestA digest version of the msql-mysql-modules list.  You subscribe or unsubscribe to all lists in the same way as described previously. In your subscribe or unsubscribe message, just put the appropriate mailing list name rather than mysql. For example, to subscribe to or unsubscribe from the myodbc list, send a message to myodbc-subscribe@lists.mysql.com or  bugs-subscribe@lists.mysql.com4 myodbc-unsubscribe@lists.mysql.com.  If you can't get an answer for your questions from the mailing list, one option is to pay for support from MySQL AB, which will put you in direct contact with MySQL developers. See section 1.4.1 Support Offered by MySQL AB.  The following table shows some MySQL mailing in languages other than English. Note that these are not operated by MySQL AB, so we can't guarantee the quality on these. mysql-france-subscribe@yahoogroups.com A French mailing list list@tinc.net A Korean mailing list E-mail subscribe mysql your@e-mail.address to this list. mysql-de-request@lists.4t2.com A German mailing list E-mail subscribe mysql-de your@e-mail.address to this list. You can find information about thismailing list at http://www.4t2.com/mysql/. mysql-br-request@listas.linkway.com.br A Portugese mailing list E-mail subscribe mysql-br your@e-mail.address to this list. mysql-alta@elistas.net A Spanish mailing list E-mail subscribe mysql your@e-mail.address to this list.  1.6.2.2 Asking Questions or Reporting Bugs  Before posting a bug report or question, please do the following: * Start by searching the MySQL online manual at: http://www.mysql.com/doc/  We try to keep the manual up to date by updating it frequently with solutions to newly found problems! * Search the MySQL mailing list archives: http://lists.mysql.com/ * You can also use http://www.mysql.com/search.html to search all the web pages (including the manual) that are located at http://www.mysql.com/.  If you can't find an answer in the manual or the archives, check with your local MySQL expert. If you still can't find an answer to your question, go ahead and read the next section about how to send mail to mysql@lists.mysql.com.  1.6.2.3 How to Report Bugs or Problems  Writing a good bug report takes patience, but doing it right the first time saves time for us and for you. A good bug report containing a full test case for the bug will make it very likely that we will fix it in the next release. This section will help you write your report correctly so that you don't waste your time doing things that may not help us much or at all.  We encourage everyone to use the mysqlbug script to generate a bug report (or a report about any problem), if possible. mysqlbug can be found in the `scripts' directory in the source distribution, or for a binary distribution, in the `bin' directory under your MySQL installation directory. If you are unable to use mysqlbug, you should still include all the necessary information listed in this section.  myodbc-unsubscribe@lists.mysql.com5  The mysqlbug script helps you generate a report by determining much of the following information automatically, but if something important is missing, please include it with your message! Please read this section carefully and make sure that all the information described here is included in your report.  The normal place to report bugs and problems is mysql@lists.mysql.com. If you can make a test case that clearly demonstrates the bug, you should post it to the bugs@lists.mysql.com list. Note that on this list you should only post a full, repeatable bug report using the mysqlbug script. If you are running on Windows, you should include a description of the operating system and the MySQL version. Preferably, you should test the problem using the latest stable or development version of MySQL Server before posting! Anyone should be able to repeat the bug by just using ``mysql test < script'' on the included test case or run the shell or Perl script that is included in the bug report. All bugs posted on the bugs list will be corrected or documented in the next MySQL release! If only small code changes are needed to correct this problem, we will also post a patch that fixes the problem.  If you have found a sensitive security bug in MySQL, you should send an e-mail to security@mysql.com.  Remember that it is possible to respond to a message containing too much information, but not to one containing too little. Often people omit facts because they think they know the cause of a problem and assume that some details don't matter. A good principle is: if you are in doubt about stating something, state it! It is a thousand times faster and less troublesome to write a couple of lines more in your report than to be forced to ask again and wait for the answer because you didn't include enough information the first time.  The most common errors are that people don't indicate the version number of the MySQL distribution they are using, or don't indicate what platform they have the MySQL server installed on (including the platform version number). This is highly relevant information, and in 99 cases out of 100 the bug report is useless without it! Very often we get questions like, ``Why doesn't this work for me?'' Then we find that the feature requested wasn't implemented in that MySQL version, or that a bug described in a report has been fixed already in newer MySQL versions. Sometimes the error is platform-dependent; in such cases, it is next to impossible to fix anything without knowing the operating system and the version number of the platform.  Remember also to provide information about your compiler, if it is related to the problem. Often people find bugs in compilers and think the problem is MySQL-related. Most compilers are under development all the time and become better version by version. To determine whether your problem depends on your compiler, we need to know what compiler is used. Note that every compiling problem should be regarded as a bug report and reported accordingly.  It is most helpful when a good description of the problem is included in the bug report. That is, a good example of all the things you did that led to the problem and the problem itself exactly described. The best reports are those that include a full example showing how to reproduce the bug or problem. See section E.1.6 Making a Test Case When You Experience Table Corruption.  If a program produces an error message, it is very important to include the message in your report! If we try to search for something from the archives using programs, it is better that the error message mysql@lists.mysql.com6 reported exactly matches the one that the program produces. (Even the case should be observed!) You should never try to remember what the error message was; instead, copy and paste the entire message into your report!  If you have a problem with MyODBC, you should try to generate a MyODBC trace file. See section 8.3.7 Reporting Problems with MyODBC.  Please remember that many of the people who will read your report will do so using an 80-column display. hen generating reports or examples using the mysql command-line tool, you should therefore use the --vertical option (or the \G statement terminator) for output that would exceed the available width for such a display (for example, with the EXPLAIN SELECT statement; see the example later in this section).  Please include the following information in your report: * The version number of the MySQL distribution you are using (for example, MySQL Version 3.22.22). You can find out which version you are running by executing mysqladmin version. mysqladmin can be found in the `bin' directory under your MySQL installation directory. * The manufacturer and model of the machine you are working on. * The operating system name and version. For most operating systems, you can get this information by executing the Unix command uname -a. * Sometimes the amount of memory (real and virtual) is relevant. If in doubt, include these values. * If you are using a source distribution of the MySQL software, the name and version number of the compiler used is needed. If you have a binary distribution, the distribution name is needed. * If the problem occurs during compilation, include the exact error message(s) and also a few lines of context around the offending code in the file where the error occurred. * If mysqld died, you should also report the query that crashed mysqld. You can usually find this out by running mysqld with logging enabled. See section E.1.5 Using Log Files to Find Cause of Errors in  mysqld. * If any database table is related to the problem, include the output from mysqldump --no-data db_name tbl_name1 tbl_name2 .... This is very easy to do and is a powerful way to get information about any table in a database that will help us create a situation matching the one you have. * For speed-related bugs or problems with SELECT statements, you should always include the output of EXPLAIN SELECT ..., and at least the number of rows that the SELECT statement produces. The more information you give about your situation, the more likely it is that someone can help you! For example, the following is an example of a very good bug report (it should of course be posted with the mysqlbug script): Example run using the mysql command-line tool (note the use of the \G statement terminator for statements whose output width would otherwise exceed that of an 80-column display device): mysql> SHOW VARIABLES; mysql> SHOW COLUMNS FROM ...\G  mysql> EXPLAIN SELECT ...\G  mysql> FLUSH STATUS; mysql> SELECT ...;  8.3.7 Reporting Problems with MyODBC7 mysql> SHOW STATUS;  * If a bug or problem occurs while running mysqld, try to provide an input script that will reproduce the anomaly. This script should include any necessary source files. The more closely the script can reproduce your situation, the better. If you can make a reproduceable test case, you should post this to bugs@lists.mysql.com for a high-priority treatment! If you can't provide a script, you should at least include the output from mysqladmin variables extended-status processlist in your mail to provide some information of how your system is performing! * If you can't produce a test case in a few rows, or if the test table is too big to be mailed to the mailing list (more than 10 rows), you should dump your tables using mysqldump and create a `README' file that describes your problem. Create a compressed archive of your files using tar and gzip or zip, and use ftp to transfer the archive to ftp://support.mysql.com/pub/mysql/secret/. Then send a short description of the problem to bugs@lists.mysql.com. If you think that the MySQL server produces a strange result from a query, include not only the result, but also your opinion of what the result should be, and an account describing the basis for your opinion. When giving an example of the problem, it's better to use the variable names, table names, etc.,  that exist in your actual situation than to come up with new names. The problem could be related to the name of a variable or table! These cases are rare, perhaps, but it is better to be safe than  sorry. After all, it should be easier for you to provide an example that uses your actual situation,  and it is by all means better for us. In case you have data you don't want to show to others, youan use ftp to transfer it to ftp://support.mysql.com/pub/mysql/secret/. If the data is really top  secret and you don't want to show it even to us, then go ahead and provide an example using other names, but please regard this as the last choice.nclude all the options given to the relevant programs, if possible. For example, indicate the options that you use when you start the mysqld daemon and that you use to run any MySQL client programs. The options to programs like mysqld and mysql, and to the configure script, are often keys  to answers and are very relevant! It is never a bad idea to include them anyway! If you use any modules, such as Perl or PHP, please include the version number(s) of those as well. * If your question is related to the privilege system, please include the output of mysqlaccess, the  output of mysqladmin reload, and all the error messages you get when trying to connect! When you test your privileges, you should first run mysqlaccess. After this, execute mysqladmin reload version and try to connect with the program that gives you trouble. mysqlaccess can be found in the `bin' directory under your MySQL installation directory. * If you have a patch for a bug, that is good. But don't assume the patch is all we need, or that we will use it, if you don't provide some necessary information such as test cases showing the bug that your patch fixes. We might find problems with your patch or we might not understand it at all; if so, we can't use it. If we can't verify exactly what the patch is meant for, we won't use it. Test cases will help us here. Show that the patch will handle all the situations that may occur. If we find a borderline case (even a rare one) where the patch won't work, it may be useless. * Guesses about what the bug is, why it occurs, or what it depends on are usually wrong. Even the MySQL team can't guess such things without first using a debugger to determine the real cause of a bug. * Indicate in your mail message that you have checked the reference manual and mail archive so that others know you have tried to solve the problem yourself. * If you get a parse error, please check your syntax closely! If you can't find something wrong with bugs@lists.mysql.com8 it, it's extremely likely that your current version of MySQL Server doesn't support the query you are using. If you are using the current version and the manual at http://www.mysql.com/doc/ doesn't  cover the syntax you are using, MySQL Server doesn't support your query. In this case, your only options are to implement the syntax yourself or e-mail licensing@mysql.com and ask for an offer to implement it! If the manual covers the syntax you are using, but you have an older version of MySQL Server, you should check the MySQL change history to see when the syntax was implemented. In this case, you have the option of upgrading to a newer version of MySQL Server. See section D MySQL Change History.have a problem such that your data appears corrupt or you get errors when you access some particular table, you should first check and then try repairing your tables with myisamchk or CHECK TABLE and REPAIR TABLE. See section 4 Database Administration. * If you often get corrupted tables you should try to find out when and why this happens. In this case, the `mysql-data-directory/'hostname'.err' file may contain some information about what  happened. See section 4.9.1 The Error Log. Please include any relevant information from this file in your bug report. Normally mysqld should never crash a table if nothing killed it in the middle of an update! If you can find the cause of mysqld dying, it's much easier for us to provide you with a fix  for the problem. See section A.1 How to Determine What Is Causing Problems. * If possible, download and install the most recent version of MySQL Server and check whether it solves your problem. All versions of the MySQL software are thoroughly tested and should work without problems. We believe in making everything as backward-compatible as possible, and you should be able to switch MySQL versions without any hassle. See section 2.2.3 Which MySQL Version to Use.  If you are a support customer, please cross-post the bug report to mysql-support@mysql.com for higher-priority treatment, as well as to the appropriate mailing list to see if someone else has experienced (and perhaps solved) the problem.  For information on reporting bugs in MyODBC, see section 8.3.4 How to Report Problems with MyODBC.  For solutions to some common problems, see section A Problems and Common Errors.  When answers are sent to you individually and not to the mailing list, it is considered good etiquette to summarise the answers and send the summary to the mailing list so that others may have the benefit of responses you received that helped you solve your problem!  1.6.2.4 Guidelines for Answering Questions on the Mailing List  If you consider your answer to have broad interest, you may want to post it to the mailing list instead of replying directly to the individual who asked. Try to make your answer general enough that people other than the original poster may benefit from it. When you post to the list, please make sure that your answer is not a duplication of a previous answer.  Try to summarise the essential part of the question in your reply; don't feel obliged to quote the entire original message.  Please don't post mail messages from your browser with HTML mode turned on! Many users don't read mail with a browser!  http://www.mysql.com/doc/9  1.7 How Standards-compatible Is MySQL?  This section describes how MySQL relates to the ANSI SQL standards. MySQL Server has many extensions to the ANSI SQL standards, and here you will find out what they are and how to use them. You will also find information about functionality missing from MySQL Server, and how to work around some differences.  Our goal is to not, without a very good reason, restrict MySQL Server usability for any usage. Even if we don't have the resources to do development for every possible use, we are always willing to help and offer suggestions to people who are trying to use MySQL Server in new territories.  One of our main goals with the product is to continue to work toward ANSI 99 compliancy, but without sacrificing speed or reliability. We are not afraid to add extensions to SQL or support for non-SQL features if this greatly increases the usability of MySQL Server for a big part of our users. (The new HANDLER interface in MySQL Server 4.0 is an example of this strategy. See section 6.4.2 HANDLER Syntax.)  We will continue to support transactional and non-transactional databases to satisfy both heavy web/logging usage and mission-critical 24/7 usage.  MySQL Server was designed from the start to work with medium size databases (10-100 million rows, or about 100 MB per table) on small computer systems. We will continue to extend MySQL Server to work even better with terabyte-size databases, as well as to make it possible to compile a reduced MySQL version that is more suitable for hand-held devices and embedded usage. The compact design of the MySQL server makes both of these directions possible without any conflicts in the source tree.  We are currently not targeting realtime support or clustered databases (even if you can already do a lot of things with our replication services). We don't believe that one should have native XML support in the database, but will instead add the XML support our users request from us on the client side. We think it's better to keep the main server code as ``lean and clean'' as possible and instead develop libraries to deal with the complexity on the client side. This is part of the strategy mentioned previously of not sacrificing speed or reliability in the server. 1.7.1 What Standards Does MySQL Follow? Entry-level SQL92. ODBC levels 0-3.51.  We are aiming toward supporting the full ANSI SQL99 standard, but without concessions to speed and quality of the code. 1.7.2 Running MySQL in ANSI Mode  If you start mysqld with the --ansi option, the following behaviour of MySQL Server changes: * || is string concatenation instead of OR. * You can have any number of spaces between a function name and the `('. This forces all function  1.7 How Standards-compatible Is MySQL?30 names to be treated as reserved words. * `"' will be an identifier quote character (like the MySQL Server ``' quote character) and not a string quote character. * REAL will be a synonym for FLOAT instead of a synonym for DOUBLE. * The default transaction isolation level is SERIALIZABLE. See section 6.7.3 SET TRANSACTION Syntax.  This is the same as using --sql-mode=REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES, IGNORE_SPACE,SERIALIZE,ONLY_FULL_GROUP_BY.  1.7.3 MySQL Extensions to ANSI SQL92 MySQL Server includes some extensions that you probably will not find in other SQL databases. Be warned that if you use them, your code will not be portable to other SQL servers. In some cases, you can write code that includes MySQL extensions, but is still portable, by using comments of the form /*! ... */. In this case, MySQL Server will parse and execute the code within the comment as it would any other MySQL statement, but other SQL servers will ignore the extensions. For example: SELECT /*! STRAIGHT_JOIN */ col_name FROM table1,table2 WHERE ...  If you add a version number after the '!', the syntax will be executed only if the MySQL version is equal to or newer than the used version number: CREATE /*!32302 TEMPORARY */ TABLE (a int);  This means that if you have Version 3.23.02 or newer, MySQL Server will use the TEMPORARY keyword.  The following is a list of MySQL extensions: * The field types MEDIUMINT, SET, ENUM, and the different BLOB and TEXT types. * The field attributes AUTO_INCREMENT, BINARY, NULL, UNSIGNED, and ZEROFILL. * All string comparisons are case-insensitive by default, with sort ordering determined by the current character set (ISO-8859-1 Latin1 by default). If you don't like this, you should declare your columns with the BINARY attribute or use the BINARY cast, which causes comparisons to be done according to the ASCII order used on the MySQL server host. * MySQL Server maps each database to a directory under the MySQL data directory, and tables within a database to filenames in the database directory. This has a few implications:+ Database names and table names are case-sensitive in MySQL Server on operating systems that have case-sensitive filenames (like most Unix systems). See section 6.1.3 Case Sensitivity inNames. + Database, table, index, column, or alias names may begin with a digit (but may not consistsolely of digits). + You can use standard system commands to back up, rename, move, delete, and copy tables. For example, to rename a table, rename the `.MYD', `.MYI', and `.frm' files to which the tablecorresponds. * In SQL statements, you can access tables from different databases with the db_name.tbl_name syntax. Some SQL servers provide the same functionality but call this User space. MySQL Server doesn't support tablespaces as in: create table ralph.my_table...IN my_tablespace. LIKE is allowed on numeric columns. Use of INTO OUTFILE and STRAIGHT_JOIN in a SELECT statement. See section 6.4.1 SELECT Syntax. 6.7.3 SET TRANSACTION Syntax1 * The SQL_SMALL_RESULT option in a SELECT statement. EXPLAIN SELECT to get a description on how tables are joined. * Use of index names, indexes on a prefix of a field, and use of INDEX or KEY in a CREATE TABLE  statement. See section 6.5.3 CREATE TABLE Syntax. Use of TEMPORARY or IF NOT EXISTS with CREATE TABLE. * Use of COUNT(DISTINCT list) where list is more than one element. * Use of CHANGE col_name, DROP col_name, or DROP INDEX, IGNORE or RENAME in an ALTER TABLE statement. See section 6.5.4 ALTER TABLE Syntax. * Use of RENAME TABLE. See section 6.5.5 RENAME TABLE Syntax. * Use of multiple ADD, ALTER, DROP, or CHANGE clauses in an ALTER TABLE statement. * Use of DROP TABLE with the keywords IF EXISTS. * You can drop multiple tables with a single DROP TABLE statement. * The LIMIT clause of the DELETE statement. * The DELAYED clause of the INSERT and REPLACE statements. * The LOW_PRIORITY clause of the INSERT, REPLACE, DELETE, and UPDATE statements. * Use of LOAD DATA INFILE. In many cases, this syntax is compatible with Oracle's LOAD DATA INFILE. See section 6.4.9 LOAD DATA INFILE Syntax. * The ANALYZE TABLE, CHECK TABLE, OPTIMIZE TABLE, and REPAIR TABLE statements. * The SHOW statement. See section 4.5.6 SHOW Syntax. * Strings may be enclosed by either `"' or `'', not just by `''. * Use of the escape `\' character. * The SET statement. See section 5.5.6 SET Syntax. * You don't need to name all selected columns in the GROUP BY part. This gives better performance for some very specific, but quite normal queries. See section 6.3.7 Functions for Use with GROUP BY  Clauses. One can specify ASC and DESC with GROUP BY.o make it easier for users who come from other SQL environments, MySQL Server supports aliases for  many functions. For example, all string functions support both ANSI SQL syntax and ODBC syntax. * MySQL Server understands the || and && operators to mean logical OR and AND, as in the C programming language. In MySQL Server, || and OR are synonyms, as are && and AND. Because of this nice syntax, MySQL Server doesn't support the ANSI SQL || operator for string concatenation; use CONCAT()  instead. Because CONCAT() takes any number of arguments, it's easy to convert use of the || operator to MySQL Server. * CREATE DATABASE or DROP DATABASE. See section 6.5.1 CREATE DATABASE Syntax. * The % operator is a synonym for MOD(). That is, N % M is equivalent to MOD(N,M). % is supported for C programmers and for compatibility with PostgreSQL. * The =, <>, <= ,<, >=,>, <<, >>, <=>, AND, OR, or LIKE operators may be used in column comparisons to the left of the FROM in SELECT statements. For example: mysql> SELECT col1=1 AND col2=2 FROM tbl_name; * The LAST_INSERT_ID() function. See section 8.4.3.126 mysql_insert_id(). * The REGEXP and NOT REGEXP extended regular expression operators. CONCAT() or CHAR() with one argument or more than two arguments. (In MySQL Server, these functions can take any number of arguments.) * The BIT_COUNT(), CASE, ELT(), FROM_DAYS(), FORMAT(), IF(), PASSWORD(), ENCRYPT(), MD5(), ENCODE(),  DECODE(), PERIOD_ADD(), PERIOD_DIFF(), TO_DAYS(), or WEEKDAY() functions.TRIM() to trim substrings. ANSI SQL only supports removal of single characters. 6.5.3 CREATE TABLE Syntax2GROUP BY functions STD(), BIT_OR(), and BIT_AND(). Use of REPLACE instead of DELETE + INSERT. See section 6.4.8 REPLACE Syntax. The FLUSH, RESET and DO statements. * The ability to set variables in a statement with :=: SELECT @a:=SUM(total),@b=COUNT(*),@a/@b AS avg FROM test_table; SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;  1.7.4 MySQL Differences Compared to ANSI SQL92  We try to make MySQL Server follow the ANSI SQL standard and the ODBC SQL standard, but in some cases MySQL Server does things differently: For VARCHAR columns, trailing spaces are removed when the value is stored. See section 1.7.5 Known  Errors and Design Deficiencies in MySQL. In some cases, CHAR columns are silently changed to VARCHAR columns. See section 6.5.3.1 Silent  Column Specification Changes. Privileges for a table are not automatically revoked when you delete a table. You must explicitly issue a REVOKE to revoke privileges for a table. See section 4.3.1 GRANT and REVOKE Syntax. NULL AND FALSE will evaluate to NULL and not to FALSE. This is because we don't think it's good to  have to evaluate a lot of extra conditions in this case.  For a prioritised list indicating when new extensions will be added to MySQL Server, you should consult the online MySQL TODO list at http://www.mysql.com/documentation/manual.php?section=TODO. That is the latest version of the TODO list in this manual. See section 1.8 MySQL and The Future (The TODO).  1.7.4.1 SubSELECTs  MySQL Server currently only supports nested queries of the form INSERT ... SELECT ... and REPLACE ... SELECT .... You can, however, use the function IN() in other contexts. Subselects are currently being implemented in the 4.1 development tree.  Meanwhile, you can often rewrite the query without a subselect: SELECT * FROM table1 WHERE id IN (SELECT id FROM table2);  This can be rewritten as: SELECT table1.* FROM table1,table2 WHERE table1.id=table2.id;  The queries: SELECT * FROM table1 WHERE id NOT IN (SELECT id FROM table2); SELECT * FROM table1 WHERE NOT EXISTS (SELECT id FROM table2 WHERE table1.id=table2.id);  Can be rewritten as: SELECT table1.* FROM table1 LEFT JOIN table2 ON table1.id=table2.id WHERE table2.id IS NULL;  For more complicated subqueries you can often create temporary tables to hold the subquery. In some  6.4.8 REPLACE Syntax3 cases, however, this option will not work. The most frequently encountered of these cases arises with DELETE statements, for which standard SQL does not support joins (except in subselects). For this situation there are two options available until subqueries are supported by MySQL Server.  The first option is to use a procedural programming language (such as Perl or PHP) to submit a SELECT query to obtain the primary keys for the records to be deleted, and then use these values to construct the DELETE statement (DELETE FROM ... WHERE ... IN (key1, key2, ...)).  The second option is to use interactive SQL to construct a set of DELETE statements automatically, using the MySQL extension CONCAT() (in lieu of the standard || operator). For example: SELECT CONCAT('DELETE FROM tab1 WHERE pkid = ', "'", tab1.pkid, "'", ';') FROM tab1, tab2 WHERE tab1.col1 = tab2.col2;  You can place this query in a script file and redirect input from it to the mysql command-line interpreter, piping its output back to a second instance of the interpreter: shell> mysql --skip-column-names mydb < myscript.sql | mysql mydb  MySQL Server 4.0 supports multi-table deletes that can be used to efficiently delete rows based on information from one table or even from many tables at the same time.  1.7.4.2 SELECT INTO TABLE  MySQL Server doesn't yet support the Oracle SQL extension: SELECT ... INTO TABLE .... MySQL Server supports instead the ANSI SQL syntax INSERT INTO ... SELECT ..., which is basically the same thing. See section 6.4.3.1 INSERT ... SELECT Syntax. INSERT INTO tblTemp2 (fldID) SELECT tblTemp1.fldOrder_ID FROM tblTemp1 WHERE tblTemp1.fldOrder_ID > 100;  Alternatively, you can use SELECT INTO OUTFILE... or CREATE TABLE ... SELECT.  1.7.4.3 Transactions and Atomic Operations MySQL Server supports transactions with the InnoDB and BDB Transactional table handlers. See section 7  MySQL Table Types. InnoDB provides ACID compliancy. However, the non-transactional table types in MySQL Server such as MyISAM follow another paradigm for data integrity called ``Atomic Operations.'' Atomic operations often offer equal or even better integrity with much better performance. With MySQL Server supporting both paradigms, the user is able to decide if he needs the speed of atomic operations or if he need to use transactional features in his applications. This choice can be made on a per-table basis.  How does one use the features of MySQL Server to maintain rigorous integrity and how do these features compare with the transactional paradigm? 1. In the transactional paradigm, if your applications are written in a way that is dependent on the calling of ROLLBACK instead of COMMIT in critical situations, transactions are more convenient.  1.7.4.2 SELECT INTO TABLE4 Transactions also ensure that unfinished updates or corrupting activities are not committed to the database; the server is given the opportunity to do an automatic rollback and your database is saved. MySQL Server, in almost all cases, allows you to resolve potential problems by including simple checks before updates and by running simple scripts that check the databases for inconsistencies and automatically repair or warn if such an inconsistency occurs. Note that just by using the MySQL log or even adding one extra log, one can normally fix tables perfectly with no data integrity loss. 2. More often than not, fatal transactional updates can be rewritten to be atomic. Generally speaking, all integrity problems that transactions solve can be done with LOCK TABLES or atomic updates, ensuring that you never will get an automatic abort from the database, which is a common problem with transactional databases. 3. Even a transactional system can lose data if the server goes down. The difference between different systems lies in just how small the time-lap is where they could lose data. No system is 100% secure, only ``secure enough.'' Even Oracle, reputed to be the safest of transactional databases, is reported to sometimes lose data in such situations. To be safe with MySQL Server, whether using transactional tables or not, you only need to have backups and have the update logging turned on. With this you can recover from any situation that you could with any other transactional database. It is, of course, always good to have backups, independent of which database you use.  The transactional paradigm has its benefits and its drawbacks. Many users and application developers depend on the ease with which they can code around problems where an abort appears to be, or is necessary. However, even if you are new to the atomic operations paradigm, or more familiar with transactions, do consider the speed benefit that non-transactional tables can offer on the order of three to five times the speed of the fastest and most optimally tuned transactional tables.  In situations where integrity is of highest importance, MySQL Server offers transaction-level or better reliability and integrity even for non-transactional tables. If you lock tables with LOCK TABLES, all updates will stall until any integrity checks are made. If you only obtain a read lock (as opposed to a write lock), reads and inserts are still allowed to happen. The new inserted records will not be seen by any of the clients that have a read lock until they release their read locks. With INSERT DELAYED you can queue inserts into a local queue, until the locks are released, without having the client wait for the insert to complete. See section 6.4.4 INSERT DELAYED Syntax. ``Atomic,'' in the sense that we mean it, is nothing magical. It only means that you can be sure that while each specific update is running, no other user can interfere with it, and there will never be an automatic rollback (which can happen with transactional tables if you are not very careful). MySQL Server also guarantees that there will not be any dirty reads.  Following are some techniques for working with non-transactional tables: * Loops that need transactions normally can be coded with the help of LOCK TABLES, and you don't need cursors when you can update records on the fly. * To avoid using ROLLBACK, you can use the following strategy: 1. Use LOCK TABLES ... to lock all the tables you want to access. 2. Test conditions.  3. Update if everything is okay.  4. Use UNLOCK TABLES to release your locks. 6.4.4 INSERT DELAYED Syntax5his is usually a much faster method than using transactions with possible ROLLBACKs, although not always. The only situation this solution doesn't handle is when someone kills the threads in the middle of an update. In this case, all locks will be released but some of the updates may not have been executed. * You can also use functions to update records in a single operation. You can get a very efficient application by using the following techniques:  + Modify fields relative to their current value.  + Update only those fields that actually have changed. For example, when we are doing updates to some customer information, we update only the customer data that has changed and test only that none of the changed data, or data that depends on the changed data, has changed compared to the original row. The test for changed data is done with the  WHERE clause in the UPDATE statement. If the record wasn't updated, we give the client a message: "Some of the data you have changed has been changed by another user." Then we show the old row versus the new row in a window, so the user can decide which version of the customer record he should use. This gives us something that is similar to column locking but is actually even better because we only update some of the columns, using values that are relative to their current values. This means that typical UPDATE statements look something like these: UPDATE tablename SET pay_back=pay_back+'relative change'; UPDATE customer SET  customer_date='current_date', address='new address', phone='new phone', money_he_owes_us=money_he_owes_us+'new_money' WHERE  customer_id=id AND address='old address' AND phone='old phone'; As you can see, this is very efficient and works even if another client has changed the values in the pay_back or money_he_owes_us columns. * In many cases, users have wanted ROLLBACK and/or LOCK TABLES for the purpose of managing unique identifiers for some tables. This can be handled much more efficiently by using an AUTO_INCREMENT column and either the SQL function LAST_INSERT_ID() or the C API function mysql_insert_id(). See section 8.4.3.126 mysql_insert_id(). You can generally code around row-level locking. Some situations really need it, but they are very few. InnoDB tables support row-level locking. With MyISAM, you can use a flag column in the table and do something like the following: UPDATE tbl_name SET row_flag=1 WHERE id=ID; MySQL returns 1 for the number of affected rows if the row was found and row_flag wasn't already 1 in the original row. You can think of it as though MySQL Server changed the preceding query to: UPDATE tbl_name SET row_flag=1 WHERE id=ID AND row_flag <> 1;  1.7.4.4 Stored Procedures and Triggers  A stored procedure is a set of SQL commands that can be compiled and stored in the server. Once this has been done, clients don't need to keep re-issuing the entire query but can refer to the stored procedure. This provides better performance because the query has to be parsed only once, and less information needs to be sent between the server and the client. You can also raise the conceptual level by having 8.4.3.126 mysql_insert_id()6 libraries of functions in the server.  A trigger is a stored procedure that is invoked when a particular event occurs. For example, you can install a stored procedure that is triggered each time a record is deleted from a transaction table and that automatically deletes the corresponding customer from a customer table when all his transactions are deleted.  The planned update language will be able to handle stored procedures. Our aim is to have stored procedures implemented in MySQL Server around version 5.0. We are also looking at triggers.  1.7.4.5 Foreign Keys  Note that foreign keys in SQL are not used to join tables, but are used mostly for checking referential integrity (foreign key constraints). If you want to get results from multiple tables from a SELECT statement, you do this by joining tables: SELECT * FROM table1,table2 WHERE table1.id = table2.id;  See section 6.4.1.1 JOIN Syntax. See section 3.5.6 Using Foreign Keys. In MySQL Server 3.23.44 and up, InnoDB tables support checking of foreign key constraints. See section 7.5 InnoDB Tables. For other table types, MySQL Server does parse the FOREIGN KEY syntax in CREATE TABLE commands, but without further action being taken.  The FOREIGN KEY syntax without ON DELETE ... is mostly used for documentation purposes. Some ODBC applications may use this to produce automatic WHERE clauses, but this is usually easy to override. FOREIGN KEY is sometimes used as a constraint check, but this check is unnecessary in practice if rows are inserted into the tables in the right order.  In MySQL Server, you can work around the problem of ON DELETE ... not being implemented by adding the appropriate DELETE statement to an application when you delete records from a table that has a foreign key. In practice this is as quick (in some cases quicker) and much more portable than using foreign keys.  In MySQL Server 4.0 you can use multi-table delete to delete rows from many tables with one command. See section 6.4.6 DELETE Syntax.  In the near future we will extend the FOREIGN KEY implementation so that the information will be saved in the table specification file and may be retrieved by mysqldump and ODBC. At a later stage we will implement the foreign key constraints for applications that can't easily be coded to avoid them. Do keep in mind that foreign keys are often misused, which can cause severe problems. Even when used properly, it is not a magic solution for the referential integrity problem, although it does make things easier in some cases.  Some advantages of foreign key enforcement: * Assuming proper design of the relations, foreign key constraints will make it more difficult for a  1.7.4.5 Foreign Keys7 programmer to introduce an inconsistency into the database. * Using cascading updates and deletes can simplify the client code. * Properly designed foreign key rules aid in documenting relations between tables.  Disadvantages: * Mistakes, which are easy to make in designing key relations, can cause severe problems@-for example, circular rules, or the wrong combination of cascading deletes. * A properly written application will make sure internally that it is not violating referential integrity constraints before proceding with a query. Thus, additional checks on the database level will only slow down performance for such an application.  * It is not uncommon for a DBA to make such a complex topology of relations that it becomes very difficult, and in some cases impossible, to back up or restore individual tables.  1.7.4.6 Views  It is planned to implement views in MySQL Server around version 5.0. Views are mostly useful for letting users access a set of relations as one table (in read-only mode). Many SQL databases don't allow one to update any rows in a view, but you have to do the updates in the separate tables.  As MySQL Server is mostly used in applications and on web systems where the application writer has full control on the database usage, most of our users haven't regarded views to be very important. (At least no one has been interested enough in this to be prepared to finance the implementation of views.)  One doesn't need views in MySQL Server to restrict access to columns, as MySQL Server has a very sophisticated privilege system. See section 4.2 General Security Issues and the MySQL Access Privilege System.  1.7.4.7 `--' as the Start of a Comment  Some other SQL databases use `--' to start comments. MySQL Server has `#' as the start comment character. You can also use the C comment style /* this is a comment */ with MySQL Server. See section 6.1.6 Comment Syntax.  MySQL Server Version 3.23.3 and above support the `--' comment style, provided the comment is followed by a space. This is because this comment style has caused many problems with automatically generated SQL queries that have used something like the following code, where we automatically insert the value of the payment for !payment!: UPDATE tbl_name SET credit=credit-!payment!  Think about what happens if the value of payment is negative. Because 1--1 is legal in SQL, the consequences of allowing comments to start with `--' are terrible. Using our implementation of this method of commenting in MySQL Server Version 3.23.3 and up, 1-- This is a comment is actually safe.  1.7.4.6 Views8  Another safe feature is that the mysql command-line client removes all lines that start with `--'.  The following information is relevant only if you are running a MySQL version earlier than 3.23.3:  If you have a SQL program in a text file that contains `--' comments you should use: shell> replace " --" " #" < text-file-with-funny-comments.sql \  | mysql database  instead of the usual: shell> mysql database < text-file-with-funny-comments.sql  You can also edit the command file ``in place'' to change the `--' comments to `#' comments: shell> replace " --" " #" -- text-file-with-funny-comments.sql Change them back with this command: shell> replace " #" " --" -- text-file-with-funny-comments.sql  1.7.5 Known Errors and Design Deficiencies in MySQL  The following problems are known and have a very high priority to get fixed: * ANALYZE TABLE on a BDB table may in some case make the table unusable until one has restarted mysqld. When this happens you will see errors like the following in the MySQL error file: 001207 22:07:56 bdb: log_flush: LSN past current end-of-log * Don't execute ALTER TABLE on a BDB table on which you are running multi-statement transactions until all those transactions complete. (The transaction will probably be ignored.) * ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE may cause problems on tables for which you are using INSERT DELAYED. * Doing a LOCK TABLE ... and FLUSH TABLES ... doesn't guarantee that there isn't a half-finished  transaction in progress on the table. * BDB tables are a bit slow to open. If you have many BDB tables in a database, it will take a long time to use the mysql client on the database if you are not using the -A option or if you are using rehash. This is especially notable when you have a big table cache. * The current replication protocol cannot deal with LOAD DATA INFILE and line terminator characters of more than 1 character.  The following problems are known and will be fixed in due time: * When using SET CHARACTER SET, one can't use translated characters in database, table, and column names. * If you have a DECIMAL column with a number stored in different formats (+01.00, 1.00, 01.00), GROUP BY may regard each value as a different value. * DELETE FROM merge_table used without a WHERE will only clear the mapping for the table, not delete everything in the mapped tables. * You cannot build the server in another directory when using MIT-pthreads. Because this requires changes to MIT-pthreads, we are not likely to fix this. See section 2.3.6 MIT-pthreads Notes. * BLOB values can't ``reliably'' be used in GROUP BY or ORDER BY or DISTINCT. Only the first  1.7.5 Known Errors and Design Deficiencies in MySQL9 max_sort_length bytes (default 1024) are used when comparing BLOBs in these cases. This can be changed with the -O max_sort_length option to mysqld. A workaround for most cases is to use a substring: SELECT DISTINCT LEFT(blob,2048) FROM tbl_name. * Calculation is done with BIGINT or DOUBLE (both are normally 64 bits long). It depends on the function which precision one gets. The general rule is that bit functions are done with BIGINT precision, IF, and ELT() with BIGINT or DOUBLE precision and the rest with DOUBLE precision. One should try to avoid using unsigned long long values if they resolve to be bigger than 63 bits (9223372036854775807) for anything else than bit fields! MySQL Server 4.0 has better BIGINT handling than 3.23. * All string columns, except BLOB and TEXT columns, automatically have all trailing spaces removed when retrieved. For CHAR types this is okay, and may be regarded as a feature according to ANSI SQL92. The bug is that in MySQL Server, VARCHAR columns are treated the same way. * You can only have up to 255 ENUM and SET columns in one table. * safe_mysqld redirects all messages from mysqld to the mysqld log. One problem with this is that if you execute mysqladmin refresh to close and reopen the log, stdout and stderr are still redirected to the old log. If you use --log extensively, you should edit safe_mysqld to log to `'hostname'.err' instead of `'hostname'.log' so you can easily reclaim the space for the old log by deleting the old one and executing mysqladmin refresh. * In the UPDATE statement, columns are updated from left to right. If you refer to an updated column, you will get the updated value instead of the original value. For example: mysql> UPDATE tbl_name SET KEY=KEY+1,KEY=KEY+1;  This will update KEY with 2 instead of with 1. * You can't use temporary tables more than once in the same query. For example, the following doesn't work: mysql> SELECT * FROM temporary_table, temporary_table AS t2; * RENAME doesn't work with TEMPORARY tables or tables used in a MERGE table. The optimiser may handle DISTINCT differently if you are using 'hidden' columns in a join or not. In a join, hidden columns are counted as part of the result (even if they are not shown) while in  normal queries hidden columns don't participate in the DISTINCT comparison. We will probably changehis in the future to never compare the hidden columns when executing DISTINCT. An example of this  is: SELECT DISTINCT mp3id FROM band_downloads WHERE userid = 9 ORDER BY id DESC;  and SELECT DISTINCT band_downloads.mp3id FROM band_downloads,band_mp3 WHERE band_downloads.userid = 9  AND band_mp3.id = band_downloads.mp3id ORDER BY band_downloads.id DESC;  In the second case you may in MySQL Server 3.23.x get two identical rows in the result set (because the hidden id column may differ). Note that this happens only for queries where you don't have the  ORDER BY columns in the result, something that you are not allowed to do in ANSI SQL. * Because MySQL Server allows you to work with table types that don't support transactions, and thus  can't rollback data, some things behave a little differently in MySQL Server than in other SQL servers. This is just to ensure that MySQL Server never needs to do a rollback for a SQL command.  This may be a little awkward at times as column values must be checked in the application, but this 40 will actually give you a nice speed increase as it allows MySQL Server to do some optimisations that otherwise would be very hard to do. If you set a column to an incorrect value, MySQL Server will, instead of doing a rollback, store the best possible value in the column:  + If you try to store a value outside the range in a numerical column, MySQL Server will instead  store the smallest or biggest possible value in the column.  + If you try to store a string that doesn't start with a number into a numerical column, MySQL  Server will store 0 into it.  + If you try to store NULL into a column that doesn't take NULL values, MySQL Server will store 0  or '' (empty string) in it instead. (This behaviour can, however, be changed with the  -DDONT_USE_DEFAULT_FIELDS compile option.)  + MySQL allows you to store some wrong date values into DATE and DATETIME columns (like  2000-02-31 or 2000-02-00). The idea is that it's not the SQL server job to validate date. If  MySQL can store a date and retrieve exactly the same date, then MySQL will store the date. If  the date is totally wrong (outside the server's ability to store it), then the special date  value 0000-00-00 will be stored in the column.  + If you set an ENUM column to an unsupported value, it will be set to the error value empty  string, with numeric value 0.  + If you set a SET column to an unsupported value, the value will be ignored.f you execute a PROCEDURE on a query that returns an empty set, in some cases the PROCEDURE will not transform the columns. * Creation of a table of type MERGE doesn't check if the underlying tables are of compatible types. * MySQL Server can't yet handle NaN, -Inf, and Inf values in double. Using these will cause problems  when trying to export and import data. We should as an intermediate solution change NaN to NULL (if possible) and -Inf and Inf to the minimum respective maximum possible double value. * LIMIT on negative numbers are treated as big positive numbers. If you use ALTER TABLE to first add a UNIQUE index to a table used in a MERGE table and then use  ALTER TABLE to add a normal index on the MERGE table, the key order will be different for the tables if there was an old key that was not unique in the table. This is because ALTER TABLE puts UNIQUE keys before normal keys to be able to detect duplicate keys as early as possible.  The following are known bugs in earlier versions of MySQL: * You can get a hung thread if you do a DROP TABLE on a table that is one among many tables that is locked with LOCK TABLES. * In the following case you can get a core dump: + Delayed insert handler has pending inserts to a table.  + LOCK table with WRITE.  + FLUSH TABLES. * Before MySQL Server Version 3.23.2 an UPDATE that updated a key with a WHERE on the same key may have failed because the key was used to search for records and the same row may have been found multiple times: UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100; A workaround is to use: mysql> UPDATE tbl_name SET KEY=KEY+1 WHERE KEY+0 > 100; This will work because MySQL Server will not use an index on expressions in the WHERE clause. * Before MySQL Server Version 3.23, all numeric types where treated as fixed-point fields. That means you had to specify how many decimals a floating-point field shall have. All results were returned 1th the correct number of decimals.  For platform-specific bugs, see the sections about compiling and porting.  1.8 MySQL and The Future (The TODO)  This section lists the features that we plan to implement in MySQL Server.  Everything in this list is approximately in the order it will be done. If you want to affect the priority order, please register a license or support us and tell us what you want to have done more quickly. See section 1.4 MySQL Support and Licensing.  The plan is that we in the future will support the full ANSI SQL99 standard, but with a lot of useful extensions. The challenge is to do this without sacrificing the speed or compromising the code.  1.8.1 Things That Should be in 4.0  All done. We now only do bug fixes for MySQL 4.0. See section D.1 Changes in release 4.0.x (Beta). Development has shifted to 4.1  1.8.2 Things That Should be in 4.1  The following features are planned for inclusion into MySQL 4.1. Note that because we have many developers that are working on different projects, there will also be many additional features. There is also a small chance that some of these features will be added to MySQL 4.0. Some of the work on MySQL 4.1 is already in progress. * Subqueries. SELECT id FROM t WHERE grp IN (SELECT grp FROM g WHERE u > 100); * New table definition file format (`.frm' files). This will enable us to not run out of bits when adding more table options. One will still be able to use the old `.frm' file format with 4.0. All newly created tables will, however, use the new format. The new file format will enable us to add  new column types, more options for keys, and possibly to store and retrieve FOREIGN KEY definitions. * SHOW COLUMNS FROM table_name (used by mysql client to allow expansions of column names) should not  open the table, only the definition file. This will require less memory and be much faster. * Foreign keys for MyISAM tables, including cascading delet * Fail-safe replication. * Replication should work with RAND() and user variables @var. Online backup with very low performance penalty. The online backup will make it easy to add a new replication slave without taking down the master. * Derived tabl SELECT a.col1, b.col2 FROM (SELECT MAX(col1) AS col1 FROM root_table) a, other_table b WHERE a.col1=b.col1;  This could be done by automatically creating temporary tables for the derived tables for the duration of the query. 1.8 MySQL and The Future (The TODO)2 * ROLLUP and CUBE OLAP (Online Analytical Processing) grouping options for data warehousing applications. * Allow DELETE on MyISAM tables to use the record cache. To do this, we need to update the threads record cache when we update the `.MYD' file. * When using SET CHARACTER SET we should translate the whole query at once and not only strings. This will enable users to use the translated characters in database, table, and column names. * Add record_in_range() method to MERGE tables to be able to choose the right index when there are many to choose from. We should also extend the info interface to get the key distribution for each index, if analyze is run on all subtables. * Resolving the issue of RENAME TABLE on a table used in an active MERGE table possibly corrupting the table. * A faster, smaller embedded MySQL library (compatible with the old one). * Stable OpenSSL support (MySQL 4.0 supports rudimentary, not 100% tested, support for OpenSSL). * Add support for sorting on UNICODE. * Character set casts and syntax for handling multiple character sets. * Help for all commands from the client. * New faster client/server protocol which will support prepared statements, bound parameters, and bound result columns, binary transfer of data, warnings... * Add database and real table name (in case of alias) to the MYSQL_FIELD structure. * Add options to the client/server protocol to get progress notes for long running commands. * Implement RENAME DATABASE. To make this safe for all table handlers, it should work as follows:+ Create the new database. + For every table do a rename of the table to another database, as we do with the RENAME command. + Drop the old database. * Add true VARCHAR support (there is already support for this in MyISAM). * Optimise BIT type to take 1 bit (now BIT takes 1 char). New internal file interface change. This will make all file handling much more general and make it easier to add extensions like RAID. (the current implementation is a hack.) Better in-memory (HEAP) tables:  + Support for B-tree indexes  + Dynamic size rows  + Faster row handling (less copying)  1.8.3 Things That Must be Done in the Near Future  Atomic multi-table updates: UPDATE items,month SET items.price=month.price WHERE items.id=month.id; * Don't allow more than a defined number of threads to run MyISAM recover at the same time. Change INSERT ... SELECT to optionally use concurrent inserts. * Return the original field types() when doing SELECT MIN(column) ... GROUP BY. * Multiple result sets. * Make it possible to specify long_query_time with a granularity in microseconds. * Link the myisampack code into the server. * Port of the MySQL code to QNX. * Port of the MySQL code to BeOS.  1.8.3 Things That Must be Done in the Near Future3 Port of the MySQL clients to LynxOS. * Add a temporary key buffer cache during INSERT/DELETE/UPDATE so that we can gracefully recover if  the index file gets full. * If you perform an ALTER TABLE on a table that is symlinked to another disk, create temporary tables  on this disk. * Implement a DATE/DATETIME type that handles time zone information properly so that dealing with  dates in different time zones is easier. * FreeBSD and MIT-pthreads; do sleeping threads take CPU time? * Check if locked threads take any CPU time Fix configure so that one can compile all libraries (like MyISAM) without threads. * Add an option to periodically flush key pages for tables with delayed keys if they haven't been used  in a while. Allow join on key parts (optimisation issue). INSERT SQL_CONCURRENT and mysqld --concurrent-insert to do a concurrent insert at the end of the  file if the file is read-locked. Server-side cursors. Check if lockd works with modern Linux kernels; if not, we have to fix lockd! To test this, start mysqld with --enable-locking and run the different fork* test suits. They shouldn't give any errors  if lockd works.llow SQL variables in LIMIT, like in LIMIT @a,@b. Allow update of variables in UPDATE statements. For example: UPDATE TABLE foo SET @a=a+b,a=@a, b=@a+c. * Change when user variables are updated so that one can use them with GROUP BY, as in the following example: SELECT id, @a:=COUNT(*), SUM(sum_col)/@a FROM table_name GROUP BY id. Don't add automatic DEFAULT values to columns. Give an error when using an INSERT that doesn't  contain a column that doesn't have a DEFAULT. Fix `libmysql.c' to allow two mysql_query() commands in a row without reading results or give a nicerror message when one does this. Check why MIT-pthreads ctime() doesn't work on some FreeBSD systems. * Add an IMAGE option to LOAD DATA INFILE to not update TIMESTAMP and AUTO_INCREMENT fields. * Added LOAD DATE INFILE ... UPDATE syntax.or tables with primary keys, if the data contains the primary key, entries matching thatprimary key are updated from the remainder of the columns. However, columns missing from the incoming data feed are not touched. + For tables with primary keys that are missing some part of the key in the incoming data stream,  or that have no primary key, the feed is treated as a LOAD DATA INFILE ... REPLACE INTO now. * Make LOAD DATA INFILE understand syntax like: LOAD DATA INFILE 'file_name.txt' INTO TABLE tbl_name TEXT_FIELDS (text_field1, text_field2, text_field3) SET table_field1=CONCAT(text_field1, text_field2),  table_field3=23 IGNORE text_field3  This can be used to skip over extra columns in the text file, or update columns based on expressions  of the read data. LOAD DATA INFILE 'file_name' INTO TABLE 'table_name' ERRORS TO err_table_name. This would cause any  errors and warnings to be logged into the err_table_name table. That table would have a structure 4  like: line_number - line number in datafile error_message - the error/warning message and maybe data_line - the line from the datafile Automatic output from mysql to Netscape. * LOCK DATABASES (with various options.) unctions: ADD_TO_SET(value,set) and REMOVE_FROM_SET(value,set). Add use of t1 JOIN t2 ON ... and t1 JOIN t2 USING ... Currently, you can only use this syntax with  LEFT JOIN. Many more variables for show status. Records reads and updates. Selects on 1 table and selects with joins. Mean number of tables in select. Number of ORDER BY and GROUP BY queries. If you abort mysql in the middle of a query, you should open another connection and kill the old  running query. Alternatively, an attempt should be made to detect this in the server. * Add a handler interface for table information so that you can use it as a system table. This would  be a bit slow if you requested information about all tables, but very flexible. SHOW INFO FROM  tbl_name for basic table information should be implemented. * NATURAL JOIN. * Allow SELECT a FROM crash_me LEFT JOIN crash_me2 USING (a); in this case a is assumed to come from  the crash_me table. Fix so that ON and USING works with the JOIN join type. * Oracle-like CONNECT BY PRIOR ... to search hierarchy structures. mysqladmin copy database new-database; requires COPY command to be added to mysqld. * Processlist should show number of queries/threads. SHOW HOSTS for printing information about the hostname cache. * DELETE and REPLACE options to the UPDATE statement (this will delete rows when one gets a duplicate  key error while updating). * Change the format of DATETIME to store fractions of seconds. Add all missing ANSI92 and ODBC 3.0 types. Change table names from empty strings to NULL for calculated columns. Don't use Item_copy_string on numerical values to avoid number->string->number conversion in case of: SELECT COUNT(*)*(id+0) FROM table_name GROUP BY id * Make it possible to use the new GNU regexp library instead of the current one (the GNU library should be much faster than the old one) * Change so that ALTER TABLE doesn't abort clients that execute INSERT DELAYED. * Fix so that when columns are referenced in an UPDATE clause, they contain the old values from before  the update started. * Add simulation of pread()/pwrite() on Windows to enable concurrent inserts. * A logfile analyser that could parse out information about which tables are hit most often, how often  multi-table joins are executed, etc. It should help users identify areas or table design that could be optimised to execute much more efficient queries. * Add SUM(DISTINCT). * Add ANY(), EVERY(), and SOME() group functions. In ANSI SQL these work only on boolean columns, but we can extend these to work on any columns/expressions by applying: value == 0 -> FALSE and value <>  0 -> TRUE. * Fix that the type for MAX(column) is the same as the column type: 5 mysql> CREATE TABLE t1 (a DATE); mysql> INSERT INTO t1 VALUES (NOW()); mysql> CREATE TABLE t2 SELECT MAX(a) FROM t1; mysql> SHOW COLUMNS FROM t2; * Come up with a nice syntax for a statement that will UPDATE the row if it exists and INSERT a new  row if the row didn't exist (like REPLACE works with INSERT / DELETE).  1.8.4 Things That Have to be Done Sometime  * Implement function: get_changed_tables(timeout,table1,table2,...). Change reading through tables to use memmap when possible. Now only compressed tables use memmap. * Make the automatic timestamp code nicer. Add timestamps to the update log with SET TIMESTAMP=#;. Use read/write mutex in some places to get more speed. * Full foreign key support in for MyISAM tables, probably after the implementation of stored  procedures with triggers. * Simple views (first on one table, later on any expression). * Automatically close some tables if a table, temporary table, or temporary files gets error 23 (not  enough open files). When one finds a field=#, change all occurrences of field to #. Now this is only done for some simple cases. Change all const expressions with calculated expressions if possible.ptimise key = expression. At the moment only key = field or key = constant are optimised. Join some of the copy functions for nicer code. Change `sql_yacc.yy' to an inline parser to reduce its size and get better error messages (5 days). Change the parser to use only one rule per different number of arguments in function. Use of full calculation names in the order part (for ACCESS97). * MINUS, INTERSECT, and FULL OUTER JOIN. (Currently UNION [in 4.0] and LEFT OUTER JOIN are supported.) SQL_OPTION MAX_SELECT_TIME=# to put a time limit on a query Make the update log write to a database. Add to LIMIT to allow retrieval of data from the end of a result set Alarm around client connect/read/write functions. * Please note the changes to safe_mysqld: according to FSSTND (which Debian tries to follow) PID files  should go into `/var/run/.pid' and log files into `/var/log'. It would be nice if you could put the "DATADIR" ifirst declaration of "pidfile" and "log", so the placement of these  files can be changed with a single statement. Allow a client to request logging. * Add use of zlib() for gzip-ed files to LOAD DATA INFILE. Fix sorting and grouping of BLOB columns (partly solved now). Stored procedures. Triggers are also being looked at. * A simple (atomic) update language that can be used to write loops and such in the MySQL server. * Change to use semaphores when counting threads. One should first implement a semaphore library to  MIT-pthreads. Don't assign a new AUTO_INCREMENT value when one sets a column to 0. Use NULL instead. * Add full support for JOIN with parentheses. * As an alternative for one thread/connection manage a pool of threads to handle the queries. Allow one to get more than one lock with GET_LOCK. When doing this, one must also handle the  1.8.4 Things That Have to be Done Sometime6 possible deadlocks this change will introduce.  Time is given according to amount of work, not real time.  1.8.5 Things We Don't Plan To Do  * Nothing; we aim toward full ANSI 92/ANSI 99 compliancy.  1.9 How MySQL Compares to Other Databases  Our users have successfully run their own benchmarks against a number of Open Source and traditional database servers. We are aware of tests against Oracle server, DB/2 server, Microsoft SQL Server, and other commercial products. Due to legal reasons we are restricted from publishing some of those benchmarks in our reference manual.  This section includes a comparison with mSQL for historical reasons and with PostgreSQL as it is also an Open Source database. If you have benchmark results that we can publish, please contact us at benchmarks@mysql.com.  For comparative lists of all supported functions and types as well as measured operational limits of many different database systems, see the crash-me web page at http://www.mysql.com/information/crash-me.php.  1.9.1 How MySQL Compares to mSQL  Performance  For a true comparison of speed, consult the growing MySQL benchmark suite. See section 5.1.4 The  MySQL Benchmark Suite. Because there is no thread creation overhead, a small parser, few  features, and simple security, mSQL should be quicker at:  + Tests that perform repeated connects and disconnects, running a very simple query during each  connection.  + INSERT operations into very simple tables with few columns and keys.  + CREATE TABLE and DROP TABLE.  + SELECT on something that isn't an index. (A table scan is very easy.)  Because these operations are so simple, it is hard to be better at them when you have a higher  startup overhead. After the connection is established, MySQL Server should perform much better.  On the other hand, MySQL Server is much faster than mSQL (and most other SQL implementations) on  the following:  + Complex SELECT operations.  + Retrieving large results (MySQL Server has a better, faster,afer protocol).  + Tables with variable-length strings because MySQL Server has more efficient handling and can  have indexes on VARCHAR columns.  + Handling tables with many columns.  + Handling tables with large record lengths.  + SELECT with many expressions.  + SELECT on large tables.  1.8.5 Things We Don't Plan To Do7  + Handling many connections at the same time. MySQL Server is fully multi-threaded. Eachconnection has its own thread, which means that no thread has to wait for another (unless a thread is modifying a table another thread wants to access). In mSQL, once one connection isestablished, all others must wait until the first has finished, regardless of whether the connection is running a query that is short or long. When the first connection terminates, thenext can be served, while all the others wait again, etc.  + Joins. mSQL can become pathologically slow if you change the order of tables in a SELECT. Inthe benchmark suite, a time more than 15,000 times slower than MySQL Server was seen. This is due to mSQL's lack of a join optimiser to order tables in the optimal order. However, if youput the tables in exactly the right order in mSQL2 and the WHERE is simple and uses index columns, the join will be relatively fast! See section 5.1.4 The MySQL Benchmark Suite. + ORDER BY and GROUP BY. + DISTINCT. + Using TEXT or BLOB columns. SQL Features  + GROUP BY and HAVING. mSQL does not support GROUP BY at all. MySQL Server supports a full GROUP BY with both HAVING and the following functions: COUNT(), AVG(), MIN(), MAX(), SUM(), and STD(). COUNT(*) is optimised to return very quickly if the SELECT retrieves from one table, noother columns are retrieved, and there is no WHERE clause. MIN() and MAX() may take string arguments. + INSERT and UPDATE with calculations. MySQL Server can do calculations in an INSERT or UPDATE. For example: mysql> UPDATE SET x=x*10+y WHERE x<20; + Aliasing. MySQL Server has column aliasing.+ Qualifying column names. In MySQL Server, if a column name is unique among the tables used in a query, you do not have to use the full qualifier.+ SELECT with functions. MySQL Server has many functions (too many to list here; see section 6.3 Functions for Use in SELECT and WHERE Clauses). Disk Space EfficiencyThat is, how small can you make your tables? MySQL Server has very precise types, so you can create tables that take very little space. An example of a useful MySQL datatype is the MEDIUMINTthat is 3 bytes long. If you have 100 million records, saving even 1 byte per record is veryimportant. mSQL2 has a more limited set of column types, so it is more difficult to get smalltables. Stability This is harder to judge objectively. For a discussion of MySQL Server stability, see section 1.2.3 How Stable Is MySQL?. We have no experience with mSQL stability, so we cannot say anythingabout that. Price Another important issue is the license. MySQL Server has a more flexible license than mSQL, andis also less expensive than mSQL. Whichever product you choose to use, remember to at least consider paying for a license or e-mail support. Perl InterfacesMySQL Server has basically the same interfaces to Perl as mSQL with some added features. JDBC (Java) MySQL Server currently has a lot of different JDBC drivers: 5.1.4 The MySQL Benchmark Suite8The mm driver: a type 4 JDBC driver by Mark Matthews mmatthew@ecn.purdue.edu. This is releasedunder the LGPL.+ The Resin driver: this is a commercial JDBC driver released under open source. http://www.caucho.com/projects/jdbc-mysql/index.xtp+ The gwe driver: a Java interface by GWE technologies (not supported anymore). + The jms driver: an improved gwe driver by Xiaokun Kelvin ZHU X.Zhu@brad.ac.uk (not supported anymore).+ The twz driver: a type 4 JDBC driver by Terrence W. Zellers zellert@voicenet.com. This is commercial but is free for private and educational use (not supported anymore). The recommended driver is the mm driver. The Resin driver may also be good (at least the benchmarks look good), but we haven't received that much information about this yet. We know thatmSQL has a JDBC driver, but we have too little experience with it to compare. Rate of DevelopmentMySQL Server has a small core team of developers, but we are quite used to coding C and C++ very rapidly. Because threads, functions, GROUP BY, and so on are still not implemented in mSQL, ithas a lot of catching up to do. To get some perspective on this, you can view the mSQL `HISTORY'file for the last year and compare it with the News section of the MySQL Reference Manual (seesection D MySQL Change History). It should be pretty obvious which one has developed most rapidly. Utility Programs Both mSQL and MySQL Server have many interesting third-party tools. Because it is very easy to port upward (from mSQL to MySQL Server), almost all the interesting applications that are available for mSQL are also available for MySQL Server. MySQL Server comes with a simplemsql2mysql program that fixes differences in spelling between mSQL and MySQL Server for themost-used C API functions. For example, it changes instances of msqlConnect() to mysql_connect().Converting a client program from mSQL to MySQL Server usually requires only minor effort.  1.9.1.1 How to Convert mSQL Tools for MySQL  According to our experience, it doesn't take long to convert tools such as msql-tcl and msqljava that use the mSQL C API so that they work with the MySQL C API.  The conversion procedure is: 1. Run the shell script msql2mysql on the source. This requires the replace program, which is distributed with MySQL Server. 2. Compile. 3. Fix all compiler errors.  Differences between the mSQL C API and the MySQL C API are: * MySQL Server uses a MYSQL structure as a connection type (mSQL uses an int). * mysql_connect() takes a pointer to a MYSQL structure as a parameter. It is easy to define one globally or to use malloc() to get one. mysql_connect() also takes two parameters for specifying the user and password. You may set these to NULL, NULL for default use. * mysql_error() takes the MYSQL structure as a parameter. Just add the parameter to your old msql_error() code if you are porting old code. * MySQL Server returns an error number and a text error message for all errors. mSQL returns only a  mmatthew@ecn.purdue.edu9 text error message. * Some incompatibilities exist as a result of MySQL Server supporting multiple connections to the server from the same process.  1.9.1.2 How mSQL and MySQL Client/Server Communications Protocols Differ  There are enough differences that it is impossible (or at least not easy) to support both.  The most significant ways in which the MySQL protocol differs from the mSQL protocol are listed here: * A message buffer may contain many result rows. * The message buffers are dynamically enlarged if the query or the result is bigger than the current buffer, up to a configurable server and client limit. * All packets are numbered to catch duplicated or missing packets. * All column values are sent in ASCII. The lengths of columns and rows are sent in packed binary coding (1, 2, or 3 bytes). * MySQL can read in the result unbuffered (without having to store the full set in the client). * If a single read/write takes more than 30 seconds, the server closes the connection. * If a connection is idle for 8 hours, the server closes the connection.  1.9.1.3 How mSQL 2.0 SQL Syntax Differs from MySQL  Column types MySQL Server Has the following additional types (among others; see section 6.5.3 CREATE TABLE Syntax): + ENUM type for one of a set of strings.+ SET type for many of a set of strings.+ BIGINT type for 64-bit integers.  MySQL Server also supports the following additional type attributes:+ UNSIGNED option for integer and floating-point columns. + ZEROFILL option for integer columns. + AUTO_INCREMENT option for integer columns that are a PRIMARY KEY. See section 8.4.3.126mysql_insert_id(). + DEFAULT value for all columns. mSQL2  mSQL column types correspond to the MySQL types shown in the following table:  mSQL type Corresponding MySQL typeCHAR(len) CHAR(len) TEXT(len) TEXT(len). len is the maximal length. And LIKE works.  INT INT. With many more options!  REAL REAL. Or FLOAT. Both 4- and 8-byte versions are available.  UINT INT UNSIGNED  DATE DATE. Uses ANSI SQL format rather than mSQL's own format.  TIME TIME  MONEY DECIMAL(12,2). A fixed-point value with two decimals.   1.9.1.2 How mSQL and MySQL Client/Server Communications Protocols Differ50 Index Creation MySQL Server  Indexes may be specified at table creation time with the CREATE TABLE statement. mSQL  Indexes must be created after the table has been created, with separate CREATE INDEX statements. To Insert a Unique Identifier into a Table MySQL Server Use AUTO_INCREMENT as a column type specifier. See section 8.4.3.126 mysql_insert_id(). mSQL  Create a SEQUENCE on a table and select the _seq column.  To Obtain a Unique Identifier for a Row MySQL Server  Add a PRIMARY KEY or UNIQUE key to the table and use this. New in Version 3.23.11: If the PRIMARY  or UNIQUE key consists of only one column and this is of type integer, one can also refer to it  as _rowid. mSQL Use the _rowid column. Observe that _rowid may change over time depending on many factors.  To Get the Time a Column Was Last Modified MySQL Server Add a TIMESTAMP column to the table. This column is automatically set to the current date andtime for INSERT or UPDATE statements if you don't give the column a value or if you give it aNULL value. mSQL Use the _timestamp column.  NULL Value Comparisons MySQL Server MySQL Server follows ANSI SQL, and a comparison with NULL is always NULL. mSQL In mSQL, NULL = NULL is TRUE. You must change =NULL to IS NULL and <>NULL to IS NOT NULL when porting old code from mSQL to MySQL Server.  String Comparisons MySQL Server Normally, string comparisons are performed in case-independent fashion with the sort orderdetermined by the current character set (ISO-8859-1 Latin1 by default). If you don't like this,declare your columns with the BINARY attribute, which causes comparisons to be done according tothe ASCII order used on the MySQL server host. mSQL All string comparisons are performed in case-sensitive fashion with sorting in ASCII order.  Case-insensitive Searching MySQL Server 8.4.3.126 mysql_insert_id()1 LIKE is a case-insensitive or case-sensitive operator, depending on the columns involved. If possible, MySQL uses indexes if the LIKE argument doesn't start with a wildcard character. mSQL  Use CLIKE.  Handling of Trailing Spaces MySQL Server Strips all spaces at the end of CHAR and VARCHAR columns. Use a TEXT column if this behaviour isnot desired.Retains trailing space. WHERE ClausesMySQL correctly prioritises everything (AND is evaluated before OR). To get mSQL behaviour in MySQL Server, use parentheses (as shown in an example later in this section). mSQL Evaluates everything from left to right. This means that some logical calculations with more thanthree arguments cannot be expressed in any way. It also means you must change some queries whenyou upgrade to MySQL Server. You do this easily by adding parentheses. Suppose you have the following mSQL query: mysql> SELECT * FROM table WHERE a=1 AND b=2 OR a=3 AND b=4;To make MySQL Server evaluate this the way that mSQL would, you must add parentheses: mysql> SELECT * FROM table WHERE (a=1 AND (b=2 OR (a=3 AND (b=4))));  Access Control MySQL Server Has tables to store grant (permission) options per user, host, and database. See section 4.2.6  How the Privilege System Works. mSQL Has a file `mSQL.acl' in which you can grant read/write privileges for users.  1.9.2 How MySQL Compares to PostgreSQL  When reading the following, please note that both products are continually evolving. We at MySQL AB and the PostgreSQL developers are both working on making our respective databases as good as possible, so we are both a serious alternative to any commercial database.  The following comparison is made by us at MySQL AB. We have tried to be as accurate and fair as possible, but although we know MySQL Server thoroughly, we don't have a full knowledge of all PostgreSQL features, so we may have got some things wrong. We will, however, correct these when they come to our attention.  We would first like to note that PostgreSQL and MySQL Server are both widely used products, but with different design goals, even if we are both striving toward ANSI SQL compliancy. This means that for some applications MySQL Server is more suited, while for others PostgreSQL is more suited. When choosing 4.2.6How the Privilege System Works2 which database to use, you should first check if the database's feature set satisfies your application. If you need raw speed, MySQL Server is probably your best choice. If you need some of the extra features that only PostgreSQL can offer, you should use PostgreSQL.  1.9.2.1 MySQL and PostgreSQL development strategies  When adding things to MySQL Server we take pride to do an optimal, definite solution. The code should be so good that we shouldn't have any need to change it in the foreseeable future. We also do not like to sacrifice speed for features but instead will do our utmost to find a solution that will give maximal throughput. This means that development will take a little longer, but the end result will be well worth this. This kind of development is only possible because all server code are checked by one of a few (currently two) persons before it's included in the MySQL server.  We at MySQL AB believe in frequent releases to be able to push out new features quickly to our users. Because of this we do a new small release about every three weeks, and a major branch every year. All releases are thoroughly tested with our testing tools on a lot of different platforms.  PostgreSQL is based on a kernel with lots of contributors. In this setup it makes sense to prioritise adding a lot of new features, instead of implementing them optimally, because one can always optimise things later if there arises a need for this.  Another big difference between MySQL Server and PostgreSQL is that nearly all of the code in the MySQL server is coded by developers that are employed by MySQL AB and are still working on the server code. The exceptions are the transaction engines and the regexp library. This is in sharp contrast to the PostgreSQL code, the majority of which is coded by a big group of people with different backgrounds. It was only recently that the PostgreSQL developers announced that their current developer group had finally had time to take a look at all the code in the current PostgreSQL release.  Both of the aforementioned development methods have their own merits and drawbacks. We here at MySQL AB think, of course, that our model is better because our model gives better code consistency, more optimal and reusable code, and in our opinion, fewer bugs. Because we are the authors of the MySQL server code, we are better able to coordinate new features and releases.  1.9.2.2 Featurewise Comparison of MySQL and PostgreSQL  On the crash-me page (http://www.mysql.com/information/crash-me.php) you can find a list of those database constructs and limits that one can detect automatically with a program. Note, however, that a lot of the numerical limits may be changed with startup options for their respective databases. This web page is, however, extremely useful when you want to ensure that your applications work with many different databases or when you want to convert your application from one database to another. MySQL Server offers the following advantages over PostgreSQL: * MySQL Server is generally much faster than PostgreSQL. MySQL 4.0.1 also has a query cache that can boost up the query speed for mostly-read-only sites many times.  1.9.2.1 MySQL and PostgreSQL development strategies3 * MySQL has a much larger user base than PostgreSQL. Therefore, the code is tested more and has historically proven more stable than PostgreSQL. MySQL Server is used more in production environments than PostgreSQL, mostly thanks to the fact that MySQL AB, formerly TCX DataKonsult AB, has provided top-quality commercial support for MySQL Server from the day it was released, whereas  until recently PostgreSQL was unsupported. * MySQL Server works better on Windows than PostgreSQL does. MySQL Server runs as a native Windows application (a service on NT/2000/XP), while PostgreSQL is run under the Cygwin emulation. We have heard that PostgreSQL is not yet that stable on Windows but we haven't been able to verify this ourselves. * MySQL has more APIs to other languages and is supported by more existing programs than PostgreSQL. See section B Contributed Programs. * MySQL Server works on 24/7 heavy-duty systems. In most circumstances you never have to run any cleanups on MySQL Server. PostgreSQL doesn't yet support 24/7 systems because you have to run VACUUM once in a while to reclaim space from UPDATE and DELETE commands and to perform statistics analyses that are critical to get good performance with PostgreSQL. VACUUM is also needed after adding a lot of new rows to a table. On a busy system with lots of changes, VACUUM must be run very frequently, in the worst cases even many times a day. During the VACUUM run, which may take hours if the database is big, the database is, from a production standpoint, practically dead. Please note: in PostgreSQL version 7.2, basic vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new VACUUM FULL command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. * MySQL replication has been thoroughly tested, and is used by sites like: + Yahoo Finance (http://finance.yahoo.com/) + Mobile.de (http://www.mobile.de/)+ Slashdot (http://www.slashdot.org/) * Included in the MySQL distribution are two different testing suites, `mysql-test-run' and crash-me (http://www.mysql.com/information/crash-me.php), as well as a benchmark suite. The test system is actively updated with code to test each new feature and almost all reproduceable bugs that have come to our attention. We test MySQL Server with these on a lot of platforms before every release. These tests are more sophisticated than anything we have seen from PostgreSQL, and they ensure that the MySQL Server is kept to a high standard. * There are far more books in print about MySQL Server than about PostgreSQL. O'Reilly, SAMS, Que, and New Riders are all major publishers with books about MySQL. All MySQL features are also documented in the MySQL online manual because when a new feature is implemented, the MySQL developers are required to document it before it's included in the source.  * MySQL Server supports more of the standard ODBC functions than PostgreSQL. * MySQL Server has a much more sophisticated ALTER TABLE. * MySQL Server has support for tables without transactions for applications that need all the speed they can get. The tables may be memory-based, HEAP tables or disk based MyISAM. See section 7 MySQL  Table Types. * MySQL Server has support for two different table handlers that support transactions, InnoDB, and BerkeleyDB. Because every transaction engine performs differently under different conditions, this gives the application writer more options to find an optimal solution for his or her setup, if need be per individual table. See section 7 MySQL Table Types.ERGE tables gives you a unique way to instantly make a view over a set of identical tables and use these as one. This is perfect for systems where you have log files that you order, for example, by B Contributed Programs4  month. See section 7.2 MERGE Tables. * The option to compress read-only tables, but still have direct access to the rows in the table, gives you better performance by minimising disk reads. This is very useful when you are archiving things. See section 4.7.4 myisampack, The MySQL Compressed Read-only Table Generator. * MySQL Server has internal support for full-text search. See section 6.8 MySQL Full-text Search. You can access many databases from the same connection (depending, of course, on your privileges). * MySQL Server is coded from the start to be multi-threaded, while PostgreSQL uses processes. Context switching and access to common storage areas is much faster between threads than between separate processes. This gives MySQL Server a big speed advantage in multi-user applications and also makes  it easier for MySQL Server to take full advantage of symmetric multiprocessor (SMP) systems. * MySQL Server has a much more sophisticated privilege system than PostgreSQL. While PostgreSQL only  supports INSERT, SELECT, and UPDATE/DELETE grants per user on a database or a table, MySQL Server allows you to define a full set of different privileges on the database, table, and column level. MySQL Server also allows you to specify the privilege on host and user combinations. See section 4.3.1 GRANT and REVOKE Syntax. * MySQL Server supports a compressed client/server protocol which improves performance over slow links. * MySQL Server employs a ``table handler'' concept, and is the only relational database we know of built around this concept. This allows different low-level table types to be called from the SQL engine, and each table type can be optimised for different performance characteristics. * All MySQL table types (except InnoDB) are implemented as files (one table per file), which makes it  really easy to back up, move, delete, and even symlink databases and tables, even when the server is down. * Tools to repair and optimise MyISAM tables (the most common MySQL table type). A repair tool is only needed when a physical corruption of a datafile happens, usually from a hardware failure. It allows  a majority of the data to be recovered. * Upgrading MySQL Server is painless. When you are upgrading MySQL Server, you don't need to dump/restore your data, as you have to do with most PostgreSQL upgrades.  Drawbacks with MySQL Server compared to PostgreSQL: * The transaction support in MySQL Server is not yet as well tested as PostgreSQL's system. Because MySQL Server uses threads, which are not yet flawless on many OSes, one must either use binaries from http://www.mysql.com/downloads/, or carefully follow our instructions on http://www.mysql.com/doc/I/n/Installing_source.html to get an optimal binary that works in all cases. Table locking, as used by the non-transactional MyISAM tables, is in many cases faster than page  locks, row locks, or versioning. The drawback, however, is that if one doesn't take into account how  table locks work, a single long-running query can block a table for updates for a long time. This can usually be avoided when designing the application. If not, one can always switch the trouble table to use one of the transactional table types. See section 5.3.2 Table Locking Issues. With UDF (user-defined functions) one can extend MySQL Server with both normal SQL functions aggregates, but this is not yet as easy or as flexible as in PostgreSQL. See section 9.2 Adding New Functions to MySQL. * Updates that run over multiple tables are harder to do in MySQL Server. This will, however, be fixed  in MySQL Server 4.0.2 with multi-table UPDATE and in MySQL Server 4.1 with subselects. In MySQL Server 4.0 one can use multi-table deletes to delete from many tables at the same time. See section 7.2 MERGE Tables5 6.4.6 DELETE Syntax.  PostgreSQL currently offers the following advantages over MySQL Server:  Note that because we know the MySQL road map, we have included in the following table the version when MySQL Server should support this feature. Unfortunately we couldn't do this for previous comparisons, because we don't know the PostgreSQL roadmap.  Feature MySQL version Subselects 4.1 Foreign keys 4.1 (3.23 with InnoDB) Views 5.0 Stored procedures 5.0 Triggers 5.0 Unions 4.0 Full join 4.1 Constraints4.1 or 5.0 Cursors 4.1 or 5.0 R-trees 4.1 (for MyISAM tables) Inherited tables Not planned Extensible type system Not planned  Other reasons someone may consider using PostgreSQL: Standard usage in PostgreSQL is closer to ANSI SQL in some cases. * One can speed up PostgreSQL by coding things as stored procedures. * For geographical data, R-trees make PostgreSQL better than MySQL Server. (note: MySQL version 4.1  will have R-trees for MyISAM tables). * The PostgreSQL optimiser can do some optimisation that the current MySQL optimiser can't do. Most notable is doing joins when you don't have the proper keys in place and doing a join where you are using different keys combined with OR. The MySQL benchmark suite at  http://www.mysql.com/information/benchmarks.html shows you what kind of constructs you should watch  out for when using different databases. * PostgreSQL has a bigger team of developers that contribute to the server.  Drawbacks with PostgreSQL compared to MySQL Server: VACUUM makes PostgreSQL hard to use in a 24/7 environment. * Only transactional tables. * Much slower INSERT, DELETE, and UPDATE.  For a complete list of drawbacks, you should also examine the first table in this section.  1.9.2.3 Benchmarking MySQL and PostgreSQL  The only Open Source benchmark that we know of that can be used to benchmark MySQL Server and PostgreSQL (and other databases) is our own. It can be found at http://www.mysql.com/information/benchmarks.html.   6.4.6 DELETE Syntax6 We have many times asked the PostgreSQL developers and some PostgreSQL users to help us extend this benchmark to make it the definitive benchmark for databases, but unfortunately we haven't gotten any feedback for this. We, the MySQL developers, have, because of this, spent a lot of hours to get maximum performance from PostgreSQL for the benchmarks, but because we don't know PostgreSQL intimately, we are sure that there are things that we have missed. We have on the benchmark page documented exactly how we did run the benchmark so that it should be easy for anyone to repeat and verify our results.  The benchmarks are usually run with and without the --fast option. When run with --fast we are trying to use every trick the server can do to get the code to execute as fast as possible. The idea is that the normal run should show how the server would work in a default setup and the --fast run shows how the server would do if the application developer would use extensions in the server to make his application run faster.  When running with PostgreSQL and --fast we do a VACUUM after every major table UPDATE and DROP TABLE to make the database in perfect shape for the following SELECTs. The time for VACUUM is measured separately.  When running with PostgreSQL 7.1.1 we could, however, not run with --fast because during the INSERT test, the postmaster (the PostgreSQL deamon) died and the database was so corrupted that it was impossible to restart postmaster. After this happened twice, we decided to postpone the --fast test until the next PostgreSQL release. The details about the machine we run the benchmark on can be found on the benchmark page.  Before going to the other benchmarks we know of, we would like to give some background on benchmarks.  It's very easy to write a test that shows any database to be the best database in the world, by just restricting the test to something the database is very good at and not testing anything that the database is not good at. If one, after doing this, summarises the result as a single figure, things are even easier.  This would be like us measuring the speed of MySQL Server compared to PostgreSQL by looking at the summary time of the MySQL benchmarks on our web page. Based on this MySQL Server would be more than 40 times faster than PostgreSQL, something that is, of course, not true. We could make things even worse by just taking the test where PostgreSQL performs worst and claim that MySQL Server is more than 2000 times faster than PostgreSQL.  The case is that MySQL does a lot of optimisations that PostgreSQL doesn't do. This is, of course, also true the other way around. An SQL optimiser is a very complex thing, and a company could spend years just making the optimiser faster and faster.  When looking at the benchmark results you should look for things that you do in your application and just use these results to decide which database would be best suited for your application. The benchmark results also show things a particular database is not good at and should give you a notion about things to avoid and what you may have to do in other ways. 7  We know of two benchmark tests that claim that PostgreSQL performs better than MySQL Server. These both where multi-user tests, a test that we here at MySQL AB haven't had time to write and include in the benchmark suite, mainly because it's a big task to do this in a manner that is fair to all databases.  One is the benchmark paid for by Great Bridge, the company that for 16 months attempted to build a business based on PostgreSQL but now has ceased operations. This is probably the worst benchmark we have ever seen anyone conduct. This was not only tuned to only test what PostgreSQL is absolutely best at, but it was also totally unfair to every other database involved in the test.  Note: We know that even some of the main PostgreSQL developers did not like the way Great Bridge conducted the benchmark, so we don't blame the PostgreSQL team for the way the benchmark was done.  This benchmark has been condemned in a lot of postings and newsgroups, so here we will just briefly repeat some things that were wrong with it. * The tests were run with an expensive commercial tool that makes it impossible for an Open Source company like us to verify the benchmarks, or even check how the benchmarks were really done. The tool is not even a true benchmark tool, but an application/setup testing tool. To refer to this as a ``standard'' benchmark tool is to stretch the truth a long way. * Great Bridge admitted that they had optimised the PostgreSQL database (with VACUUM before the test) and tuned the startup for the tests, something they hadn't done for any of the other databases involved. They say ``This process optimises indexes and frees up disk space a bit. The optimised indexes boost performance by some margin.'' Our benchmarks clearly indicate that the difference in running a lot of selects on a database with and without VACUUM can easily differ by a factor of 10. * The test results were also strange. The AS3AP test documentation mentions that the test does ``selections, simple joins, projections, aggregates, one-tuple updates, and bulk updates.'' PostgreSQL is good at doing SELECTs and JOINs (especially after a VACUUM), but doesn't perform as well on INSERTs or UPDATEs. The benchmarks seem to indicate that only SELECTs were done (or very few updates). This could easily explain the good results for PostgreSQL in this test. The bad results for MySQL will be obvious a bit down in this document. * They did run the so-called benchmark from a Windows machine against a Linux machine over ODBC, a setup that no normal database user would ever do when running a heavy multi-user application. This tested more the ODBC driver and the Windows protocol used between the clients than the database itself. * When running the database against Oracle and MS-SQL (Great Bridge has indirectly indicated the databases they used in the test), they didn't use the native protocol but instead ODBC. Anyone that has ever used Oracle knows that all real applications use the native interface instead of ODBC. Doing a test through ODBC and claiming that the results had anything to do with using the database in a real-world situation can't be regarded as fair. They should have done two tests with and without ODBC to provide the right facts (after having gotten experts to tune all involved databases, of course). * They refer to the TPC-C tests, but they don't mention anywhere that the test they did was not a true TPC-C test and they were not even allowed to call it a TPC-C test. A TPC-C test can only be conducted by the rules approved by the TPC Council (http://www.tpc.org/). Great Bridge didn't do that. By doing this they have both violated the TPC trademark and miscredited their own benchmarks. The rules set by the TPC Council are very strict to ensure that no one can produce false results or http://www.tpc.org/8 make unprovable statements. Apparently Great Bridge wasn't interested in doing this. * After the first test, we contacted Great Bridge and mentioned to them some of the obvious mistakes they had done with MySQL Server: + Running with a debug version of our ODBC driver+ Running on a Linux system that wasn't optimised for threads + Using an old MySQL version when there was a recommended newer one available + Not starting MySQL Server with the right options for heavy multi-user use (the default installation of MySQL Server is tuned for minimal resource use) Great Bridge did run a new test, with our optimised ODBC driver and with better startup options for MySQL Server, but refused to either use our updated glibc library or our standard binary (used by 80% of our users), which was statically linked with a fixed glibc library. According to what we know, Great Bridge did nothing to ensure that the other databases were set up correctly to run well in their test environment. We are sure, however, that they didn't contact Oracle or Microsoft to ask for their advice in this matter. ;) * The benchmark was paid for by Great Bridge, and they decided to publish only partial, chosen results  (instead of publishing it all).  Tim Perdue, a long-time PostgreSQL fan and a reluctant MySQL user, published a comparison on PHPbuilder (http://www.phpbuilder.com/columns/tim20001112.php3).  When we became aware of the comparison, we phoned Tim Perdue about this because there were a lot of strange things in his results. For example, he claimed that MySQL Server had a problem with five users in his tests, when we know that there are users with similar machines as his that are using MySQL Server with 2000 simultaneous connections doing 400 queries per second. (In this case the limit was the web bandwidth, not the database.)  It sounded like he was using a Linux kernel that either had some problems with many threads, such as kernels before 2.4, which had a problem with many threads on multi-CPU machines. We have documented in this manual how to fix this and Tim should be aware of this problem.  The other possible problem could have been an old glibc library and that Tim didn't use a MySQL binary from our site, which is linked with a corrected glibc library, but had compiled a version of his own. In any of these cases, the symptom would have been exactly what Tim had measured.  We asked Tim if we could get access to his data so that we could repeat the benchmark and if he could check the MySQL version o e machine to find out what was wrong and he promised to come back to us about this. He has not done that yet.  Because of this we can't put any trust in this benchmark either. :(  Over time things also change and the preceding benchmarks are not that relevant anymore. MySQL Server now has a couple of different table handlers with different speed/concurrency tradeoffs. See section 7 MySQL Table Types. It would be interesting to see how the above tests would run with the different transactional table types in MySQL Server. PostgreSQL has, of course, also got new features since the test was made. As these tests are not publicly available there is no way for us to know how the database would perform in the same tests today.  (http://www.phpbuilder.com/columns/tim20001112.php39  Conclusion:  The only benchmarks that exist today that anyone can download and run against MySQL Server and PostgreSQL are the MySQL benchmarks. We here at MySQL AB believe that Open Source databases should be tested with Open Source tools! This is the only way to ensure that no one does tests that nobody can reproduce and use this to claim that one database is better than another. Without knowing all the facts it's impossible to answer the claims of the tester.  The thing we find strange is that every test we have seen about PostgreSQL, that is impossible to reproduce, claims that PostgreSQL is better in most cases while our tests, which anyone can reproduce, clearly show otherwise. With this we don't want to say that PostgreSQL isn't good at many things (it is!) or that it isn't faster than MySQL Server under certain conditions. We would just like to see a fair test where PostgreSQL performs very well, so that we could get some friendly competition going!  For more information about our benchmark suite, see section 5.1.4 The MySQL Benchmark Suite. We are working on an even better benchmark suite, including multi-user tests, and a better documentation of what the individual tests really do and how to add more tests to the suite.  2 MySQL Installation  This chapter describes how to obtain and install MySQL: * For a list of sites from which you can obtain MySQL, see section 2.2.1 How to Get MySQL. * To see which platforms are supported, see section 2.2.2 Operating Systems Supported by MySQL. Please note that not all supported systems are equally good for running MySQL on them. On some it is much more robust and efficient than others@-see section 2.2.2 Operating Systems Supported by MySQL for details. * Several versions of MySQL are available in both binary and source distributions. We also provide public access to our current source tree for those who want to see our most recent developments and help us test new code. To determine which version and type of distribution you should use, see section 2.2.3 Which MySQL Version to Use. When in doubt, use the binary distribution. * Installation instructions for binary and source distributions are described in section 2.2.7 Installing a MySQL Binary Distribution, and section 2.3 Installing a MySQL Source Distribution. Each set of instructions includes a section on system-specific problems you may run into. * For post-installation procedures, see section 2.4 Post-installation Setup and Testing. These procedures apply whether you install MySQL using a binary or source distribution. 2.1 Quick Standard Installation of MySQL 2.1.1 Installing MySQL on Linux  The recommended way to install MySQL on Linux is by using an RPM file. The MySQL RPMs are currently being built on a RedHat Version 6.2 system but should work on other versions of Linux that support rpm and use glibc.  5.1.4 The MySQL Benchmark Suite5.1.4 The MySQL Benchmark Suite2 MySQL Installation2 MySQL Installation2.2.1 How to Get MySQL2.2.1 How to Get MySQL2.2.2 Operating Systems Supported by MySQL2.2.2 Operating Systems Supported by MySQL2.2.2 Operating Systems Supported by MySQL2.2.2 Operating Systems Supported by MySQL2.2.3 Which MySQL Version to Use2.2.3 Which MySQL Version to Use2.2.7 Installing a MySQL Binary Distribution2.2.7 Installing a MySQL Binary Distribution2.3 Installing a MySQL Source Distribution2.3 Installing a MySQL Source Distribution2.4 Post-installation Setup and Testing2.4 Post-installation Setup and Testing2.1 Quick Standard Installation of MySQL2.1 Quick Standard Installation of MySQL 2.1.1 Installing MySQL on Linux60 If you have problems with an RPM file, for example, if you receive the error ``Sorry, the host 'xxxx' could not be looked up''@-see section 2.6.1.1 Linux Notes for Binary Distributions. RPM files you may want to use are: * MySQL-VERSION.i386.rpm The MySQL server. You will need this unless you only want to connect to a MySQL server running on another machine. * MySQL-client-VERSION.i386.rpm The standard MySQL client programs. You probably always want to install this package. * MySQL-bench-VERSION.i386.rpm Tests and benchmarks. Requires Perl and msql-mysql-modules RPMs. * MySQL-devel-VERSION.i386.rpm Libraries and include files needed if you want to compile other MySQL clients, such as the Perl modules. * MySQL-VERSION.src.rpm This contains the source code for all of the previous packages. It can also be used to try to build RPMs for other architectures (for example, Alpha or SPARC).  To see all files in an RPM package, run: shell> rpm -qpl MySQL-VERSION.i386.rpm To perform a standard minimal installation, run: shell> rpm -i MySQL-VERSION.i386.rpm MySQL-client-VERSION.i386.rpm To install just the client package, run: shell> rpm -i MySQL-client-VERSION.i386.rpm  The RPM places data in `/var/lib/mysql'. The RPM also creates the appropriate entries in `/etc/rc.d/' to start the server automatically at boot time. (This means that if you have performed a previous installation, you may want to make a copy of your previously installed MySQL startup file if you made any changes to it, so you don't lose your changes.)  After installing the RPM file(s), the mysqld daemon should be running and you should now be able to start using MySQL. See section 2.4 Post-installation Setup and Testing.  If something goes wrong, you can find more information in the binary installation chapter. See section 2.2.7 Installing a MySQL Binary Distribution.  2.1.2 Installing MySQL on Windows  The MySQL server for Windows is available in two distribution types: 1. The binary distribution contains a setup program which installs everything you need so that you can start the server immediately. 2. The source distribution contains all the code and support files for building the executables using the VC++ 6.0 compiler. See section 2.3.7 Windows Source Distribution. Generally speaking, you should use the binary distribution.  You will need the following: * A 32-bit Windows Operating System such as 9x, Me, NT, 2000, or XP. The NT family (NT, Windows 2000 2.6.1.1 Linux Notes for Binary Distributions2.6.1.1 Linux Notes for Binary Distributions2.4 Post-installation Setup and Testing2.4 Post-installation Setup and Testing 2.2.7 Installing a MySQL Binary Distribution 2.2.7 Installing a MySQL Binary Distribution 2.1.2 Installing MySQL on Windows 2.1.2 Installing MySQL on Windows2.3.7 Windows Source Distribution1 and XP) permits running the MySQL server as a service. See section 2.6.2.2 Starting MySQL on Windows  NT, 2000 or XP. If you want to use tables bigger than 4G, you should install MySQL on an NTFS or newer filesystem. Don't forget to use MAX_ROWS and AVG_ROW_LENGTH when you create the table. See section 6.5.3 CREATE TABLE Syntax. TCP/IP protocol support. * A copy of the MySQL binary or distribution for Windows, which can be downloaded from  http://www.mysql.com/downloads/. Note: The distribution files are supplied with a zipped format and we recommend the use of an adequate FTP client with resume feature to avoid corruption of files  during the download process. A ZIP program to unpack the distribution file. * Enough space on the hard drive to unpack, install, and create the databases in accorandance with  your requirements. * If you plan to connect to the MySQL server via ODBC, you will also need the MyODBC driver. See section 8.3 MySQL ODBC Support.  2.1.2.1 Installing the Binaries 1. If you are working on an NT/2000/XP server, logon as a user with with administrator privileges. 2. If you are doing an upgrade of an earlier MySQL installation, it is necessary to stop the server. If you are running the server as a service, use: C:\> NET STOP MySQL Otherwise, use: C:\mysql\bin> mysqladmin -u root shutdown 3. On NT/2000/XP machines, if you want to change the server executable (e.g., -max or -nt), it is also necessary to remove the service: C:\mysql\bin> mysqld-max-nt --remove 4. Unzip the distribution file to a temporary directory. 5. Run the `setup.exe' file to begin the installation process. If you want to install into another directory than the default `c:\mysql', use the Browse button to specify your preferred directory. 6. Finish the install process. 2.1.2.2 Preparing the Windows MySQL Environment  Starting with MySQL 3.23.38, the Windows distribution includes both the normal and the MySQL-Max server binaries. Here is a list of the different MySQL servers you can use: Binary Description mysqld Compiled with full debugging and automatic memory allocation checking, symbolic links, InnoDB, and BDB tables. mysqld-opt Optimised binary with no support for transactional tables. mysqld-nt Optimised binary for NT/2000/XP with support for named pipes. You can run this version on Windows 9x/Me, but in this case no named pipes are created and you must have TCP/IP installed. mysqld-max Optimised binary with support for symbolic links, InnoDB and BDB tables. mysqld-max-nt Like mysqld-max, but compiled with support for named pipes.  Starting from 3.23.50, named pipes are only enabled if one starts mysqld with --enable-named-pipe.  2.6.2.2 Starting MySQL on Windows NT, 2000 or XP 2.6.2.2 Starting MySQL on Windows NT, 2000 or XP6.5.3 CREATE TABLE Syntax6.5.3 CREATE TABLE Syntaxhttp://www.mysql.com/downloads/http://www.mysql.com/downloads/8.3 MySQL ODBC Support8.3 MySQL ODBC Support 2.1.2.1 Installing the Binaries 2.1.2.1 Installing the Binaries 2.1.2.2 Preparing the Windows MySQL Environment2  All of the preceding binaries are optimised for the Pentium Pro processor but should work on any Intel processor >= i386.  You will need to use an option file to specify your MySQL configuration under the following circumstances: * The installation or data directories are different from the default locations (`c:\mysql' and `c:\mysql\data'). * You want to use one of these servers:  + mysqld.exe  + mysqld-max.exe  + mysqld-max-nt.exe You need to tune the server settings.  Normally you can use the WinMySQLAdmin tool to edit the option file my.ini. In this case you don't have to worry about the following section. There are two option files with the same function: `my.cnf' and `my.ini'. However, to avoid confusion, it's best if you use only of one them. Both files are plain text. The `my.cnf' file, if used, should be created in the root directory of the C drive. The `my.ini' file, if used, should be created in the Windows system directory. (This directory is typically something like `C:\WINDOWS' or `C:\WINNT'. You can determine its exact location from the value of the windir environment variable.) MySQL looks first for the my.ini file, then for the `my.cnf' file.  If your PC uses a boot loader where the C drive isn't the boot drive, your only option is to use the `my.ini' file. Also note that if you use the WinMySQLAdmin tool, it uses only the `my.ini' file. The `\mysql\bin' directory contains a help file with instructions for using this tool.  Using notepad.exe, create the option file and edit the [mysqld] section to specify values for the basedir and datadir parameters: [mysqld] # set basedir to installation path, e.g., c:/mysql basedir=the_install_path # set datadir to location of data directory, # e.g., c:/mysql/data or d:/mydata/data datadir=the_data_path  Note that Windows pathnames should be specified in option files using forward slashes rather than backslashes. If you do use backslashes, you must double them.  If you would like to use a data directory different from the default of `c:\mysql\data', you must copy the entire contents of the `c:\mysql\data' directory to the new location.  If you want to use the InnoDB transactional tables, you need to manually create two new directories to hold the InnoDB data and log files@-e.g., `c:\ibdata' and `c:\iblogs'. You will also need to add some extra lines to the option file. See section 7.5.2 InnoDB Startup Options. 7.5.2 InnoDB Startup Options 3 If you don't want to use InnoDB tables, add the skip-innodb option to the option file.  Now you are ready to test starting the server.  2.1.2.3 Starting the Server for the First Time  Testing from a DOS command prompt is the best thing to do because the server displays status messages that appear in the DOS window. If something is wrong with your configuration, these messages will make it easier for you to identify and fix any problems.  Make sure you are in the directory where the server is located, then enter this command: C:\mysql\bin> mysqld-max --standalone You should see the following messages as the server starts up: InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: creating foreign key constraint system tables InnoDB: foreign key constraint system tables created 011024 10:58:25 InnoDB: Started  For further information about running MySQL on Windows, see section 2.6.2 Windows Notes.  2.2 General Installation Issues  2.2.1 How to Get MySQL Check the MySQL homepage (http://www.mysql.com/) for information about the current version and for downloading instructions. Our main mirror is located at http://mirrors.sunsite.dk/mysql/.  For a complete upto-date list of MySQL web/download mirrors, see http://www.mysql.com/downloads/mirrors.html. There you will also find information about becoming a MySQL mirror site and how to report a bad or out-of-date mirror.   2.1.2.3 Starting the Server for the First Time 2.1.2.3 Starting the Server for the First Time2.6.2 Windows Notes2.6.2 Windows Notes2.2 General Installation Issues2.2 General Installation Issues 2.2.1 How to Get MySQL 2.2.1 How to Get MySQLhttp://www.mysql.com/http://www.mysql.com/http://mirrors.sunsite.dk/mysql/http://mirrors.sunsite.dk/mysql/ http://www.mysql.com/downloads/mirrors.html4 2.2.2 Operating Systems Supported by MySQL  We use GNU Autoconf, so it is possible to port MySQL to all modern systems with working Posix threads and a C++ compiler. (To compile only the client code, a C++ compiler is required but not threads.) We use and develop the software ourselves primarily on Sun Solaris (Versions 2.5 - 2.7) and SuSE Linux Version 7.x. Note that for many operating systems, the native thread support works only in the latest versions. MySQL has been reported to compile successfully on the following operating system/thread package combinations: * AIX 4.x with native threads. See section 2.6.6.4 IBM-AIX notes. * Amiga. * BSDI 2.x with the MIT-pthreads package. See section 2.6.4.5 BSD/OS Version 2.x Notes. * BSDI 3.0, 3.1 and 4.x with native threads. See section 2.6.4.5 BSD/OS Version 2.x Notes. * DEC Unix 4.x with native threads. See section 2.6.6.6 Alpha-DEC-UNIX Notes (Tru64). * FreeBSD 2.x with the MIT-pthreads package. See section 2.6.4.1 FreeBSD Notes. * FreeBSD 3.x and 4.x with native threads. See section 2.6.4.1 FreeBSD Notes. * HP-UX 10.20 with the DCE threads or the MIT-pthreads package. See section 2.6.6.2 HP-UX Version  10.20 Notes. * HP-UX 11.x with the native threads. See section 2.6.6.3 HP-UX Version 11.x Notes. * Linux 2.0+ with LinuxThreads 0.7.1+ or glibc 2.0.7+. See section 2.6.1 Linux Notes (All Linux  Versions). * Mac OS X Server. See section 2.6.5 Mac OS X Notes. * NetBSD 1.3/1.4 Intel and NetBSD 1.3 Alpha (Requires GNU make). See section 2.6.4.2 NetBSD notes. * OpenBSD > 2.5 with native threads. OpenBSD < 2.5 with the MIT-pthreads package. See section 2.6.4.3  OpenBSD 2.5 Notes. * OS/2 Warp 3, FixPack 29 and OS/2 Warp 4, FixPack 4. See section 2.6.7 OS/2 Notes. * SGI Irix 6.x with native threads. See section 2.6.6.8 SGI Irix Notes. * Solaris 2.5 and above with native threads on SPARC and x86. See section 2.6.3 Solaris Notes. * SunOS 4.x with the MIT-pthreads package. See section 2.6.3 Solaris Notes. * Caldera (SCO) OpenServer with a recent port of the FSU Pthreads package. See section 2.6.6.9 Caldera (SCO) Notes. * Caldera (SCO) UnixWare 7.0.1. See section 2.6.6.10 Caldera (SCO) Unixware Version 7.0 Notes. * Tru64 Unix * Windows 9x, Me, NT, 2000 and XP. See section 2.6.2 Windows Notes. Note that not all platforms are suited equally well for running MySQL. How well a certain platform is suited for a high-load mission-critical MySQL server is determined by the following factors: * General stability of the thread library. A platform may have excellent reputation otherwise, but if the thread library is unstable in the code that is called by MySQL, even if everything else is perfect, MySQL will be only as stable as the thread library. * The ability of the kernel and/or thread library to take advantage of SMP on multi-processor systems. In other words, when a process creates a thread, it should be possible for that thread to run on a different CPU than the original process. * The ability of the kernel and/or the thread library to run many threads which acquire/release a mutex over a short critical region frequently without excessive context switches. In other words, if the implementation of pthread_mutex_lock() is too anxious to yield CPU time, this will hurt MySQL  2.2.2 Operating Systems Supported by MySQL 2.2.2 Operating Systems Supported by MySQL2.6.6.4 IBM-AIX notes2.6.6.4 IBM-AIX notes2.6.4.5 BSD/OS Version 2.x Notes2.6.4.5 BSD/OS Version 2.x Notes2.6.4.5 BSD/OS Version 2.x Notes2.6.4.5 BSD/OS Version 2.x Notes2.6.6.6 Alpha-DEC-UNIX Notes (Tru64)2.6.6.6 Alpha-DEC-UNIX Notes (Tru64)2.6.4.1 FreeBSD Notes2.6.4.1 FreeBSD Notes2.6.4.1 FreeBSD Notes2.6.4.1 FreeBSD Notes2.6.6.2 HP-UX Version 10.20 Notes2.6.6.2 HP-UX Version 10.20 Notes2.6.6.3 HP-UX Version 11.x Notes2.6.6.3 HP-UX Version 11.x Notes2.6.1 Linux Notes (All Linux Versions)2.6.1 Linux Notes (All Linux Versions)2.6.5 Mac OS X Notes2.6.5 Mac OS X Notes2.6.4.2 NetBSD notes2.6.4.2 NetBSD notes2.6.4.3 OpenBSD 2.5 Notes2.6.4.3 OpenBSD 2.5 Notes2.6.7 OS/2 Notes2.6.7 OS/2 Notes2.6.6.8 SGI Irix Notes2.6.6.8 SGI Irix Notes2.6.3 Solaris Notes2.6.3 Solaris Notes2.6.3 Solaris Notes2.6.3 Solaris Notes2.6.6.9 Caldera (SCO) Notes2.6.6.9 Caldera (SCO) Notes2.6.6.10 Caldera (SCO) Unixware Version 7.0 Notes2.6.6.10 Caldera (SCO) Unixware Version 7.0 Notes2.6.2 Windows Notes5 tremendously. If this issue is not taken care of, adding extra CPUs will actually make MySQL slower. * General filesystem stability/performance. * Ability of the filesystem to deal with large files at all and deal with them efficiently, if your tables are big. * Our level of expertise here at MySQL AB with the platform. If we know a platform well, we introduce platform-specific optimisations/fixes enabled at compile time. We can also provide advice on configuring your system optimally for MySQL. * The amount of testing of similar configurations we have done internally. * The number of users that have successfully run MySQL on that platform in similar configurations. If  this number is high, the chances of hitting some platform-specific surprises are much smaller.  Based on the preceding criteria, the best platforms for running MySQL at this point are x86 with SuSE Linux 7.1, 2.4 kernel, and ReiserFS (or any similar Linux distribution) and SPARC with Solaris 2.7 or 2.8. FreeBSD comes third, but we really hope it will join the top club once the thread library is improved. We also hope that at some point we will be able to include all other platforms on which MySQL compiles, runs okay, but not quite with the same level of stability and performance, into the top category. This will require some effort on our part in cooperation with the developers of the OS/library components MySQL depends upon. If you are interested in making one of those components better, are in a position to influence their development, and need more detailed instructions on what MySQL needs to run better, send an e-mail to internals@lists.mysql.com.  Please note that the preceding comparison is not to say that one OS is better or worse than the other in general. We are talking about choosing a particular OS for a dedicated purpose@-running MySQL, and compare platforms in that regard only. With this in mind, the result of this comparison would be different if we included more issues into it. And in some cases, the reason one OS is better than the other could simply be that we have put forth more effort into testing on and optimising for that particular platform. We are just stating our observations to help you decide on which platform to use MySQL on in your setup.  2.2.3 Which MySQL Version to Use  The first decision to make is whether you want to use the latest development release or the last stable release: Normally, if you are beginning to use MySQL for the first time or trying to port it to some system for which there is no binary distribution, we recommend going with the stable release (currently version 3.23). Note that all MySQL releases are checked with the MySQL benchmarks and an extensive test suite before each release (even the development releases). Otherwise, if you are running an old system and want to upgrade, but don't want to take chances with a non-seamless upgrade, you should upgrade to the latest in the same branch you are using (where only the last version number is newer than yours). We have tried to fix only fatal bugs and make  small, relatively safe changes to that version.  The second decision to make is whether you want to use a source distribution or a binary distribution. In most cases you should probably use a binary distribution, if one exists for your platform, as this generally will be easier to install than a source distribution.  internals@lists.mysql.cominternals@lists.mysql.com 2.2.3 Which MySQL Version to Use6 In the following cases you probably will be better off with a source installation: If you want to install MySQL at some explicit location. (The standard binary distributions are  ``ready to run'' at any place, but you may want to get even more flexibility). * To be able to satisfy different user requirements, we are providing two different binary versions:  one compiled with the non-transactional table handlers (a small, fast binary), and one configured with the most important extended options like transaction-safe tables. Both versions are compiled from the same source distribution. All native MySQL clients can connect to both MySQL versions. The  extended MySQL binary distribution is marked with the -max suffix and is configured with the same  options as mysqld-max. See section 4.7.5 mysqld-max, An Extended mysqld Server. If you want to use e MySQL-Max RPM, you must first install the standard MySQL RPM. * If you want to configure mysqld with some extra features that are not in the standard binary distributions. Here is a list of the most common extra options that you may want to use: + --with-innodb + --with-berkeley-db + --with-raid + --with-libwrap + --with-named-z-lib (This is done for some of the binaries) + --with-debug[=full] * The default binary distribution is normally compiled with support for all character sets and should work on a variety of processors from the same processor family. If you want a faster MySQL server you may want to recompile it with support for only the character sets you need, use a better compiler (like pgcc), or use compiler options that are better optimised for your processor. * If you have found a bug and reported it to the MySQL development team you will probably receive a patch that you need to apply to the source distribution to get the bug fixed. * If you want to read (and/or modify) the C and C++ code that makes up MySQL, you should get a source distribution. The source code is always the ultimate manual. Source distributions also contain more tests and examples than binary distributions.  The MySQL naming scheme uses release numbers that consist of three numbers and a suffix. For example, a release name like mysql-3.21.17-beta is interpreted like this: * The first number (3) describes the file format. All Version 3 releases have the same file format. * The second number (21) is the release level. Normally there are two to choose from. One is the release/stable branch (currently 23) and the other is the development branch (currently 4.0).   both are stable, but the development version may have quirks, may be missing documentation on new features, or may fail to compile on some systems. * The third number (17) is the version number within the release level. This is incremented for each new distribution. Usually you want the latest version for the release level you have chosen. The suffix (beta) indicates the stability level of the release. The possible suffixes are:  + alpha indicates that the release contains some large section of new code that hasn't been 100%  tested. Known bugs (usually there are none) should be documented in the News section. See  section D MySQL Change History. There are also new commands and extensions in most alphareleases. Active development that may involve major code changes can occur on an alpha release, but everything will be tested before doing a release. There should be no known bugs in any MySQL release. + beta means that all new code has been tested. No major new features that could cause corruptionon old code are added. There should be no known bugs. A version changes from alpha to beta when 4.7.5 mysqld-max, An Extended mysqld Server5 tremendously. If this issue is not taken care of, adding extra CPUs will actually make MySQL slower. General filesystem stability/performance. * Ability of the filesystem to deal with large files at all and deal with them efficiently, if your  tables are big. * Our level of expertise here at MySQL AB with the platform. If we know a platform well, we introduce platform-specific optimisations/fixes enabled at compile time. We can also provide advice on configuring your system optimally for MySQL. * The amount of testing of similar configurations we have done internally. * The number of users that have successfully run MySQL on that platform in similar configurations. Ifis number is high, the chances of hitting some platform-specific surprises are much smaller.  Based on the preceding criteria, the best platforms for running MySQL at this point are x86 with SuSE Linux 7.1, 2.4 kernel, and ReiserFS (or any similar Linux distribution) and SPARC with Solaris 2.7 or 2.8. FreeBSD comes third, but we really hope it will join the top club once the thread library is improved. We also hope that at some point we will be able to include all other platforms on which MySQL compiles, runs okay, but not quite with the same level of stability and performance, into the top category. This will require some effort on our part in cooperation with the developers of the OS/library components MySQL depends upon. If you are interested in making one of those components better, are in a position to influence their development, and need more detailed instructions on what MySQL needs to run better, send an e-mail to internals@lists.mysql.com.  Please note that the preceding comparison is not to say that one OS is better or worse than the other in general. We are talking about choosing a particular OS for a dedicated purpose@-running MySQL, and compare platforms in that regard only. With this in mind, the result of this comparison would be different if we included more issues into it. And in some cases, the reason one OS is better than the other could simply be that we have put forth more effort into testing on and optimising for that particular platform. We are just stating our observations to help you decide on which platform to use MySQL on in your setup.  2.2.3 Which MySQL Version to Use  The first decision to make is whether you want to use the latest development release or the last stable release: *, if you are beginning to use MySQL for the first time or trying to port it to some system for which there is no binary distribution, we recommend going with the stable release (currently  version 3.23). Note that all MySQL releases are checked with the MySQL benchmarks and an extensive test suite before each release (even the development releases). Otherwise, if you are running an old system and want to upgrade, but don't want to take chances with a non-seamless upgrade, you should upgrade to the latest in the same branch you are using (where only the last version number is newer than yours). We have tried to fix only fatal bugs and make small, relatively safe changes to that version.  The second decision to make is whether you want to use a source distribution or a binary distribution. In most cases you should probably use a binary distribution, if one exists for your platform, as this generally will be easier to install than a source distribution.   2.2.3 Which MySQL Version to Use 2.2.3 Which MySQL Version to Useinternals@lists.mysql.com6 In the following cases you probably will be better off with a source installation: If you want to install MySQL at some explicit location. (The standard binary distributions are  ``ready to run'' at any place, but you may want to get even more flexibility). * To be able to satisfy different user requirements, we are providing two different binary versions:  one compiled with the non-transactional table handlers (a small, fast binary), and one configured with the most important extended options like transaction-safe tables. Both versions are compiled from the same source distribution. All native MySQL clients can connect to both MySQL versions. The  extended MySQL binary distribution is marked with the -max suffix and is configured with the same  options as mysqld-max. See section 4.7.5 mysqld-max, An Extended mysqld Server. If you want to use e MySQL-Max RPM, you must first install the standard MySQL RPM. * If you want to configure mysqld with some extra features that are not in the standard binary distributions. Here is a list of the most common extra options that you may want to use: + --with-innodb + --with-berkeley-db + --with-raid + --with-libwrap + --with-named-z-lib (This is done for some of the binaries) + --with-debug[=full] * The default binary distribution is normally compiled with support for all character sets and should work on a variety of processors from the same processor family. If you want a faster MySQL server you may want to recompile it with support for only the character sets you need, use a better compiler (like pgcc), or use compiler options that are better optimised for your processor. * If you have found a bug and reported it to the MySQL development team you will probably receive a patch that you need to apply to the source distribution to get the bug fixed. * If you want to read (and/or modify) the C and C++ code that makes up MySQL, you should get a source distribution. The source code is always the ultimate manual. Source distributions also contain more tests and examples than binary distributions.  The MySQL naming scheme uses release numbers that consist of three numbers and a suffix. For example, a release name like mysql-3.21.17-beta is interpreted like this: * The first number (3) describes the file format. All Version 3 releases have the same file format. * The second number (21) is the release level. Normally there are two to choose from. One is the release/stable branch (currently 23) and the other is the development branch (currently 4.0).   both are stable, but the development version may have quirks, may be missing documentation on new features, or may fail to compile on some systems. * The third number (17) is the version number within the release level. This is incremented for each new distribution. Usually you want the latest version for the release level you have chosen. The suffix (beta) indicates the stability level of the release. The possible suffixes are:  + alpha indicates that the release contains some large section of new code that hasn't been 100%  tested. Known bugs (usually there are none) should be documented in the News section. See  section D MySQL Change History. There are also new commands and extensions in most alphareleases. Active development that may involve major code changes can occur on an alpha release, but everything will be tested before doing a release. There should be no known bugs in any MySQL release. + beta means that all new code has been tested. No major new features that could cause corruptionon old code are added. There should be no known bugs. A version changes from alpha to beta when 4.7.5 mysqld-max, An Extended mysqld Server7 there haven't been any reported fatal bugs within an alpha version for at least a month and we  don't plan to add any features that could make any old command more unreliable.  + gamma is a beta that has been around a while and seems to work fine. Only minor fixes are  added. This is what many other companies call a release.  + If there is no suffix, it means that the version has been run for a while at many different  sites with no reports of bugs other than platform-specific bugs. Only critical bug fixes are  applied to the release. This is what we call a stable release.  All versions of MySQL are run through our standard tests and benchmarks to ensure that they are relatively safe to use. Because the standard tests are extended over time to check for all previously found bugs, the test suite keeps getting better.  Note that all releases have been tested at least with: An internal test suite This is part of a production system for a customer. It has many tables with hundreds of megabytesof data. The MySQL benchmark suiteThis runs a range of common queries. It is also a test to see whether the latest batch of  optimisations actually made the code faster. See section 5.1.4 The MySQL Benchmark Suite. The crash-me test  This tries to determine what features the database supports and what its capabilities and  limitations are. See section 5.1.4 The MySQL Benchmark Suite.  Another test is that we use the newest MySQL version in our internal production environment, on at least one machine. We have more than 100 gigabytes of data to work with.  2.2.4 Installation Layouts is section describes the default layout of the directories created by installing binary and source distributions.  A binary distribution is installed by unpacking it at the installation location you choose (typically `/usr/local/mysql') and creates the following directories in that location:  Directory Contents of directory `bin' Client programs and the mysqld server `data' Log files, databases `include' Include (header) files `lib' Libraries `scripts' mysql_install_db `share/mysql' Error message files `sql-bench' Benchmarks  A source distribution is installed after you configure and compile it. By default, the installation step installs files under `/usr/local', in the following subdirectories:  5.1.4 The MySQL Benchmark Suite8 Directory Contents of directory `bin' Client programs and scripts `include/mysql' Include (header) files `info' Documentation in Info format `lib/mysql' Libraries `libexec' The mysqld server `share/mysql' Error message files `sql-bench' Benchmarks and crash-me test `var' Databases and log files  Within an installation directory, the layout of a source installation differs from that of a binary installation in the following ways: * The mysqld server is installed in the `libexec' directory rather than in the `bin' directory. * The data directory is `var' rather than `data'. * mysql_install_db is installed in the `/usr/local/bin' directory rather than in `/usr/local/mysql/scripts'. * The header file and library directories are `include/mysql' and `lib/mysql' rather than `include' and `lib'.  You can create your own binary installation from a compiled source distribution by executing the script `scripts/make_binary_distribution'.  2.2.5 How and When Updates Are Released  MySQL is evolving quite rapidly here at MySQL AB and we want to share this with other MySQL users. We try to make a release when we have very useful features that others seem to have a need for.  We also try to help out users who request features that are easy to implement. We take note of what our licensed users want to have, and we especially take note of what our extended e-mail supported customers want and try to help them out. No one has to download a new release. The News section will tell you if the new release has something you really want. See section D MySQL Change History. We use the following policy when updating MySQL: * For each minor update, the last number in the version string is incremented. When there are major new features or minor incompatibilities with previous versions, the second number in the version string is incremented. When the file format changes, the first number is increased. * Stable-tested releases are meant to appear about 1-2 times a year, but if small bugs are found, a release with only bug fixes will be released. * Working releases/bug fixes to old releases are meant to appear about every 1-8 weeks. * Binary distributions for some platforms will be made by us for major releases. Other people may make binary distributions for other systems but probably less frequently. * We usually make patches available as soon as we have located and fixed small bugs. They are posted to bugs@lists.mysql.com and will be added to the next release. * For non-critical but annoying bugs, we will add them the MySQL source repository and they will be  2.2.5 How and When Updates Are Released9 fixed in the next release. * If there is, by any chance, a fatal bug in a release we will make a new release as soon as possible. We would like other companies to do this, too.  The current stable release is Version 3.23; we have already moved active development to Version 4.0. Bugs will still be fixed in the stable version. We don't believe in a complete freeze, as this also leaves out bug fixes and things that ``must be done.'' ``Somewhat frozen'' means that we may add small things that ``almost surely will not affect anything that's already working.''  MySQL uses a slightly different naming scheme from most other products. In general it's relatively safe to use any version that has been out for a couple of weeks without being replaced with a new version. See section 2.2.3 Which MySQL Version to Use.  2.2.6 MySQL Binaries Compiled by MySQL AB  As a service, we at MySQL AB provide a set of binary distributions of MySQL that are compiled at our site or at sites where customers kindly have given us access to their machines.  These distributions are generated with scripts/make_binary_distribution and are configured with the following compilers and options: SunOS 4.1.4 2 sun4c with gcc 2.7.2.1CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" ./configure --prefix=/usr/local/mysql --disable-shared --with-extra-charsets=complex --enable-assembler SunOS 5.5.1 (and above) sun4u with egcs 1.0.3a or 2.90.27 or gcc 2.95.2 and newer CC=gcc CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex--enable-assembler SunOS 5.6 i86pc with gcc 2.8.1 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex Solaris 2.8 sparc with gcc 2.95.3 CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql"--with-comment=Official MySQL binary" --with-extra-charsets=complex "--with-server-suffix=" --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared Linux 2.0.33 i386 with pgcc 2.90.29 (egcs 1.0.3a)  CFLAGS="-O3 -mpentium -mstack-align-double" CXX=gcc CXXFLAGS="-O3 -mpentium -mstack-align-double  -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql  --enable-assembler --with-mysqld-ldflags=-all-static --with-extra-charsets=complex Linux 2.2.xx686 with gcc 2.95.2  CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions  -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler  --with-mysqld-ldflags=-all-static --disable-shared --with-extra-charset=complex SCO 3.2v5.0.4 i386 with gcc 2.7-95q4  CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex AIX 2 4 with gcc 2.7.2.2 2.2.3 Which MySQL Version to Use70  CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex OSF/1 V4.0 564 alpha with gcc 2.8.1  CC=gcc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory--with-extra-charsets=complex Irix 6.3 IP32 with gcc 2.8.0 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 3.1 i386 with gcc 2.7.2.1 CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 2.1 i386 with gcc 2.7.2 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex FreeBSD 4.4-stable i386 with gcc 2.95.3 CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer-felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql "--with-comment=Official MySQL binary" --with-extra-charsets=complex "--with-server-suffix="--enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared  Anyone who has more optimal options for any of the preceding configurations listed can always mail them to the developer's mailing list at internals@lists.mysql.com.  RPM distributions prior to MySQL Version 3.22 are user-contributed. Beginning with Version 3.22, the RPMs are generated by us at MySQL AB.  If you want to compile a debug version of MySQL, you should add --with-debug or --with-debug=full to the preceding configure lines and remove any -fomit-frame-pointer options.  For the Windows distribution, please see section 2.1.2 Installing MySQL on Windows.  2.2.7 Installing a MySQL Binary Distribution  See also section 2.1.2.1 Installing the Binaries, section 2.1.1 Installing MySQL on Linux, and section 8.4.7 Building Client Programs.  You need the following tools to install a MySQL binary distribution: * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have problems.  An alternative installation method under Linux is to use RPM (RedHat Package Manager) distributions. See section 2.1.1 Installing MySQL on Linux.  If you run into problems, please always use mysqlbug when posting questions to mysql@lists.mysql.com. Even if the problem isn't a bug, mysqlbug gathers system information that will help others solve your problem. By not using mysqlbug, you lessen the likelihood of getting a solution to your problem! You will find mysqlbug in the `bin' directory after you unpack the distribution. See section 1.6.2.3 How to Report Bugs or Problems. internals@lists.mysql.cominternals@lists.mysql.com2.1.2 Installing MySQL on Windows2.1.2 Installing MySQL on Windows 2.2.7 Installing a MySQL Binary Distribution 2.2.7 Installing a MySQL Binary Distribution2.1.2.1 Installing the Binaries2.1.2.1 Installing the Binaries2.1.1 Installing MySQL on Linux2.1.1 Installing MySQL on Linux 8.4.7 Building Client Programs 8.4.7 Building Client Programs2.1.1 Installing MySQL on Linux2.1.1 Installing MySQL on Linuxmysql@lists.mysql.commysql@lists.mysql.com1.6.2.3 How to Report Bugs or Problems 1  The basic commands you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or shell> bin/mysqld_safe --user=mysql & if you are running MySQL 4.x You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules. A more detailed description follows.  To install a binary distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation setup and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. In the following example, we unpack the distribution under `/usr/local' and create a directory `/usr/local/mysql' into which MySQL is installed. (The following instructions, therefore, assume you have permission to create files in `/usr/local'. If that directory is protected, you will need to perform the installation as root.) 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. MySQL binary distributions are provided as compressed tar archives and have names like `mysql-VERSION-OS.tar.gz', where VERSION is a number (for example, 3.21.15), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-gnu-i586). 3. If you see a binary distribution marked with the -max suffix, this means that the binary has support  for transaction-safe tables and other features. See section 4.7.5 mysqld-max, An Extended mysqld  Server. Note that all binaries are built from the same MySQL source distribution. 4. Add a user and group for mysqld to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Change into the intended installation directory: shell> cd /usr/local 6. Unpack the distribution and create the installation directory: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - 2.4 Post-installation Setup and Testing0CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex OSF/1 V4.0 564 alpha with gcc 2.8.1 CC=gcc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex Irix 6.3 IP32 with gcc 2.8.0 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 3.1 i386 with gcc 2.7.2.1 CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 2.1 i386 with gcc 2.7.2 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex FreeBSD 4.4-stable i386 with gcc 2.95.3 CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql "--with-comment=Official MySQL binary" --with-extra-charsets=complex "--with-server-suffix=" --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared Anyone who has more optimal options for any of the preceding configurations listed can always mail them to the developer's mailing list at internals@lists.mysql.com. RPM distributions prior to MySQL Version 3.22 are user-contributed. Beginning with Version 3.22, the RPMs are generated by us at MySQL AB.  If you want to compile a debug version of MySQL, you should add --with-debug or --with-debug=full to the preceding configure lines and remove any -fomit-frame-pointer options.  For the Windows distribution, please see section 2.1.2 Installing MySQL on Windows.  2.2.7 Installing a MySQL Binary Distribution  See also section 2.1.2.1 Installing the Binaries, section 2.1.1 Installing MySQL on Linux, and section 8.4.7 Building Client Programs.  You need the following tools to install a MySQL binary distribution: * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have  problems.  An alternative installation method under Linux is to use RPM (RedHat Package Manager) distributions. See section 2.1.1 Installing MySQL on Linux.  If you run into problems, please always use mysqlbug when posting questions to mysql@lists.mysql.com. Even if the problem isn't a bug, mysqlbug gathers system information that will help others solve your problem. By not using mysqlbug, you lessen the likelihood of getting a solution to your problem! You will find mysqlbug in the `bin' directory after you unpack the distribution. See section 1.6.2.3 How to  Report Bugs or Problems. 1.6.2.3 How to Report Bugs or Problems MySQL Reference Manual for version 4.0.3-beta. (p60 of 660) The basic commands you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or shell> bin/mysqld_safe --user=mysql & if you are running MySQL 4.x You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules. A more detailed description follows. To install a binary distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation setup and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. In the following example, we unpack the distribution under `/usr/local' and create a directory `/usr/local/mysql' into which MySQL is installed. (The following instructions, therefore, assume you have permission to create files in `/usr/local'. If that directory is protected, you will need to perform the installation as root.) 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. MySQL binary distributions are provided as compressed tar archives and have names like `mysql-VERSION-OS.tar.gz', where VERSION is a number (for example, 3.21.15), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-gnu-i586). 3. If you see a binary distribution marked with the -max suffix, this means that the binary has support for transaction-safe tables and other features. See section 4.7.5 mysqld-max, An Extended mysqld Server. Note that all binaries are built from the same MySQL source distribution. 4. Add a user and group for mysqld to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Change into the intended installation directory: shell> cd /usr/local 6. Unpack the distribution and create the installation directory: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql The first command creates a directory named `mysql-VERSION-OS'. The second command makes a symbolic link to that directory. This lets you refer more easily to the installation directory as `/usr/local/mysql'. 7. Change into the installation directory: shell> cd mysql You will find several files and subdirectories in the mysql directory. The most important for installation purposes are the `bin' and `scripts' subdirectories. Arrow keys: Up and Down to move. Right to follow a link; Left to go back. H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list -- press space for next page --2.4 Post-installation Setup and Testing59--enable-assembler --with-mysqld-ldflags=-all-static --with-extra-charsets=complex Linux 2.2.x with x686 with gcc 2.95.2 CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler --with-mysqld-ldflags=-all-static --disable-shared --with-extra-charset=complex SCO 3.2v5.0.4 i386 with gcc 2.7-95q4 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex AIX 2 4 with gcc 2.7.2.2 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex OSF/1 V4.0 564 alpha with gcc 2.8.1 CC=gcc CFLAGS=-O CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charsets=complex Irix 6.3 IP32 with gcc 2.8.0 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 3.1 i386 with gcc 2.7.2.1 CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex BSDI BSD/OS 2.1 i386 with gcc 2.7.2 CC=gcc CXX=gcc CXXFLAGS=-O3 ./configure --prefix=/usr/local/mysql --with-extra-charsets=complex FreeBSD 4.4-stable i386 with gcc 2.95.3CC=gcc CFLAGS="-O3 -fno-omit-frame-pointer" CXX=gcc CXXFLAGS="-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local/mysql"--with-comment=Official MySQL binary" --with-extra-charsets=complex "--with-server-suffix=" --enable-thread-safe-client --enable-local-infile --enable-assembler --with-named-z-libs=not-used --disable-shared  Anyone who has more optimal options for any of the preceding configurations listed can always mail them to the developer's mailing list at internals@lists.mysql.com.  RPM distributions prior to MySQL Version 3.22 are user-contributed. Beginning with Version 3.22, the RPMs are generated by us at MySQL AB.  If you want to compile a debug version of MySQL, you should add --with-debug or --with-debug=full to the preceding configure lines and remove any -fomit-frame-pointer options.  For the Windows distribution, please see section 2.1.2 Installing MySQL on Windows.  2.2.7 Installing a MySQL Binary Distribution  See also section 2.1.2.1 Installing the Binaries, section 2.1.1 Installing MySQL on Linux, and section 8.4.7 Building Client Programs.  You need the following tools to install a MySQL binary distribution:  * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have  problems.  An alternative installation method under Linux is to use RPM (RedHat Package Manager) distributions. See section 2.1.1 Installing MySQL on Linux.  If you run into problems, please always use mysqlbug when posting questions to mysql@lists.mysql.com. Even if the problem isn't a bug, mysqlbug gathers system information that will help others solve your problem. By not using mysqlbug, you lessen the likelihood of getting a solution to your problem! You will find mysqlbug in the `bin' directory after you unpack the distribution. See section 1.6.2.3 How to Report Bugs or Problems. 1.6.2.3 How to Report Bugs or Problems 60  The basic commands you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or shell> bin/mysqld_safe --user=mysql & if you are running MySQL 4.x  You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules.  A more detailed description follows.  To install a binary distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation setup and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. In the following example, we unpack the distribution under `/usr/local' and create a directory `/usr/local/mysql' into which MySQL is installed. (The following instructions, therefore, assume you have permission to create files in `/usr/local'. If that directory is protected, you will need to perform the installation as root.) 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. MySQL binary distributions are provided as compressed tar archives and have names like `mysql-VERSION-OS.tar.gz', where VERSION is a number (for example, 3.21.15), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-gnu-i586). 3. If you see a binary distribution marked with the -max suffix, this means that the binary has support for transaction-safe tables and other features. See section 4.7.5 mysqld-max, An Extended mysqld Server. Note that all binaries are built from the same MySQL source distribution. 4. Add a user and group for mysqld to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Change into the intended installation directory: shell> cd /usr/local 6. Unpack the distribution and create the installation directory: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql The first command creates a directory named `mysql-VERSION-OS'. The second command makes a symbolic link to that directory. This lets you refer more easily to the installation directory as `/usr/local/mysql'. 7. Change into the installation directory: shell> cd mysql You will find several files and subdirectories in the mysql directory. The most important for installation purposes are the `bin' and `scripts' subdirectories. 2.4 Post-installation Setup and Testing2.4 Post-installation Setup and Testing2.2.1 How to Get MySQL2.2.1 How to Get MySQL4.7.5 mysqld-max, An Extended mysqld ServerMMMMMM1`bin' This directory contains client programs and the server You should add the full pathname ofthis directory to your PATH environment variable so that your shell finds the MySQL programsproperly. See section F Environment Variables.`scripts' This directory contains the mysql_install_db script used to initialise the mysql databasecontaining the grant tables that store the server access permissions. 8. If you would like to use mysqlaccess and have the MySQL distribution in some non-standard place, you must change the location where mysqlaccess expects to find the mysql client. Edit the `bin/mysqlaccess' script at approximately line 18. Search for a line that looks like this: $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable Change the path to reflect the location where mysql actually is stored on your system. If you do not do this, you will get a Broken pipe error when you run mysqlaccess. 9. Create the MySQL grant tables (necessary only if you haven't installed MySQL before): Note that MySQL versions older than Version 3.22.10 started the MySQL server when you run mysql_install_db. This is no longer true! 10. Change ownership of binaries to root and ownership of the data directory to the user that you will run mysqld as: shell> chown -R root /usr/local/mysql/. shell> chown -R mysql /usr/local/mysql/data shell> chgrp -R mysql /usr/local/mysql/. The first command changes the owner attribute of the files to the root user, the second one changes the owner attribute of the data directory to the mysql user, and the third one changes the group  attribute to the mysql group. 11. If you want to install support for the Perl DBI/DBD interface, see section 2.7 Perl Installation Comments. 12. If you would like MySQL to start automatically when you boot your machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information  can be found in the support-files/mysql.server script itself and in section 2.4.3 Starting and Stopping MySQL Automatically.  After everything has been unpacked and installed, you should initialise and test your distribution.  You can start the MySQL server with the following command: shell> bin/safe_mysqld --user=mysql &  Now proceed to section 4.7.2 safe_mysqld, The Wrapper Around mysqld, and See section 2.4  Post-installation Setup and Testing.  2.3 Installing a MySQL Source Distribution  Before you proceed with the source installation, check first to see if our binary is available for your platform and if it will work for you. We put a lot of effort into making sure that our binaries are built with the best possible options.  You need the following tools to build and install MySQL from source: * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have problems.  * A working ANSI C++ compiler. gcc >= 2.95.2, egcs >= 1.0.2 or egcs 2.91.66, SGI C++, and SunPro C++ are some of the compilers that are known to work. libg++ is not needed when using gcc. gcc 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you only have gcc 2.7.x, you must upgrade your gcc to be able to compile MySQL. gcc 2.8.1 is also F Environment VariablesF Environment Variables2.7 Perl Installation Comments2.7 Perl Installation CommentsF Environment Variables0  The basic commands you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or bin/mysqld_safe --user=mysql & if you are running MySQL 4.x  You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules.  A more detailed description follows.  To install a binary distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation setup and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. In the following example, we unpack the distribution under `/usr/local' and create a directory `/usr/local/mysql' into which MySQL is installed. (The following instructions, therefore, assume you have permission to create files in `/usr/local'. If that directory is protected, you will need to perform the installation as root.) 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. MySQL binary distributions are provided as compressed tar archives and have names like `mysql-VERSION-OS.tar.gz', where VERSION is a number (for example, 3.21.15), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-gnu-i586). 3. If you see a binary distribution marked with the -max suffix, this means that the binary has support for transaction-safe tables and other features. See section 4.7.5 mysqld-max, An Extended mysqld  Server. Note that all binaries are built from the same MySQL source distribution. 4. Add a user and group for mysqld to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Change into the intended installation directory: shell> cd /usr/local 6. Unpack the distribution and create the installation directory: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql  The first command creates a directory named `mysql-VERSION-OS'. The second command makes a symbolic  link to that directory. This lets you refer more easily to the installation directory as `/usr/local/mysql'. 7. Change into the installation directory: shell> cd mysql You will find several files and subdirectories in the mysql directory. The most important for installation purposes are the `bin' and `scripts' subdirectories. 4.7.5 mysqld-max, An Extended mysqld ServerMMMMMM1`bin' This directory contains client programs and the server You should add the full pathname ofthis directory to your PATH environment variable so that your shell finds the MySQL programsproperly. See section F Environment Variables.`scripts' This directory contains the mysql_install_db script used to initialise the mysql databasecontaining the grant tables that store the server access permissions. 8. If you would like to use mysqlaccess and have the MySQL distribution in some non-standard place, you must change the location where mysqlaccess expects to find the mysql client. Edit the `bin/mysqlaccess' script at approximately line 18. Search for a line that looks like this: $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable Change the path to reflect the location where mysql actually is stored on your system. If you do not do this, you will get a Broken pipe error when you run mysqlaccess. 9. Create the MySQL grant tables (necessary only if you haven't installed MySQL before): Note that MySQL versions older than Version 3.22.10 started the MySQL server when you run mysql_install_db. This is no longer true! 10. Change ownership of binaries to root and ownership of the data directory to the user that you will run mysqld as: shell> chown -R root /usr/local/mysql/. shell> chown -R mysql /usr/local/mysql/data shell> chgrp -R mysql /usr/local/mysql/. The first command changes the owner attribute of the files to the root user, the second one changes the owner attribute of the data directory to the mysql user, and the third one changes the group  attribute to the mysql group. 11. If you want to install support for the Perl DBI/DBD interface, see section 2.7 Perl Installation Comments. 12. If you would like MySQL to start automatically when you boot your machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information  can be found in the support-files/mysql.server script itself and in section 2.4.3 Starting and Stopping MySQL Automatically.  After everything has been unpacked and installed, you should initialise and test your distribution.  You can start the MySQL server with the following command: shell> bin/safe_mysqld --user=mysql &  Now proceed to section 4.7.2 safe_mysqld, The Wrapper Around mysqld, and See section 2.4  Post-installation Setup and Testing.  2.3 Installing a MySQL Source Distribution  Before you proceed with the source installation, check first to see if our binary is available for your platform and if it will work for you. We put a lot of effort into making sure that our binaries are built with the best possible options.  You need the following tools to build and install MySQL from source: * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have problems.  * A working ANSI C++ compiler. gcc >= 2.95.2, egcs >= 1.0.2 or egcs 2.91.66, SGI C++, and SunPro C++ are some of the compilers that are known to work. libg++ is not needed when using gcc. gcc 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you only have gcc 2.7.x, you must upgrade your gcc to be able to compile MySQL. gcc 2.8.1 is also F Environment Variables0  The basic commands you must execute to install and use a MySQL binary distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db shell> chown -R root . shell> chown -R mysql data shell> chgrp -R mysql . shell> bin/safe_mysqld --user=mysql & or bin/mysqld_safe --user=mysql & if you are running MySQL 4.x  You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules.  A more detailed description follows.  To install a binary distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation setup and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. In the following example, we unpack the distribution under `/usr/local' and create a directory `/usr/local/mysql' into which MySQL is installed. (The following instructions, therefore, assume you have permission to create files in `/usr/local'. If that directory is protected, you will need to perform the installation as root.) 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. MySQL binary distributions are provided as compressed tar archives and have names like `mysql-VERSION-OS.tar.gz', where VERSION is a number (for example, 3.21.15), and OS indicates the type of operating system for which the distribution is intended (for example, pc-linux-gnu-i586). 3. If you see a binary distribution marked with the -max suffix, this means that the binary has support for transaction-safe tables and other features. See section 4.7.5 mysqld-max, An Extended mysqld  Server. Note that all binaries are built from the same MySQL source distribution. 4. Add a user and group for mysqld to run as: shell> groupadd mysql shell> useradd -g mysql mysql These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Change into the intended installation directory: shell> cd /usr/local 6. Unpack the distribution and create the installation directory: shell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf - shell> ln -s full-path-to-mysql-VERSION-OS mysql  The first command creates a directory named `mysql-VERSION-OS'. The second command makes a symbolic  link to that directory. This lets you refer more easily to the installation directory as `/usr/local/mysql'. 7. Change into the installation directory: shell> cd mysql You will find several files and subdirectories in the mysql directory. The most important for installation purposes are the `bin' and `scripts' subdirectories. 4.7.5 mysqld-max, An Extended mysqld Server4.7.5 mysqld-max, An Extended mysqld Server2.2.1 How to Get MySQLMMMMMM1`bin' This directory contains client programs and the server You should add the full pathname ofthis directory to your PATH environment variable so that your shell finds the MySQL programsproperly. See section F Environment Variables.`scripts' This directory contains the mysql_install_db script used to initialise the mysql databasecontaining the grant tables that store the server access permissions. 8. If you would like to use mysqlaccess and have the MySQL distribution in some non-standard place, you must change the location where mysqlaccess expects to find the mysql client. Edit the `bin/mysqlaccess' script at approximately line 18. Search for a line that looks like this: $MYSQL = '/usr/local/bin/mysql'; # path to mysql executable Change the path to reflect the location where mysql actually is stored on your system. If you do not do this, you will get a Broken pipe error when you run mysqlaccess. 9. Create the MySQL grant tables (necessary only if you haven't installed MySQL before): Note that MySQL versions older than Version 3.22.10 started the MySQL server when you run mysql_install_db. This is no longer true! 10. Change ownership of binaries to root and ownership of the data directory to the user that you will run mysqld as: shell> chown -R root /usr/local/mysql/. shell> chown -R mysql /usr/local/mysql/data shell> chgrp -R mysql /usr/local/mysql/. The first command changes the owner attribute of the files to the root user, the second one changes the owner attribute of the data directory to the mysql user, and the third one changes the group  attribute to the mysql group. 11. If you want to install support for the Perl DBI/DBD interface, see section 2.7 Perl Installation Comments. 12. If you would like MySQL to start automatically when you boot your machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information  can be found in the support-files/mysql.server script itself and in section 2.4.3 Starting and Stopping MySQL Automatically.  After everything has been unpacked and installed, you should initialise and test your distribution.  You can start the MySQL server with the following command: shell> bin/safe_mysqld --user=mysql &  Now proceed to section 4.7.2 safe_mysqld, The Wrapper Around mysqld, and See section 2.4  Post-installation Setup and Testing.  2.3 Installing a MySQL Source Distribution  Before you proceed with the source installation, check first to see if our binary is available for your platform and if it will work for you. We put a lot of effort into making sure that our binaries are built with the best possible options.  You need the following tools to build and install MySQL from source: * GNU gunzip to uncompress the distribution. * A reasonable tar to unpack the distribution. GNU tar is known to work. Sun tar is known to have problems.  * A working ANSI C++ compiler. gcc >= 2.95.2, egcs >= 1.0.2 or egcs 2.91.66, SGI C++, and SunPro C++ are some of the compilers that are known to work. libg++ is not needed when using gcc. gcc 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you only have gcc 2.7.x, you must upgrade your gcc to be able to compile MySQL. gcc 2.8.1 is also F Environment VariablesF Environment Variables2.7 Perl Installation Comments2.7 Perl Installation Comments2.4.3 Starting and Stopping MySQL Automatically2.4.3 Starting and Stopping MySQL Automatically4.7.2 safe_mysqld, The Wrapper Around mysqld4.7.2 safe_mysqld, The Wrapper Around mysqld2.4 Post-installation Setup and Testing2.4 Post-installation Setup and Testing2.3 Installing a MySQL Source Distribution2 known to have problems on some platforms, so it should be avoided if a new compiler exists for the platform. gcc >= 2.95.2 is recommended when compiling MySQL Version 3.23.x. * A good make program. GNU make is always recommended and is sometimes required. If you have problems, we recommend trying GNU make 3.75 or newer.  If you are using a recent version of gcc, recent enough to understand the -fno-exceptions option, it is very important that you use it. Otherwise, you may compile a binary that crashes randomly. We also recommend that you use -felide-constructors and -fno-rtti along with -fno-exceptions. When in doubt, do the following:  CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions \ -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static  On most systems this will give you a fast and stable binary.  If you run into problems, please always use mysqlbug when posting questions to mysql@lists.mysql.com. Even if the problem isn't a bug, mysqlbug gathers system information that will help others solve your problem. By not using mysqlbug, you lessen the likelihood of getting a solution to your problem! You will find mysqlbug in the `scripts' directory after you unpack the distribution. See section 1.6.2.3 How  to Report Bugs or Problems.  2.3.1 Quick Installation Overview  The basic commands you must execute to install a MySQL source distribution are: shell> groupadd mysql shell> useradd -g mysql mysql shell> gunzip < mysql-VERSION.tar.gz | tar -xvf - shell> cd mysql-VERSION shell> ./configure --prefix=/usr/local/mysql shell> make shell> make install shell> scripts/mysql_install_db shell> chown -R root /usr/local/mysql shell> chown -R mysql /usr/local/mysql/var chgrp -R mysql /usr/local/mysql shell> cp support-files/my-medium.cnf /etc/my.cnf shell> /usr/local/mysql/bin/safe_mysqld --user=mysql & or shell> /usr/local/mysql/bin/mysqld_safe --user=mysql & if you are running MySQL 4.x. If you want to have support for InnoDB tables, you should edit the /etc/my.cnf file and remove the # character before the parameter that starts with innodb_.... See section 4.1.2 `my.cnf' Option Files, and section 7.5.2 InnoDB Startup Options If you start from a source RPM, do the following: shell> rpm --rebuild MySQL-VERSION.src.rpm  This will make a binary RPM that you can install.  You can add new users using the bin/mysql_setpermission script if you install the DBI and Msql-Mysql-modules Perl modules.  mysql@lists.mysql.com  3 A more detailed description follows.  To install a source distribution, follow these steps, then proceed to section 2.4 Post-installation Setup and Testing, for post-installation initialisation and testing: 1. Pick the directory under which you want to unpack the distribution, and move into it. 2. Obtain a distribution file from one of the sites listed in section 2.2.1 How to Get MySQL. 3. If you are interested in using Berkeley DB tables with MySQL, you will need to obtain a patched version of the Berkeley DB source code. Please read the chapter on Berkeley DB tables before proceeding. See section 7.6 BDB or BerkeleyDB Tables. MySQL source distributions are provided as compressed tar archives and have names like `mysql-VERSION.tar.gz', where VERSION is a number like 4.0.3-beta. 4. Add a user and group for mysqld to run as: These commands add the mysql group and the mysql user. The syntax for useradd and groupadd may differ slightly on different versions of Unix. They may also be called adduser and addgroup. You may wish to call the user and group something else instead of mysql. 5. Unpack the distribution into the current directory: shell> gunzip < /path/to/mysql-VERSION.tar.gz | tar xvf - This command creates a directory named `mysql-VERSION'. 6. Change into the top-level directory of the unpacked distribution: Note that currently you must configure and build MySQL from this top-level directory. You cannot build it in a different directory. 7. Configure the release and compile everything: ./configure --prefix=/usr/local/mysql shell> make When you run configure, you might want to specify some options. Run ./configure --help for a list of options. section 2.3.3 Typical configure Options, discusses some of the more useful options. If configure fails, and you are going to send mail to mysql@lists.mysql.com to ask for assistance, please include any lines from `config.log' that you think can help solve the problem. Also include the last couple of lines of output from configure if configure aborts. Post the bug report using the mysqlbug script. See section 1.6.2.3 How to Report Bugs or Problems. If the compile fails, see section 2.3.5 Problems Compiling?, for help with a number of common problems. 8. Install everything: make install You might need to run this command as root. 9. Create the MySQL grant tables (necessary only if you haven't installed MySQL before): shell> scripts/mysql_install_db Note that MySQL versions older than Version 3.22.10 started the MySQL server when you run mysql_install_db. This is no longer true! 10. Change ownership of binaries to root and ownership of the data directory to the user that you will run mysqld as: shell> chown -R root /usr/local/mysql shell> chown -R mysql /usr/local/mysql/var shell> chgrp -R mysql /usr/local/mysql The first command changes the owner attribute of the files to the root user, the second one changes the owner attribute of the data directory to the mysql user, and the third one changes the group attribute to the mysql group. 11. If you want to install support for the Perl DBI/DBD interface, see section 2.7 Perl Installation Comments. 12. If you would like MySQL to start automatically when you boot your machine, you can copy support-files/mysql.server to the location where your system has its startup files. More information can be found in the support-files/mysql.server script itself and in section 2.4.3 Starting and   2.4 Post-installation Setup and Testing4 Stopping MySQL Automatically. After everything has been installed, you should initialise and test your distribution: shell> /usr/local/mysql/bin/safe_mysqld --user=mysql &  If that command fails immediately with mysqld daemon ended, you can find some information in the file `mysql-data-directory/'hostname'.err'. The likely reason is that you already have another mysqld server running. See section 4.1.4 Running Multiple MySQL Servers on the Same Machine.  Now proceed to section 2.4 Post-installation Setup and Testing.  2.3.2 Applying Patches  Sometimes patches appear on the mailing list or are placed in the patches area of the MySQL web site (http://www.mysql.com/Downloads/Patches/).  To apply a patch from the mailing list, save the message in which the patch appears in a file, change into the top-level directory of your MySQL source tree, and run these commands: patch -p1 < patch-file-name shell> rm config.cache shell> make clean  Patches from the FTP site are distributed as plain text files or as files compressed with gzip. Apply a plain patch as shown previously for mailing list patches. To apply a compressed patch, change into the top-level directory of your MySQL source tree and run these commands: gunzip < patch-file-name.gz | patch -p1 rm config.cache shell> make clean  After applying a patch, follow the instructions for a normal source install, beginning with the ./configure step. After running the make install step, restart your MySQL server.  You may need to bring down any currently running server before you run make install. (Use mysqladmin shutdown to do this.) Some systems do not allow you to install a new version of a program if it replaces the version that is currently executing.  2.3.3 Typical configure Options  The configure script gives you a great deal of control over how you configure your MySQL distribution. Typically you do this using options on the configure command-line. You can also affect configure using certain environment variables. See section F Environment Variables. For a list of options supported by configure, run this command: shell> ./configure --help  Some of the more commonly-used configure options are described here: * To compile just the MySQL client libraries and client programs and not the server, use the --without-server option: shell> ./configure --without-server If you don't have a C++ compiler, mysql will not compile (it is the one client program that requires C++). In this case, you can remove the code in configure that tests for the C++ compiler and then run ./configure with the --without-server option. The compile step will still try to build mysql, but you can ignore any warnings about `mysql.cc'. (If make stops, try make -k to tell it to continue with the rest of the build even if errors occur.) * If you want to get an embedded MySQL library (libmysqld.a) you should use the --with-embedded-server 4.1.4 Running Multiple MySQL Servers on the Same Machine5 option. * If you don't want your log files and database directories located under `/usr/local/var', use a configure command, something like one of these: ./configure --prefix=/usr/local/mysql shell> ./configure --prefix=/usr/local \ --localstatedir=/usr/local/mysql/data The first command changes the installation prefix so that everything is installed under `/usr/local/mysql' rather than the default of `/usr/local'. The second command preserves the default installation prefix, but overrides the default location for database directories (normally `/usr/local/var') and changes it to /usr/local/mysql/data. After you have compiled MySQL, you can change these options with option files. See section 4.1.2 `my.cnf' Option Files. * If you are using Unix and you want the MySQL socket located somewhere other than the default location (normally in the directory `/tmp' or `/var/run') use a configure command like this: shell> ./configure --with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock Note that the given file must be an absolute pathname! You can also later change the location `mysql.sock' by using the MySQL option files. See section A.4.5 How to Protect or Change the MySQL  Socket File `/tmp/mysql.sock'. * If you want to compile statically linked programs (for example, to make a binary distribution, to get more speed, or to work around problems with some RedHat Linux distributions), run configure like this: ./configure --with-client-ldflags=-all-static \--with-mysqld-ldflags=-all-static * If you are using gcc and don't have libg++ or libstdc++ installed, you can tell configure to use gcc as your C++ compiler: shell> CC=gcc CXX=gcc ./configure When you use gcc as your C++ compiler, it will not attempt to link in libg++ or libstdc++. This may be a good idea to do even if you have the above libraries installed, as some versions of these libraries have caused strange problems for MySQL users in the past. Here are some common environment variables to set depending on the compiler you are using:  Compiler Recommended options gcc 2.7.2.1 CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors" egcs 1.0.3a CC=gcc CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" gcc 2.95.2 CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" pgcc 2.90.29 or newer CFLAGS="-O3 -mpentiumpro -mstack-align-double" CXX=gcc \ CXXFLAGS="-O3 -mpentiumpro -mstack-align-double -felide-constructors \ -fno-exceptions -fno-rtti" In most cases you can get a reasonably optimal MySQL binary by using the options from the preceding table and adding the following options to the configure line: --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static The full configure line would, in other words, be something like the following for all recent gcc versions: CFLAGS="-O3 -mpentiumpro" CXX=gcc CXXFLAGS="-O3 -mpentiumpro \ -felide-constructors -fno-exceptions -fno-rtti" ./configure \ --prefix=/usr/local/mysql --enable-assembler \ --with-mysqld-ldflags=-all-static The binaries we provide on the MySQL web site at http://www.mysql.com/ are all compiled with full optimisation and should be perfect for most users. See section 2.2.6 MySQL Binaries Compiled by MySQL AB. There are some things you can tweak to make an even faster binary, but this is only for advanced users. See section 5.5.3 How Compiling and Linking Affects the Speed of MySQL. If the build fails and produces errors about your compiler or linker not being able to create the shared library `libmysqlclient.so.#' (`#' is a version number), you can work around this problem by giving the  --disable-shared option to configure. In this case, configure will not build a shared 4.1.2 `my.cnf' Option Files6 libmysqlclient.so.# library. You can configure MySQL not to use DEFAULT column values for non-NULL columns (that is, columns that are not allowed to be NULL). This causes INSERT statements to generate an error unless you explicitly specify values for all columns that require a non-NULL value. To suppress use of default values, run configure like this: shell> CXXFLAGS=-DDONT_USE_DEFAULT_FIELDS ./configure * By default, MySQL uses the ISO-8859-1 (Latin1) character set. To change the default set, use the --with-charset option: shell> ./configure --with-charset=CHARSET CHARSET may be one of big5, cp1251, cp1257, czech, danish, dec8, dos, euc_kr, gb2312, gbk, german1, hebrew, hp8, hungarian, koi8_ru, koi8_ukr, latin1, latin2, sjis, swe7, tis620, ujis, usa7, or  win1251ukr. See section 4.6.1 The Character Set Used for Data and Sorting. If you want to convert characters between the server and the client, you should take a look at the SET CHARACTER SET command. See section 5.5.6 SET Syntax. Warning: If you change character sets after having created any tables, you will have to run myisamchk -r -q on every table. Your indexes may be sorted incorrectly otherwise. (This can happen if you install MySQL, create some tables, then reconfigure MySQL to use a different character set and reinstall it.) With the option --with-extra-charsets=LIST  you can define which additional character sets should be compiled into the server. Here LIST is either a list of character sets separated with spaces, complex to include all characters that can't be dynamically loaded, or all to include all character sets into the binaries. * To configure MySQL with debugging code, use the --with-debug option: shell> ./configure --with-debug  This causes a safe memory allocator to be included that can find some errors and that provides output about what is happening. See section E.1 Debugging a MySQL server. * If your client programs are using threads, you need to also compile a thread-safe version of the MySQL client library with the --enable-thread-safe-client configure options. This will create a libmysqlclient_r library with which you should link your threaded applications. See section 8.4.8 How to Make a Threaded Client. * Options that pertain to particular systems can be found in the system-specific section of this manual. See section 2.6 Operating System Specific Notes.  2.3.4 Installing from the Development Source Tree  Caution: You should read this section only if you are interested in helping us test our new code. If you just want to get MySQL up and running on your system, you should use a standard release distribution (either a source or binary distribution will do).  To obtain our most recent development source tree, use these instructions: 1. Download BitKeeper from http://www.bitmover.com/cgi-bin/download.cgi. You will need Bitkeeper 2.0 or newer to access our repository. 2. Follow the instructions to install it. 3. After BitKeeper is installed, first go to the directory you want to work from, and then use this command if you want to clone the MySQL 3.23 branch: shell> bk clone bk://work.mysql.com:7000 mysql To clone the 4.0 branch, use this command instead: shell> bk clone bk://work.mysql.com:7001 mysql-4.0 In the preceding examples the source tree will be set up in the `mysql/' or `mysql-4.0/' subdirectory of your current directory. The initial download of the source tree may take a while, depending on the speed of your connection; be patient. 4. You will need GNU autoconf 2.52, automake 1.4, libtool, and m4 to run the next set of commands. utomake (1.5) doesn't yet work. shell> cd mysql-4.0 shell> bk -r get -Sq shell> aclocal; autoheader; autoconf; automake; 4.6.1 The Character Set Used for Data and Sorting7 shell> ./configure # Add your favorite options here shell> make If you get some strange error during this stage, check that you really have libtool installed! A collection of our standard configure scripts is located in the `BUILD/' subdirectory. If you are lazy, you can use `BUILD/compile-pentium-debug'. To compile on a different architecture, modify the script by removing flags that are Pentium-specific. 5. When the build is done, run make install. Be careful with this on a production machine; the command may overwrite your live release installation. If you have another installation of MySQL, we recommand that you run ./configure with different values for the prefix, with-tcp-port, and unix-socket-path options than those used for your production server. 6. Play hard with your new installation and try to make the new features crash. Start by running make test. See section 9.1.2 MySQL Test Suite. 7. If you have gotten to the make stage and the distribution does not compile, please report it to bugs@lists.mysql.com. If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. However, if you execute aclocal and get a command not found error or a similar problem, do not report it. Instead, make sure all the necessary tools are installed and that your PATH variable is set correctly so that your shell can find them. 8. After the initial bk clone operation to get the source tree, you should run bk pull periodically to get the updates. 9. You can examine the change history for the tree with all the diffs by using bk sccstool. If you see some funny diffs or code that you have a question about, do not hesitate to send e-mail to internals@lists.mysql.com. Also, if you think you have a better idea on how to do something, send an e-mail to the same address with a patch. bk diffs will produce a patch for you after you have made  changes to the source. If you do not have the time to code your idea, just send a description. 10. BitKeeper has a nice help utility that you can access via bk helptool. 11. Please note that any commits (bk ci or bk citool) will trigger the posting of a message with the changeset to our internals mailing list, as well as the usual openlogging.org submission with just  the changeset comments. Generally, you wouldn't need to use commit (since the public tree will not allow bk push), but rather use the bk diffs method described previously. 5 Problems Compiling? All MySQL programs compile cleanly for us with no warnings on Solaris using gcc. On other systems, warnings may occur due to differences in system include files. See section 2.3.6 MIT-pthreads Notes for warnings that may occur when using MIT-pthreads. For other problems, check the following list. he solution to many problems involves reconfiguring. If you do need to reconfigure, take note of the following:  * If configure is run after it already has been run, it may use information that was gathered during  its previous invocation. This information is stored in `config.cache'. When configure starts up, it looks for that file and reads its contents if it exists, on the assumption that the information is still correct. That assumption is invalid when you reconfigure. * Each time you run configure, you must run make again to recompile. However, you may want to remove old object files from previous builds first because they were compiled using different configuration options.  To prevent old configuration information or object files from being used, run these commands before rerunning configure: shell> rm config.cache make clean  Alternatively, you can run make distclean. 9.1.2 MySQL Test Suite8  The following list describes some of the problems when compiling MySQL that have been found to occur most often: * If you get errors when compiling `sql_yacc.cc', such as the ones shown here, you have probably run out of memory or swap space: Internal compiler error: program cc1plus got fatal signal 11 or Out of virtual memory or Virtual memory exhausted  The problem is that gcc requires huge amounts of memory to compile `sql_yacc.cc' with inline functions. Try running configure with the --with-low-memory option: shell> ./configure --with-low-memory This option causes -fno-inline to be added to the compile line if you are using gcc and -O0 if you are using something else. You should try the --with-low-memory option even if you have so much memory and swap space that you think you can't possibly have run out. This problem has been observed to occur even on systems with generous hardware configurations, and the --with-low-memory option usually fixes it.  * By default, configure picks c++ as the compiler name and GNU c++ links with -lg++. If you are usingcc, that behaviour can cause problems during configuration such as this: configure: error: installation or configuration problem: C++ compiler cannot create executables. You might also observe problems during compilation related to g++, libg++, or libstdc++. One cause of these problems is that you may not have g++, or you may have g++ but not libg++, or libstdc++. Take a look at the `config.log' file. It should contain the exact reason why your c++ compiler didn't work! To work around these problems, you can use gcc as your C++ compiler. Try setting the environment variable CXX to "gcc -O3". For example: shell> CXX="gcc -O3" ./configure This works because gcc compiles C++ sources as well as g++ does, but does not link in libg++ or libstdc++ by default. Another way to fix these problems, of course, is to install g++, libg++, and libstdc++. We would however like to recommend you to not use libg++ or libstdc++ with MySQL as this will only increase the binary size of mysqld without giving you any benefits. Some versions of these libraries have also caused strange problems for MySQL users in the past. * If your compile fails with errors, such as any of the following, you must upgrade your version of make to GNU make: making all in mit-pthreads make: Fatal error in reader: Makefile, line 18: Badly formed macro assignment or make: file `Makefile' line 18: Must be a separator (: or pthread.h: No such file or directory Solaris and FreeBSD are known to have troublesome make programs. GNU make Version 3.75 is known to work. If you want to define flags to be used by your C or C++ compilers, do so by adding the flags to the CFLAGS and CXXFLAGS environment variables. You can also specify the compiler names this way using CC and CXX. For example: shell> CC=gcc shell> CFLAGS=-O3 shell> CXX=gcc CXXFLAGS=-O3 export CC CFLAGS CXX CXXFLAGS See section 2.2.6 MySQL Binaries Compiled by MySQL AB, for a list of flag definitions that have been found to be useful on various systems 2.2.6 MySQL Binaries Compiled by MySQL AB 9 * If you get an error message like this, you need to upgrade your gcc compiler: client/libmysql.c:273: parse error before `__attribute__' gcc 2.8.1 is known to work, but we recommend using gcc 2.95.2 or egcs 1.0.3a instead.such as those shown here when compiling mysqld, configure didn't correctly detect the type of the last argument to accept(), getsockname(), or getpeername(): cxx: Error: mysqld.cc, line 645: In this statement, the referenced type of the pointer value "&length" is "unsigned long", which is not compatible with "int". new_sock = accept(sock, (struct sockaddr *)&cAddr, &length); To fix this, edit the `config.h' file (which is generated by configure). Look for these lines: /* Define as the base type of the last arg to accept */ #define SOCKET_SIZE_TYPE XXX Change XXX to size_t or int, depending on your operating system. (Note that you will have to do this each time you run configure because configure regenerates `config.h'.) * The `sql_yacc.cc' file is generated from `sql_yacc.yy'. Normally the build process doesn't need to create `sql_yacc.cc', because MySQL comes with an already generated copy. However, if you do need to re-create it, you might encounter this error: "sql_yacc.yy", line xxx fatal: default action causes potential...  This is a sign that your version of yacc is deficient. You probably need to install bison (the GNU version of yacc) and use that instead. * If you need to debug mysqld or a MySQL client, run configure with the --with-debug option, then recompile and link your clients with the new client library. See section E.2 Debugging a MySQL client.  2.3.6 MIT-pthreads Notes  This section describes some of the issues involved in using MIT-pthreads.  Note that on Linux you should not use MIT-pthreads but install LinuxThreads! See section 2.6.1 Linux Notes (All Linux Versions).  If your system does not provide native thread support, you will need to build MySQL using the MIT-pthreads package. This includes older FreeBSD systems, SunOS 4.x, Solaris 2.4 and earlier, and some others. See section 2.2.2 Operating Systems Supported by MySQL. * On most systems, you can force MIT-pthreads to be used by running configure with the --with-mit-threads option: shell> ./configure --with-mit-threads Building in a non-source directory is not supported when using MIT-pthreads because we want to minimise our changes to this code. * The checks that determine whether to use MIT-pthreads occur only during the part of the configuration process that deals with the server code. If you have configured the distribution using --without-server to build only the client code, clients will not know whether MIT-pthreads is being used and will use Unix socket connections by default. Because Unix sockets do not work under MIT-pthreads on some platforms, this means you will need to use -h or --host when you run client  programs. * When MySQL is compiled using MIT-pthreads, system locking is disabled by default for performance reasons. You can tell the server to use system locking with the --external-locking option. This is only needed if you want to be able to run two MySQL servers against the same data files (not recommended). * Sometimes the pthread bind() command fails to bind to a socket without any error message (at least on Solaris). The result is that all connections to the server fail. For example: mysqladmin version mysqladmin: connect to server at '' failed; error: 'Can't connect to mysql server on localhost (146)' E.2 Debugging a MySQL client70  The solution to this is to kill the mysqld server and restart it. This has only happened to us when we have forced the server down and done a restart immediately. * With MIT-pthreads, the sleep() system call isn't interruptible with SIGINT (break). This is only  noticeable when you run mysqladmin --sleep. You must wait for the sleep() call to terminate before interrupt is served and the process stops. * When linking, you may receive warning messages like these (at least on Solaris); they can be  ignored: ld: warning: symbol `_iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken ld: warning: symbol `__iob' has differing sizes: (file /my/local/pthreads/lib/libpthread.a(findfp.o) value=0x4; file /usr/lib/libc.so value=0x140); /my/local/pthreads/lib/libpthread.a(findfp.o) definition taken * Some other warnings also can be ignored: implicit declaration of function `int strtoll(...)' implicit declaration of function `int strtoul(...)' * We haven't gotten readline to work with MIT-pthreads. (This isn't needed, but may be interesting for someone.)  2.3.7 Windows Source Distribution  You will need the following: * VC++ 6.0 compiler (updated with 4 or 5 SP and Pre-processor package) The Pre-processor package is necessary for the macro assembler. More details at: http://msdn.microsoft.com/vstudio/sp/vs6sp5/faq.asp. * The MySQL source distribution for Windows, which can be downloaded from http://www.mysql.com/downloads/.  Building MySQL 1. Create a work directory (e.g., workdir). 2. Unpack the source distribution in the aforementioned directory. 3. Start the VC++ 6.0 compiler. 4. In the File menu, select Open Workspace. 5. Open the `mysql.dsw' workspace you find on the work directory. 6. From the Build menu, select the Set Active Configuration menu. 7. Click over the screen selecting mysqld - Win32 Debug and click OK. 8. Press F7 to begin the build of the debug server, libs, and some client applications. 9. When the compilation finishes, copy the libs and the executables to a separate directory. 10. Compile the release versions that you want, in the same way. 11. Create the directory for the MySQL stuff: e.g., `c:\mysql' 12. From the workdir directory copy for the c:\mysql directory the following directories:  + Data  + Docs  + Share 13. Create the directory `c:\mysql\bin' and copy all the servers and clients that you compiled previously. 14. If you want, also create the `lib' directory and copy the libs that you compiled previously. 15. Do a clean using Visual Studio.  Set up and start the server in the same way as for the binary Windows distribution. See section 2.1.2.2  Preparing the Windows MySQL Environment.   2.3.7 Windows Source Distribution1 2.4 Post-installation Setup and Testing  Once you've installed MySQL (from either a binary or source distribution), you need to initialise the grant tables, start the server, and make sure that the server works okay. You may also wish to arrang for the server to be started and stopped automatically when your system starts up and shuts down.  Normally you install the grant tables and start the server like this for installation from a source distribution: shell> ./scripts/mysql_install_db shell> cd mysql_installation_directory shell> ./bin/safe_mysqld --user=mysql &  For a binary distribution (not RPM or pkg packages), do this: shell> cd mysql_installation_directory shell> ./bin/mysql_install_db shell> ./bin/safe_mysqld --user=mysql &  This creates the mysql database which will hold all database privileges, the test database which you can use to test MySQL, and also privilege entries for the user that run mysql_install_db and a root user (without any passwords). This also starts the mysqld server. mysql_install_db will not overwrite any old privilege tables, so it should be safe to run in any circumstances. If you don't want to have the test database you can remove it with mysqladmin -u root drop test.  Testing is most easily done from the top-level directory of the MySQL distribution. For a binary distribution, this is your installation directory (typically something like `/usr/local/mysql'). For a source distribution, this is the main directory of your MySQL source tree.  In the commands shown in this section and in the following subsections, BINDIR is the path to the location in which programs like mysqladmin and safe_mysqld are installed. For a binary distribution, this is the `bin'within the distribution. For a source distribution, BINDIR is probably `/usr/local/bin', unless you specified an installation directory other than `/usr/local' when you ran configure. EXECDIR is the location in which the mysqld server is installed. For a binary distribution, this is the same as BINDIR. For a source distribution, EXECDIR is probably `/usr/local/libexec'.  Testing is described in detail: 1. If necessary, start the mysqld server and set up the initial MySQL grant tables containing the  privileges that determine how users are allowed to connect to the server. This is normally done with  the mysql_install_db script: shell> scripts/mysql_install_db Typically, mysql_install_db needs to be run only the first time you install MySQL. Therefore, if you are upgrading an existing installation, you can skip this step. (However, mysql_install_db is quite safe to use and will not update any tables that already exist, so if you are unsure of what to do, you can always run mysql_install_db.) mysql_install_db creates six tables (user, db, host, tables_priv, columns_priv, and func) in the mysql database. A description of the initial privileges is given in section 4.3.4 Setting Up the Initial MySQL Privileges. Briefly, these privileges allow the MySQL root user to do anything, and allow anybody to create or use databases with a name of test or starting with test_. If you don't set up the grant tables, the following error will appear in the log file when you start the server: mysqld: Can't find file: 'host.frm' This may also happen with a binary MySQL distribution if you don't start MySQL by executing exactly ./bin/safe_mysqld! See section 4.7.2 safe_mysqld, The Wrapper Around mysqld. You might need to run mysql_install_db as root. However, if you prefer, you can run the MySQL server as an unprivileged  2.4 Post-installation Setup and Testing2 (non-root) user, provided that the user can read and write files in the database directory. Instructions for running MySQL as an unprivileged user are given in section A.3.2 How to Run MySQL  As a Normal User. If you have problems with mysql_install_db, see section 2.4.1 Problems Running mysql_install_db. There are some alternatives to running the mysql_install_db script as it is provided in the MySQL distribution:+ You may want to edit mysql_install_db before running it, to change the initial privileges that areed into the grant tables. This is useful if you want to install MySQL on a lot of machines with the same privileges. In this case you probably should need only to add a few extra INSERT statements to the mysql.user and mysql.db tables! + If you want to change things in the grant tables after installing them, you can run mysql_install_db, then use mysql -u root mysql to connect to the grant tables as the MySQL rootuser and issue SQL statements to modify the grant tables directly. + It is possible to re-create the grant tables completely after they have already been created. You might want to do this if you've already installed the tables but then want to re-create them after editing mysql_install_db. For more information about these alternatives, see section 4.3.4 Setting Up the Initial MySQL Privileges. 2. Start the MySQL server like this: shell> cd mysql_installation_directory shell> bin/safe_mysqld & If you have problems starting the server, see section 2.4.2 Problems Starting the MySQL Server. 3. Use mysqladmin to verify that the server is running. The following commands provide a simple test to check that the server is up and responding to connections: shell> BINDIR/mysqladmin version shell> BINDIR/mysqladmin variables The output from mysqladmin version varies slightly depending on your platform and version of MySQL, but should be similar to that shown here: shell> BINDIR/mysqladmin version mysqladmin Ver 8.14 Distrib 3.23.32, for linux on i586 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license.  Server version 3.23.32-debug Protocol version 10 ConnectionLocalhost via Unix socket TCP port 3306 UNIX socket /tmp/mysql.sock Uptime: 16 sec  Threads: 1 Questions: 9 Slow queries: 0 Opens: 7 Flush tables: 2 Open tables: 0 Queries per second avg: 0.000 Memory in use: 132K Max memory used: 16773K To get a feeling for what else you can do with BINDIR/mysqladmin, invoke it with the --help option. 4. Verify that you can shut down the server: shell> BINDIR/mysqladmin -u root shutdown 5. Verify that you can restart the server. Do this using safe_mysqld or by invoking mysqld directly. For example: shell> BINDIR/safe_mysqld --log & If safe_mysqld fails, try running it from the MySQL installation directory (if you are not already there). If that doesn't work, see section 2.4.2 Problems Starting the MySQL Server. 6. Run some simple tests to verify that the server is working. The output should be similar to what is shown here:  A.3.2 How to Run MySQL As a Normal User3 shell> BINDIR/mysqlshow +-----------+ | Databases | +-----------+ | mysql | +-----------+  shell> BINDIR/mysqlshow mysql Database: mysql +--------------+ | Tables | +--------------+ | columns_priv | | db | | func | | host | | tables_priv | | user | +--------------+  shell> BINDIR/mysql -e "SELECT host,db,user FROM db" mysql +------+--------+------+ | host | db | user | +------+--------+------+ | % | test | | | % | test_% | | +------+--------+------+ There is also a benchmark suite in the `sql-bench' directory (under the MySQL installation directory) that you can use to compare how MySQL performs on different platforms. The `sql-bench/Results' directory contains the results from many runs against different databases and platforms. To run all tests, execute these commands: shell> cd sql-bench shell> run-all-tests If you don't have the `sql-bench' directory, you are probably using an RPM for a binary distribution. (Source distribution RPMs include the benchmark directory.) In this case, you must first install the benchmark suite before you can use it. Beginning with MySQL Version 3.22, there are benchmark RPM files named `mysql-bench-VERSION-i386.rpm' that contain benchmark code and data. If you have a source distribution, you can also run the tests in the `tests' subdirectory. For example, to run `auto_increment.tst', do this: shell> BINDIR/mysql -vvf test < ./tests/auto_increment.tst The expected results are shown in the `./tests/auto_increment.res' file.  2.4.1 Problems Running mysql_install_db  The purpose of the mysql_install_db script is to generate new MySQL privilege tables. It will not affect any other data! It will also not do anything if you already have MySQL privilege tables installed!  If you want to re-create your privilege tables, you should take down the mysqld server, if it's running, and then do something like: mv mysql-data-directory/mysql mysql-data-directory/mysql-old mysql_install_db  This section lists problems you might encounter when you run mysql_install_db: mysql_install_db doesn't install the grant tables   2.4.1 Problems Running mysql_install_db4 You may find that mysql_install_db fails to install the grant tables and terminates after displaying the following messages: starting mysqld daemon with databases from XXXXXX mysql daemon ended In this case, you should examine the log file very carefully! The log should be located in the directory `XXXXXX' named by the error message, and should indicate why mysqld didn't start. Ifyou don't understand what happened, include the log when you post a bug report using mysqlbug! See section 1.6.2.3 How to Report Bugs or Problems. There is already a mysqld daemon running  In this case, you probably don't have to run mysql_install_db at all. You have to run mysql_install_db only once, when you install MySQL the first time. Installing a second mysqld daemon doesn't work when one daemon is running  This can happen when you already have an existing MySQL installation, but want to put a new installation in a different place (for example, for testing, or perhaps you simply want to run two installations at the same time). Generally the problem that occurs when you try to run the second server is that it tries to use the same socket and port as the old one. In this case you will get the error message: Can't start server: Bind on TCP/IP port: Address already in use or Can't start server: Bind on unix socket.... See section 4.1.3 Installing Many Servers on the Same  Machine. You don't have write access to `/tmp'  If you don't have write access to create a socket file at the default place (in `/tmp') or permission to create temporary files in `/tmp,' you will get an error when running mysql_install_db or when starting or using mysqld. You can specify a different socket and temporary directory as follows: shell> TMPDIR=/some_tmp_dir/ shell> MYSQL_UNIX_PORT=/some_tmp_dir/mysqld.sock shell> export TMPDIR MYSQL_UNIX_PORT  See section A.4.5 How to Protect or Change the MySQL Socket File `/tmp/mysql.sock'.  `some_tmp_dir' should be the path to some directory for which you have write permission. See  section F Environment Variables. After this you should be able to run mysql_install_db and start  the server with these commands: scripts/mysql_install_db BINDIR/safe_mysqld & mysqld crashes immediately  If you are running RedHat Version 5.0 with a version of glibc older than 2.0.7-5, you should make  sure you have installed all glibc patches! There is a lot of information about this in the MySQL  mail archives. Links to the mail archives are available online at http://lists.mysql.com/. Also,  see section 2.6.1 Linux Notes (All Linux Versions). You can also start mysqld manually using the  --skip-grant-tables option and add the privilege information yourself using mysql:safe_mysqld --skip-grant-tables & shell> BINDIR/mysql -u root mysqlFrom mysql, manually execute the SQL commands in mysql_install_db. Make sure you run mysqladmin flush-privileges or mysqladmin reload afterward to tell the server to reload the grant tables. 2.4.2 Problems Starting the MySQL Server  If you are going to use tables that support transactions (InnoDB, BDB), you should first create a my.cnf file and set startup options for the table types you plan to use. See section 7 MySQL Table Types.  Generally, you start the mysqld server in one of these ways: * By invoking mysql.server. This script is used primarily at system startup and shutdown, and is described more fully in section 2.4.3 Starting and Stopping MySQL Automatically. * By invoking safe_mysqld, which tries to determine the proper options for mysqld and then runs it with those options. See section 4.7.2 safe_mysqld, The Wrapper Around mysqld. 1.6.2.3 How to Report Bugs or Problems5 * For Windows NT/2000/XP, please see section 2.6.2.2 Starting MySQL on Windows NT, 2000 or XP. * By invoking mysqld directly.  When the mysqld daemon starts up, it changes the directory to the data directory. This is where it expects to write log files and the pid (process ID) file, and where it expects to find databases.  The data directory location is hardwired in when the distribution is compiled. However, if mysqld expects to find the data directory somewhere other than where it really is on your system, it will not work properly. If you have problems with incorrect paths, you can find out what options mysqld allows and what the default path settings are by invoking mysqld with the --help option. You can override the defaults by specifying the correct pathnames as command-line arguments to mysqld. (These options can be used with safe_mysqld as well.)  Normally you should need to tell mysqld only the base directory under which MySQL is installed. You can do this with the --basedir option. You can also use --help to check the effect of changing path options (note that --help must be the final option of the mysqld command). For example: shell> EXECDIR/mysqld --basedir=/usr/local --help  Once you determine the path settings you want, start the server without the --help option.  Whichever method you use to start the server, if it fails to start up correctly, check the log file to see if you can find out why. Log files are located in the data directory (typically `/usr/local/mysql/data' for a binary distribution, `/usr/local/var' for a source distribution, and `\mysql\data\mysql.err' on Windows). Look in the data directory for files with names of the form `host_name.err' and `host_name.log' where host_name is the name of your server host. Then check the last few lines of these files: tail host_name.err shell> tail host_name.log  Look for something like the following in the log file: 000729 14:50:10 bdb: Recovery function for LSN 1 27595 failed 000729 14:50:10 bdb: warning: ./test/t1.db: No such file or directory 000729 14:50:10 Can't init databases  This means that you didn't start mysqld with --bdb-no-recover and Berkeley DB found something wrong with its log files when it tried to recover your databases. To be able to continue, you should move away the old Berkeley DB log file from the database directory to some other place, where you can later examine it. The log files are named `log.0000000001', where the number will increase over time.  If you are running mysqld with BDB table support and mysqld core dumps at start this could be because of some problems with the BDB recover log. In this case you can try starting mysqld with --bdb-no-recover. If this helps, then you should remove all `log.*' files from the data directory and try starting mysqld again. If you get the following error, it means that some other program (or another mysqld server) is already using the TCP/IP port or socket mysqld is trying to use: Can't start server: Bind on TCP/IP port: Address already in use or Can't start server : Bind on unix socket...  Use ps to make sure that you don't have another mysqld server running. If you can't find another server running, you can try to execute the command telnet your-host-name tcp-ip-port-number and press Enter a couple of times. If you don't get an error message like telnet: Unable to connect to remote host: Connection refused, something is using the TCP/IP port mysqld is trying to use. See section 2.4.1   2.6.2.2 Starting MySQL on Windows NT, 2000 or XP6 Problems Running mysql_install_db and section 4.1.4 Running Multiple MySQL Servers on the Same Machine.  If mysqld is currently running, you can find out what path settings it is using by executing this command: shell> mysqladmin variables or shell> mysqladmin -h 'your-host-name' variables  If you get Errcode 13, which means Permission denied, when starting mysqld this means that you didn't have the right to read/create files in the MySQL database or log directory. In this case you should either start mysqld as the root user or change the permissions for the involved files and directories so that you have the right to use them.  If safe_mysqld starts the server but you can't connect to it, you should make sure you have an entry in `/etc/hosts' that looks like this: 127.0.0.1 localhost This problem occurs only on systems that don't have a working thread library and for which MySQL must be configured to use MIT-pthreads.  If you can't get mysqld to start you can try to make a trace file to find the problem. See section E.1.2 Creating Trace Files.  If you are using InnoDB tables, refer to the InnoDB-specific startup options. See section 7.5.2 InnoDB Startup Options.  If you are using BDB (Berkeley DB) tables, you should familiarise yourself with the different BDB specific startup options. See section 7.6.3 BDB startup options.  2.4.3 Starting and Stopping MySQL Automatically  The mysql.server and safe_mysqld scripts can be used to start the server automatically at system startup time. mysql.server can also be used to stop the server.  The mysql.server script can be used to start or stop the server by invoking it with start or stop arguments: shell> mysql.server start shell> mysql.server stop  mysql.server can be found in the `share/mysql' directory under the MySQL installation directory or in the `support-files' directory of the MySQL source tree.  Before mysql.server starts the server, it changes the directory to the MySQL installation directory, then invokes safe_mysqld. You might need to edit mysql.server if you have a binary distribution that you've installed in a non-standard location. Modify it to cd into the proper directory before it runs safe_mysqld. If you want the server to run as some specific user, add an appropriate user line to the `/etc/my.cnf' file, as shown later in this section.  mysql.server stop brings down the server by sending a signal to it. You can take down the server manually by executing mysqladmin shutdown.  You might want to add these start and stop commands to the appropriate places in your `/etc/rc*' files when you start using MySQL for production applications. Note that if you modify mysql.server, and then 4.1.4 Running Multiple MySQL Servers on the Same Machine7 upgrade MySQL sometime, your modified version will be overwritten, so you should make a copy of your edited version that you can reinstall.  If your system uses `/etc/rc.local' to start external scripts, you should append the following to it: /bin/sh -c 'cd /usr/local/mysql ; ./bin/safe_mysqld --user=mysql &' You can also add options for mysql.server in a global `/etc/my.cnf' file. A typical `/etc/my.cnf' file might look like this: [mysqld] datadir=/usr/local/mysql/var socket=/var/tmp/mysql.sock port=3306 user=mysql [mysql.server] basedir=/usr/local/mysql  The mysql.server script understands the following options: datadir, basedir, and pid-file.  The following table shows which option groups each of the startup scripts read from option files: Script Option groups mysqld mysqld and server mysql.server mysql.server, mysqld, and server safe_mysqld mysql.server, mysqld, and server  See section 4.1.2 `my.cnf' Option Files.  2.5 Upgrading/Downgrading MySQL You can always move the MySQL form and datafiles between different versions on the same architecture as long as you have the same base version of MySQL. The current base version is 3. If you change the character set when running MySQL (which may also change the sort order), you must run myisamchk -r -q on all tables. Otherwise, your indexes may not be ordered correctly. If you are afraid of new versions, you can always rename your old mysqld to something like mysqld-old-version-number. If your new mysqld then does something unexpected, you can simply shut it down and restart with your old mysqld!  When you do an upgrade you should also back up your old databases, of course.  If after an upgrade, you experience problems with recompiled client programs, like Commands out of sync or unexpected core dumps, you probably have used an old header or library file when compiling your programs. In this case you should check the date for your `mysql.h' file and `libmysqlclient.a' library o verify that they are from the new MySQL distribution. If not, please recompile your programs!  If you get some problems that the new mysqld server doesn't want to start or that you can't connect without a password, check that you don't have some old `my.cnf' file from your old installation! You can check this with: program-name --print-defaults. If this outputs anything other than the program name, you have an active `my.cnf' file that will affect things!  It is a good idea to rebuild and reinstall the Msql-Mysql-modules distribution whenever you install a new release of MySQL, particularly if you notice symptoms such as all your DBI scripts dumping core after you upgrade MySQL. 4.1.2 `my.cnf' Option Files8  2.5.1 Upgrading From Version 3.23 to Version 4.0 n general what you have to do when upgrading to 4.0 from an earlier MySQL version: * Run the mysql_fix_privilege_tables to add new privileges and features to the MySQL privilege tables. * Edit any MySQL startup scripts or configure files to not use any of the deprecated options listed below. * Convert your old ISAM files to MyISAM files with the command: mysql_convert_table_format database. Note that this should only be run if all tables in the given database is ISAM or MyISAM tables. If this is not the case you should run ALTER TABLE table_name TYPE=MyISAM on all ISAM tables. * Ensure that you don't have any MySQL clients that uses shared libraries (like the perl Msql-Mysql-modules). If you have, you should recompile them as structures used in libmysqlclient.so has changed. MySQL 4.0 will work even if you don't do the above, but you will not be able to use the new security privileges that MySQL 4.0 and you may run into problems when upgrading later to MySQL 4.1 or newer. The ISAM file format still works in MySQL 4.0 but it's deprecated and will be disabled in MySQL 5.0.  Old clients should work with a Version 4.0 server without any problems.  Even if you do the above, you can still downgrade to MySQL 3.23.52 or newer if you run into problems with the MySQL 4.0 series. In this case you have to do a mysqldump of any tables using a fulltext index and restore these in 3.23 (because 4.0 uses a new format for fulltext index).  The following is a more complete lists tell what you have to watch out for when upgrading to version 4.0;  * MySQL 4.0 has a lot of new privileges in the mysql.user table. See section 4.3.1 GRANT and REVOKE Syntax. To get these new privileges to work, one must run the mysql_fix_privilege_tables script. Until this script is run all users have the SHOW DATABASES, CREATE TEMPORARY TABLES, and LOCK TABLES privileges. SUPER and EXECUTE privileges take their value from PROCESS. REPLICATION SLAVE and REPLICATION CLIENT take their values from FILE. If you have any scripts that creates new users, you may want to change them to use the new privileges. If you are not using GRANT commands in scripts, this is a good time to change your scripts. In version 4.0.2 the option --safe-show-database is deprecated (and no longer does anything). See section 4.2.3 Startup Options for mysqld Concerning Security. If you get access denied errors for new users in version 4.0.2, you should check if you need some of the new grants that you didn't need before. In particular, you will need REPLICATION SLAVE (instead of FILE) for new slaves. * The startup parameters myisam_max_extra_sort_file_size and myisam_max_extra_sort_file_size are now given in bytes (was megabytes before 4.0.3). External system locking of MyISAM/ISAM files is now turned off by default. One can turn this on by doing --external-locking. (For most users this is never needed). * The following startup variables/options have been renamed:  From to. myisam_bulk_insert_tree_size bulk_insert_buffer_size query_cache_startup_type query_cache_type record_buffer read_buffer_size record_rnd_buffer read_rnd_buffer_size sort_buffer sort_buffer_size warnings log-warnings The startup options record_buffer, sort_buffer and warnings will still work in MySQL 4.0 but are deprecated. * The following SQL variables have changed name.   2.5.1 Upgrading From Version 3.23 to Version 4.09 FromTo. SQL_BIG_TABLES BIG_TABLES SQL_LOW_PRIORITY_UPDATES LOW_PRIORITY_UPDATES SQL_MAX_JOIN_SIZE MAX_JOIN_SIZE  SQL_QUERY_CACHE_TYPE QUERY_CACHE_TYPE  The old names still work in MySQL 4.0 but are deprecated. * You have to use SET GLOBAL SQL_SLAVE_SKIP_COUNTER=# instead of SET SQL_SLAVE_SKIP_COUNTER=#. Renamed mysqld startup options --skip-locking to --skip-external-locking and --enable-locking to --external-locking. * SHOW MASTER STATUS now returns an empty set if binary log is not enabled. SHOW SLAVE STATUS now returns an empty set if slave is not initialised. * mysqld now has the option --temp-pool enabled by default as this gives better performance with some OS. * DOUBLE and FLOAT columns now honour the UNSIGNED flag on storage (before, UNSIGNED was ignored for these columns). * ORDER BY column DESC now always sorts NULL values first; in 3.23 this was not always consistent. * SHOW INDEX has 2 columns more (Null and Index_type) than it had in 3.23. * SIGNED is a reserved word. * The result of all bitwise operators |, &, <<, >>, and ~ is now unsigned. This may cause problems if you are using them in a context where you want a signed result. See section 6.3.5 Cast Functions. * Note: when you use subtraction between integer values where one is of type UNSIGNED, the result will be unsigned! In other words, before upgrading to MySQL 4.0, you should check your application for cases where you are subtracting a value from an unsigned entity and want a negative answer or subtracting an unsigned value from an integer column. You can disable this behaviour by using the --sql-mode=NO_UNSIGNED_SUBTRACTION option when starting mysqld. See section 6.3.5 Cast Functions. * To use MATCH ... AGAINST (... IN BOOLEAN MODE) with your tables, you need to rebuild them with ALTER  TABLE table_name TYPE=MyISAM, even if they are of MyISAM type. * LOCATE() and INSTR() are case-sensitive if one of the arguments is a binary string. Otherwise they are case-insensitive. * STRCMP() now uses the current character set when doing comparisons, which means that the default comparison behaviour now is case-insensitive. * HEX(string) now returns the characters in string converted to hexadecimal. If you want to convert a number to hexadecimal, you should ensure that you call HEX() with a numeric argument. * In 3.23, INSERT INTO ... SELECT always had IGNORE enabled. In 4.0.1, MySQL will stop (and possibly roll back) in case of an error if you don't specify IGNORE. * `safe_mysqld' is renamed to `mysqld_safe'. For some time we will in our binary distributions include safe_mysqld as a symlink to mysqld_safe. old C API functions mysql_drop_db, mysql_create_db, and mysql_connect are not supported anymore, unless you compile MySQL with CFLAGS=-DUSE_OLD_FUNCTIONS. Instead of doing this, it is preferable to change the client to use the new 4.0 API. * In the MYSQL_FIELD structure, length and max_length have changed from unsigned int to unsigned long.  This should not cause any problems, except that they may generate warning messages when used as arguments in the printf() class of functions. * You should use TRUNCATE TABLE when you want to delete all rows from a table and you don't care howany rows were deleted. (Because TRUNCATE TABLE is faster than DELETE FROM table_name). * You will get an error if you have an active LOCK TABLES or transaction when trying to execute TRUNCATE TABLE or DROP DATABASE. * You should use integers to store values in BIGINT columns (instead of using strings, as you did in MySQL 3.23). Using strings will still work, but using integers is more efficient. * Format of SHOW OPEN TABLE has changed. * Multi-threaded clients should use mysql_thread_init() and mysql_thread_end(). See section 8.4.8 How to Make a Threaded Client. If you want to recompile the Perl DBD::mysql module, you must get Msql-Mysql-modules version 1.2218 or newer because the older DBD modules used the deprecated drop_db() call. 6.3.5 Cast Functions80 * RAND(seed) returns a different random number series in 4.0 than in 3.23; this was done to further differentiate RAND(seed) and RAND(seed+1).  2.5.2 Upgrading From Version 3.22 to Version 3.23  MySQL Version 3.23 supports tables of the new MyISAM type and the old ISAM type. You don't have to convert your old tables to use these with Version 3.23. By default, all new tables will be created with type MyISAM (unless you start mysqld with the --default-table-type=isam option). You can change an ISAM table to a MyISAM table with ALTER TABLE table_name TYPE=MyISAM or the Perl script mysql_convert_table_format.  Version 3.22 and 3.21 clients will work without any problems with a Version 3.23 server.  The following list tells what you have to watch out for when upgrading to Version 3.23: * All tables that use the tis620 character set must be fixed with myisamchk -r or REPAIR TABLE. If you do a DROP DATABASE on a symbolic linked database, both the link and the original database are  deleted. (This didn't happen in 3.22 because configure didn't detect the readlink system call.) OPTIMIZE TABLE now only works for MyISAM tables. For other table types, you can use ALTER TABLE to  optimise the table. During OPTIMIZE TABLE the table is now locked from other threads. * The MySQL client mysql is now by default started with the option --no-named-commands (-g). This  option can be disabled with --enable-named-commands (-G). This may cause incompatibility problems in some cases@-for example, in SQL scripts that use named commands without a semicolon! Long format ommands still work from the first line. * Date functions that work on parts of dates (like MONTH()) will now return 0 for 0000-00-00 dates. (MySQL 3.22 returned NULL.) If you are using the german character sort order, you must repair all your tables with isamchk -r, as we have made some changes in the sort order! The default return type of IF will now depend on bothand not only the first argument. * AUTO_INCREMENT will not work with negative numbers. The reason for this is that negative numbers  caused problems when wrapping from -1 to 0. AUTO_INCREMENT for MyISAM tables is no handled at a lower level and is much faster than before. For MyISAM tables old numbers are also not reused  anymore, even if you delete some rows from the table. * CASE, DELAYED, ELSE, END, FULLTEXT, INNER, RIGHT, THEN, and WHEN are now reserved words. FLOAT(X) is now a true floating-point type and not a value with a fixed number of decimals. * When declaring DECIMAL(length,dec) the length argument no longer includes a place for the sign or  the decimal point. * A TIME string must now be of one of the following formats: [[[DAYS] [H]H:]MM:]SS[.fraction] or  [[[[[H]H]H]H]MM]SS[.fraction]. * LIKE now compares strings using the same character comparison rules as =. If you require the old behaviour, you can compile MySQL with the CXXFLAGS=-DLIKE_CMP_TOUPPER flag. REGEXP is now case-insensitive for normal (not binary) strings. * When you check/repair tables you should use CHECK TABLE or myisamchk for MyISAM tables (`.MYI') and isamchk for ISAM (`.ISM') tables. If you want your mysqldump files to be compatible between MySQL Version 3.22 and Version 3.23, you should not use the --opt or --full option to mysqldump. Check all your calls to DATE_FORMAT() to make sure there is a `%' before each format character. (MySQL Version 3.22 and later already allowed this syntax.) mysql_fetch_fields_direct is now a function (it was a macro) and it returns a pointer to a YSQL_FIELD instead of a MYSQL_FIELD. mysql_num_fields() can no longer be used on a MYSQL* object (it's now a function that takes  MYSQL_RES* as an argument, so you should use mysql_field_count() instead). * In MySQL Version 3.22, the output of SELECT DISTINCT ... was almost always sorted. In Version 3.23,  you must use GROUP BY or ORDER BY to obtain sorted output. * SUM() now returns NULL, instead of 0, if there are no matching rows. This is according to ANSI SQL.  2.5.2 Upgrading From Version 3.22 to Version 3.231 An AND or OR with NULL values will now return NULL instead of 0. This mostly affects queries that use NOT on an AND/OR expression as NOT NULL = NULL. LPAD() and RPAD() will shorten the result string if it's longer than the length argument.  2.5.3 Upgrading from Version 3.21 to Version 3.22  Nothing that affects compatibility has changed between versions 3.21 and 3.22. The only pitfall is that new tables that are created with DATE type columns will use the new way to store the date. You can't access these new fields from an old version of mysqld.  After installing MySQL Version 3.22, you should start the new server and then run the mysql_fix_privilege_tables script. This will add the new privileges that you need to use the GRANT command. If you forget this, you will get Access denied when you try to use ALTER TABLE, CREATE INDEX, or DROP INDEX. If your MySQL root user requires a password, you should give this as an argument to mysql_fix_privilege_tables.  The C API interface to mysql_real_connect() has changed. If you have an old client program that calls this function, you must place a 0 for the new db argument (or recode the client to send the db element for faster connections). You must also call mysql_init() before calling mysql_real_connect()! This change was done to allow the new mysql_options() function to save options in the MYSQL handler structure.  The mysqld variable key_buffer has changed names to key_buffer_size, but you can still use the old name in your startup files.  2.5.4 Upgrading from Version 3.20 to Version 3.21  If you are running a version older than Version 3.20.28 and want to switch to Version 3.21, you need to do the following:  You can start the mysqld Version 3.21 server with safe_mysqld --old-protocol to use it with clients from a Version 3.20 distribution. In this case, the new client function mysql_errno() will not return any server error, only CR_UNKNOWN_ERROR (but it works for client errors), and the server uses the old password() checking rather than the new one.  If you are not using the --old-protocol option to mysqld, you will need to make the following changes:ll client code must be recompiled. If you are using ODBC, you must get the new MyODBC 2.x driver. * The script scripts/add_long_password must be run to convert the Password field in the mysql.user  table to CHAR(16). * All passwords must be reassigned in the mysql.user table (to get 62-bit rather than 31-bit  passwords). The table format hasn't changed, so you don't have to convert any tables.  MySQL Version 3.20.28 and above can handle the new user table format without affecting clients. If have a MySQL version earlier than Version 3.20.28, passwords will no longer work with it if you convert the user table. So to be safe, you should first upgrade to at least Version 3.20.28 and then upgrade to Version 3.21.  The new client code works with a 3.20.x mysqld server, so if you experience problems with 3.21.x, you can use the old 3.20.x server without having to recompile the clients again.  If you are not using the --old-protocol option to mysqld, old clients will issue the error message: ERROR: Protocol mismatch. Server Version = 10 Client Version = 9   2.5.3 Upgrading from Version 3.21 to Version 3.222 The new Perl DBI/DBD interface also supports the old mysqlperl interface. The only change you have to make if you use mysqlperl is to change the arguments to the connect() function. The new arguments are: host, database, user, and password (the user and password arguments have changed places). See section 8.2.2 The DBI Interface.  The following changes may affect queries in old applications: * HAVING must now be specified before any ORDER BY clause. * The parameters to LOCATE() have been swapped. * There are some new reserved words. The most notable are DATE, TIME, and TIMESTAMP. 2.5.5 Upgrading to Another Architecture  If you are using MySQL Version 3.23, you can copy the `.frm', `.MYI', and `.MYD' files between different architectures that support the same floating-point format. (MySQL takes care of any byte-swapping issues.) MySQL ISAM data and index files (`.ISD' and `*.ISM', respectively) are architecture-dependent and in some cases OS-dependent. If you want to move your applications to another machine that has a differ architecture or OS than your current machine, you should not try to move a database by simply copying the files to the other machine. Use mysqldump instead.  By default, mysqldump will create a file full of SQL statements. You can then transfer the file to the other machine and feed it as input to the mysql client.  Try mysqldump --help to see what options are available. If you are moving the data to a newer version of MySQL, you should use mysqldump --opt with the newer version to get a fast, compact dump. The easiest (although not the fastest) way to move a database between two machines is to run the following commands on the machine on which the database is located: shell> mysqladmin -h 'other hostname' create db_name shell> mysqldump --opt db_name \ | mysql -h 'other hostname' db_name  If you want to copy a database from a remote machine over a slow network, you can use: shell> mysqladmin create db_name shell> mysqldump -h 'other hostname' --opt --compress db_name \  | mysql db_name  You can also store the result in a file, then transfer the file to the target machine and load the file into the database there. For example, you can dump a database to a file on the source machine like this: shell> mysqldump --quick db_name | gzip > db_name.contents.gz  (The file created in this example is compressed.) Transfer the file containing the database contents to the target machine and run these commands there: shell> mysqladmin create db_name shell> gunzip < db_name.contents.gz | mysql db_name  You can also use mysqldump and mysqlimport to accomplish the database transfer. For big tables, this is much faster than simply using mysqldump. In the following commands, DUMPDIR represents the full pathname of the directory you use to store the output from mysqldump. First, create the directory for the output files and dump the database: shell> mkdir DUMPDIR shell> mysqldump --tab=DUMPDIR db_name  8.2.2 The DBI Interface3  Then transfer the files in the DUMPDIR directory to some corresponding directory on the target machine and load the files into MySQL there: shell> mysqladmin create db_name# create database shell> cat DUMPDIR/*.sql | mysql db_name # create tables in database shell> mysqlimport db_name DUMPDIR/*.txt # load data into tables  Also, don't forget to copy the mysql database because that's where the grant tables (user, db, host) are stored. You may have to run commands as the MySQL root user on the new machine until you have the mysql database in place.  After you import the mysql database on the new machine, execute mysqladmin flush-privileges so that the server reloads the grant table information.  2.6 Operating System Specific Notes 2.6.1 Linux Notes (All Linux Versions)  The following notes regarding glibc apply only to the situation when you build MySQL yourself. If you are running Linux on an x86 machine, in most cases it is much better for you to just use our binary. We link our binaries against the best patched version of glibc we can come up with and with the best compiler options, in an attempt to make it suitable for a high-load server. So if you read the following text, and are in doubt about what you should do, try our binary first to see if it meets your needs, and worry about your own build only after you have discovered that our binary is not good enough. In that case, we would appreciate a note about it, so we can build a better binary next time. For a typical user, even for setups with a lot of concurrent connections and/or tables exceeding the 2G limit, our binary in most cases is the best choice.  MySQL uses LinuxThreads on Linux. If you are using an old Linux version that doesn't have glibc2, you must install LinuxThreads before trying to compile MySQL. You can get LinuxThreads at http://www.mysql.com/Downloads/Linux/.  Note: we have seen some strange problems with Linux 2.2.14 and MySQL on SMP systems. If you have a SMP system, we recommend you upgrade to Linux 2.4 as soon as possible! Your system will be faster and more stable by doing this!  Note that glibc versions before and including Version 2.1.1 have a fatal bug in pthread_mutex_timedwait handling, which is used when you do INSERT DELAYED. We recommend that you not use INSERT DELAYED before upgrading glibc.  If you plan to have 1000+ concurrent connections, you will need to make some changes to LinuxThreads, recompile it, and relink MySQL against the new `libpthread.a'. Increase PTHREAD_THREADS_MAX in `sysdeps/unix/sysv/linux/bits/local_lim.h' to 4096 and decrease STACK_SIZE in `linuxthreads/internals.h' o 256 KB. The paths are relative to the root of glibc Note that MySQL will not be stable with around 600-1000 connections if STACK_SIZE is the default of 2 MB.  If MySQL can't open enough files, or connections, it may be that you haven't configured Linux to handle enough files.  In Linux 2.2 and onward, you can check the number of allocated file handlers by doing: cat /proc/sys/fs/file-max cat /proc/sys/fs/dquot-max cat /proc/sys/fs/super-max  2.6 Operating System Specific Notes4 If you have more than 16 MB of memory, you should add something like the following in your boot script (`/etc/rc/boot.local' on SuSE): echo 65536 > /proc/sys/fs/file-max echo 8192 > /proc/sys/fs/dquot-max echo 1024 > /proc/sys/fs/super-max  You can also run the preceding commands from the command-line as root, but in this case your old limits will be used the next time your computer reboots.  You should also add /etc/my.cnf: [safe_mysqld] open-files-limit=8192  This should allow MySQL to create up to 8192 connections + files.  The STACK_SIZE constant in LinuxThreads controls the spacing of thread stacks in the address space. It needs to be large enough so that there will be plenty of room for the stack of each individual thread, but small enough to keep the stack of some threads from running into the global mysqld data. Unfortunately, the Linux implementation of mmap(), as we have experimentally discovered, will successfully unmap an already mapped region if you ask it to map out an address already in use, zeroing out the data on the entire page, instead of returning an error. So, the safety of mysqld or any other threaded application depends on the "gentleman" behaviour of the code that creates threads. The user must take measures to make sure the number of running threads at any time is sufficiently low for threa stacks to stay away from the global heap. With mysqld, you should enforce this "gentleman" behaviour by setting a reasonable value for the max_connections variable.  If you build MySQL yourself and do not want to mess with patching LinuxThreads, you should set max_connections to a value no higher than 500. It should be even less if you have a large key buffer, large heap tables, or some other things that make mysqld allocate a lot of memory, or if you are running a 2.2 kernel with a 2G patch. If you are using our binary or RPM version 3.23.25 or later, you can safely set max_connections at 1500, assuming no large key buffer or heap tables with lots of data. The more you reduce STACK_SIZE in LinuxThreads the more threads you can safely create. We recommend the values between 128K and 256K.  If you use a lot of concurrent connections, you may suffer from a "feature" in the 2.2 kernel that penalises a process for forking or cloning a child in an attempt to prevent a fork bomb attack. This will cause MySQL not to scale well as you increase the number of concurrent clients. On single-CPU systems, we have seen this manifested in a very slow thread creation, which means it may take a long time to connect to MySQL (as long as 1 minute), and it may take just as long to shut it down. On multiple-CPU systems, we have observed a gradual drop in query speed as the number of clients increases. n the process of trying to find a solution, we have received a kernel patch from one of our users, who claimed it made a lot of difference for his site. The patch is available at http://www.mysql.com/Downloads/Patches/linux-fork.patch. We have now done rather extensive testing of his patch on both development and production systems. It has significantly improved MySQL performance without causing any problems and we now recommend it to our users who are still running high-load servers on 2.2 kernels. This issue has been fixed in the 2.4 kernel, so if you are not satisfied with the current performance of your system, rather than patching your 2.2 kernel, it might be easier to just upgrade to 2.4, which will also give you a nice SMP boost in addition to fixing this fairness bug. We have tested MySQL on the 2.4 kernel on a 2-CPU machine and found MySQL scales much better@-there was virtually no slowdown on queries throughput all the way up to 1000 clients, and the MySQL scaling factor (computed as the ratio of maximum throughput to the throughput with one client) was 180%. We have observed similar results on a 4-CPU system@-virtually no slowdown as the number of clients was increased up to 1000, and 300% scaling factor. So for a high-load SMP server we would definitely recommend the 2.4  http://www.mysql.com/Downloads/Patches/linux-fork.patch5 kernel at this point. We have discovered that it is essential to run mysqld process with the highest possible priority on the 2.4 kernel to achieve maximum performance. This can be done by adding renice -20 $$ command to safe_mysqld. In our testing on a 4-CPU machine, increasing the priority gave 60% increase in throughput with 400 clients.  We are currently also trying to collect more info on how well MySQL performs on 2.4 kernel on 4-way and 8-way systems. If you have access such a system and have done some benchmarks, please send a mail to docs@mysql.com with the results - we will include them in the manual. There is another issue that greatly hurts MySQL performance, especially on SMP systems. The implementation of mutex in LinuxThreads in glibc-2.1 is very bad for programs with many threads that only hold the mutex for a short time. On an SMP system, ironic as it is, if you link MySQL against unmodified LinuxThreads, removing processors from the machine improves MySQL performance in many cases. We have made a patch available for glibc 2.1.3 to correct this behaviour (http://www.mysql.com/Downloads/Linux/linuxthreads-2.1-patch).  With glibc-2.2.2 MySQL version 3.23.36use the adaptive mutex, which is much better than even the patched one in glibc-2.1.3. Be warned, however, that under some conditions, the current mutex code in glibc-2.2.2 overspins, which hurts MySQL performance. The chance of this condition can be reduced by renicing mysqld process to the highest priority. We have also been able to correct the overspin behaviour with a patch, available at http://www.mysql.com/Downloads/Linux/linuxthreads-2.2.2.patch. It combines the correction of overspin, maximum number of threads, and stack spacing all in one. You will need to apply it in the linuxthreads directory with patch -p0 cp support-files/mysql.server /etc/init.d/mysql.server shell> /usr/sbin/update-rc.d mysql.server defaults 99  mysql.server can be found in the `share/mysql' directory under the MySQL installation directory or in the `support-files' directory of the MySQL source tree. If mysqld always core dumps when it starts up, the problem may be that you have an old `/lib/libc.a'. Try renaming it, then remove `sql/mysqld' and do a new make install and try again. This problem has been reported on some Slackware installations.  If you get the following error when linking mysqld, it means that your `libg++.a' is not installed correctly: /usr/lib/libc.a(putc.o): In function `_IO_putc': putc.o(.text+0x0): multiple definition of `_IO_putc'  You can avoid using `libg++.a' by running configure like this: shell> CXX=gcc ./configure  2.6.1.3 Linux SPARC Notes  In some implementations, readdir_r() is broken. The symptom is that SHOW DATABASES always returns an empty set. This can be fixed by removing HAVE_READDIR_R from `config.h' after configuring and before compiling.  Some problems will require patching your Linux installation. The patch can be found at http://www.mysql.com/Downloads/patches/Linux-sparc-2.0.30.diff. This patch is against the Linux distribution `sparclinux-2.0.30.tar.gz' that is available at vger.rutgers.edu (a version of Linux that was never merged with the official 2.0.30). You must also install LinuxThreads Version 0.6 or newer.  2.6.1.4 Linux Alpha Notes  MySQL Version 3.23.12 is the first MySQL version that is tested on Linux-Alpha. If you plan to use MySQL on Linux-Alpha, you should ensure that you have this version or newer.  We have tested MySQL on Alpha with our benchmarks and test suite, and it appears to work nicely. The main thing we haven't yet had time to test is how things works with many concurrent users. When we compiled the standard MySQL binary we are using SuSE 6.4, kernel 2.2.13-SMP, Compaq C compiler (V6.2-504) and Compaq C++ compiler (V6.3-005) on a Comaq DS20 machine with an Alpha EV6 processor.  You can find the above compilers at http://www.support.compaq.com/alpha-tools/). By using these compilers, instead of gcc, we get about 9-14% better performance with MySQL.  Note that the configure line optimised the binary for the current CPU; this means you can only use our binary if you have an Alpha EV6 processor. We also compile staticall