Kbase P126748: MATCHES ignores collation when character data contains special characters
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/03/2011 |
|
Status: Verified
SYMPTOM(s):
MATCHES ignores collation when character data contains special characters
COMPARE with MATCHES operator also ignores collation
character data contains special characters such as diacritical marks due to different client keyboards
lookup operations that should take into account alternate spelling fails does not return the expected results.
collation tables do not require indexes:
MESSAGE "Francois" = "François". returns YES
queries being very slow if CONTAINS returns a large result
FACT(s) (Environment):
Progress 9.1E
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
Supporting collations in MATCHES would resolve i18N lookup problems. BEGINS has two behaviours, one for indices (which does use the collation) and one for non-index comparisons (which does not use the collation, as shown in the attachment). MATCHES is always a strict char-for-char comparison, with case-sensitivity support. It never considers the collation.
CAUSE:
Bug# OE00160509
FIX:
Use another field for lookup that does not need to populate extended characters.