[client-v2] Binary String support#2887
Conversation
|
Repository collaborators can run the JMH benchmark suite against this PR by commenting: Optional regression threshold override (Δ% on Time or Alloc/op; defaults to 10%): Only one benchmark run per PR is active at a time — issuing a new |
Client V2 CoverageCoverage Report
Class Coverage
|
JDBC V2 CoverageCoverage Report
Class Coverage
|
JDBC V1 CoverageCoverage Report
Class Coverage
|
Client V1 CoverageCoverage Report
Class Coverage
|
TriageCategory: Summary What this impacts
Concerns
Required reviewer action
|
…rted to StringValue
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b35806d. Configure here.
|




Summary
There are a few problems with reading binary strings:
This PR introduces
StringValuethat acts asbyte[]holder to createStringad-hoc instead of when read. So strings that suppose to be read viabyte[]will stay asbyte[].This affects also JDBC where
ResultSethasgetBinaryStreamfor such cases. Now it is supported operation.Part of #2263
Checklist
Delete items not relevant to your PR: