Bug #6292 | MySQL CC 0.9.4 prevents selection of InnoDB Tables | ||
---|---|---|---|
Submitted: | 27 Oct 2004 19:55 | Modified: | 28 Oct 2004 11:34 |
Reporter: | Philip G. Duffy | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 0.9.4 | OS: | Windows (Windows XP Pro SP1) |
Assigned to: | CPU Architecture: | Any |
[27 Oct 2004 19:55]
Philip G. Duffy
[27 Oct 2004 21:08]
Hartmut Holzgraefe
Thank you for your interest in the MySQL graphical administration tools. We recommend that you use our MySQL Administrator and MySQL Query Browser. The MySQLGUI and MySQL Command Center legacy products are deprecated, and we are no longer maintaining those projects. For more information on MySQL Administrator, see: http://www.mysql.com/products/administrator/
[27 Oct 2004 23:00]
Philip G. Duffy
I understand that you have deprecated MySQL Control Center and are recommending its replacement with MySQL Administrator and possibly MySQL Query Browser. Are both necessary to replace MySQL CC (I am accessing MySQL through PHP)? What are the licensing costs? Also, do I have any alternatives to $295/incident support which prices the small developer out of the market? If I install these products, should I previously upgrade MySQL to Version 4.1.7? How do I maintain my existing database? Thank you. Phil Duffy
[28 Oct 2004 11:34]
Hartmut Holzgraefe
Could it be that the server does not have InnoDB support activated? In that case a CREATE TABLE (...) TYPE=InnoDB; would fall back to using the default table type (usually MyISAM) and this would happen with any client, not only MySQL CC. MySQL Adminstrator and Query are released under the GPL just as MySQL CC was before so the licensing situation has not changed. Both tools work with MySQL 4.0 and above. MySQL 3.23 and older are not officially supported but may work, too.