Kbase 14036: Why don't certain FIND, FOR EACH return AMBIGUOUS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Why don't certain FIND, FOR EACH return AMBIGUOUS
If there is a one exact match, even though it is a substring of
another match, then it is considered a unique hit. It will NOT be
considered AMBIGUOUS. Consider the following example:
FIND testfile WHERE a = '1' AND b BEGINS '1234'.
If there are records in the database where
record1.a = 1 and record1.b = '1234'
record2.a = 1 and record2.b = '1234 p'
Then record1 will be returned as a unique hit (AMBIGUOUS will be
false).
It is a feature of Progress that if there is one exact match it will
be returned and not considered a unique hit.
However, if you were to change the query as follows then it will be
ambiguous:
FIND testfile WHERE a = '1' AND b BEGINS '123'.
Progress Software Technical Support Note # 14036