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.
Informix ESQL/C ifx_var_getdata() should do charset conversion when binding with CLVCHARPTRTYPE
Environment: Linux Debian 10.7 or Windows 10 Informix server: IDS-14.10.FC5 Informix client: CSDK 4.50.FC5
With the DB in UTF-8 (DB_LOCALE = en_us.utf8) and client app in another character encoding (CLIENT_LOCALE=en_us.8859-15):
When fetching an LVARCHAR column, and binding with ifx_sqlvar_t sqltype=CLVCHARPTRTYPE, after the fetch we want to get the character string with ifx_var_getdata().
But it appears that the sequence of bytes returned by the ifx_var_getdata() function is pure UTF-8, and is not converted to ISO-8859-15 ...
Documentation says that this function returns ASCII data ... we assume that no conversion is done at all and it returns just the UTF-8 byte sequence.
The string should be converted to the charset of CLIENT_LOCALE, just as when binding with CVCHARTYPE and a self-allocated buffer. But that solution is not acceptable for LVARCHAR because we would need to allocate large buffers to cover the max LVARCHAR size!
"..The lvarchar pointer type is not equivalent to a C-language char pointer. Informix® ESQL/C maintains its own internal representation for the lvarchar pointer type. This representation is identical to the representation of a var binary host variable, except that it supports ASCII data as opposed to binary data..."
Do not place IBM confidential, company confidential, or personal information into any field.