Symptom
The SQL Anywhere JDBC driver has many different methods to input large binary long objects (BLOBs) via the JDBC interface:
- Using SQL Anywhere's native read_client_file SQL function via a Statement object
- The binary and blob methods available to the Statement JDBC object:
setBinaryStream(int parameterIndex, InputStream x)
setBinaryStream(int parameterIndex, InputStream x, int length)
setBinaryStream(int parameterIndex, InputStream x, long length)
setBlob(int parameterIndex, Blob x)
setBlob(int parameterIndex, InputStream inputStream)
setBlob(int parameterIndex, InputStream inputStream, long length)
Which is the most efficient method to use over the SQL Anywhere JDBC driver interface?
Read more...
Environment
- SAP SQL Anywhere 16
SAP SQL Anywhere 12
SAP SQL Anywhere 11 - SQL Anywhere JDBC Driver
Product
SAP SQL Anywhere 16.0 ; SAP Sybase SQL Anywhere 12.0 ; Sybase SQL Anywhere 11.0
Keywords
11558380, sybase, memory, SQL Anywhere, binary, blob, read_client_file, .setBlob, .setBinaryStream, sajdbc4, sajdbc, jdbc, efficient. performance, Java , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.