Bug #8
misconversion of single-table REPEAT/DO for FIRST/LAST/UNIQUE
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:
History
#1 Updated by Stanislav Lomany almost 15 years ago
@45265 - testcase:
def temp-table tt1 field f1 as integer.
create tt1. f1 = 1.
create tt1. f1 = 2.
repeat preselect first tt1:
find next tt1.
if avail tt1 then message "test2".
else leave.
end.
#2 Updated by Stanislav Lomany almost 15 years ago
@45111 - issue description:
Single-table REPEAT/DO for the FIRST/LAST/UNIQUE component. Mistakenly converted in the same way as EACH component (i.e. provides multiple resulting records).
#3 Updated by Redmine Admin almost 15 years ago
@45126 - Status changed from WIP to Hold
#4 Updated by Stanislav Lomany over 14 years ago
Imported from JPRM on 2012-04-12 11:23:01.323:
TASKID = 6101 PROJECTID = 124 STATUS = 3 (Hold) DESCRIPTION = misconversion of single-table REPEAT/DO for FIRST/LAST/UNIQUE OWNER = SVL ASSIGNEE = BILLABLE = false PRIORITY = 5 (Normal) PHASE = 52 (Problem Resolution) COMPONENT = 97 ESTEFFORT = 0.000000 ESTSTART = 2011-10-03 ESTSTOP = ACTSTOP = CASENUM = VENDORID = COMMENT = '' LASTWIP = 2011-10-17