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
{{ message }}
Repository navigation
COMMIT results in "Invalid or unsupported FunctionCode" #304
When I execute a "commit" statement, this results in the following error:
Error: Invalid or unsupported FunctionCode
at Result.handle (.../node_modules/hdb/lib/protocol/Result.js:113:13)
at handleReply (.../node_modules/hdb/lib/protocol/Statement.js:173:12)
at receive (.../node_modules/hdb/lib/util/Queue.js:114:18)
at Connection.receive (.../node_modules/hdb/lib/protocol/Connection.js:455:5)
at TLSSocket.ondata (.../node_modules/hdb/lib/protocol/Connection.js:289:12)
at TLSSocket.emit (node:events:519:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:189:23)
The commit works, and I can circumvent the problem by try-catching the exception and ignoring it, but it would be nice if this was supported.
Hi @daniel-kullmann, could you please provide more information about this issue so that we could take a futher look? For example, briefly describe how to reproduce this issue and the version of the node-hdb you're using. Thank you!
Hi @daniel-kullmann, could you please let us know if this issue still persists? If so, could you please provide us more information about it so that we can investigate further? For example, briefly describe how to reproduce this issue and the version of the node-hdb you're using. Thank you!
As there has been no response on this issue since June 12 and there is not enough information available for the HANA Clients team to investigate further, we will be closing this issue for now.
Sorry, I didn't see the comment. I was just using a db.exec("COMMIT") in my Typescript code, and that resulted in this error.
In your code, you react react to certain types of returned result, and apparently, commit uses a return type code that is not supported at the moment. Would be nice to add that .
Hi @daniel-kullmann, could you please let us know the node-hdb version you are using? Also, as a workaround, please try using connection.commit() and see if that better suits your use case. Thanks.
Hi @daniel-kullmann, a fix for this issue is in progress. Version 2.30 of the node-hdb client is planned for release today, but the fix might not be available until the first patch release of v2.30. Thanks.
Activity
linjun-he-sap commentedon Jun 12, 2026
Hi @daniel-kullmann, could you please provide more information about this issue so that we could take a futher look? For example, briefly describe how to reproduce this issue and the version of the node-hdb you're using. Thank you!
jyotsanagupta01 commentedon Sep 21, 2026
Hi @daniel-kullmann, could you please let us know if this issue still persists? If so, could you please provide us more information about it so that we can investigate further? For example, briefly describe how to reproduce this issue and the version of the node-hdb you're using. Thank you!
jyotsanagupta01 commentedon Sep 24, 2026
As there has been no response on this issue since June 12 and there is not enough information available for the HANA Clients team to investigate further, we will be closing this issue for now.
daniel-kullmann commentedon Sep 24, 2026
Sorry, I didn't see the comment. I was just using a db.exec("COMMIT") in my Typescript code, and that resulted in this error.
In your code, you react react to certain types of returned result, and apparently, commit uses a return type code that is not supported at the moment. Would be nice to add that .
jyotsanagupta01 commentedon Sep 25, 2026
Hi @daniel-kullmann, could you please let us know the node-hdb version you are using? Also, as a workaround, please try using connection.commit() and see if that better suits your use case. Thanks.
jyotsanagupta01 commentedon Sep 25, 2026
Hi @daniel-kullmann, a fix for this issue is in progress. Version 2.30 of the node-hdb client is planned for release today, but the fix might not be available until the first patch release of v2.30. Thanks.