We ran across this problem a couple of weeks ago. Calling setObject
with a "longvarbinary" type on a statement was causing an "Unknown Types
value." SQLException. Is there any reason why the case statements at
AbstractJdbc1Statement:1385 should not include Types.LONGVARBINARY? I'm
fairly new to this codebase - so, it's possible I overlooked something
obvious.
Thank you,
Amit Gollapudi
