Bug #108967 Unknown Index out of range reported by Workbench
Submitted: 2 Nov 2022 11:42 Modified: 2 Dec 2022 13:03
Reporter: Robert Coffield Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version: OS:Windows
Assigned to: MySQL Verification Team CPU Architecture:x86 (Windows 10)
Tags: MySQL 8

[2 Nov 2022 11:42] Robert Coffield
Description:
I was working on a MYSQL STORED PROCEDURE for my class at UCSC Extension class.
The stored procedure was dropping table constraints: FOREIGN KEY, PRIMARY KEY and UNIQUE constraints in two tables.  

I was running the MySQL 8 and Workbench on my laptop (Windows 10).

The tables are 'vendors' and 'invoices' from "Murach's MySQL 2nd Edition".
The tables were for test purposes only. My stored procedure used the
"ALTER TABLE" command to DROP the FOREIGN KEY and PRIMARY KEY constraints.
But I had to use the DROP INDEX command to DROP the UNIQUE constraint. After my stored procedure terminated - I used a SELECT statement on the INFORMATION_SCHEMA.TABLE_CONTRAINTS table to just the effect of my stored procedure.

On returning to WORKBENCH and error message was displayed saying that an "index was out of range".

How to repeat:
I have not been able to repeat the bug.
[2 Nov 2022 13:03] MySQL Verification Team
Hello Robert,

Thank you for the bug report.
Are you able to repeat the issue? If yes, please launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html). Thanks.

Regards,
Ashwini Patil
[3 Dec 2022 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".