Bug #115774 MySQL Workbench: Index out of range
Submitted: 5 Aug 17:18 Modified: 5 Aug 17:43
Reporter: Hridia Tanha Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0 CE OS:Windows
Assigned to: MySQL Verification Team CPU Architecture:Any

[5 Aug 17:18] Hridia Tanha
Description:
MySQL Workbench has encountered a problem
Index was out of range. Must be non-negative and less than the size of the collection

How to repeat:
create and load the table 'fy21_c1' with 707281 rows and then execute fy21c1_ASSMT_yearCheck.sql.

cr_c1_21.sql:
USE dbmaster;
DROP TABLE IF EXISTS fy21_c1;
CREATE TABLE fy21_c1
(PARID VARCHAR(255),
BORO VARCHAR(1),
BLOCK VARCHAR(5),
LOT VARCHAR(4),
EASE VARCHAR(25),
SUBIDENT_REUC VARCHAR(25),
RECTYPE VARCHAR(25),
YEAR VARCHAR(25),
IDENT VARCHAR(25),
SUBIDENT VARCHAR(25),
ROLL_SECTION VARCHAR(25),
SECVOL VARCHAR(25),
PYMKTLAND VARCHAR(25),
PYMKTTOT VARCHAR(25),
PYACTLAND VARCHAR(25),
PYACTTOT VARCHAR(25),
PYACTEXTOT VARCHAR(25),
PYTRNLAND VARCHAR(25),
PYTRNTOT VARCHAR(25),
PYTRNEXTOT VARCHAR(25),
PYTXBTOT VARCHAR(25),
PYTXBEXTOT VARCHAR(25),
PYTAXCLASS VARCHAR(2),
TENMKTLAND VARCHAR(25),
TENMKTTOT VARCHAR(25),
TENACTLAND VARCHAR(25),
TENACTTOT VARCHAR(25),
TENACTEXTOT VARCHAR(25),
TENTRNLAND VARCHAR(25),
TENTRNTOT VARCHAR(25),
TENTRNEXTOT VARCHAR(25),
TENTXBTOT VARCHAR(25),
TENTXBEXTOT VARCHAR(25),
TENTAXCLASS VARCHAR(2),
CBNMKTLAND VARCHAR(25),
CBNMKTTOT VARCHAR(25),
CBNACTLAND VARCHAR(25),
CBNACTTOT VARCHAR(25),
CBNACTEXTOT VARCHAR(25),
CBNTRNLAND VARCHAR(25),
CBNTRNTOT VARCHAR(25),
CBNTRNEXTOT VARCHAR(25),
CBNTXBTOT VARCHAR(25),
CBNTXBEXTOT VARCHAR(25),
CBNTAXCLASS VARCHAR(2),
FINMKTLAND VARCHAR(25),
FINMKTTOT VARCHAR(25),
FINACTLAND VARCHAR(25),
FINACTTOT VARCHAR(25),
FINACTEXTOT VARCHAR(25),
FINTRNLAND VARCHAR(25),
FINTRNTOT VARCHAR(25),
FINTRNEXTOT VARCHAR(25),
FINTXBTOT VARCHAR(25),
FINTXBEXTOT VARCHAR(25),
FINTAXCLASS VARCHAR(2),
CURMKTLAND VARCHAR(25),
CURMKTTOT VARCHAR(25),
CURACTLAND VARCHAR(25),
CURACTTOT VARCHAR(25),
CURACTEXTOT VARCHAR(25),
CURTRNLAND VARCHAR(25),
CURTRNTOT VARCHAR(25),
CURTRNEXTOT VARCHAR(25),
CURTXBTOT VARCHAR(25),
CURTXBEXTOT VARCHAR(25),
CURTAXCLASS VARCHAR(2),
PERIOD VARCHAR(25),
NEWDROP VARCHAR(25),
NOAV VARCHAR(25),
VALREF VARCHAR(25),
BLDG_CLASS VARCHAR(2),
OWNER VARCHAR(80),
ZONING VARCHAR(25),
HOUSENUM_LO VARCHAR(12),
HOUSENUM_HI VARCHAR(12),
STREET_NAME VARCHAR(30),
ZIP_CODE VARCHAR(25),
GEOSUPPORT_RC VARCHAR(2),
STCODE VARCHAR(25),
LOT_FRT DECIMAL(6,2),
LOT_DEP DECIMAL(6,2),
LOT_IRREG VARCHAR(25),
BLD_FRT DECIMAL(6,2),
BLD_DEP DECIMAL(6,2),
BLD_EXT DECIMAL(6,2),
BLD_STORY DECIMAL(5,2),
CORNER VARCHAR(2),
LAND_AREA VARCHAR(9),
NUM_BLDGS VARCHAR(5),
YRBUILT VARCHAR(25),
YRBUILT_RANGE VARCHAR(25),
YRBUILT_FLAG VARCHAR(25),
YRALT1 VARCHAR(25),
YRALT1_RANGE VARCHAR(25),
YRALT2 VARCHAR(25),
YRALT2_RANGE VARCHAR(25),
COOP_APTS VARCHAR(5),
UNITS VARCHAR(5),
REUC_REF VARCHAR(20),
APTNO VARCHAR(25),
COOP_NUM VARCHAR(6),
CPB_BORO VARCHAR(25),
CPB_DIST VARCHAR(2),
APPT_DATE VARCHAR(8),
APPT_BORO VARCHAR(25),
APPT_BLOCK VARCHAR(5),
APPT_LOT VARCHAR(25),
APPT_EASE VARCHAR(25),
CONDO_Number VARCHAR(6),
CONDO_SFX1 VARCHAR(25),
CONDO_SFX2 VARCHAR(25),
CONDO_SFX3 VARCHAR(25),
UAF_LAND DECIMAL(10,7),
UAF_BLDG DECIMAL(10,7),
PROTEST_1 VARCHAR(3),
PROTEST_2 VARCHAR(3),
PROTEST_OLD VARCHAR(3),
ATTORNEY_GROUP1 VARCHAR(25),
ATTORNEY_GROUP2 VARCHAR(25),
ATTORNEY_GROUP_OLD VARCHAR(25),
GROSS_SQFT VARCHAR(9),
HOTEL_AREA_GROSS VARCHAR(8),
OFFICE_AREA_GROSS VARCHAR(8),
RESIDENTIAL_AREA_GROSS VARCHAR(8),
RETAIL_AREA_GROSS VARCHAR(8),
LOFT_AREA_GROSS VARCHAR(8),
FACTORY_AREA_GROSS VARCHAR(8),
WAREHOUSE_AREA_GROSS VARCHAR(8),
STORAGE_AREA_GROSS VARCHAR(8),
GARAGE_AREA VARCHAR(8),
OTHER_AREA_GROSS VARCHAR(8),
REUC_DESCRIPTION VARCHAR(500),
EXTRACTDT DATE,
PYTAXFLAG VARCHAR(25),
TENTAXFLAG VARCHAR(25),
CBNTAXFLAG VARCHAR(25),
FINTAXFLAG VARCHAR(25),
CURTAXFLAG VARCHAR(25)
);

