JDBC suport of collection data types in scroll cursors

Currently the usage of collection data type columns in scroll cursors are disabled by default throwing an Exception with this stack trace.

Stack trace returned is:

at com.informix.util.IfxErrMsg.buildExceptionWithMessage(IfxErrMsg.java:416)

at com.informix.util.IfxErrMsg.buildIsamException(IfxErrMsg.java:401)

at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3022)

at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3273)

at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2269)

at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2194)

at com.informix.jdbc.IfxSqli.sendStatementQuery(IfxSqli.java:1524)

at com.informix.jdbc.IfxSqli.executeStatementQuery(IfxSqli.java:1474)

at com.informix.jdbc.IfxResultSet.executeQuery(IfxResultSet.java:183)

at com.informix.jdbc.IfxStatement.executeQueryImpl(IfxStatement.java:909)

at com.informix.jdbc.IfxStatement.executeQuery(IfxStatement.java:169)

This behavour is a protection because if column data size > 4K the column is really stored as an smartblob, as explained in internal case:

idsdb00012263 - SCROLL CURSOR CANNOT BE USED WITH COLLECTION COLUMN

The reasoning behind this is that collection types can grow to the size of blobs and blobs have never been supported with Informix JDBC and scrollable cursors.

The reason behind this is understandable as a smartblob cannot be part of an scroll cursor, but in most business cases, the content of the SET or LIST types in the tables are discrete values and always have a size < 4K.

This RFE is for revisiting this case and removing the protection to disable collection types in scroll cursor at the prepare phase, and fail only at runtime if the cursor retrieves a row with a column (collection data type) that is internaly a smartblob.

Said more directly, allow collection data types in jdbc scroll cursors and fail with a runtime error only if you get any row with columns internaly represented by a smartblob.