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
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.