loadc1_fy21.sql:
USE dbmaster;
LOAD DATA LOCAL INFILE "C:/Users/HridiaTanha/Documents/fy16_24_c1/fy21_c1.txt"
Into table fy21_c1
fields terminated by '\t'
OPTIONALLY ENCLOSED BY '"'
ESCAPED BY '"'
LINES TERMINATED BY '\n'
IGNORE 1 LINES
(PARID,
BORO,
BLOCK,
LOT,
EASE,
SUBIDENT_REUC,
RECTYPE,
YEAR,
IDENT,
SUBIDENT,
ROLL_SECTION,
SECVOL,
PYMKTLAND,
PYMKTTOT,
PYACTLAND,
PYACTTOT,
PYACTEXTOT,
PYTRNLAND,
PYTRNTOT,
PYTRNEXTOT,
PYTXBTOT,
PYTXBEXTOT,
PYTAXCLASS,
TENMKTLAND,
TENMKTTOT,
TENACTLAND,
TENACTTOT,
TENACTEXTOT,
TENTRNLAND,
TENTRNTOT,
TENTRNEXTOT,
TENTXBTOT,
TENTXBEXTOT,
TENTAXCLASS,
CBNMKTLAND,
CBNMKTTOT,
CBNACTLAND,
CBNACTTOT,
CBNACTEXTOT,
CBNTRNLAND,
CBNTRNTOT,
CBNTRNEXTOT,
CBNTXBTOT,
CBNTXBEXTOT,
CBNTAXCLASS,
FINMKTLAND,
FINMKTTOT,
FINACTLAND,
FINACTTOT,
FINACTEXTOT,
FINTRNLAND,
FINTRNTOT,
FINTRNEXTOT,
FINTXBTOT,
FINTXBEXTOT,
FINTAXCLASS,
CURMKTLAND,
CURMKTTOT,
CURACTLAND,
CURACTTOT,
CURACTEXTOT,
CURTRNLAND,
CURTRNTOT,
CURTRNEXTOT,
CURTXBTOT,
CURTXBEXTOT,
CURTAXCLASS,
PERIOD,
NEWDROP,
NOAV,
VALREF,
BLDG_CLASS,
OWNER,
ZONING,
HOUSENUM_LO,
HOUSENUM_HI,
STREET_NAME,
ZIP_CODE,
GEOSUPPORT_RC,
STCODE,
LOT_FRT,
LOT_DEP,
LOT_IRREG,
BLD_FRT,
BLD_DEP,
BLD_EXT,
BLD_STORY,
CORNER,
LAND_AREA,
NUM_BLDGS,
YRBUILT,
YRBUILT_RANGE,
YRBUILT_FLAG,
YRALT1,
YRALT1_RANGE,
YRALT2,
YRALT2_RANGE,
COOP_APTS,
UNITS,
REUC_REF,
APTNO,
COOP_NUM,
CPB_BORO,
CPB_DIST,
APPT_DATE,
APPT_BORO,
APPT_BLOCK,
APPT_LOT,
APPT_EASE,
CONDO_Number,
CONDO_SFX1,
CONDO_SFX2,
CONDO_SFX3,
UAF_LAND,
UAF_BLDG,
PROTEST_1,
PROTEST_2,
PROTEST_OLD,
ATTORNEY_GROUP1,
ATTORNEY_GROUP2,
ATTORNEY_GROUP_OLD,
GROSS_SQFT,
HOTEL_AREA_GROSS,
OFFICE_AREA_GROSS,
RESIDENTIAL_AREA_GROSS,
RETAIL_AREA_GROSS,
LOFT_AREA_GROSS,
FACTORY_AREA_GROSS,
WAREHOUSE_AREA_GROSS,
STORAGE_AREA_GROSS,
GARAGE_AREA,
OTHER_AREA_GROSS,
REUC_DESCRIPTION,
EXTRACTDT,
PYTAXFLAG,
TENTAXFLAG,
CBNTAXFLAG,
FINTAXFLAG,
CURTAXFLAG
)
;

fy21c1_ASSMT_yearCheck.sql:
SELECT 
PARID,
YEAR,
BORO
FROM fy21_c1
WHERE BORO = 1
ORDER BY YEAR DESC

This isn't specific to just this; the error message comes up often out of no where. If I restart my laptop, it works fine and the error goes away. But it keep coming back every once in a while.
[5 Aug 17:43] MySQL Verification Team
Hi MR. Tanha,

Thank you for your bug report.

However, in order to repeat the bug, we need all the 700K+ rows and we need the file for LOAD DATA.

We can not continue without those.

Waiting on your full feedback.