Korinne Adler

The latest IBM i Access ODBC driver now supports SQL_ATTR_LOGIN_TIMEOUT; and SQL_ATTR_CONNECTION_TIMEOUT on systems other than Windows. It also changes behavior of SQL_ATTR_CONNECTION_DEAD and SQL_DATA_SOURCE_READ_ONLY to only report the state...

As long as the socket is still up, the dead connection check will still report it's good. That is all the ODBC spec says that should happen. If the remote...

I think this is basically the same issue as #255 and Mark's suggestion here would be helpful: https://github.com/markdirish/node-odbc/issues/63#issuecomment-581983751 This prevents handing out "known bad" connections, however there could still be...

I think changing the default to `SQL_CD_TRUE` would be good. Not sure the benefit of checking the return value, unless you're going to call SQLGetDiagRec or something. Either the call...

@labflow Can you give more details about the driver you're using along with the database you're connecting to? @snotmare What JDBC and ODBC drivers are you using and what database...

Are you using the IBM i Access driver? If so, they work on the same protocol so they should have roughly the same performance, though certainly there are different options...

@snotmare No, I want driver traces. jt400 trace: https://www.ibm.com/support/pages/how-enable-jdbc-trace-toolbox-driver (this is for WAS, but you can set the properties any way, eg. from the command line) IBM i Access odbc...

No. Instructions are in my previous post, though I just remembered that if you're on Windows, the commands are different for ODBC. On Windows, run `cwbcotrc ON` and then find...

@snotmare From the trace, I see 3 connections being made. I'm guessing you're using a pool? None of these connections ever do anything though - your statement is never sent...

So jdbc is running on the IBM i system, but you're running odbc remotely?