MySQL Bugs: #25861: "Table Engine" list is empty

Bug #25861	"Table Engine" list is empty
Submitted:	26 Jan 2007 10:38	Modified:	29 Jan 2007 15:54
Reporter:	Anders	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.9	OS:	Windows (Windows 2k)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When using the dialog "MySQL Table Editor" in the graphical tools "MySQL Administrator" or "MySQL Query Browser", then the "Table Engine"-list on the "Table Options"-tab is empty.
The server version is: MySQL 4.0.20-standard-log via TCP/IP
The client is: MySQL Client Version 5.1.11

How to repeat:
Connect to a database server using either "MySQL Administrator" or "MySQL Query Browser" and try to edit a table or try to create a new table. Observe that on the "Table Options"-tab it is not possible to choose a table engine since the "Table Engine"-list is empty and the field is restricted to the list.

Suggested fix:
Fill the list with allowed values or allow the user to enter free text into the "Table Engine"-field.

This might be related:
If I have changed to storage engine of a table to InnoDB (using e.g. the query "ALTER TABLE t ENGINE = InnoDB;"), I open the table editor for the table, and enter the "Foreign Keys"-tab, I get the message Foreign Keys are currently only support [sic] for the InnoDB storage engine. Your foreign key definitions will be ignored." That is, even though the table uses the InnoDB storage engine (as can be verified using the "Catalogs"-item in MySQL Administrator), I get a warning that foreign keys will be ignored and the fields on the foreign keys tab are disabled.

(minor note: The alert is only shown if I manually activate the "Foreign Keys"-tab. If the tab is already the active tab when the "Table Editor" is opened, the alert is not shown)

Thank you for the bug report. I was able to repeat only with servers 4.0.XX.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html