Kbase P6360: Behavioral differences seen with & without 'qt_no_bind_where
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/02/2003 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
FACT(s) (Environment):
Progress 9.1B
SYMPTOM(s):
Behavioral differences are seen in the result set with or without using 'qt_no_bind_where' parameter against a FIND occur.
When parameter 'qt_no_bind_where' is used, the FIND NEXT will display the first record in the table.
When parameter 'qt_no_bind_where; is not used, a FIND NEXT will display the second record previously accessed.
This result set inconsistency is not seen in Progress 8.3D
CAUSE:
Bug# 20010201-007
CAUSE:
There should be no inconsistencies in result set with or without using the 'qt_no_bind_where' parameter
FIX:
Issue has been fixed in 9.1B patch and higher