Bug #116859 index set to invisible
Submitted: 3 Dec 2024 16:20 Modified: 3 Dec 2024 16:42
Reporter: Jonathan Kapteijn Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:8.0.40 OS:Windows (Microsoft Windows 10 Pro)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: WBBugReporter

[3 Dec 2024 16:20] Jonathan Kapteijn
Description:
The last index of a table is unintentionaly set to INVISIBLE when viewing existing indexes for the table.
This becomes a problem if you add or edit an index and apply the changes without assessing the created SQL-query.

How to repeat:
When viewing the indexex for a table, the last index is set to invisible while navigating between indexes.
At the moment you navigate past the last index, so the empty line is selected. This is the line where a new index can be created... and then you navigate up one index, then this last index is set to INVISIBLE.

Suggested fix:
Re-apply the correct/current value for the visible check-box of the selected index when navigating between the indexes.
[3 Dec 2024 16:42] MySQL Verification Team
HI Mr. Kaptein,

Thank you for your bug report.

However, let us inform you that this is a forum for reports with fully repeatable test cases. Each of those test cases should consist of a set of SQL statements leading to the problem surfacing ........ Also, you should provide all the settings of the Workbench and exact list of the set of actions that led to the index being invisible in Workbench 8.0.40 being connected to MySQL 8.0.40.

Can't repeat.