SAP / SAP/node-hdb

COMMIT results in "Invalid or unsupported FunctionCode"

Open
#304 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
322
Forks
99
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in lib/protocol/Result.js at handle(), then trace the reply flow through Statement.js, Queue.js, and Connection.js. Reproduce the issue with a COMMIT statement and inspect how its FunctionCode is handled. Done means COMMIT completes without raising the unsupported-FunctionCode error, with coverage for this result if the repository has a relevant test location.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.