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
When using pool, and when an open connection did not receive any new requests for a long time, the connection becomes stale, and any new requests are failing out.
The text was updated successfully, but these errors were encountered:
clach04
pushed a commit
to clach04/node-odbc__DO_NOT_USE
that referenced
this issue
Dec 17, 2020
When calling stored procedures with output parameters, the output is
always blank. This is due to using the wrong size field when querying
SQLProcedureColumns to retrieve the column size for each parameter. This
field is defined by ODBC as an INTEGER, but the pointer is read from a
SMALLINT instead. This results in the size being read from only the top
2 bytes of the 4 byte value. On little endian systems, this will be OK
so long as the size is < 32k. On big endian systems it will always be 0
unless the size is > 32k or negative; regardless it will always be
*wrong*.
Signed-off-by: Kevin Adler <[email protected]>
Fixesw1nk#103
When using pool, and when an open connection did not receive any new requests for a long time, the connection becomes stale, and any new requests are failing out.
The text was updated successfully, but these errors were encountered: