Abdirahim Musse

> I will prepare the script... Thank you!

I've formatted JSON from https://github.com/IBM/nodejs-idb-connector/issues/173#issuecomment-1637502311 and https://github.com/IBM/nodejs-idb-connector/issues/173#issuecomment-1637504547 for readability # https://github.com/IBM/nodejs-idb-connector/issues/173#issuecomment-1637502311 ```json { "COLUMN_NAME": "PARCOURS", "TABLE_NAME": "BTRLIG", "TABLE_OWNER": "EUREKA", "ORDINAL_POSITION": "46", "DATA_TYPE": "CLOB ", "LENGTH": "99999", "NUMERIC_SCALE": null, "IS_NULLABLE": "Y",...

Hi @Didier68 👋🏿 Per out last discussion see https://github.com/IBM/nodejs-idb-connector/issues/173#issuecomment-1635033531, https://github.com/IBM/nodejs-idb-connector/issues/173#issuecomment-1637502311 were you able to create a script that reproduces the error? If so, please paste the script in a comment...

Hello @nedi-dev :wave: Interesting that when using `odbc` transport you do not run into the errors. Does the error occur every time using `idb` transport or randomly? I noticed from...

What version of idb-connector do you have installed? ``` $ npm ls idb-connector ``` I'm thinking this could be an issue with [dbstmt.fetchAll](https://github.com/IBM/nodejs-itoolkit/blob/master/lib/transports/idbTransport.js#L91). Can you add the following to line...

From your output looks like the data retrieved using `idb-connector` is already corrupted before we iterate over `results` array and append to the `xmlOutput`. So seems to be an issue...

@dmabupt Any thoughts on what may be causing this issue?

Interesting I wonder if this issue is related to https://github.com/IBM/nodejs-idb-connector/issues/70.

@richardlau I think things are looking good in this PR. Do you know who should be added as a reviewer so that we can get this reviewed and merged?