Jdbc update blob column

Next, read data from the sample resume file using FileInputStream and call setBinaryStream method to set parameters for the PreparedStatement. After that, call the executeUpdate method of the PreparedStatement object. Finally, close the PreparedStatement and Connection objects by calling the close methods. As you see, we have BLOB data updated in the resume column of the candidates table for record with id Finally, call the close methods of PreparedStatment and Connection objects.

File; import java. FileInputStream; import java. FileNotFoundException; import java. Connection; import java. PreparedStatement; import java. The update approach you mention in the first case can be rewritten using pure JDBC code and thus reduce your dependency on Oracle-specific classes.

This could be helpful if your app needs to be database agnostic. Another point of view from Oracle DBA. Sun guys did very poor job when they designed JDBC standards 1. BLOB stands for large object and therefore it can be very large. It is something that can not be stored in JVM heap. Oracle thinks of BLOBs as something like file handles it fact they are call then "lob locators". LOBS can not be created via constructor and are not Java objects.

Also LOB locators oracle. In Oracle there are two ways how to create a LOB. Nothing is stored in JVM heap. All the writes are "guarded" by writes into redo-logs. The returning clause was not supported by JDBC standards 1.

They can not be passed from one connection to another. You second example can work, but will require excessive copying if data from temporary tablespace into data tablespace. The Oracle server's LOB handling is pretty poor and can suffer from serious performance problems e. I would suggest trying both approaches. The ojdbc6. Provided the CLOB data is small enough to fit in your memory without blowing up, you can just create a prepared statement and simply call. There may be other size limitations, but it seems to work for the sizes we're dealing with kB max.

I have to release blob after the statement is completed - or otherwise blob is closed when session is closed which can take long time with connection pooling. I found a simple call to setObject pos, byte[] works for my case. If size of inserting BLOB is greater than blob. It is suggested as follows: a Set jdbc connection autoCommit property to false.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 12 years, 8 months ago. Active 5 years, 4 months ago. Viewed 44k times.

The exact same question applies for CLOB fields. Add a comment. Active Oldest Votes. It doesn't seem to work in SQL Server, for example. But maybe it's not essential to the above technique anyway It's important in this case because the resultset is going to update those rows. If you are reasonably certain that nobody else will update those rows, you might not need the lock.

You are not inserting a BLOB here, you are just updating it. The OP was specifically about inserting. Ivan Ivan 71 1 1 silver badge 1 1 bronze badge. So in your last case how would java code be written?