Project

General

Profile

Bug #2602

A record returned twice because of RELEASE

Added by Stanislav Lomany about 11 years ago. Updated about 11 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
06/30/2015
Due date:
% Done:

0%

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

History

#1 Updated by Stanislav Lomany about 11 years ago

Testcase:

DEFINE TEMP-TABLE tt
     FIELD f1 as decimal 
     FIELD f2 as char
     FIELD f3 as char 
     index idx1 is unique f1.

def buffer xtt for tt.

def var i as integer.
repeat i = 1 to 30:
  create tt. tt.f1 = i. tt.f2 = string(i * 10 + i). 
end.

def query q1 for tt.
open query q1 for each tt. 

get next q1.
get next q1.
get next q1.

create xtt.
xtt.f1 = 3.5.

get next q1.
message string(tt.f1).

release tt.

get next q1.
message string(tt.f1).

4GL output:

3.5
4

P2J output:

3.5
3.5

The bug happens because of release tt line. RELEASE is used in REPOSITION and used by browse, so I can see double records if I create a new record just after the last record in the browse view. IIRC, I've checked this browse functionality about 6 months ago so this might be a regression.

Also available in: Atom PDF