Oracle just does not get it! Any java programmer who has written code against an Oracle database knows about the dreaded CLOB issue -- string values over 4000 characters cannot be stored using PreparedStatement.setString; instead you're forced to bind to Oracle's proprietary oracle.sql.CLOB class. In the new 10g release, Oracle claims to have rectified the issue, but in actuality all they've done is up the limit to 32765, unless you set a "SetBigStringTryClob=true" property in the connection or data source. When you're Oracle, you don't have to play by the rules, apparently...
9:55:58 AM 
|
|
