MySQL does not support InnoDB's solution

After G1, the solution is as follows:
Under /var/lib/mysql, delete ibdata1, ib_logfile1, ib_logfile0, and then restart MySql to rebuild the above files:
mysqladmin -uroot -p shutdown
sudo mysqld_safe &
Done!

Here are some other articles on the web. You can also refer to it.
When I got up in the morning, I went to the PHP site to check it out, ready to test an CMS system written by someone else, happily downloaded the program, and then copied it to the directory. Since the program does not have install.php, it only contains a *.sql database statement, so only the mysql database can execute this statement:
After entering the database, enter the directory where source is located /*.sql
At this point the question arises:
QUOTE:

 
MySQL Server Error: 
The 'InnoDB' feature is disabled; you need MySQL built with 'InnoDB' to have it working 

Enter SHOW variables like "have_%" in mysql and it will display as follows:

 
mysql> SHOW variables like "have_%" 
-> ; 
+-----------------------+----------+ 
| Variable_name | Value | 
+-----------------------+----------+ 
| have_archive | YES | 
| have_bdb | NO | 
| have_blackhole_engine | NO | 
| have_compress | YES | 
| have_crypt | NO | 
| have_csv | NO | 
| have_dynamic_loading | YES | 
| have_example_engine | NO | 
| have_federated_engine | NO | 
| have_geometry | YES | 
| have_innodb | DISABLED | 
| have_isam | NO | 
| have_merge_engine | YES | 
| have_ndbcluster | NO | 
| have_openssl | DISABLED | 
| have_query_cache | YES | 
| have_raid | NO | 
| have_rtree_keys | YES | 
| have_symlink | YES | 
+-----------------------+----------+ 
19 rows in set (0.00 sec) 

Blue indicates that my MYSQL does not support innodb.


The difference between the InnoDB and MyISAM types in MySQL

 
InnoDB and MyISAM Is in use MySQL The two most commonly used table types each have advantages and disadvantages, depending on the application. The following are known differences between the two, for reference only.  
1.InnoDB Does not support FULLTEXT Type index.  
2.InnoDB  Does not save the exact number of rows in the table, that is, executes select count(*) from table When, InnoDB To scan 1 Go through the table to figure out how many rows there are, but MyISAM Simply read the number of lines saved. Notice, when count(*) Statement contains  where The operation of the two tables is 1 Kind of.  
3. for AUTO_INCREMENT Field of type, InnoDB Must contain an index for only that field, but in MyISAM Table, can and other fields 1 Set up a joint index.  
4.DELETE FROM table When, InnoDB Instead of resetting the table, instead 1 line 1 Row deletion.  
5.LOAD TABLE FROM MASTER Operation of InnoDB It doesn't work. The solution is to take it first InnoDB Table to MyISAM Table, change it after importing data InnoDB Table, but extra for use InnoDB Tables with features such as foreign keys are not applicable.  
 In addition, InnoDB The table's row locking is also not absolute, if executed at all 1 a SQL statements MySQL Not sure what range to scan, InnoDB The table also locks the full table, for example update table set num=1 where name like  " %aaa% "  
 any 1 All kinds of tables are not panacea, only the appropriate business type to choose the appropriate table type, in order to maximize the play MySQL Performance advantage.  
 If you want to use foreign keys, transactions, etc., use them innodb The engine. The method of use is create table xxx()engine=innodb; If you want to use all of the tables that you set up innodb The engine can turn" default-storage-engine=INNODB "Added to the /etc/mysql/my.cnf (the location may be different). You can use" show engines; "Check that it's set. But it is said to be set at 5.0.22 It might not work.  

I looked it up on the Internet, opened my my.ini file, found skip-innodb, and changed it to # skip-innodb.

Then restart mysql. Problem solving.

 
mysql> SHOW variables like "have_%" 
-> ; 
+-----------------------+----------+ 
| Variable_name | Value | 
+-----------------------+----------+ 
| have_archive | YES | 
| have_bdb | NO | 
| have_blackhole_engine | NO | 
| have_compress | YES | 
| have_crypt | NO | 
| have_csv | NO | 
| have_dynamic_loading | YES | 
| have_example_engine | NO | 
| have_federated_engine | NO | 
| have_geometry | YES | 
| have_innodb | YES | 
| have_isam | NO | 
| have_merge_engine | YES | 
| have_ndbcluster | NO | 
| have_openssl | DISABLED | 
| have_query_cache | YES | 
| have_raid | NO | 
| have_rtree_keys | YES | 
| have_symlink | YES | 
+-----------------------+----------+ 
19 rows in set (0.00 sec)