Informix - Problembeschreibung
Problem IT27531 | Status: Geschlossen |
INDEX DOES NOT WORK CORRECTLY WHEN THE KEY CONTAINS UTF8 0XC2A0 NON BREAKING SPACE | |
Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problembeschreibung: | |
here is a 16 columns unique index that contains two columns where the data contains 0xc2a0 in two of the columns. When the 2nd column that contains this 0xc2a0 is removed, the query that originally fails would work. Steps to reproduce: 1. Set the environment variables : GL_USEGLU, DB_LOCALE and CLIENT_LOCALE. GL_USEGLU=0 (Problem reproduces with either GL_USEGLU 0 or 1). DB_LOCALE=en_US.UTF8 CLIENT_LOCALE=en_US.UTF8 2. Create a 8K page dbspace and create new database in the 8k dbspace For ex: dbspace dbspace8k; database name en3; create database en3 in dbspace8k; 3. dbaccess en3 t_address2.sql 4. dbaccess en3 insert_statement.sql 5. dbaccess en3 select.sql - select * from t_address2 where a_flr_no is null; (SEQ SCAN) works fine. - force use of uq_addr_all_fields would fail. 6. dbaccess en3 t_address2_idx.sql - t_address2_idx.sql will recreate the index and exclude a_str_nm, the index works fine. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS 12.10.xC10 and earlier versions. * **************************************************************** * PROBLEM DESCRIPTION: * * Index does not work correctly when the key contains utf8 * * 0xc2a0 non breaking space. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.12.2018 07.10.2019 07.10.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC11 | |
Problem behoben lt. FixList in der Version |