Skip to content

jdbc: Support Statement max field size #189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nicktorwald opened this issue May 21, 2019 · 0 comments · Fixed by #206
Closed

jdbc: Support Statement max field size #189

nicktorwald opened this issue May 21, 2019 · 0 comments · Fixed by #206
Labels
Milestone

Comments

@nicktorwald
Copy link

Support following API get/set maxFieldSize

... the limit for the maximum number of bytes that can be returned for character and binary column values in a ResultSet object produced by this Statement object. This limit applies only to BINARY, VARBINARY, LONGVARBINARY, CHAR, VARCHAR, NCHAR, NVARCHAR, LONGNVARCHAR and LONGVARCHAR fields. If the limit is exceeded, the excess data is silently discarded. For maximum portability, use values greater than 256.

It may be done on the driver side. For example, ResultSet can trim string/bytes results internally.

@nicktorwald nicktorwald added this to the JDBC MVP milestone May 21, 2019
nicktorwald added a commit that referenced this issue Jul 13, 2019
Add a capability to limit resultSet values of character or binary types.

Closes: #189
nicktorwald added a commit that referenced this issue Jul 18, 2019
Add a capability to limit resultSet values of character or binary types.

Closes: #189
nicktorwald added a commit that referenced this issue Aug 14, 2019
Add a capability to limit resultSet values of character or binary types.

Closes: #189
nicktorwald added a commit that referenced this issue Aug 14, 2019
Add a capability to limit resultSet values of character or binary types.

Closes: #189
nicktorwald added a commit that referenced this issue Aug 14, 2019
Add a capability to limit resultSet values of character or binary types.

Closes: #189
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant