Bug #114625 Can't query table: 'Index was out of range.'
Submitted: 11 Apr 2024 14:17 Modified: 12 May 2024 11:41
Reporter: John Noad Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0 CE OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any

[11 Apr 2024 14:17] John Noad
Description:
Ran query: 'SELECT * FROM people;'

Returned:
'Index was out of range. Must be non-negative and less than the size of the collection.'

People is a table with over 1000 entries, However it cannot be queries without the above error popping up. 

How to repeat:
-Table was created and dropped a few times before. 
-Table was populated via a NodeJS script. 
-When populated previously in the same way, there was no issue.
-Suddenly after the latest population of the table, running a simple select statement returns the error.

Not sure what caused this, but it makes all the data in the table inaccessable.
[12 Apr 2024 11:41] MySQL Verification Team
Hello John,

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to 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)?

Regards,
Ashwini Patil
[13 May 2024 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".