Skip to content

jdbc: Support PreparedStatement.set*Stream #190

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 #208
Closed

jdbc: Support PreparedStatement.set*Stream #190

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

Comments

@nicktorwald
Copy link

No description provided.

@nicktorwald nicktorwald added this to the JDBC MVP milestone May 21, 2019
nicktorwald added a commit that referenced this issue Jul 22, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. Tarantool does not support a data streaming
via ip-proto so it leads the driver materializes the streams in proper
data in advance and sends prepared data as ordinary text or raw bytes.

Closes: #190
@nicktorwald nicktorwald self-assigned this Aug 3, 2019
nicktorwald added a commit that referenced this issue Aug 14, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. Tarantool does not support a data streaming
via IPPROTO so it leads the driver materializes the streams in proper
data in advance and sends prepared data as ordinary text or raw bytes.

Closes: #190
nicktorwald added a commit that referenced this issue Aug 15, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. Tarantool does not support a data streaming
via IPPROTO so it leads the driver materializes the streams in proper
data in advance and sends prepared data as ordinary text or raw bytes.

Closes: #190
nicktorwald added a commit that referenced this issue Aug 22, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. The input streams often are size unaware so
it can be difficult to calculate the data size and, consequently, the
iproto packet size. It leads the driver materializes the streams in
proper data in advance and sends prepared the data as an ordinary text
or raw bytes. Follow API is more important thing now than performance
issues with streams.

Closes: #190
nicktorwald added a commit that referenced this issue Aug 30, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. The input streams often are size unaware so
it can be difficult to calculate the data size and, consequently, the
iproto packet size. It leads the driver materializes the streams in
proper data in advance and sends prepared the data as an ordinary text
or raw bytes. Follow API is more important thing now than performance
issues with streams.

Closes: #190
nicktorwald added a commit that referenced this issue Aug 30, 2019
Add capability to set streams as a parameter of ASCII or UNICODE text as
well as SCALAR binary data. The input streams often are size unaware so
it can be difficult to calculate the data size and, consequently, the
iproto packet size. It leads the driver materializes the streams in
proper data in advance and sends prepared the data as an ordinary text
or raw bytes. Follow API is more important thing now than performance
issues with streams.

Closes: #190
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