Skip to content

fix: preserve GB18030 CLOB write boundaries - #17

Merged
skhe merged 1 commit into
mainfrom
codex/gb18030-clob-boundary
Sep 26, 2026
Merged

skhe merged 1 commit into
mainfrom
codex/gb18030-clob-boundary

Conversation

@skhe

@skhe skhe commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • Keep GB18030 CLOB PUT_DATA chunks on complete character boundaries, preventing incorrect database-side CLOB length near 16 KB boundaries.
  • Run ARM Linux real-DM CI across Python 3.9–3.13 and both UTF-8 / GB18030 server encodings, with an explicit UNICODE assertion.
  • Document the regression and vendored driver patch.

Validation

  • Official ARM DM8 UTF-8: 166 passed, 2 deselected, 0 skipped.
  • Official ARM DM8 GB18030: 166 passed, 2 deselected, 0 skipped.
  • Vendored Go module: go test ./... passed.
  • Pinned CI image locally confirmed CHARSET=0 yields UNICODE=0.

@skhe
skhe merged commit c428be0 into main Sep 26, 2026
18 checks passed
@skhe
skhe deleted the codex/gb18030-clob-boundary branch September 26, 2026 16:31
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