This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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:
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.
Do not place IBM confidential, company confidential, or personal information into any field.