Bug #9
invalid sorting for FOR/REPEAT/DO with FIRST/LAST BREAK BY
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#1 Updated by Stanislav Lomany over 12 years ago
@45266 - testcase:
def temp-table tt1 field f1 as integer field f2 as integer index idx is primary f1. create tt1. f1 = 1. f2 = 2. /* should be the first (and the single) outputted record */ create tt1. f1 = 2. f2 = 1. repeat preselect first tt1 break by f2: find next tt1. if avail tt1 then message string(f1) + " " + string(f2). else leave. end. Note that this testcase is also affected by the "Single-table REPEAT/DO for the FIRST/LAST/UNIQUE component" issue.
#2 Updated by Stanislav Lomany over 12 years ago
@45110 - issue description:
Single-table FOR/REPEAT/DO with the FIRST/LAST component and BREAK keyword or complex by clause should use pure index-driven sorting too.
#3 Updated by Redmine Admin over 12 years ago
@45127 - Status changed from WIP to Hold
#4 Updated by Stanislav Lomany about 12 years ago
Imported from JPRM on 2012-04-12 11:23:02.151:
TASKID = 6102 PROJECTID = 124 STATUS = 3 (Hold) DESCRIPTION = invalid sorting for FOR/REPEAT/DO with FIRST/LAST BREAK BY 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