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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Automatic conversion of ifx_loc_t (TEXT/BYTE) to/from ifx_lo_t (CLOB/BLOB)
We have legacy ESQL/C code using ifx_loc_t to handle TEXT/BYTE columns.
Customers want now to replace TEXT/BYTE by CLOB/BLOB columns in the database... and we would avoid to touch our ESQL/C code.
Informix can support simple type conversion. For example, when binding an (int) C sqlvar to insert data into a VARCHAR column, and it can fetch a varchar value into an int, as long as the string represents a valid integer... same for dates, decimals... as long as conversion rules are satisfied.
It would save us a lot of work, if Informix could do the same conversion between TEXT/BYTE sqlvar (ifx_loc_t) and CLOB/BLOB columns in the database!
The only need we have is to insert/update complete TEXT/BYTE variables in the client program to CLOB/BLOB columns, or to fetch as a whole the CLOB/BLOB data into TEXT/BYTE variables. We do not need to handle CLOB/BLOB pieces. If the CLOB/BLOB does not fit into a TEXT/BYTE locator, just raise an overflow error...
Do not place IBM confidential, company confidential, or personal information into any field.