Bug #14930 Index creation: ListView / ListStore bug - displays NULLs
Submitted: 14 Nov 2005 22:46 Modified: 7 Dec 2005 3:55
Reporter: Daniel Kasak (Candidate Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.1.4 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[14 Nov 2005 22:46] Daniel Kasak
Description:
The ListView that a user drags columns to when creating an index is broken. Instead of receiving details of columns, it receives NULL values.

How to repeat:
Go to the Catalogs section.
Go to a table.
Add a new index.
Drag a column into the ListView to add it to the index.
Note that nothing appears to happen.
Try dragging another column into the ListView.
Note again that nothing appears to happen.
Click around inside the ListView.
Note that there *ARE* rows being appended to the ListStore, but these rows all have NULL values in them instead of the column's details.
Hit the apply button to submit the changes.
Note the SQL generated. Instead of listing the names of the columns that were dragged, index definition instead has a list of NULL values, eg:

ADD INDEX `IDX_Line` ( `(null)`, `(null)`, `(null)` );

Note that the ListStore *is* populated correctly for existing indexes - this error is in the drag & drop functionality when adding columns to an index.

Suggested fix:
Fix drag & drop of columns into the ListStore.
[21 Nov 2005 17:21] Jorge del Conde
Thanks for your bug report.  I was able to reproduce this bug using 1.1.4 under FC4
[7 Dec 2005 3:55] Alfredo Kojima
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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html