Kbase P157381: CONTAINS does not return the expected records with client/server connections
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/12/2009 |
|
Status: Unverified
SYMPTOM(s):
CONTAINS does not return the expected records with client/server connections.
Using a FOR EACH of the form:
FOR EACH <table> WHERE (<field> CONTAINS "din 6796 | din 27205-2 Ber*")
The records that match the first component of the CONTAINS operator (i.e. those with a value of "din 6796") are not returned by the query in sessions using client/server connections.
Sessions using shared memory connections return the correct results.
FACT(s) (Environment):
The first component of the CONTAINS operator uses a exact value match, but the second component uses a wildcard (*).
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
Bug# OE00194076
FIX:
As a workaround, add a wildcard character to the first component of the CONTAINS operator, even though it shouldn't actually be needed. For example:
FOR EACH <table> WHERE (<field> CONTAINS "din 6796* | din 27205-2 Ber*")
The code will now return the correct results set.