You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All current, including 11.1.2. Discovered when using 9.2.1
SQL Server version
irrelevant
Client Operating System
Debian 11.4
JAVA/JVM version
11.0.15
Problem description
Calling a method with 10 parameters. Getting this error when setting the 8th.
com.microsoft.sqlserver.jdbc.SQLServerException: The index 11 is out of range.
I've located the problem occurs when a method calls findColumn(parameterName) multiple times.
the problem is inside private int findColumn(String columnName)
map.putIfAbsent(columnName, ai.incrementAndGet());
returnmap.get(columnName);// attempting to look up the first column will return no access exception
The ai.incrementAndGet() is called even though the parameter is already present.
This is fine if there are no more parameters after it, but there are this time.
suggested correction:
Hi @coladict, thanks for bringing this to our attention. Currently we're busy preparing for release, would it be possible for you to open a PR? Or could you provide us a repro that we can use for a test? If not we'll try and address this as soon as we can.
tkyc
added
the
Backlog
The topic in question has been recognized and added to development backlog
label
Jul 26, 2022
Driver version
All current, including 11.1.2. Discovered when using 9.2.1
SQL Server version
irrelevant
Client Operating System
Debian 11.4
JAVA/JVM version
11.0.15
Problem description
Calling a method with 10 parameters. Getting this error when setting the 8th.
I've located the problem occurs when a method calls
findColumn(parameterName)
multiple times.the problem is inside
private int findColumn(String columnName)
The
ai.incrementAndGet()
is called even though the parameter is already present.This is fine if there are no more parameters after it, but there are this time.
suggested correction:
The text was updated successfully, but these errors were encountered: