Skip to content

docs: psqlodbc #207 and #208 fixed in 18.00.0003, verified on the release build - #101

Merged
singhpratech merged 1 commit into
mainfrom
docs/psqlodbc-18-00-0003
Sep 10, 2026
Merged

docs: psqlodbc #207 and #208 fixed in 18.00.0003, verified on the release build#101
singhpratech merged 1 commit into
mainfrom
docs/psqlodbc-18-00-0003

Conversation

@singhpratech

Copy link
Copy Markdown
Owner

psqlodbc REL-18_00_0003 was released on 2026-09-10 and carries #209 (savepoint-free DEALLOCATE at rollback level 0), #210 (22003 on out-of-range integer conversion) and #211 (indicator untouched on that path).

Verified on the tag built from source in a clean Ubuntu 24.04 container (libpq 16.15, unixODBC 2.3.12):

  • #207 program against PostgreSQL 16.15: out-of-range rows return SQL_ERROR 22003 with the data buffer and indicator untouched, on SQLGetData and SQLBindCol; in-range rows unchanged.
  • #208 program: QuestDB keeps both rows when the statement is freed before the commit (stock 16.00.0000 loses both); PostgreSQL 16.15 is 2/2 in both modes.

Both UPSTREAM rows now read "fixed in psqlodbc 18.00.0003". Docs only; the psqlodbc note is updated in the site source and goes out with the next gh-pages push.

🤖 Generated with Claude Code

https://claude.ai/code/session_012QpuUDF9x53Bi3sGo9zXDT

…ease tag build

Dave Cramer released psqlodbc 18.00.0003 on 2026-09-10 with #209, #210 and
#211. The tag was built from source in a clean Ubuntu 24.04 container and
both programs re-run: #207 returns 22003 with the buffer and indicator
untouched on SQLGetData and SQLBindCol against PostgreSQL 16.15; #208 keeps
both rows on QuestDB when the statement is freed before the commit (stock
16.00 loses both), PostgreSQL 16.15 unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012QpuUDF9x53Bi3sGo9zXDT
@singhpratech
singhpratech merged commit 5fdb657 into main Sep 10, 2026
5 checks passed
@singhpratech
singhpratech deleted the docs/psqlodbc-18-00-0003 branch September 10, 2026 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant