|
Problem IT39101
|
Status: Closed |
NOT LIKE ON BSON::JSON:LVARCHAR CAST RETURNS 788 UNKNOWN OPERATOR/TYPE IF CLIENT_LOCALE OR DB_LOCALE IS SET TO EN_US.UTF8
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
When either the env variable CLIENT_LOCALE or DB_LOCALE are set
to en_us.utf8 and you create a database
with a table that has a bson column like
export CLIENT_LOCALE=en_us.utf8
export DB_LOCALE=en_us.utf8
create database testdb with log;
create table test(col1 char(36) not null, col2 char(36) not
null, col3 bson);
then a query like the following after loading a couple rows
select col3::json::lvarchar(256) from test where
col3::json::lvarchar(256) not like "%xConfiguration%";
will return the following error regardless of the bson data
788: Unknown operator/type |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 (if available) or *
* 14.10.xC8. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC8. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 (if available) or *
* 14.10.xC8. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC16 and 14.10.xC8. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.11.2021
30.09.2022
07.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
