[ http://issues.apache.org/jira/browse/IBATIS-62?page=comments#action_59084 ] Clinton Begin commented on IBATIS-62: -------------------------------------
Personally, I really don't like that idea. The pluggable piece of this framework in this context is CustomTypeHandler. You should be able to do everything you've mentioned above within the CTH. It seems to me that all you would need is access to either the connection, or the prepared statement (and ResultSet I suppose) within the CTH. I'd rather not support a two-tier pluggable feature like this. Furthermore, if the code that you're using to build CLOBs is a crazy as you've described above, you should really be sending support messages to the two groups responsible: Oracle and WebSphere. That code is absolutely ridiculous (not a criticism of you, but of how poor the support for CLOBs is in that environmental combination). In my opinion, iBATIS should not adopt the role of solving problems for vendors who don't support the standard APIs. Your company has probably spent millions on each of those products -- get your money's worth....call their support line. PS: We've had MANY people report great success with the standard 2.0.9 CLOB handler when used with Oracle 10g drivers. The 4k limit has not been an issue. > BLOB Handling in IBATIS 2.0.9 > ----------------------------- > > Key: IBATIS-62 > URL: http://issues.apache.org/jira/browse/IBATIS-62 > Project: iBatis for Java > Type: Bug > Components: SQL Maps > Versions: 2.0.9 > Reporter: Martin Dawe > Priority: Critical > > We are currently trying to utilise the new BLOB handling features of IBATIS > 2.0.9. We have managed to pull back a BLOB from ORACLE as a byte[], but we're > only pulling back 86bytes (as mentioned in a previous post by another member) > of data for large .pdf documents. > It is unclear from previous posts whether this feature actually works > entirely, but it would be greatly appreciated if we could have some example > implementation of the BLOB handling in IBATIS. > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
