Project

General

Profile

Bug #9399

Record cannot be found by ROWID in non-default buffer

Added by Stanislav Lomany over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

rowid.p Magnifier (208 Bytes) Stanislav Lomany, 11/28/2024 09:50 AM

History

#1 Updated by Stanislav Lomany over 1 year ago

Testcase attached. 4GL displays "1", FWD throws "xtt record not on file".
Checked on trunk rev 15583. Checked that it's not a regression down to rev 14500.

#2 Updated by Stanislav Lomany over 1 year ago

OK, I resolved the issue for myself. It is a weird FWD conversion issue. In my .df file I had a permanent table called ttw and non-default buffer xtt for tt for some reason was converted as a buffer for ttw and not tt. The testcase was converted to a compilable state, that's why I didn't notice it. I removed ttw from .df and the issue is gone.

What should I do with this task?


ADD TABLE "ttw" 
  AREA "Schema Area" 
  DUMP-NAME "ttw" 

ADD FIELD "ff1" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 10
  MAX-WIDTH 4
  ORDER 100

ADD FIELD "ff2" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 20
  MAX-WIDTH 4
  ORDER 200

ADD FIELD "ff3" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 30
  MAX-WIDTH 4
  ORDER 300
  extent 5

ADD FIELD "ff4" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 40
  MAX-WIDTH 4
  ORDER 400

ADD FIELD "ff5" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 50
  MAX-WIDTH 4
  ORDER 500
  extent 5

ADD FIELD "ff6" OF "ttw" AS integer
  FORMAT "->,>>>,>>9" 
  INITIAL "0" 
  POSITION 60
  MAX-WIDTH 4
  ORDER 600
  extent 5.

#3 Updated by Constantin Asofiei over 1 year ago

Please run the test in OpenEdge with the same .df schema as you originally used in FWD - if OpenEdge behaves the same as FWD, then we can close this.

#4 Updated by Stanislav Lomany over 1 year ago

No, 4GL doesn't behave in this way.

Also available in: Atom PDF