Kbase P19412: After ProtoOra and having loaded data, order of records is not correct
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
SYMPTOM(s):
After ProtoOra and having loaded data, order of records is not correct
Two unique indexes on the table, on progress_recid and on cust-num
CAUSE:
The .d file loaded manually was not ordered according to cust_num first field but like
1 nameA ...
5 nameB ...
4 nameC ...
2 nameD ...
FIX:
Add to all 4GL queries either "BY cust-num" or "USE-INDEX cust-num".
Add for Oracle SELECT statement either "ORDER BY cust_num" or an index-hint (see sample below).
SELECT /*+ INDEX_ASC(customer##cust_num) */ * FROM customer;