Featured post
java - Performance implications of handling CLOBs with Oracle JDBC using SetBigStringTryClob -
i in process of reviewing old java/jdbc code clob-handling on oracle database. existing code uses approach similar approach mentioned in this question.
i found an article states:
prior oracle jdbc 10g, manipulate clob data in jdbc, oracle extension class oracle.sql.clob used. now, oracle jdbc 10g has few enhancements simplifies clob manipulation in jdbc applications. enables handling of large data using of available standard apis, instead of using oracle extension classes.
the article gives following information details of enhancement:
by default, method preparedstatement.setstring() allow processing of strings 32765 bytes. in order insert data greater 32765 bytes, newly introduced connection property - setbigstringtryclob can set. forces preparedstatement.setstring() use newly introduced method, oraclepreparedstatement.setstringforclob() instead.
however warns:
... handling large amounts of data way may not wise; streaming data better alternative.
but above performance-related warning in article. question if of clob access in code already being done through string objects, should worry other potential performance problems change of approach might cause? in other words, app not using benefit offered streaming load clobs in string objects above warning can ignored because not aiming @ performance improvement @ moment. there other performance-related issues might arise because of switching technique?
how big talking about? regularly handle short audio files , web images in memory without performance issues. these kilobyte scale files. think if run megabyte sizes streaming better. using streaming lob pretty easy standardized stuff.
- Get link
- X
- Other Apps
Comments
Post a Comment