[BUG] Actian/Pervasive cursor fails with specific queries following upgrade from 2.4.7
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- database
Research direction
Start with the README, especially the debugging and ODBC tracing instructions, then inspect the commit history around version 2.4.8 where static cursor mode was removed. Reproduce the reported Actian Zen/Pervasive query failure against the stated versions and trace the cursor configuration. Done means queries using cursors succeed while preserving the intended behavior for other ODBC drivers.
Written by the indexing model from the issue text.
Description
Describe your system
odbcPackage Version: 2.5.0- ODBC Driver: Pervasive ODBC Interface
- Database Name: Actian Zen / Pervasive
- Database Version: 14
- Database OS: Windows Server 2019
- Node.js Version: 24.18.0
- Node.js OS: Windows 11
Describe the bug
Following an upgrade of odbc from version 2.4.7 , cursors for some queries are resulting in the following error:
[Zen][ODBC Client Interface][LNA][Zen][SQL Engine]Invalid cursor position; no keyset defined.
After looking through the commit history, I saw that 2.4.8 removed the setting of static cursor mode to increase performance. This is not playing nice with this database. Do we have the option to add the specification of a cursor mode?
Expected behavior
Query to successfully run within a cursor
- Dominant language
- JavaScript
- Stars
- 158
- Forks
- 92
- Avg merge
- 5h 59m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from IBM/node-odbc
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
security
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
[Bug] Sybase ASE: Encoding issue (works in msnodesqlv8, fails in node-odbc with \x1A artifacts)Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
smansfield635-create/smansfield635-create.github.io#5818 · 4 comments ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danjdewhurst/story-skills#538 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anoopcodehack/DevBoard#589 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 Under an hour Newbie friendliness 85/100
capricorn86/happy-dom#2474 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
vigetlabs/mega-menu-block#30 ·
Maintainers usually reply within 2 days