Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312753 - [2.3.2][Automation]The joint result of script computed column is incorrect
Summary: [2.3.2][Automation]The joint result of script computed column is incorrect
Status: VERIFIED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.2.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.6.1   Edit
Assignee: Zhang Lei CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard: Obsolete
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-13 04:08 EDT by mindan xu CLA
Modified: 2010-08-05 22:36 EDT (History)
2 users (show)

See Also:


Attachments
Report (19.08 KB, application/octet-stream)
2010-05-13 04:08 EDT, mindan xu CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description mindan xu CLA 2010-05-13 04:08:15 EDT
Created attachment 168348 [details]
Report

Description:
1, Each dataset including a computed column:
name: index; type:integer; expression:0
2, Specify the script of datasets to:
   beforeOpen: index=0;
   onFetch: row["index"] = index;
            index++;
3, Join the two datasets

Build number: 
2.3.2.v20100115-1545

Steps to reproduce:
1, open the attached report design
2, open the joint dataset and preview 

Actual result:
Result is null.
Comment 1 Zhang Lei CLA 2010-08-05 02:11:52 EDT
In this case, both sub-datasets has a script computed column. and both of them use the same variable "index". Currently, the process of preparing joined dataset is first, we prepare some metadata of both datasets and then execute until the execution is needed such as dataset preview. since both datasets use the same variable and they will be considered as a global variable in the same scope of jointdataset, when execution, after the first dataset is executed, the variable value will be kept. and when the second dataset is executed, this kept value will be used. We use the new logic after the fix of bugzilla bug 235707. And the current process is more reasonable than preparing one data set, execute it and preparing the second and execute. It is an order issue, Users should use different variable names if they want to support this case. so set this issue as invalid.
Comment 2 Xiaoying Gu CLA 2010-08-05 22:36:55 EDT
Verified.