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
Support IDataReader::GetBytes / IfxDataReader::GetBytes for BSON fields
We're using the BSON capabilities of the Informix server in order to store data in a separate BSON colum - like additional information for the data row or optional fields that may vary from row to row (e.g. translations to different languages).
With the current Client SDK (v4.50xC5), it is not possible to access the binary representation of that field by issuing a SELECT statement using the Informix.Net.Core driver as the driver currently does not support the GetBytes function for any other field types than BLOBs or BYTEs.
That requires us to either issue multiple bson_value_xxx statements to access all those optional fields -or- to cast the field from BSON to JSON on the server side to then perform the creation of the client-side data object by translating the returned values for a second time.
A more direct approach by returning the byte represenation of the BSON column would have two nice side effects:
a) There's no need for double conversion (either by calling bson_value_xx and then issuing the corresponing GetValue calls from the IDataReader to build up the data object at client side -or- by casting BSON to JSON and then parsing JSON at client side), thus the load on the server is reduced
b) The limit from 32767 characters (currently imposed for a VARCHAR - what the result of the BSON to JSON conversion is) would be omitted
Do not place IBM confidential, company confidential, or personal information into any field.