Kbase P169467: Primary unique index is returning data in a Type II area differently than it does for existing Type
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/9/2010 |
|
Status: Unverified
SYMPTOM(s):
Primary unique index is returning data in a Type II area differently than it does for existing Type I storage areas.
Data in an existing Type I storage area is being returned in what appears to be descending order.
FACT(s) (Environment):
In a Type II storage area the data is being returned in ascending order which is consistent with the primary unique index.
If data in the existing Type I storage area is dumped and loaded into a fresh Type I storage area the data is returned in ascending order based on the primary unique index as expected.
Compile with the XREF option shows that the ABL query is making use of two indexes.
First index in the query is a non-unique index.
Second index in the query is a unique index.
All Supported Operating Systems
Progress/OpenEdge Product Family
OpenEdge Category: Language (4GL/ABL)
CHANGE:
Recently migrated the data from a Type I storage area to a Type II storage area via a binary dump and load of the data.
CAUSE:
The dump load process changes the RECID for the record, causing the query behavior change.
FIX:
To guarantee the sort order when using a non-unique index is necessary to specify a sort criteria on the query, otherwise the RECID order will be used.