[BUG] Statement execute thrown exception doesn't populate the odbcErrors array

[phpdave]

Describe your system

• odbc Package Version: 2.4.9
• ODBC Driver: 1.1.0.28-0
• unixODBC 2.3.9
• Database Name: DB2 for i
• Database Version: V7R5M0
• Database OS: IBM i
• Node.js Version: 18.18.2
• Node.js OS: IBM i

Describe the bug
The error doesn't contain the odbcErrors data. console.log of the error in a catch block will give you

[Error: [odbc] Error executing the statement] { odbcErrors: [] }

Expected behavior
odbcErrors to have the information about what caused the error

To Reproduce
Steps to reproduce the behavior:

1. Run the node.js code below:

Code

try {
const connection = await odbc.connect(my_connection_string);
const statement = await connection.createStatement();
let bindVal = [
        field1 || '',
        field2 || '']
await statement.prepare(`UPDATE MYLIB.MYTABLE
      SET 
      FIELD1 = ?
      WHERE FIELD2 = ?`);
await statement.bind(bindVal);
const result = await statement.execute();
} catch (error) {
        console.log(error);
        const odbc_error = error?.odbcErrors || 'No ODBC error object';
        console.log(odbc_error)
        const odbc_error_message = error?.odbcErrors?.[0]?.message || 'No ODBC error message';
        console.log(odbc_error_message)
}

Additional context
Checked the following table to find out what the error was but couldn't find anything there either:
qsys2.history_log_info
qsys2.joblog_info
#389 - @harsh-savvient mentioned this issue
#363 - @mikemicmike also raised this issue Dec 21, 2023 and @FredoMartini confirmed it March 1, 2024 and the robot closed the issue May 30, 2024 as stale
#30

[phpdave]

It might be when the where clause filters to 0 rows. In DB2 for i VS code extension it returns this instead of an error message :

Statement executed with no result set returned. Rows affected: 0