Error updating CLOB w/ UTF8 charset
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 2.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
- What versions are you using?
Oracle 23.9.0.0, thin client.
process.platform: darwin
process.version: v24.2.0
process.arch: arm64
oracledb.versionString: 6.9.0
oracledb.oracleClientVersionString: undefined
- Is it an error or a hang or a crash?
Error
- What error(s) or behavior you are seeing?
When DB has charset UTF8 (instead of default AL32UTF8), UPDATE to CLOB column when it's not the only field being bound results in error:
ORA-01461: The value at bind position 2 exceeded the maximum VARCHAR2 length.
- Include a runnable Node.js script that shows the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the runnable Node.js reproduction linked in the issue and reproduce the UPDATE against Oracle 23.9 using the UTF8 charset, focusing on the CLOB bind at position 2. Compare the failing multi-bind update with the working case and verify that the CLOB update no longer raises ORA-01461.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100