Kbase P30312: Modified _field-rpos in the metaschema to remove gaps & wrong data returned from queries
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/18/2010 |
|
Status: Verified
SYMPTOM(s):
Modified _field-rpos in the metaschema to remove gaps
Recompiled application source code
Progress seems to be 'off by 1' when resolving field names at runtime
FACT(s) (Environment):
Progress 9.1C
Sun Solaris SPARC
CAUSE:
Bug# 20030710-008
CAUSE:
A change in the field record position (_Field-rpos) should cause the corresponding table _Version to be incremented.
This bug manifests itself when the following is true:
You need a hole in the logical rpos near the end of the sequence; there should be a field (fldA) of type character after the hole and a non-indexed character field (fldB) following fldA. Each of the clients needs to first find a record in the table. Then client X should compile a program to cause selection on the server based on the fldB (For each tbl where fldB <> "fldB init value": display fldA
fldB.). Each of the clients should run the compiled program (and get no records). Then client Y should reset the field-rpos values so there's no hole. Client X should recompile the .p. When X runs the .p, it'll work fine. But if client Z runs the .p, it'll return records when it shouldn't.
FIX:
Upgrade to Progress 9.1D07 or later