Folks,

I don't know if you're already aware of this one or not, but I couldn't find a bug related FAQ on the website, so I thought I'd just tell you about it. Sorry if it's old news.

This pertains to the MySQL Control Center (Windows Binary, 0.8.9b).

As this relates to the GUI I'd like to include screen shots as they may greatly clarify things, but since I presume this is going to a list, I'll refrain and simply provide a link to the images.

The bug is that under certain conditions, you may delete an extra row when using the MySQLCC to delete a row.

How-To-Repeat:

-Start MySQLCC -Connect to a DB -Expand the DB -Expand Tables -double-click on a table name to view the contents of that table

Now that you're viewing the contents of a table, my screen shots may help: http://www.sibre.org/public/MySQLCC-Bug-20030128.tar.gz You should see something like ScreenShot1. I learned about this bug on the mysql.db table, so that's where I'm demonstrating it.

(Below, I will make repeated reference to a 'data cursor:' I'm talking about the bold outline that surrounds the cell which has focus, and which can be controlled by the cursor keys on the keyboard.)

-Click in one of the 'data' columns of a row. (In ScreenShot2 I clicked in the 'user' column of row 13.) -Now click on the row selector (the part where the row number is, but isn't part of the table data) of the row you want to delete. In ScreenShot3, I clicked on the '9', which highlighted row 9 appropriately. Note that the 'data cursor' stays on the original row. -Press the Delete button. (Sorry, no screen shot ;) ) -Answer Yes to the following prompt about deleting rows... (ScreenShot4) -Note that both the highlighted row, and the row with the 'data cursor' have been deleted. A look at the History pane shows that two DELETEs were fired instead of one. (ScreenShot5)

While I can understand the behaviour (technically, the row with the 'data cursor' is, sort of, selected), I consider it a bug, because it's not what I expected. I think the correct behaviour would be either: - Remove the 'data cursor' when a row selector has been clicked. - Ignore the 'data cursor' if any rows have been selected via the row selector, and preparing to perform any row operations.

A distant third option might be to always highlight the row that contains the data cursor, but I don't really care for that approach.

I hope that gives you enough info to fix this bug, but if not, I can be reached at jsibre at chironsys.com

Thanks for your time,

To request this thread, e-mail bugs...@lists.mysql.com To unsubscribe, e-mail <bugs...@lists.mysql.com>